BSOD DRIVER_POWER_STATE_FAILURE randomly after cold boot/sleep


  1. Posts : 2
    Windows 10 Pro 64-Bit
       #1

    BSOD DRIVER_POWER_STATE_FAILURE randomly after cold boot/sleep


    For the past month I have been getting random BSOD's all with driver power state failure. They happen randomly, usually within the first 5-10 minutes of cold booting or waking my computer. Steps I have taken to attempt to fix the problem:
    1. Reinstalled GPU drivers/ tried old drivers
    2. Fresh installed Windows 1803, still happened, then fresh installed 1709
    3. Disabled Fast Boot

    None of these things fixed the issue, any help would be much appreciated at pinpointing the issue. Thanks
      My Computer


  2. Posts : 207
    Windows 10 Pro
       #2

    It looks like a power command is getting stuck in the driver stack which included the Focusrite USB driver.
    Code:
    0: kd> !devstack ffffb50c32857060
      !DevObj           !DrvObj            !DevExt           ObjectName
      ffffb50c332a7c60 Unable to load image \SystemRoot\System32\drivers\FocusriteUSB.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for FocusriteUSB.sys
    *** ERROR: Module load completed but symbols could not be loaded for FocusriteUSB.sys
     \Driver\FocusriteUSBffffb50c332d8cf0  InfoMask field not found for _OBJECT_HEADER at ffffb50c332a7c30
    
      ffffb50c332aa4a0  \Driver\ACPI       ffffb50c30bc3870  
      ffffb50c332aa870  \Driver\ACPI       ffffb50c30bc7c40  
    > ffffb50c32857060  \Driver\usbhub     ffffb50c328571b0  Cannot read info offset from nt!ObpInfoMaskToOffset
    
    !DevNode ffffb50c332aad20 :
      DeviceInst is "USB\VID_1235&PID_801C\6&df2ee03&0&1"
      ServiceName is "FocusriteUSB"
    
    0: kd> lmDvm FocusriteUSB
    Browse full module list
    start             end                 module name
    fffff80f`ce970000 fffff80f`ce989000   FocusriteUSB T (no symbols)           
        Loaded symbol image file: FocusriteUSB.sys
        Image path: \SystemRoot\System32\drivers\FocusriteUSB.sys
        Image name: FocusriteUSB.sys
        Browse all global symbols  functions  data
        Timestamp:        Tue Jan  9 06:47:56 2018 (5A54D61C)
        CheckSum:         00022425
        ImageSize:        00019000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
        Information from resource tables:
    I've seen that driver show up recently for other people having 0x9F bugchecks. The version on your system doesn't look terribly old but I'd suggest checking the product support site to see if there's a newer version available for Windows 10. If there isn't a newer driver available I'd suggest trying a different USB port. I can't tell what you have on your system but sometimes USB devices work more reliably when connected to Intel USB ports rather than other 3rd party USB ports.

    Are you intentionally not upgrading Windows 10 beyond 1709?
      My Computer


  3. Posts : 2
    Windows 10 Pro 64-Bit
    Thread Starter
       #3

    cwsink said:
    It looks like a power command is getting stuck in the driver stack which included the Focusrite USB driver.
    Code:
    0: kd> !devstack ffffb50c32857060
      !DevObj           !DrvObj            !DevExt           ObjectName
      ffffb50c332a7c60 Unable to load image \SystemRoot\System32\drivers\FocusriteUSB.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for FocusriteUSB.sys
    *** ERROR: Module load completed but symbols could not be loaded for FocusriteUSB.sys
     \Driver\FocusriteUSBffffb50c332d8cf0  InfoMask field not found for _OBJECT_HEADER at ffffb50c332a7c30
    
      ffffb50c332aa4a0  \Driver\ACPI       ffffb50c30bc3870  
      ffffb50c332aa870  \Driver\ACPI       ffffb50c30bc7c40  
    > ffffb50c32857060  \Driver\usbhub     ffffb50c328571b0  Cannot read info offset from nt!ObpInfoMaskToOffset
    
    !DevNode ffffb50c332aad20 :
      DeviceInst is "USB\VID_1235&PID_801C\6&df2ee03&0&1"
      ServiceName is "FocusriteUSB"
    
    0: kd> lmDvm FocusriteUSB
    Browse full module list
    start             end                 module name
    fffff80f`ce970000 fffff80f`ce989000   FocusriteUSB T (no symbols)           
        Loaded symbol image file: FocusriteUSB.sys
        Image path: \SystemRoot\System32\drivers\FocusriteUSB.sys
        Image name: FocusriteUSB.sys
        Browse all global symbols  functions  data
        Timestamp:        Tue Jan  9 06:47:56 2018 (5A54D61C)
        CheckSum:         00022425
        ImageSize:        00019000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
        Information from resource tables:
    I've seen that driver show up recently for other people having 0x9F bugchecks. The version on your system doesn't look terribly old but I'd suggest checking the product support site to see if there's a newer version available for Windows 10. If there isn't a newer driver available I'd suggest trying a different USB port. I can't tell what you have on your system but sometimes USB devices work more reliably when connected to Intel USB ports rather than other 3rd party USB ports.

    Are you intentionally not upgrading Windows 10 beyond 1709?
    Thanks for posting, really appreciate it. Originally I tried downgrading with a clean install to 1709 because with 1803 I was getting the same BSOD and it seemed to happen only when I had my xbox 360 wireless receiver plugged. I would definitely believe the Focusrite driver could be causing it. I'm going to keep it unplugged and see if I get any BSOD in the next 24 hours.
      My Computer


  4. Posts : 207
    Windows 10 Pro
       #4

    Please do let us know how it goes.
      My Computer


 

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

Designer Media Ltd
All times are GMT -5. The time now is 06:36.
Find Us




Windows 10 Forums