locked
BSOD DRIVER_POWER_STATE_FAILURE 0x9F (0x4,0x258,...,...) RRS feed

  • Question

  • Hey guys,

    Looks like you were straight to the point when I found other posts about this issue. Hoping you can do the same for me. Previous to these BSODs, I've been experiencing "stuttering," for lack of a better term, after bootup. Several restarts normally resolve the issue.

    Machine is custom build - Win 7 Pro
    Intel i7 950
    GeForce GTX 480
    Don't remember HDD name and Device Manager is shows a less-than-useful display name. 

    I believe this is a link to the log files? Never used SkyDrive before, and it's less than intuitive for linking files...

    https://skydrive.live.com/self.aspx/.Public/080911-14336-01.dmp?cid=a554df84006bbd9d&sc=documents

    In the meantime, I'll begin updating as many drivers as I can find. 

    I'm also having issues with my DVD RW drive not responding, though it does show up in My Computer + Device Manager. The FixIt utility hasn't proved helpful. Should I open a new thread for that? What information should I provide?

    EDIT: The DVD RW drive issue is on another machine - Acer Aspire 57739G.

    Thanks!!


    ~The Beege
    • Edited by The Beege Tuesday, August 9, 2011 2:37 AM Forgot to include relevant information.
    Tuesday, August 9, 2011 2:34 AM

Answers

  • Hi,

     

    I would like to know if the issue occurs in Safe Mode. From dump file, I cannot identify which driver caused the issue. Therefore, I suggest perform system restore first. If it doesn't work, try to update all possible devices' driver from manufacture's site.

     

    Also, please use Driver Verifier to collect the dump file.

     

    http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

     

    Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

     

    Best Regards,

    Niki


    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Niki Han Wednesday, August 17, 2011 8:47 AM
    Thursday, August 11, 2011 9:07 AM

All replies

  • Hi guys, 

    I see 11 threads that have gotten responses before mine. Can I get some help?

    I downloaded .NET 4 and the Windows Debugging Tools. When attempting to use WinDbg to view my minidump files, I receive the following errors:

    Executable search path is: 

    *********************************************************************

    * Symbols can not be loaded because symbol path is not initialized. *

    *                                                                   *

    * The Symbol Path can be set by:                                    *

    *   using the _NT_SYMBOL_PATH environment variable.                 *

    *   using the -y <symbol_path> argument when starting the debugger. *

    *   using .sympath and .sympath+                                    *

    *********************************************************************

     

    BugCheck 1000009F, {4, 258, fffffa8006dad740, fffff80000b9c510}

     

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

     

    *************************************************************************

    ***                                                                   ***

    ***                                                                   ***

    ***    Your debugger is not using the correct symbols                 ***

    ***                                                                   ***

    ***    In order for this command to work properly, your symbol path   ***

    ***    must point to .pdb files that have full type information.      ***

    ***                                                                   ***

    ***    Certain .pdb files (such as the public OS symbols) do not      ***

    ***    contain the required information.  Contact the group that      ***

    ***    provided you with these symbols if you need this command to    ***

    ***    work.                                                          ***

    ***                                                                   ***

    ***    Type referenced: nt!_ETHREAD                                   ***

    ***                                                                   ***

    *************************************************************************

     

    Please advise as to how I should proceed in either addressing the original issue or configuring my debugger properly.

    Thanks


    ~The Beege
    Tuesday, August 9, 2011 6:26 PM
  • Another update. I got the debugger to function (http://support.microsoft.com/kb/311503). I'm unable to determine the issue except that it has to do with drivers. I've already updated my video card driver. I'm planning to see if there are any chipset updates, and I plan to flash my BIOS up to the latest version tonight.

    Please help me determine which driver is causing the issue:

     

    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.

     

     

    Loading Dump File [C:\Windows\Minidump\080911-14336-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available

     

    Symbol search path is: SRV*C:\DebuggerSymbols\*http://msdl.microsoft.com/download/symbols;symsrv*symsrv.dll*f:\localsymbols*http://msdl.microsoft.com/download/symbols

    Executable search path is: 

    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS

    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631

    Machine Name:

    Kernel base = 0xfffff800`0321d000 PsLoadedModuleList = 0xfffff800`03462650

    Debug session time: Tue Aug  9 02:12:07.692 2011 (UTC - 5:00)

    System Uptime: 0 days 0:15:19.785

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ..............................

    Loading User Symbols

    Loading unloaded module list

    .....

    *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

     

    Use !analyze -v to get detailed debugging information.

     

    BugCheck 1000009F, {4, 258, fffffa8006dad740, fffff80000b9c510}

     

    Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a )

     

    Followup: MachineOwner

    ---------

     

    0: kd> !analyze -v

    *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

     

    DRIVER_POWER_STATE_FAILURE (9f)

    A driver is causing an inconsistent power state.

    Arguments:

    Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp

    subsystem.

    Arg2: 0000000000000258, Timeout in seconds.

    Arg3: fffffa8006dad740, The thread currently holding on to the Pnp lock.

    Arg4: fffff80000b9c510

     

    Debugging Details:

    ------------------

     

     

    DRVPOWERSTATE_SUBCODE:  4

     

    FAULTING_THREAD:  fffffa8006dad740

     

    CUSTOMER_CRASH_COUNT:  1

     

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

     

    BUGCHECK_STR:  0x9F

     

    PROCESS_NAME:  System

     

    CURRENT_IRQL:  2

     

    LOCK_ADDRESS:  fffff80003498b60 -- (!locks fffff80003498b60)

     

    Resource @ nt!PiEngineLock (0xfffff80003498b60)    Available

     

    WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.

     

     

    WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

     

    1 total locks

     

    PNP_TRIAGE: 

    Lock address  : 0xfffff80003498b60

    Thread Count  : 0

    Thread address: 0x0000000000000000

    Thread wait   : 0x0

     

    LAST_CONTROL_TRANSFER:  from fffff800032a1f92 to fffff8000329f4da

     

    STACK_TEXT:  

    fffff880`03369660 fffff800`032a1f92 : fffffa80`06dad740 fffffa80`06dad740 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a

    fffff880`033697a0 fffff800`032a47af : fffff880`03369c10 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1d2

    fffff880`03369830 fffff800`033548f5 : 00000000`00000000 00000000`00000000 fffffa80`06d0dc00 fffff800`03507100 : nt!KeWaitForSingleObject+0x19f

    fffff880`033698d0 fffff800`03638d1e : fffff800`03498920 fffff880`033699a4 00000000`00000000 00000000`00000001 : nt!PnpDeviceCompletionQueueGetCompletedRequest+0x35

    fffff880`03369920 fffff800`03685d58 : fffffa80`06d0dc60 fffffa80`06d0dc60 00000000`00000002 00000000`00000000 : nt!PnpDeviceCompletionProcessCompletedRequests+0x5e

    fffff880`03369950 fffff800`03686208 : fffff800`034964e0 00000000`00000000 00000000`00000001 fffff800`03507248 : nt!PipProcessDevNodeTree+0x378

    fffff880`03369bc0 fffff800`03396927 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98

    fffff880`03369c10 fffff800`032a7021 : fffff800`03396600 fffff800`0343a201 fffffa80`06dad700 00000000`00000000 : nt!PnpDeviceActionWorker+0x327

    fffff880`03369cb0 fffff800`0353932e : 00000000`00000000 fffffa80`06dad740 00000000`00000080 fffffa80`06d11040 : nt!ExpWorkerThread+0x111

    fffff880`03369d40 fffff800`0328e666 : fffff880`0316a180 fffffa80`06dad740 fffff880`031750c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a

    fffff880`03369d80 00000000`00000000 : fffff880`0336a000 fffff880`03364000 fffff880`063828e0 00000000`00000000 : nt!KiStartSystemThread+0x16

     

     

    STACK_COMMAND:  .thread 0xfffffa8006dad740 ; kb

     

    FOLLOWUP_IP: 

    nt!KiSwapContext+7a

    fffff800`0329f4da 488d8c2400010000 lea     rcx,[rsp+100h]

     

    SYMBOL_STACK_INDEX:  0

     

    SYMBOL_NAME:  nt!KiSwapContext+7a

     

    FOLLOWUP_NAME:  MachineOwner

     

    MODULE_NAME: nt

     

    IMAGE_NAME:  ntkrnlmp.exe

     

    DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

     

    FAILURE_BUCKET_ID:  X64_0x9F_4_nt!KiSwapContext+7a

     

    BUCKET_ID:  X64_0x9F_4_nt!KiSwapContext+7a

     

    Followup: MachineOwner

    ---------

     


    ~The Beege
    Tuesday, August 9, 2011 6:39 PM
  • Hi,

     

    I would like to know if the issue occurs in Safe Mode. From dump file, I cannot identify which driver caused the issue. Therefore, I suggest perform system restore first. If it doesn't work, try to update all possible devices' driver from manufacture's site.

     

    Also, please use Driver Verifier to collect the dump file.

     

    http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

     

    Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

     

    Best Regards,

    Niki


    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Niki Han Wednesday, August 17, 2011 8:47 AM
    Thursday, August 11, 2011 9:07 AM