Faulting application name: blender_4.79_windows_x86_64.exe


Advanced search

Message boards : Client : Faulting application name: blender_4.79_windows_x86_64.exe

Author Message
Mike Kehoe
Send message
Joined: 19 Mar 13
Posts: 2
Credit: 1,519,194
RAC: 0
Message 11656 - Posted: 22 Mar 2013, 14:45:57 UTC

For the past few days, I've been periodically receiving the following error:

Faulting application name: blender_4.79_windows_x86_64.exe, version: 0.0.0.0, time stamp: 0x4d5423fe
Faulting module name: blender_4.79_windows_x86_64.exe, version: 0.0.0.0, time stamp: 0x4d5423fe
Exception code: 0x40000015
Fault offset: 0x0000000000044338
Faulting process id: 0xf7c
Faulting application start time: 0x01ce27099d846e49
Faulting application path: C:\ProgramData\BOINC\projects\burp.renderfarming.net\blender_4.79_windows_x86_64.exe
Faulting module path: C:\ProgramData\BOINC\projects\burp.renderfarming.net\blender_4.79_windows_x86_64.exe

Are there any logs I could forward to help determine the cause of the crashing process?

My system configuration is:

------------------
System Information
------------------
Time of this report: 3/22/2013, 10:41:38
Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1(7601.win7sp1_gdr.130104-1431)
Language: English (Regional Setting: English)
System Manufacturer: LENOVO
System Model: 4229CTO
BIOS: faLENOVO BIOS Rev: A1KT39A 0.0
Processor: Intel(R) Xeon(R) CPU E5-2643 0 @ 3.30GHz (16 CPUs), ~3.3GHz
Memory: 65536MB RAM
Available OS Memory: 65486MB RAM
Page File: 34846MB used, 96125MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11

---------------
Display Devices
---------------
Card name: NVIDIA Quadro 4000
Manufacturer: NVIDIA
Chip type: Quadro 4000
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_06DD&SUBSYS_078010DE&REV_A3
Display Memory: 1718 MB
Dedicated Memory: 1999 MB
Shared Memory: 3815 MB
Current Mode: 1600 x 1200 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: DELL 2007FP
Monitor Id: DELA021
Native Mode: 1600 x 1200(p) (60.000Hz)
Output Type: DVI
Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 9.18.0013.1135 (English)
Driver Version: 9.18.13.1135
DDI Version: 11
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 2/27/2013 09:33:56, 18059304 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a
Device Identifier: {D7B71E3E-459D-11CF-0177-8D271EC2C435}
Vendor ID: 0x10DE
Device ID: 0x06DD
SubSys ID: 0x078010DE
Revision ID: 0x00A3
Driver Strong Name: oem147.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section028:9.18.13.1135:pci\ven_10de&dev_06dd
Rank Of Driver: 00E02001
Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C



Card name: NVIDIA Quadro FX 3800
Manufacturer: NVIDIA
Chip type: Quadro FX 3800
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_05FF&SUBSYS_066110DE&REV_A1
Display Memory: 485 MB
Dedicated Memory: 997 MB
Shared Memory: 3583 MB
Current Mode: 1600 x 1200 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: DELL 2007FP
Monitor Id: DELA021
Native Mode: 1600 x 1200(p) (60.000Hz)
Output Type: DVI
Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 9.18.0013.1135 (English)
Driver Version: 9.18.13.1135
DDI Version: 10
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 2/27/2013 09:33:56, 18059304 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a
Device Identifier: {D7B71E3E-46BF-11CF-0177-6C261CC2C435}
Vendor ID: 0x10DE
Device ID: 0x05FF
SubSys ID: 0x066110DE
Revision ID: 0x00A1
Driver Strong Name: oem147.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section008:9.18.13.1135:pci\ven_10de&dev_05ff
Rank Of Driver: 00E02001

Speedy
Send message
Joined: 25 May 06
Posts: 206
Credit: 664,983
RAC: 496
Message 11657 - Posted: 22 Mar 2013, 21:50:00 UTC - in response to Message 11656.

Was the Blender application downloaded automatically from the server or did you create a app info file to only receive blender work units? If you used an app info file maybe you could post that and I can take a look at it and see if I can spot anything wrong with it or other members may be able to spot an issue.
____________

Have a crunching good day!!
Live in NZ y not join Smile City?

Profile Janus
Volunteer moderator
Project administrator
Avatar
Send message
Joined: 16 Jun 04
Posts: 4478
Credit: 2,094,806
RAC: 0
Message 11658 - Posted: 22 Mar 2013, 23:02:25 UTC

If you go to the results for the failing host and click on any of the failing result ids you will get a log for that workunit. It looks like something is knocking out BOINCs heartbeat mechanism:


---------------------------
Exception caught: Heartbeat detection indicates that BOINC is unresponsive.
Status: -7
---------------------------
terminate called after throwing an instance of 'Exception'
10:19:05 (8420): No heartbeat from core client for 30 sec - exiting

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.


There's a lot of things that could influence BOINC, but typically this would feel like a general slowdown of the computer too, so that could help you pinpoint the issue.

Profile DoctorNow
Project donor
Avatar
Send message
Joined: 11 Apr 05
Posts: 392
Credit: 2,168,338
RAC: 34
Message 11660 - Posted: 23 Mar 2013, 7:24:21 UTC - in response to Message 11657.
Last modified: 23 Mar 2013, 7:24:43 UTC

I think it's more a problem with session 1566, maybe some WUs are faulty or simply overload the most systems.
Looking at his results and the wingmen he has on the faulty WUs (and these are all 1566) it appears that most of them fail at a lot of comps - best example is this one.
____________
Life is Science, and Science rules. To the universe and beyond
Proud member of BOINC@Heidelberg
My BOINC-Stats

Mike Kehoe
Send message
Joined: 19 Mar 13
Posts: 2
Credit: 1,519,194
RAC: 0
Message 11676 - Posted: 26 Mar 2013, 14:35:37 UTC - in response to Message 11657.
Last modified: 26 Mar 2013, 14:40:28 UTC

I'm not sure if this is the answer to your question, but, I downloaded the BOINC client and joined BURP. The BURP files downloaded automatically afterwards and started processing work units.

With regard to the heartbeat, could someone give me a general overview of how the heartbeat mechanism is supposed to work? Do the clients attempt to pole the server or is it the other way around? I'm asking because I have a networking and data communications background, if I know what is supposed to happen and the hosts involved, I can put monitors on that and see where that communication is failing.

I do not see a slow down on the machine, which leads me to suspect it's either some race condition with the renderer/boinc scheduling/some other WU or a genuine network problem.

Profile noderaser
Project donor
Avatar
Send message
Joined: 28 Mar 06
Posts: 507
Credit: 1,549,461
RAC: 95
Message 11677 - Posted: 27 Mar 2013, 3:11:19 UTC

The "heartbeat" is local, between the BOINC manager and the Blender instance.
____________


Post to thread

Message boards : Client : Faulting application name: blender_4.79_windows_x86_64.exe