BSoD, driver_power_state_failure, probable cause: ntoskrnl.exe

KR0N · 30 Dec 2012

Hello,

Could I please have some help solving a BSoD (driver_power_state_failure) I have been having on my laptop.

I have done a little digging with the WinDbg package and it points to a probable cause of: ntoskrnl.exe.

The problem seems to (obviously it doesn't) happen at random, after the machine has been on for longer than five minutes.

I've just had it happen as I was writing this. Slightly annoying.

I would like to know more about about this sort of problem, one so I can sort it out and two so I can learn more about this device I have come to rely on so much. Help me to help myself kind of thing.

Thank you.

**Pauly** · 30 Dec 2012

Hello KR0N, Welcome to SF

First off if your OCing in anyway stop, return everything to stock settings for the purposes of testing

If you havent already, fill in your system specs so we know what we are dealing with
System Info - See Your System Specs

Make sure you have read the guide on asking for help with BSOD so you know what we need
https://www.sevenforums.com/crashes-d...tructions.html

Run some scans to check against virus or infection
http://support.kaspersky.com/5350
Windows Defender Offline

OK have run the three dumps you uploaded and they are all the same
Bug Check Code 0x9F BSOD Index this would point at a faulting driver

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa800e40ba10, fffff8000486a748, fffffa800e7ba170}
Unable to load image 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 : pci.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800e40ba10, Physical Device Object of the stack
Arg3: fffff8000486a748, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800e7ba170, The blocked IRP
Debugging Details:
------------------
 
DRVPOWERSTATE_SUBCODE:  3
IMAGE_NAME:  pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f
MODULE_NAME: pci
FAULTING_MODULE: fffff88000e0a000 pci
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  mscorsvw.exe
CURRENT_IRQL:  2
TAG_NOT_DEFINED_c000000f:  FFFFF8000486AFB0
STACK_TEXT:  
fffff800`0486a6f8 fffff800`02b366c2 : 00000000`0000009f 00000000`00000003 fffffa80`0e40ba10 fffff800`0486a748 : nt!KeBugCheckEx
fffff800`0486a700 fffff800`02ad6e3c : fffff800`0486a848 fffff800`0486a848 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34050
fffff800`0486a7a0 fffff800`02ad6cd6 : fffff800`02c73f20 00000000`0002bf88 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`0486a810 fffff800`02ad6bbe : 00000006`8aad5078 fffff800`0486ae88 00000000`0002bf88 fffff800`02c42388 : nt!KiProcessExpiredTimerList+0xc6
fffff800`0486ae60 fffff800`02ad69a7 : fffffa80`0d3c80c2 fffff800`0002bf88 00000000`00000001 00000000`00000088 : nt!KiTimerExpiration+0x1be
fffff800`0486af00 fffff800`02acf305 : 00000000`00000000 fffffa80`0d7d4b50 00000000`00000000 fffff880`0126c8e4 : nt!KiRetireDpcList+0x277
fffff800`0486afb0 fffff800`02acf11c : 00000000`00000000 fffff800`02a0e895 fffff800`02a34460 fffff880`070bfb60 : nt!KyRetireDpcList+0x5
fffff880`070bfaa0 fffff800`02b17193 : fffff800`02ac8740 fffff800`02ac87ac 00000000`00000001 00000000`0051e000 : nt!KiDispatchInterruptContinue
fffff880`070bfad0 fffff800`02ac87ac : 00000000`00000001 00000000`0051e000 00000000`0026ca01 00000000`00510000 : nt!KiDpcInterruptBypass+0x13
fffff880`070bfae0 000007fe`e280d890 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x1fc
00000000`0026c510 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`e280d890
 
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
FAILURE_BUCKET_ID:  X64_0x9F_3_ACPI_IMAGE_pci.sys
BUCKET_ID:  X64_0x9F_3_ACPI_IMAGE_pci.sys
Followup: MachineOwner
---------

All dumps point at system driver pci.sys but looking at driver date shows it is part of SP1 update i believe so this should be good and looks like a false positive, there are mention of nvlddmkm.sys so my initial feeling is this will be gfx driver related so i would start by updating your graphics drivers to most recent ones available but do not get beta version stick to proper releases preferably WHQL certified if poss you may also want to run Drivers - Clean Left over Files after Uninstalling after uninstalling your old drivers before installing new ones to ensure there is no conflicting junk left behind as this can sometimes cause issues.

Only other reference i can find in one of your dumps is one to usbhub.sys which again is a driver from windows update so driver itself would not be problem but not sure what usb devices are running on your system

Might also be worth running an sfc scan to check the integrity of system files
Start>type cmd>right click run as administrator>type sfc /scannow enter you are looking for an output that says no integrity violations found
SFC /SCANNOW Command - System File Checker

KR0N · 30 Dec 2012

Thanks Pauly.

I run the Kaspersky executable, which found 3 unknowns, cleared them out.

Checked my gfx driver, it said it was faulty, I downloaded (interupted once by BSoD) the new driver and installed it.

I also ran the SFC /SCANNOW cmd which was all clear.

I haven't had a problem since. I hope it stays this way. Thanks again.

**Pauly** · 31 Dec 2012

Glad to hear you made some progress
See how you go leave the thread open for several days before you mark as solved

KR0N · 07 Jan 2013

After a week of smooth running used only really for playing Civ 5, with very little internet use I have seemingly the same recurring BSoD. I have attached the .RAR file for your information.

I have just seen a new driver for my gfx card has been released. However I don't know how the fact that a new driver is out would start my gfx card going haywire, but then again I don't know enough about it to make informed arguments.

I've also run the two rootkit/virus detectors, no suspicious hits.

Any help would be great.

**Pauly** · 07 Jan 2013

All three are identical 0x9F probably caused by pci.sys

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa800e415a10, fffff80000b9c3d8, fffffa801c0cde10}
Unable to load image 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 : pci.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800e415a10, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa801c0cde10, The blocked IRP
Debugging Details:
------------------

DRVPOWERSTATE_SUBCODE:  3
IMAGE_NAME:  pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f
MODULE_NAME: pci
FAULTING_MODULE: fffff88000e00000 pci
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
CURRENT_IRQL:  2
TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0
STACK_TEXT:  
fffff800`00b9c388 fffff800`02d3b6d2 : 00000000`0000009f 00000000`00000003 fffffa80`0e415a10 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`02cdbc3c : fffff800`00b9c4f0 fffff800`00b9c4f0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33ac0
fffff800`00b9c430 fffff800`02cdbad6 : fffff800`02e78f20 00000000`00014452 00000000`00000000 fffffa80`1b214bb8 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`02cdb9be : 00000003`04029e0e fffff800`00b9cb18 00000000`00014452 fffff800`02e46cc8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`02cdb7a7 : 00000000`cb342dc3 00000000`00014452 00000000`cb342d0a 00000000`00000051 : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`02cc8cca : fffff800`02e43e80 fffff800`02e51cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
FAILURE_BUCKET_ID:  X64_0x9F_3_ACPI_IMAGE_pci.sys
BUCKET_ID:  X64_0x9F_3_ACPI_IMAGE_pci.sys
Followup: MachineOwner
---------

strangely though there still seems to be an issue with your gfx drivers try uninstalling them running the tool above and then installing the one that just came out, see how you go and let me know
will go through them more later and let you know if i find any thing else

KR0N · 07 Jan 2013

Driver uninstalled, in the process I received two BSoDs - I will upload them if problems persist. Uninstalled all Nvidia components, ran the driver sweeper program to remove leftovers.

This time I will download driver from Dell and not the vendor, perhaps that might make a difference. IDK.

**Pauly** · 07 Jan 2013

Sorry i did not spot that Dell very often mod their gfx drivers specifically for their machines so you are probably best doing that although generally if your machine is running modded drivers it will warn/stop you from installng nvidia ones direct

KR0N · 07 Jan 2013

After some trouble I have reinstalled the graphics driver from the Dell website. The system doesn't seem to want to shut down now either, and it is still BSoDing.

I didn't have any problems when the system was using the integrated graphics instead of the Nvidia card. During this time the system would also shut down properly.

I'm stumped.

KR0N · 09 Jan 2013

Any more ideas Pauly?