locked
BSOD Driver powerstate failure RRS feed

  • Question

  • My computer, wich is running w7, will suddenly restart itself, and give me the errorcode Driver Powerstate failure. I have no idea what it can be.

    I've searched the internet for answers, but then I find induviduals that upload their files from their own computerm, and I don't know if it's the same reason of shutdowm as myself.

    Is it enough to upload files from my computer here, that you can help me solve my problem? I don't know what files I should upload, so please tell me where and which. 

    Thanks.

    Thursday, August 12, 2010 4:37 PM

Answers

  • It appears that this was caused by the driver o2sd.sys. After doing a
    quick Google search, this might be a Fujitsu SD card reader,
     
     
    You can probably track down which device is using the driver through the
    components node of the msinfo32.exe utility. I would recommend updating
    the drivers for any devices that use the driver. If you want help
    identifying the device that was using it, please upload the .nfo file
    from your system using Skydrive and I can take a look at it.
     
    To generate the .nfo file, click start -> search box, enter msinfo32.exe
    and press enter. When the system information application opens, select
    file -> save and upload the resulting file.
     
    *******************************************************************************
    *
          *
    *                        Bugcheck Analysis
          *
    *
          *
    *******************************************************************************
     
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 00000003, A device object has been blocking an Irp for too long a time
    Arg2: 856652e0, Physical Device Object of the stack
    Arg3: 8078adb0, Functional Device Object of the stack
    Arg4: 851873c0, The blocked IRP
     
    Debugging Details:
    ------------------
     
    *** WARNING: Unable to verify timestamp for o2sd.sys
    *** ERROR: Module load completed but symbols could not be loaded for
    o2sd.sys
     
    DRVPOWERSTATE_SUBCODE:  3
     
    DRIVER_OBJECT: 86187298
     
    IMAGE_NAME:  o2sd.sys
     
    DEBUG_FLR_IMAGE_TIMESTAMP:  47f47de2
     
    MODULE_NAME: o2sd
     
    FAULTING_MODULE: 907d4000 o2sd
     
    CUSTOMER_CRASH_COUNT:  1
     
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
     
    BUGCHECK_STR:  0x9F
     
    PROCESS_NAME:  chrome.exe
     
    CURRENT_IRQL:  2
     
    STACK_TEXT:
    8078ad64 82e51054 0000009f 00000003 856652e0 nt!KeBugCheckEx+0x1e
    8078add0 82e508e8 8078ae70 00000000 8525b788 nt!PopCheckIrpWatchdog+0x1f5
    8078ae08 82e7f04d 82f56a20 00000000 63f1616d nt!PopCheckForIdleness+0x73
    8078ae4c 82e7eff1 82f3ed20 8078af78 00000001 nt!KiProcessTimerDpcTable+0x50
    8078af38 82e7eeae 82f3ed20 8078af78 00000000
    nt!KiProcessExpiredTimerList+0x101
    8078afac 82e7d20e 004a237f aa8d3d34 00000000 nt!KiTimerExpiration+0x25c
    8078aff4 82e7c9dc aa8d3ce4 00000000 00000000 nt!KiRetireDpcList+0xcb
    8078aff8 aa8d3ce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    82e7c9dc 00000000 0000001a 00d6850f bb830000 0xaa8d3ce4
     STACK_COMMAND:  kb
     
    FOLLOWUP_NAME:  MachineOwner
     
    FAILURE_BUCKET_ID:  0x9F_3_IMAGE_o2sd.sys
     
    BUCKET_ID:  0x9F_3_IMAGE_o2sd.sys
     
    Followup: MachineOwner
    ---------
     
    0: kd> lmvm o2sd
    start    end        module name
    907d4000 907dd380   o2sd     T (no symbols)
        Loaded symbol image file: o2sd.sys
        Image path: \SystemRoot\system32\DRIVERS\o2sd.sys
        Image name: o2sd.sys
        Timestamp:        Thu Apr 03 00:49:06 2008 (47F47DE2)
        CheckSum:         000174FB
        ImageSize:        00009380
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
     

    -- Mike Burr
    • Marked as answer by Arthur Xie Tuesday, August 17, 2010 3:32 AM
    Friday, August 13, 2010 7:28 PM
  • Just to follow up on what Mike Burr has stated, you may be able to update the driver which is causing the crash, the o2sd.sys, by downloading and installing the O2 card reader driver from the following link:

    http://global-download.acer.com/Step5.aspx?Step1=Notebook&Step2=Extensa&Step3=Extensa%205630&BC=Acer&SC=PA_7&LC=en&OS=722&FS=O01&Category=DRIVER

    If problems persist after the driver update please post the resulting minidump file(s).

    • Marked as answer by Arthur Xie Tuesday, August 17, 2010 3:32 AM
    Friday, August 13, 2010 8:03 PM

All replies

  • Hi,
     
    Can you upload any files from \Windows\Minidump, I have posted
    instructions here,
     
     

    -- Mike Burr
    Thursday, August 12, 2010 5:33 PM
  • Like this?

     http://cid-8bb0287905d493fd.office.live.com/embedicon.aspx/.Documents/081210-25318-01.dmp

    Friday, August 13, 2010 12:12 AM
  • It appears that this was caused by the driver o2sd.sys. After doing a
    quick Google search, this might be a Fujitsu SD card reader,
     
     
    You can probably track down which device is using the driver through the
    components node of the msinfo32.exe utility. I would recommend updating
    the drivers for any devices that use the driver. If you want help
    identifying the device that was using it, please upload the .nfo file
    from your system using Skydrive and I can take a look at it.
     
    To generate the .nfo file, click start -> search box, enter msinfo32.exe
    and press enter. When the system information application opens, select
    file -> save and upload the resulting file.
     
    *******************************************************************************
    *
          *
    *                        Bugcheck Analysis
          *
    *
          *
    *******************************************************************************
     
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 00000003, A device object has been blocking an Irp for too long a time
    Arg2: 856652e0, Physical Device Object of the stack
    Arg3: 8078adb0, Functional Device Object of the stack
    Arg4: 851873c0, The blocked IRP
     
    Debugging Details:
    ------------------
     
    *** WARNING: Unable to verify timestamp for o2sd.sys
    *** ERROR: Module load completed but symbols could not be loaded for
    o2sd.sys
     
    DRVPOWERSTATE_SUBCODE:  3
     
    DRIVER_OBJECT: 86187298
     
    IMAGE_NAME:  o2sd.sys
     
    DEBUG_FLR_IMAGE_TIMESTAMP:  47f47de2
     
    MODULE_NAME: o2sd
     
    FAULTING_MODULE: 907d4000 o2sd
     
    CUSTOMER_CRASH_COUNT:  1
     
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
     
    BUGCHECK_STR:  0x9F
     
    PROCESS_NAME:  chrome.exe
     
    CURRENT_IRQL:  2
     
    STACK_TEXT:
    8078ad64 82e51054 0000009f 00000003 856652e0 nt!KeBugCheckEx+0x1e
    8078add0 82e508e8 8078ae70 00000000 8525b788 nt!PopCheckIrpWatchdog+0x1f5
    8078ae08 82e7f04d 82f56a20 00000000 63f1616d nt!PopCheckForIdleness+0x73
    8078ae4c 82e7eff1 82f3ed20 8078af78 00000001 nt!KiProcessTimerDpcTable+0x50
    8078af38 82e7eeae 82f3ed20 8078af78 00000000
    nt!KiProcessExpiredTimerList+0x101
    8078afac 82e7d20e 004a237f aa8d3d34 00000000 nt!KiTimerExpiration+0x25c
    8078aff4 82e7c9dc aa8d3ce4 00000000 00000000 nt!KiRetireDpcList+0xcb
    8078aff8 aa8d3ce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    82e7c9dc 00000000 0000001a 00d6850f bb830000 0xaa8d3ce4
     STACK_COMMAND:  kb
     
    FOLLOWUP_NAME:  MachineOwner
     
    FAILURE_BUCKET_ID:  0x9F_3_IMAGE_o2sd.sys
     
    BUCKET_ID:  0x9F_3_IMAGE_o2sd.sys
     
    Followup: MachineOwner
    ---------
     
    0: kd> lmvm o2sd
    start    end        module name
    907d4000 907dd380   o2sd     T (no symbols)
        Loaded symbol image file: o2sd.sys
        Image path: \SystemRoot\system32\DRIVERS\o2sd.sys
        Image name: o2sd.sys
        Timestamp:        Thu Apr 03 00:49:06 2008 (47F47DE2)
        CheckSum:         000174FB
        ImageSize:        00009380
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
     

    -- Mike Burr
    • Marked as answer by Arthur Xie Tuesday, August 17, 2010 3:32 AM
    Friday, August 13, 2010 7:28 PM
  • Just to follow up on what Mike Burr has stated, you may be able to update the driver which is causing the crash, the o2sd.sys, by downloading and installing the O2 card reader driver from the following link:

    http://global-download.acer.com/Step5.aspx?Step1=Notebook&Step2=Extensa&Step3=Extensa%205630&BC=Acer&SC=PA_7&LC=en&OS=722&FS=O01&Category=DRIVER

    If problems persist after the driver update please post the resulting minidump file(s).

    • Marked as answer by Arthur Xie Tuesday, August 17, 2010 3:32 AM
    Friday, August 13, 2010 8:03 PM