Solved BSOD rendering with 3ds max vray, 0x0000003b

[salvadore]

Hi,

I recently started getting some bsods when rendering in 3ds max 2014, with vray, on windows 7 ultimate 64 bit. I looked around and couldnt find any info that i could understand. I checked and win is up to date, including all/most of my drivers. No heat problems. Reset bios.
Here are my system specs:
Custom PC, gigabyte p67x-ud3-b3, uefi bios U1b, i7 2600, 16gb ram, gigabyte gtx 780 oc rev2 (recently bought), samsung evo 250 gb, wd 1tb caviar black. Hope i didnt forget anything.

Thank you in advance! I dont know where else to go for help.

 

[salvadore]

Oh i forgot to mention that i ran memtest with no issues found, sfc, scanned the harddrives, problem still persists. I will start a stress test too, maybe that will help narrow it down a bit.

 

[Thedoctor44]

Yes, the BSOD you posted is related to your graphics driver. However, it is up to date so I will first recommend running Furmark.
Follow these instructions.

http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

When you upload dump files from now on please upload them using a zip file directly to this site, please don't (unless it's necessary) upload to a website and send us the link.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80003076ac5, fffff8800c0f41f0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : [COLOR="Red"]nvlddmkm.sys[/COLOR] ( nvlddmkm+1d1579 )

 

[salvadore]

thank you very much for your reply. Just a few hours before, i ran a 3h long prime 95 with success, and a passmark burn test for cpu ram & gpu, and a occt gpu (latest occt) for just an hour because i was afraid to leave it overnight. I will definitely run furmark for at least 2-3 hours in the morning and post some updates. Thank you again for your reply.

 

[salvadore]

I ran a 30 min furmark, with no errors, temp went to a max of 80 degrees celsius. Last time i rendered in 3d a few days ago, when i came back to the pc, the monitor was in idle, and the computer didnt respond to the mouse or keyboard. So i pressed the restart button, and it got stuck on the bios screen, i had to unplug and hold the power button for 10 secs to be able to boot into windows. Very weird stuff.
What do you think i should do? revert to older drivers?
Thank you and looking forward to hearing from you.
EDIT: when i'm rendering in 3d, i'm using the processor, so there is barely any load on the gpu. It's weird that it seems like a driver problem, than it got stuck on the bios screen on boot like it's a hardware problem

 

[Thedoctor44]

That sounds like a problem with your CPU. Drivers will not cause the BIOS to freeze as it's not part of windows.
Try running memtest86, just to be safe.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[salvadore]

Thanks, i'll run memtest overnight. I did run it before but just for 1-2 passes.

 

[salvadore]

I ran memtest overnight, i had to stop it this morning because i had to start working. It ran for 10 hours and 30 mins, 4 passes and no errors. If i can't replicate a bsod with any stress test or diag tool, i can't send back any components to be replaced

 

[Thedoctor44]

You need to run memtest86 for at least 8 passes otherwise there is still a high chance the RAM could still be faulty.

 

[salvadore]

Managed to fix it. Installed microsoft patch Windows6.1-KB2836373-v4-x64.msu. Updated Corsair Link to Beta 2.6.5214 (because this was on the bottom of the crash report too).
Removed aero and some windows effects. No bluescreens since.
I wouldn't rule out my PSU either, i theoretically need 700W in Full load (calculated online) and i have a 3 year old 650W PSU, which probably can't output 650W anymore.

Thanks again Thedoctor44 for your help and patience.