BSOD when returning from sleep

#1
Hello,
BSOD or black screen when it left sleep mode.

My investigations :

-The system resumes from sleep mode perfectly if I remove the MSI GTX660 twin frozr 3 and use the integrated Intel HD2500.

-memory pass the memtest86 (several passes) with XMP profile 1 settings

-with the GTX660, sometimes returning from sleep leads to a black screen, sometimes (often) a BSOD with "driver verifier..." message, sometimes I get the "graphic driver stopped responding and has recovered" message under the win8 desktop.

-I tried nVidia drivers WHQL 306.97, 310.90 and beta 313.96, same effects.

I only get issues when leaving sleep mode. The system works perfectly elsewhere (under load, in game and so on).

Sorry for my english

View attachment W7F_16-02-2013.zip
 


Last edited by a moderator:

kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#2
Hi,

I don't have the dmp file reader app installed at the moment but a quick look through your files and I see your bios is out of date. One thing we've noticed in the forums is that windows 8 always works best with the latest bios and driver updates. :

GIGABYTE - Motherboard - Socket 1155 - GA-H77N-WIFI (rev. 1.0)
 


#3
Thank you, your help is highly appreciated.

I tried what you suggested : ie., upgraded bios to version F3C (beta). I selected Windows 8 in this bios OS settings (was not in F2 version). The problem is still there though :(
Then I tried to enable ERP, disable integrated graphic instead of auto, intitialise PEG graphic first but it did not fix the issue.

Please find the attached new dumps with the latest (F3C) BIOS.
View attachment W7F_17-02-2013.zip
 


Last edited by a moderator:

kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#4
Hi,

I've re-installed the dmp file viewer so was able to go over your dmp files.

I notice you have Rivatuner running:

Rt630x64.sys Wed Oct 19 13:12:55 2011

Please uninstall until we determine the cause of your issues as Rivatuner can cause bsod's under certain circumstances.

Please update your graphic drivers to this version:

NVIDIA DRIVERS 310.90WHQL

Turn off driver verifier by opening an cmd prompt and typing:

verifier/reset

Then reboot.

Please post back if the issues continue.
 


Last edited by a moderator:
#5
Hi,

I guess that Rivatuner is a part of MSI AfterBurner app (GPU tweak). So I removed AftreBurner. Note that I already got the issue before installing this MSI utility. I installed it in order to check GPU temp (low : 24°C idle and <60°C at OCCT full load).

The 310.90 WHQL are already installed. I've done the verifier/reset command.

The problem is still there. The new dump is the most recent in the archive.
View attachment W7F_17-02-2013_B.zip
 


Last edited by a moderator:

kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#6
Please download this application and run it to remove the nvidia graphic drivers. Then install the latest versions again.

Driver Fusion - The Complete Driver Solution
 


#7
OK, it's done. The system still crashes when returning from sleep.
Note that I got 1 good return to desktop without any message, 1 with the "driver did not respond and has recovered", 1 black screen, and finally the BSOD with "driver verifier detected violation" message.

Please find attached newest archive and a photograph of the BSOD. Note that theBSOD screen I get always corrupted display like that. My system is stable and the graphic card has never failedl in game or anywhere, it fails only when returning from sleep state.

Thank you for the time you spend :worked_till_5am:
View attachment W7F_17-02-2013_C.zip BSOD.JPG
 


Saltgrass

Excellent Member
Microsoft Community Contributor
#8
How large is your power supply? You list a Seasonic G-360 ... is 360 watts its rating?

What exact model of memory do you have so we can check the specs?
 


#9
Yes it is a 360W gold seasonic. It sounds low wattage but the 12V rail can output 30A. My system runs at stock speed.
A(t full load (OCCT) it needs less that 250W at the outlet.
System without the GTX660 needs about 90W and the GTX 660 needs 150W in the worst case.

Do you think that my PS is too weak? It works flawlessly at full load OCCT or in game though.

My memory modules are a 2x4GB 12800 Crucial ballistix tactical low profile. I tested them with memtest86 and there are no errors. Modules are these ones : 8GB Kit (4GBx2), Ballistix 240-pin DIMM, DDR3 PC3-12800 upgrades for Giga-Byte GA-H77N-WIFI Motherboard, CT3736510 from Crucial.com
 


#10
Yes it is a 360W gold seasonic. It sounds low wattage but the 12V rail can output 30A. My system runs at stock speed.
A(t full load (OCCT) it needs less that 250W at the outlet.
System without the GTX660 needs about 90W and the GTX 660 needs 150W in the worst case.

Do you think that my PS is too weak? It works flawlessly at full load OCCT or in game though.

My memory modules are a 2x4GB 12800 Crucial ballistix tactical low profile. I tested them with memtest86 and there are no errors.
 


Saltgrass

Excellent Member
Microsoft Community Contributor
#11
You seem to be very informed about Power requirements, so I will not attempt to tell you your supply should be replaced. I checked the power requirements for the card on the EVGA site and it does show a 12v rail requirement of 24 amps. But it also shows a minimum wattage of 450w.

The site probably pads the minimum requirement some just to be safe, but if you continue to have problems, replacing the supply might be something to consider.
 


#12
I will consider your idea for sure. For now I haven't another PSU but I will try the swap just in case because I want to know what is wrong.

I read someone using the same seasonic G-360 with the same graphic card (MSI GTX660 twin frozr which is one of the most powerfull GPU that needs only 1 6pin PCI-E connector) but the CPU is a 2500K which draws even more current than my 3470. But who knows, my PS may be faulty.
 


Last edited by a moderator:

kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#13
Clark may well be on to something here and it might be worth you using the calculator for your requirements here:

eXtreme Power Supply Calculator

I'm also going to ask a colleague to look over your dmp file as he's the real expert for bsod issues.
 


#14
Thank you for helping :)

Extreme Power Supply Calculator states 274W minimum PSU wattage and recommends a 324W one. It should be OK although not by a wide margin but only a PSU swap can confirm.
My mini ITX system works well under full load though, temps and noise are low : <60° (<140°F) at full load (OCCT) and <26°C (<79°F) at idle for both CPU and GPU. The PSU is keeping low temp as well and its fan stays quite enough at full load.
However that doesn't exclude a defective PSU.
View attachment eXtreme Power Supply Calculator.pdf

EDIT : 310.90 WHQL removed with Driver Fusion. 314.07 WHQL installed but the problem is still present.
 


Last edited by a moderator:

usasma

Fantastic Member
Microsoft Community Contributor
#15
There's a common misunderstanding that there's a specific size PSU appropriate for a particular video card. This is untrue.
Each system is unique and has different power requirements based upon the amount of power that each device needs/consumes at different stages of it's operation.

When a manufacturer suggests a certain wattage PSU - it's an ESTIMATE. Although reputable manufacturer's may be more reliable than others - they are still just estimates.

For example, a stock system with only a hard drive, mobo and video card needs less power than a similar system that's overclocked. If a video card is at idle it'll require less power than if it's processing an extremely intense graphics rendering session) Then, if you add fans and devices (such as a TV card, a DVD drive, etc) - then the system will obviously need more power.

The only way (IME) to tell is to remove enough power consuming devices so you can see if the BSOD's stop or decrease in frequency. Just removing a fan or two won't be sufficient to determine this. It'll take removing enough power-eating devices that you can be sure that the required power is substantially less than it was when everything was hooked up.

More To Follow.....
 


usasma

Fantastic Member
Microsoft Community Contributor
#16
First, please turn Driver Verifier off. It's no longer needed and it's still stressing drivers. To do this, open up verifier.exe and select "Delete existing settings", click on "Finish" and then reboot for the settings to take affect.

Next, one of the errors is a STOP 0x1E. Please note the Usual Causes listed here: BSOD Index
Hardware errors that affect low-level things (like power) generally spit out random errors.

But, there's a typical low-level problem driver in your memory dumps:
NTIOLib_X64.sys Tue Oct 19 23:45:49 2010 (4CBE901D)
MSI Afterburner driver (known BSOD issues with Windows 7)
http://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.sys
This driver usually belongs to MSI Afterburner/RivaTuner/EVGA Precision. Please uninstall that program IMMEDIATELY.

If the BSOD's continue after the above things are done, then I'd have to suspect that there's a hardware problem with the video card. There's just not evidence (IMO) to suspect the PSU at this time. Do you have another video card that you can borrow to test with?

BSOD SUMMARY:
Debug session time: Fri Feb 15 09:52:55.611 2013 (UTC - 8:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\021513-5734-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:10:30.239
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1b7221 )
BugCheck C4, {91, 2, fffffa8006f38080, 0}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
the operating system. The only supported way to extend a kernel
mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffffa8006f38080
Arg4: 0000000000000000
BUGCHECK_STR: 0xc4_91
PROCESS_NAME: svchost.exe
FAILURE_BUCKET_ID: 0xc4_91_nvlddmkm+1b7221
MaxSpeed: 3200
CurrentSpeed: 3193
BiosVersion = F2
BiosReleaseDate = 08/23/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Feb 15 12:38:43.590 2013 (UTC - 8:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\021513-5875-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 2:45:26.248
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1b7221 )
BugCheck C4, {91, 2, fffffa80098fbb00, 0}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
the operating system. The only supported way to extend a kernel
mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffffa80098fbb00
Arg4: 0000000000000000
BUGCHECK_STR: 0xc4_91
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0xc4_91_nvlddmkm+1b7221
MaxSpeed: 3200
CurrentSpeed: 3193
BiosVersion = F2
BiosReleaseDate = 08/23/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Feb 15 13:08:16.598 2013 (UTC - 8:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\021513-6171-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:01:51.249
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1b7221 )
BugCheck C4, {91, 2, fffff80367f6a880, 0}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
the operating system. The only supported way to extend a kernel
mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffff80367f6a880
Arg4: 0000000000000000
BUGCHECK_STR: 0xc4_91
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0xc4_91_nvlddmkm+1b7221
MaxSpeed: 3200
CurrentSpeed: 3193
BiosVersion = F2
BiosReleaseDate = 08/23/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Feb 15 03:29:37.593 2013 (UTC - 8:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\021513-6203-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:18:32.233
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1b7221 )
BugCheck C4, {91, 2, fffff80145f5b880, 0}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
the operating system. The only supported way to extend a kernel
mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffff80145f5b880
Arg4: 0000000000000000
BUGCHECK_STR: 0xc4_91
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0xc4_91_nvlddmkm+1b7221
MaxSpeed: 3200
CurrentSpeed: 3193
BiosVersion = F2
BiosReleaseDate = 08/23/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Feb 15 03:04:35.596 2013 (UTC - 8:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\021513-6234-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:03:27.236
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1b7221 )
BugCheck C4, {91, 2, fffffa800928b040, 0}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
the operating system. The only supported way to extend a kernel
mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffffa800928b040
Arg4: 0000000000000000
BUGCHECK_STR: 0xc4_91
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0xc4_91_nvlddmkm+1b7221
MaxSpeed: 3200
CurrentSpeed: 3193
BiosVersion = F2
BiosReleaseDate = 08/23/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Feb 15 05:56:25.591 2013 (UTC - 8:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\021513-6281-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 1:34:17.249
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1b7221 )
BugCheck C4, {91, 2, fffffa8007861b00, 0}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
the operating system. The only supported way to extend a kernel
mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffffa8007861b00
Arg4: 0000000000000000
BUGCHECK_STR: 0xc4_91
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0xc4_91_nvlddmkm+1b7221
MaxSpeed: 3200
CurrentSpeed: 3193
BiosVersion = F2
BiosReleaseDate = 08/23/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Feb 15 03:34:06.924 2013 (UTC - 8:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\021513-6343-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:01:31.575
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+b4820 )
BugCheck 1E, {ffffffffc0000005, fffff88003d00820, 0, ffffffffffffffff}
BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
Bugcheck code 0000001E
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88003d00820, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
BUGCHECK_STR: 0x1E_c0000005_R
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0x1E_c0000005_R_nvlddmkm+b4820
MaxSpeed: 3200
CurrentSpeed: 3193
BiosVersion = F2
BiosReleaseDate = 08/23/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Feb 15 09:16:55.600 2013 (UTC - 8:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\021513-6375-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:04:23.233
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1b7221 )
BugCheck C4, {91, 2, fffff80067f54880, 0}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
the operating system. The only supported way to extend a kernel
mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffff80067f54880
Arg4: 0000000000000000
BUGCHECK_STR: 0xc4_91
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0xc4_91_nvlddmkm+1b7221
MaxSpeed: 3200
CurrentSpeed: 3193
BiosVersion = F2
BiosReleaseDate = 08/23/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Feb 15 02:26:30.589 2013 (UTC - 8:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\021513-6531-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:01:15.241
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1b7221 )
BugCheck C4, {91, 2, fffff8007e9cb880, 0}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
the operating system. The only supported way to extend a kernel
mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffff8007e9cb880
Arg4: 0000000000000000
BUGCHECK_STR: 0xc4_91
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0xc4_91_nvlddmkm+1b7221
MaxSpeed: 3200
CurrentSpeed: 3193
BiosVersion = F2
BiosReleaseDate = 08/23/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Thu Feb 14 12:08:16.637 2013 (UTC - 8:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\021413-5875-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:02:31.290
Probably caused by : pci.sys
BugCheck 9F, {3, fffffa8006b1d060, fffff803c0dddb30, fffffa8006b41760}
BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
Bugcheck code 0000009F
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8006b1d060, Physical Device Object of the stack
Arg3: fffff803c0dddb30, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa8006b41760, The blocked IRP
BUGCHECK_STR: 0x9F
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: MsMpEng.exe
FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Thu Feb 14 13:22:52.586 2013 (UTC - 8:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\021413-6000-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:43:26.279
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1b7221 )
BugCheck C4, {91, 2, fffff803653ce880, 0}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
the operating system. The only supported way to extend a kernel
mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffff803653ce880
Arg4: 0000000000000000
BUGCHECK_STR: 0xc4_91
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0xc4_91_nvlddmkm+1b7221
MaxSpeed: 3200
CurrentSpeed: 3193
BiosVersion = F2
BiosReleaseDate = 08/23/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Feb 15 12:44:47.596 2013 (UTC - 8:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\021513-5531-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:01:51.243
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1b7221 )
BugCheck C4, {91, 2, fffffa801b491b00, 0}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
the operating system. The only supported way to extend a kernel
mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffffa801b491b00
Arg4: 0000000000000000
BUGCHECK_STR: 0xc4_91
PROCESS_NAME: svchost.exe
FAILURE_BUCKET_ID: 0xc4_91_nvlddmkm+1b7221
MaxSpeed: 3200
CurrentSpeed: 3193
BiosVersion = F2
BiosReleaseDate = 08/23/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Feb 17 00:02:56.596 2013 (UTC - 8:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\021713-5781-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:00:51.271
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1b7221 )
BugCheck C4, {91, 2, fffff80314bbd880, 0}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
the operating system. The only supported way to extend a kernel
mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffff80314bbd880
Arg4: 0000000000000000
BUGCHECK_STR: 0xc4_91
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0xc4_91_nvlddmkm+1b7221
MaxSpeed: 3200
CurrentSpeed: 3193
BiosVersion = F3c
BiosReleaseDate = 11/21/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sat Feb 16 23:58:29.596 2013 (UTC - 8:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\021713-5859-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:00:38.255
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1b7221 )
BugCheck C4, {91, 2, fffff8032a368880, 0}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
the operating system. The only supported way to extend a kernel
mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffff8032a368880
Arg4: 0000000000000000
BUGCHECK_STR: 0xc4_91
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0xc4_91_nvlddmkm+1b7221
MaxSpeed: 3200
CurrentSpeed: 3193
BiosVersion = F3c
BiosReleaseDate = 11/21/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sat Feb 16 23:54:29.596 2013 (UTC - 8:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\021713-5890-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:03:37.261
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1b7221 )
BugCheck C4, {91, 2, fffffa800676cb00, 0}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
the operating system. The only supported way to extend a kernel
mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffffa800676cb00
Arg4: 0000000000000000
BUGCHECK_STR: 0xc4_91
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0xc4_91_nvlddmkm+1b7221
MaxSpeed: 3200
CurrentSpeed: 3193
BiosVersion = F3c
BiosReleaseDate = 11/21/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sat Feb 16 23:56:24.597 2013 (UTC - 8:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\021713-5906-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:01:32.271
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1b7221 )
BugCheck C4, {91, 2, fffffa80192fa940, 0}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
the operating system. The only supported way to extend a kernel
mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffffa80192fa940
Arg4: 0000000000000000
BUGCHECK_STR: 0xc4_91
PROCESS_NAME: svchost.exe
FAILURE_BUCKET_ID: 0xc4_91_nvlddmkm+1b7221
MaxSpeed: 3200
CurrentSpeed: 3193
BiosVersion = F3c
BiosReleaseDate = 11/21/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Feb 17 00:00:43.596 2013 (UTC - 8:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\021713-5937-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:00:40.269
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1b7221 )
BugCheck C4, {91, 2, fffff8033794f880, 0}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
the operating system. The only supported way to extend a kernel
mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffff8033794f880
Arg4: 0000000000000000
BUGCHECK_STR: 0xc4_91
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0xc4_91_nvlddmkm+1b7221
MaxSpeed: 3200
CurrentSpeed: 3193
BiosVersion = F3c
BiosReleaseDate = 11/21/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sat Feb 16 23:24:45.596 2013 (UTC - 8:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\021713-5953-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:00:35.271
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1b7221 )
BugCheck C4, {91, 2, fffff802067c2880, 0}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
the operating system. The only supported way to extend a kernel
mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffff802067c2880
Arg4: 0000000000000000
BUGCHECK_STR: 0xc4_91
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0xc4_91_nvlddmkm+1b7221
MaxSpeed: 3200
CurrentSpeed: 3193
BiosVersion = F3c
BiosReleaseDate = 11/21/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Feb 17 05:48:59.593 2013 (UTC - 8:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\021713-6109-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:00:38.268
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1b7221 )
BugCheck C4, {91, 2, fffffa801945eb00, 0}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
the operating system. The only supported way to extend a kernel
mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffffa801945eb00
Arg4: 0000000000000000
BUGCHECK_STR: 0xc4_91
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0xc4_91_nvlddmkm+1b7221
MaxSpeed: 3200
CurrentSpeed: 3193
BiosVersion = F3c
BiosReleaseDate = 11/21/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Feb 17 06:37:49.595 2013 (UTC - 8:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\021713-6109-02.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:03:31.590
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1b7221 )
BugCheck C4, {91, 2, fffffa801954bb00, 0}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
the operating system. The only supported way to extend a kernel
mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffffa801954bb00
Arg4: 0000000000000000
BUGCHECK_STR: 0xc4_91
PROCESS_NAME: svchost.exe
FAILURE_BUCKET_ID: 0xc4_91_nvlddmkm+1b7221
MaxSpeed: 3200
CurrentSpeed: 3193
BiosVersion = F3c
BiosReleaseDate = 11/21/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Feb 17 02:43:16.595 2013 (UTC - 8:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\021713-6171-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 2:38:01.193
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1b7221 )
BugCheck C4, {91, 2, fffffa8019afe040, 0}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
the operating system. The only supported way to extend a kernel
mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffffa8019afe040
Arg4: 0000000000000000
BUGCHECK_STR: 0xc4_91
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0xc4_91_nvlddmkm+1b7221
MaxSpeed: 3200
CurrentSpeed: 3193
BiosVersion = F3c
BiosReleaseDate = 11/21/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

*** 3rd PARTY DRIVER LIST ***
*** 3rd PARTY DRIVER LIST ***



HECIx64.sys Mon Jul 2 15:14:58 2012 (4FF21D62)
NETwNe64.sys Tue Dec 6 09:48:39 2011 (4EDE5577)
NTIOLib_X64.sys Tue Oct 19 23:45:49 2010 (4CBE901D)
Rt630x64.sys Wed Oct 19 05:12:55 2011 (4E9EBEC7)
dump_storahci.sys Wed Jul 25 19:30:35 2012 (5010ABCB)
hiber_storahci.sys Wed Jul 25 19:30:35 2012 (5010ABCB)
intelppm.sys Mon Nov 5 19:55:02 2012 (50988A16)
nvhda64v.sys Tue Jul 3 08:25:04 2012 (4FF30ED0)
nvlddmkm.sys Fri Dec 28 22:47:52 2012 (50DE9218)
nvlddmkm.sys Tue Oct 2 11:21:13 2012 (506B3099)






http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
NETwNe64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.sys
http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys
http://www.carrona.org/drivers/driver.php?id=hiber_storahci.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
 


kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#17
Just to add to Johns post, the only other driver I saw in your dmp file which was out of date was an Intel chipset driver. I notice your motherboard drivers page is running a more current one. I'd try updating to that one or go directly to Intels site:

GIGABYTE - Motherboard - Socket 1155 - GA-H77N-WIFI (rev. 1.0)
 


#18
Hi,
I removed the MSI Afterburner utility yesterday. Driver verifier is turned off. I installed drivers from my gigabyte MB webpage :
chipset, WiFi and bluetooth (intel), audio and Ethernet (Realtek). They were all more recent than those installed by Windows 8.

Now I still have the resume from sleep issue but with a subtle change: screen takes 30s to wake and the BSOD is now a "DPC watchdog violation" instead of "driver verifier detected violation".
Last archive contains last dump and setup with new drivers.
View attachment W7F_18-02-2013.zip

I will try the video card swap with an old cheap AMD. Note that with the integrated intel HD the resume from sleep works well.
 


kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#19
Hmm.. ok. I had to re-install today myself but will have the debugger up and running by the morning. Is there anyway to disable the integrated gpu via the bios perhaps?
 


kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#20
Hi,

I'm still seeing afterburner in the driver stack:

Rt630x64.sys Wed Oct 19 13:12:55 2011

Try some of the tips found in this video to remove it completely:

How to remove and uninstall MSI Afterburner
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.