Driver Power State Failure - Windows 8.1 x64

R

RichardVN

New member
Joined
Nov 28, 2014
Posts
2
Hello. I just got my new laptop yesterday. It was running fine until DRIVER_POWER_STATE_FAILURE had shown up. I need help on this :sad:

I have done all the windows updates and updated the graphic driver.

I have uploaded the SynativeFileCollectionApp zip. However I had an error when trying to run Perfmon System Health Report.

I have some logs using the bluescreenview.

==================================================
Dump File : 112814-31046-01.dmp
Crash Time : 11/28/2014 5:05:36 PM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 00000000`00000003
Parameter 2 : ffffe000`2e3d8800
Parameter 3 : fffff801`02031960
Parameter 4 : ffffe000`32b06c60
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1509a0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.3.9600.17415 (winblue_r4.141028-1500)
Processor : x64
Crash Address : ntoskrnl.exe+1509a0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\112814-31046-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 9600
Dump File Size : 2,356,304
Dump File Time : 11/28/2014 5:06:50 PM
==================================================


- Thanks! :smile9:





 

Attachments

Code: 
[COLOR=#ff0000]BugCheck 9F[/COLOR], {[COLOR=#0000cd]3[/COLOR], [COLOR=#ff8c00]ffffe0002e3d8800[/COLOR], fffff80102031960,[COLOR=#008000] ffffe00032b06c60[/COLOR]}

Probably caused by : pci.sys

A Stop 0x9F indicates that a Power IRP wasn't processed within the specified time period, which lead to a Watchdog timer being woken and the bugcheck being produced. A full explanation of the bugcheck is provided here - https://www.sysnative.com/forums/bs...complete-guide-for-debugging-a-stop-0x9f.html

Code: 
0: kd> [COLOR=#008000]knL[/COLOR]
 # Child-SP          RetAddr           Call Site
00 fffff801`02031928 fffff801`0040f43a nt!KeBugCheckEx
01 fffff801`02031930 fffff801`0040f35a [COLOR=#ff0000]nt!PopIrpWatchdogBugcheck+0xde[/COLOR] <-- Bugcheck 
02 fffff801`02031990 fffff801`002d03a8[COLOR=#ff0000] nt!PopIrpWatchdog+0x32[/COLOR] [COLOR=#ff0000][/COLOR]<-- Our Watchdog Timer
03 fffff801`020319e0 fffff801`0035a4ea nt!KiRetireDpcList+0x4f8
04 fffff801`02031c60 00000000`00000000 nt!KiIdleLoop+0x5a

I've haven't been able to use the !irp extension with the blocked IRP, and check which driver stack it was in. I also only just managed to gather half a device stack, which suggested the below third-party graphics card driver. nVidia is notrious for bad drivers, and thereby suggest you check for any updates, otherwise roll back to an older driver.

Code: 
0: kd> [COLOR=#008000]lmvm nvlddmkm[/COLOR]
start             end                 module name
fffff800`67871000 fffff800`68551000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR=#ff0000]Wed Nov 12 20:51:31 2014[/COLOR] (5463C853)
    CheckSum:         00CA4D59
    ImageSize:        00CE0000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
 
x BlueRobot said:
Code: 
[COLOR=#ff0000]BugCheck 9F[/COLOR], {[COLOR=#0000cd]3[/COLOR], [COLOR=#ff8c00]ffffe0002e3d8800[/COLOR], fffff80102031960,[COLOR=#008000] ffffe00032b06c60[/COLOR]}

Probably caused by : pci.sys

A Stop 0x9F indicates that a Power IRP wasn't processed within the specified time period, which lead to a Watchdog timer being woken and the bugcheck being produced. A full explanation of the bugcheck is provided here - https://www.sysnative.com/forums/bs...complete-guide-for-debugging-a-stop-0x9f.html

Code: 
0: kd> [COLOR=#008000]knL[/COLOR]
 # Child-SP          RetAddr           Call Site
00 fffff801`02031928 fffff801`0040f43a nt!KeBugCheckEx
01 fffff801`02031930 fffff801`0040f35a [COLOR=#ff0000]nt!PopIrpWatchdogBugcheck+0xde[/COLOR] <-- Bugcheck 
02 fffff801`02031990 fffff801`002d03a8[COLOR=#ff0000] nt!PopIrpWatchdog+0x32[/COLOR] <-- Our Watchdog Timer
03 fffff801`020319e0 fffff801`0035a4ea nt!KiRetireDpcList+0x4f8
04 fffff801`02031c60 00000000`00000000 nt!KiIdleLoop+0x5a

I've haven't been able to use the !irp extension with the blocked IRP, and check which driver stack it was in. I also only just managed to gather half a device stack, which suggested the below third-party graphics card driver. nVidia is notrious for bad drivers, and thereby suggest you check for any updates, otherwise roll back to an older driver.

Code: 
0: kd> [COLOR=#008000]lmvm nvlddmkm[/COLOR]
start             end                 module name
fffff800`67871000 fffff800`68551000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR=#ff0000]Wed Nov 12 20:51:31 2014[/COLOR] (5463C853)
    CheckSum:         00CA4D59
    ImageSize:        00CE0000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Click to expand...

Thanks for checking out my problem! I went to the manufacture website to download the old Nvidia driver from there. So far there hasn't been many cause of a BSOD yet. I'll post if something happens.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top