WIN7_DRIVER_FAULT BSOD when waking from sleep

[bitplayer]

Hey guys. I got a BSOD this morning when I woke my machine from sleep. I actually didnt even see the bsod as the monitors were still waking. It just went back to my mobo splash screen and I had a minidump. It looks like it might be an nvidia issue but wanted to get your thoughts. If it is an nvidia issue does this look like a driver issue or a hardware issue?

Note that I uploaded this on my laptop but the BSOD occurred on my desktop so the upload may be a little funky. If so just let me know and will reupload later today.

Thank you in advance for all of your help.

UPDATE: have now uploaded dumps from the actual computer

 

[bitplayer]

Anyone?

 

[axe0]

Go to %systemroot%\minidump in Windows Explorer (not Internet Explorer) and see if a dump from 24th this month is there, if it is right click this dump > copy to > zip and upload the zip.

 

[bitplayer]

Thanks Axe.

Ive uploaded this from another computer so it may have a different computer name on it.

 

[axe0]

Well, this is a common scenario with 0x3B

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8800f2bdbea, fffff88006ea8a50, 0}

Probably caused by : nvlddmkm.sys ( nvlddmkm+89bea )

Followup: MachineOwner

3: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f234000 fffff880`0fe3e000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR="Red"]Wed Dec 16 15:13:02 2015[/COLOR] (5671716E)
    CheckSum:         00BD14EC
    ImageSize:        00C0A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Then there is also following
Driver Reference Table - MpFilter.sys

fffff880`06ea8788  fffff880`0108aa0e*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
 MpFilter+0x1fa0e

Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver.
View attachment 382518

Diagnostics Test

 System File Check

Please try following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow says "Windows Resource Protection found corrupt files but was unable to fix some of them" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

Please fill in your system specs

Please follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.
How to fill in your system specs:

 

[bitplayer]

So in your opinion is this a driver issue?

I have since done a full DDU wipe and installed the newest driver.

 

[axe0]

I have not given my opinion, I only showed what I found in the dump.

 

[bitplayer]

Let me rephrase that. Was it the driver that caused this?

Was this a software failure or a hardware failure?

 

[axe0]

It was the Nvidia display driver that caused it.

Hard to tell with 1 dump, but the start is a driver issue.