BSOD Randomly/After checkdisk - ERROR 0x0000009F


  1. Posts : 3
    Windows 7 Ultimate x64
       #1

    BSOD Randomly/After checkdisk - ERROR 0x0000009F


    Hey guys this is my first post! Sorry if i sound like a noob
    I've been getting blue screens every now and then... Okay this is what happens:

    - PC starts lagging gradually and then it'll either bluescreen or turn off
    - Its been happening for a while, its weird, it will work for a few months and bluescreens stop, then happen again !
    - The latest bluescreen I got was at the end of performing a check disk
    - Did a memory test and that was okay

    The details on the bluescreen after the check disk completed:

    DRIVER_POWER_STATE_FAILURE

    STOP: 0x0000009F (0x0000000000000004, 0x0000000000000258, 0xFFFFFA8006A00040, 0xFFFFF80000B9C4D0)
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Welcome

    The BSODs were caused by the EtronHub3.sys driver which is the USB3.0 driver
    This driver should be updated
    GIGABYTE - Motherboard - Socket 1155 - GA-Z68A-D3-B3 (rev. 1.0)

    BSOD Report
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000009F, {4, 258, fffffa80077d9b60, fffff80000b9c4d0}
    
    *** WARNING: Unable to verify timestamp for EtronHub3.sys
    *** ERROR: Module load completed but symbols could not be loaded for EtronHub3.sys
    Implicit thread is now fffffa80`077d9b60
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : EtronHub3.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: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    	subsystem.
    Arg2: 0000000000000258, Timeout in seconds.
    Arg3: fffffa80077d9b60, The thread currently holding on to the Pnp lock.
    Arg4: fffff80000b9c4d0, nt!TRIAGE_9F_PNP on Win7
    
    Debugging Details:
    ------------------
    
    Implicit thread is now fffffa80`077d9b60
    
    DRVPOWERSTATE_SUBCODE:  4
    
    DRIVER_OBJECT: fffffa80096e4a70
    
    IMAGE_NAME:  EtronHub3.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d433945
    
    MODULE_NAME: EtronHub3
    
    FAULTING_MODULE: fffff8800405a000 EtronHub3
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    STACK_TEXT:  
    fffff880`0927c170 fffff800`034906e2 : fffffa80`077d9b60 fffffa80`077d9b60 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
    fffff880`0927c2b0 fffff800`03492b9f : 00000000`c0000010 fffffa80`076e9500 fffffa80`00000000 fffff880`053e4597 : nt!KiCommitThreadWait+0x1d2
    fffff880`0927c340 fffff880`0405fd29 : 00000000`00000000 00000000`00000000 fffffa80`076e9500 fffff800`03771d00 : nt!KeWaitForSingleObject+0x19f
    fffff880`0927c3e0 00000000`00000000 : 00000000`00000000 fffffa80`076e9500 fffff800`03771d00 fffff880`02fd5180 : EtronHub3+0x5d29
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0x9F_4_IMAGE_EtronHub3.sys
    
    BUCKET_ID:  X64_0x9F_4_IMAGE_EtronHub3.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm EtronHub3
    start             end                 module name
    fffff880`0405a000 fffff880`04063c00   EtronHub3 T (no symbols)           
        Loaded symbol image file: EtronHub3.sys
        Image path: \SystemRoot\System32\Drivers\EtronHub3.sys
        Image name: EtronHub3.sys
        Timestamp:        Sat Jan 29 03:46:45 2011 (4D433945)
        CheckSum:         00011170
        ImageSize:        00009C00
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    
    Update to SP 1:
    Learn how to install Windows 7 Service Pack 1 (SP1)
      My Computer


  3. Posts : 3
    Windows 7 Ultimate x64
    Thread Starter
       #3

    did that hopefully that fixes it!
      My Computer


  4. Posts : 3
    Windows 7 Ultimate x64
    Thread Starter
       #4

    could there be another problem like a hardware issue? or do you think that's the main cause?
      My Computer


  5. Posts : 15,026
    Windows 10 Home 64Bit
       #5

    samialb said:
    could there be another problem like a hardware issue? or do you think that's the main cause?
    We need to wait & see if you still get BSOD-s
      My Computer


  6. Posts : 15,026
    Windows 10 Home 64Bit
       #6

    Any updates?
      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 18:21.
Find Us