Crashing while sleeping or away from keyboard

[technotron]

It crashed a few times while in sleep mode. But, I'm sure ONE time was because I had a VirtualBox machine open before going to sleep. Downloading the new version of VirtualBox with bugfixes for sleeping solved it for me.

One time I just went away from the keyboard and the computer just shut down. The computer also seems to crash when I wasn't at the computer, so I don't know much about when it crashed.

Last night I put the computer to sleep and when I woke up I found it crashed.

 

[x BlueRobot]

[COLOR="Red"]BugCheck 9F[/COLOR], {3, fffffa80070b3060, fffff80000b9c3d8, [COLOR="SeaGreen"]fffffa8006871630[/COLOR]}

Probably caused by : pci.sys

0: kd> [COLOR="seagreen"]!irp fffffa8006871630[/COLOR]
Irp is active with 3 stacks 2 is current (= 0xfffffa8006871748)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
[COLOR="Blue"]>[ 16, 2]   0 e1 fffffa80085bb480 00000000 00000000-00000000    pending
	      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
 \Driver\nvlddmkm[/COLOR]
			Args: 00015400 00000001 00000004 00000003
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800ae667a0    

			Args: 00000000 00000000 00000000 00000000

Your graphics driver seems to be causing some problems, and is rather outdated, please update it with the latest WHQL version which has been tested by Microsoft for compatibility and stability.

0: kd> [COLOR="SeaGreen"]lmvm nvlddmkm[/COLOR]
start             end                 module name
fffff880`0f2f4000 fffff880`0ffe8000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR="Red"]Tue Oct 02 19:21:13 2012[/COLOR] (506B3099)
    CheckSum:         00CD4613
    ImageSize:        00CF4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Version: 314.22
Release Date for Desktops and Notebooks : March 25th 2013
In Device Manager: 9.18.13.1422

• NVIDIA Driver Downloads - Advanced Search

1. Download Driver
2. Start rb: Type: Device Manager
3. Expand Display Adapters
4. Right-Click Driver Name, Uninstall
5. Reboot
6. Run Driver Sweeper
7. Reboot
8. Install Downloaded Driver

Driver Sweeper will scan for any left over files from the old driver, old driver files can cause conflicts with new driver installations. Create a System Restore point beforehand, in case any problems or issues arise.

Driver Sweeper:

• http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html

Download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Daemon Tools uses a driver called sptd.sys, which is known to cause BSODs with Windows 7. It is recommend you remove this program, and use Windows own in-built features or ImgBurn.

 

[technotron]

I try not to update my video card drivers since Nvidia's drivers tend to cause more problems and introduce more bugs in some drivers. At least in my experience. The newer drivers seem to be just performance optimizations for new games. Unless the driver fixes some major bugs. I've looked up my driver and the newer driver and its people are having trouble with drivers.
NVIDIA GeForce Video Card Drivers v314.22 Now Available
looked at comments
https://forums.geforce.com/default/topic/536887/unable-to-run-games-after-updating-to-314-22/

I'll try uninstalling Daemon Tools when I get the chance.

 

[x BlueRobot]

Fixes several issues found in Windows 8, Windows 7, Windows Vista, and Windows XP since the last WHQL release.

You could least update the driver to test, and if the problems still occur then we can assess the situation, the current driver version is causing problems anyway, the driver is blocking any further IRP's to be processed.

I've also recommended many others to update to the latest WHQL driver, and it hasn't caused problems.