BSOD power state failure


  1. Posts : 297
    Windows 7 Pro x64
       #1

    BSOD power state failure


    Woke up one day a couple weeks ago to find my laptop's onboard fan screaming. I opened the laptop to find a lovely BSOD awaiting me. All I caught before I killed the power to the machine was the term "power state failure". I'm not sure what happened, and I'm not too concerned about it now, but I'd very much like to know exactly what happened.

    DETAILS:

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.768.3
    Locale ID: 1033

    Additional information about the problem:
    BCCode: 1000009f
    BCP1: 0000000000000004
    BCP2: 0000000000000258
    BCP3: FFFFFA80073AD040
    BCP4: FFFFF80000B9C3D0
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 768_1



    MINIDUMP FILE:
    bsod_details_1.zip
      My Computer


  2. Posts : 306
    Windows 7 Ultimate x64
       #2

    Hi,

    The dump you've attached mentions memory corruption (most likely driver related until shown otherwise), although it also mentions nusb3hub.sys (NEC Electronics USB 3.0 Host Controller Driver). It's well known to cause BSODs. You can remove it yourself, or you can update it here. Choice is yours.

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000009F, {4, 258, fffffa80073ad040, fffff80000b9c3d0}
    
    Unable to load image \SystemRoot\system32\DRIVERS\nusb3hub.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nusb3hub.sys
    *** ERROR: Module load completed but symbols could not be loaded for nusb3hub.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 : memory_corruption
    
    Followup: memory_corruption
    ---------
    
    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: fffffa80073ad040, The thread currently holding on to the Pnp lock.
    Arg4: fffff80000b9c3d0
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  4
    
    FAULTING_THREAD:  fffffa80073ad040
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff80002ccef32 to fffff80002ccc4da
    
    STACK_TEXT:  
    fffff880`0355b330 fffff800`02ccef32 : fffffa80`073ad040 fffffa80`073ad040 ffffffff`00000000 fffff880`00000007 : nt!KiSwapContext+0x7a
    fffff880`0355b470 fffff800`02cd0742 : fffffa80`0b264360 fffff880`07b30d10 fffff880`00000031 fffff880`0355b668 : nt!KiCommitThreadWait+0x1d2
    fffff880`0355b500 fffff880`07b28071 : 00000000`000f4240 fffffa80`00000004 00000000`00000000 00000000`00000031 : nt!KeDelayExecutionThread+0x186
    fffff880`0355b570 00000000`000f4240 : fffffa80`00000004 00000000`00000000 00000000`00000031 00000000`00000101 : nusb3hub+0x1071
    fffff880`0355b578 fffffa80`00000004 : 00000000`00000000 00000000`00000031 00000000`00000101 fffff880`07b38534 : 0xf4240
    fffff880`0355b580 00000000`00000000 : 00000000`00000031 00000000`00000101 fffff880`07b38534 00000000`00000101 : 0xfffffa80`00000004
    
    
    STACK_COMMAND:  .thread 0xfffffa80073ad040 ; kb
    
    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
        fffff80002ccc803 - nt!SwapContext_PatchXSave+2
        [ 01:21 ]
        fffff80002ccc8e4 - nt!SwapContext_PatchXRstor+2 (+0xe1)
        [ 09:29 ]
        fffff80002cccaa3 - nt!EnlightenedSwapContext_PatchXSave+2 (+0x1bf)
        [ 01:21 ]
        fffff80002cccb86 - nt!EnlightenedSwapContext_PatchXRstor+2 (+0xe3)
        [ 09:29 ]
    4 errors : !nt (fffff80002ccc803-fffff80002cccb86)
    
    MODULE_NAME: memory_corruption
    
    IMAGE_NAME:  memory_corruption
    
    FOLLOWUP_NAME:  memory_corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MEMORY_CORRUPTOR:  ONE_BIT_LARGE
    
    FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT_LARGE
    
    BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT_LARGE
    
    Followup: memory_corruption
      My Computer


  3. Posts : 297
    Windows 7 Pro x64
    Thread Starter
       #3

    Thank you. :)
      My Computer


  4. Posts : 306
    Windows 7 Ultimate x64
       #4

    My pleasure, keep me updated :)
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 23:47.
Find Us