BSOD DRIVER_POWER_STATE_FAILURE (9f) usbhub.sys

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Mario Ceres, Mar 3, 2014.

  1. Mario Ceres

    Mario Ceres New Member

    Joined:
    Mar 3, 2014
    Messages:
    9
    Likes Received:
    0
    Need your help to find the problem of my BSOD, it happens when i leave my computer unattended for a while and it locks, when I try to log back in the BSOD occurs.
     

    Attached Files:

  2. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,818
    Likes Received:
    1,565
  3. Mario Ceres

    Mario Ceres New Member

    Joined:
    Mar 3, 2014
    Messages:
    9
    Likes Received:
    0
    Here is the dump file
     

    Attached Files:

  4. badrobot

    badrobot Senior Member

    Joined:
    Jun 14, 2012
    Messages:
    1,020
    Likes Received:
    102
    It happens to me too. I just put the power saving modes to "Never" and it goes away. Easy temporary fix because I don't mind my PC not going to sleep. But I'll watch this thread for the right solution.
     
    #4 badrobot, Mar 3, 2014
    Last edited: Mar 3, 2014
  5. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,818
    Likes Received:
    1,565
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa800a6b1440, fffff80000b9c3d8, fffffa80107e2010}
    Probably caused by : usbhub.sys
    
    Followup: MachineOwner
    
    Hi,
    with only one dump file it's difficult to get something concrete but hopefully your driver stack will tell us more:

    Several of your drivers have later versions on the website:
    http://www.dell.com/support/drivers/uk/en/ukbsdt1/Product/optiplex-9020-aio

    You also have some quite old third party drivers:
    aksifdh.sys Sun Jul 20 07:40:52 2008: Alladin eToken security see if it's possible to update this driver or if you don't use it anymore please remove:
    http://www.aladdin.co.il/support/etoken_download.aspx

    DamewareMini.sys Sun Mar 16 18:42:28 2008: Again as above see if this driver can be updated:
    http://www.dameware.com/

    dwvkbd64.sys Wed Apr 11 22:22:37 2007: Virtual keyboard driver.Try to update as above (or remove):
    http://www.dameware.com/

    Check on those driver updates and then find command prompt in the sart menu. Right click on it and click 'run as admin'. Type:
    sfc /scannow
    Press enter and await results.

    Normally I would spend longer but I'm off out tonight but will check on your reply on my return..
     
  6. Mario Ceres

    Mario Ceres New Member

    Joined:
    Mar 3, 2014
    Messages:
    9
    Likes Received:
    0
    can a driver that was not loaded at the time of the bsod cause a BSOD? i see that the compute has wdcsam64.sys but is not showing up when looking at the loaded modules in the dump file. I read that the wdcsam64.sys is known to cause BSODs.

    There are multiple computers getting BSODs, some dont have the aksifdh.sys and DamewareMini.sys driver at all, and they have a 2008 version of the dwvkbd64.sys driver.

    Thanks,
     
  7. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,818
    Likes Received:
    1,565
    It's certainly possible. As I said above with only one dump file to work from it's harder to spot multiple instances (obviously) and trends. If you have any further dump files please do send them over.
     
  8. Mario Ceres

    Mario Ceres New Member

    Joined:
    Mar 3, 2014
    Messages:
    9
    Likes Received:
    0
    Here are the rest of the log files. Thanks
     

    Attached Files:

  9. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,818
    Likes Received:
    1,565
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000009F, {4, 258, fffffa8006cd1040, fffff800045d73d0}
    
    *** WARNING: Unable to verify timestamp for IntcDAud.sys
    *** ERROR: Module load completed but symbols could not be loaded for IntcDAud.sys
    Implicit thread is now fffffa80`06cd1040
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : portcls.sys ( portcls!DispatchPnp+3dd )
    
    Followup: MachineOwner
    
    Hi,
    thanks for forwarding the dumps. They were split into two groups with a smattering of others thrown in (causes). The first group pointed to usbhub.sys as the issue which could have something to do with your USB drivers with the second largest group showing ntkrnlmp.exe as the probable cause which basically means a driver is causing an issue ( I noticed that these particular dumps were being produced when the Damewaremini.sys process was running ) Then there are the one or two odd dumps like the one above and two others which blame a driver I couldn't any information on. I will do some more investigating on those. The above dump is pointing to your Intel Audio drivers and win32k.sys. Now sometimes win32k.sys will appear if there is a hardware issue but old bioses and drivers can do the same...

    Checking on your systems website there are later drivers for most of your system (including a bios update):
    http://www.dell.com/support/drivers/us/en/19/Product/optiplex-9020-aio

    Please run a virus scan using the app found here:
    https://www.malwarebytes.org/

    wdcsam64.sys is a Western Digital WDM driver and the 2008 version is known to have bsod issues in windows but I didn't see that driver in the dumps I looked at.

    Did you run the system file checker?

    If after you've updated the above drivers you find your still betting a bsod please download and run the app found here:
    http://www.memtest.org/
     
  10. Mario Ceres

    Mario Ceres New Member

    Joined:
    Mar 3, 2014
    Messages:
    9
    Likes Received:
    0
    i have updated the bios and drivers from Dell's website, so the latest 3 dmp or so will already have the updated drivers and still getting bsod. I have seen other systems BSOD but dont have any Dameware drivers on it yet.
     
  11. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,818
    Likes Received:
    1,565
    Try testing the RAM if you're still getting bsod after updating software,
     
  12. Mario Ceres

    Mario Ceres New Member

    Joined:
    Mar 3, 2014
    Messages:
    9
    Likes Received:
    0
    Memory test and hardware test came back with no errors.
     
  13. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,818
    Likes Received:
    1,565
  14. Mario Ceres

    Mario Ceres New Member

    Joined:
    Mar 3, 2014
    Messages:
    9
    Likes Received:
    0
    I am seeing this on the sfc, could this by why I am seing the BSODs pointing to the usbhub.sys

    Line 5771: 5: Move File: Source = [l:218{109}]"\SystemRoot\WinSxS\Temp\PendingRenames\100d24b0333ecf0103200000e82ec826.$$_inf_usbhub_299dea1039e75d30.cdf-ms", Destination = [l:130{65}]"\SystemRoot\WinSxS\FileMaps\$$_inf_usbhub_299dea1039e75d30.cdf-ms"
    Line 5771: 5: Move File: Source = [l:218{109}]"\SystemRoot\WinSxS\Temp\PendingRenames\100d24b0333ecf0103200000e82ec826.$$_inf_usbhub_299dea1039e75d30.cdf-ms", Destination = [l:130{65}]"\SystemRoot\WinSxS\FileMaps\$$_inf_usbhub_299dea1039e75d30.cdf-ms"
    Line 5772: 6: Move File: Source = [l:228{114}]"\SystemRoot\WinSxS\Temp\PendingRenames\213424b0333ecf0104200000e82ec826.$$_inf_usbhub_0000_1bec33bb3c8ba8f4.cdf-ms", Destination = [l:140{70}]"\SystemRoot\WinSxS\FileMaps\$$_inf_usbhub_0000_1bec33bb3c8ba8f4.cdf-ms"
    Line 5772: 6: Move File: Source = [l:228{114}]"\SystemRoot\WinSxS\Temp\PendingRenames\213424b0333ecf0104200000e82ec826.$$_inf_usbhub_0000_1bec33bb3c8ba8f4.cdf-ms", Destination = [l:140{70}]"\SystemRoot\WinSxS\FileMaps\$$_inf_usbhub_0000_1bec33bb3c8ba8f4.cdf-ms"
    Line 5773: 7: Move File: Source = [l:228{114}]"\SystemRoot\WinSxS\Temp\PendingRenames\984525b0333ecf0105200000e82ec826.$$_inf_usbhub_0409_1bec32773c8babd1.cdf-ms", Destination = [l:140{70}]"\SystemRoot\WinSxS\FileMaps\$$_inf_usbhub_0409_1bec32773c8babd1.cdf-ms"
    Line 5773: 7: Move File: Source = [l:228{114}]"\SystemRoot\WinSxS\Temp\PendingRenames\984525b0333ecf0105200000e82ec826.$$_inf_usbhub_0409_1bec32773c8babd1.cdf-ms", Destination = [l:140{70}]"\SystemRoot\WinSxS\FileMaps\$$_inf_usbhub_0409_1bec32773c8babd1.cdf-ms"
    Line 6549: 2014-03-12 15:46:20, Info CSI 00000293 Ignoring duplicate ownership for directory [l:50{25}]"\??\C:\windows\Inf\usbhub" in component Microsoft-Windows-usbperf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
    Line 6551: 2014-03-12 15:46:20, Info CSI 00000294 Ignoring duplicate ownership for directory [l:60{30}]"\??\C:\windows\Inf\usbhub\0000" in component Microsoft-Windows-usbperf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
    Line 6555: 2014-03-12 15:46:21, Info CSI 00000296 Ignoring duplicate ownership for directory [l:60{30}]"\??\C:\windows\Inf\usbhub\0409" in component Microsoft-Windows-usbperf.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
    Line 6578: 17: Move File: Source = [l:218{109}]"\SystemRoot\WinSxS\Temp\PendingRenames\948aae1f343ecf01cc330000e82ec826.$$_inf_usbhub_299dea1039e75d30.cdf-ms", Destination = [l:130{65}]"\SystemRoot\WinSxS\FileMaps\$$_inf_usbhub_299dea1039e75d30.cdf-ms"
    Line 6578: 17: Move File: Source = [l:218{109}]"\SystemRoot\WinSxS\Temp\PendingRenames\948aae1f343ecf01cc330000e82ec826.$$_inf_usbhub_299dea1039e75d30.cdf-ms", Destination = [l:130{65}]"\SystemRoot\WinSxS\FileMaps\$$_inf_usbhub_299dea1039e75d30.cdf-ms"
    Line 6579: 18: Move File: Source = [l:228{114}]"\SystemRoot\WinSxS\Temp\PendingRenames\a4b1ae1f343ecf01cd330000e82ec826.$$_inf_usbhub_0000_1bec33bb3c8ba8f4.cdf-ms", Destination = [l:140{70}]"\SystemRoot\WinSxS\FileMaps\$$_inf_usbhub_0000_1bec33bb3c8ba8f4.cdf-ms"
    Line 6579: 18: Move File: Source = [l:228{114}]"\SystemRoot\WinSxS\Temp\PendingRenames\a4b1ae1f343ecf01cd330000e82ec826.$$_inf_usbhub_0000_1bec33bb3c8ba8f4.cdf-ms", Destination = [l:140{70}]"\SystemRoot\WinSxS\FileMaps\$$_inf_usbhub_0000_1bec33bb3c8ba8f4.cdf-ms"
    Line 6587: 25: Move File: Source = [l:228{114}]"\SystemRoot\WinSxS\Temp\PendingRenames\746ad01f343ecf01d4330000e82ec826.$$_inf_usbhub_0409_1bec32773c8babd1.cdf-ms", Destination = [l:140{70}]"\SystemRoot\WinSxS\FileMaps\$$_inf_usbhub_0409_1bec32773c8babd1.cdf-ms"
    Line 6587: 25: Move File: Source = [l:228{114}]"\SystemRoot\WinSxS\Temp\PendingRenames\746ad01f343ecf01d4330000e82ec826.$$_inf_usbhub_0409_1bec32773c8babd1.cdf-ms", Destination = [l:140{70}]"\SystemRoot\WinSxS\FileMaps\$$_inf_usbhub_0409_1bec32773c8babd1.cdf-ms"
     
  15. Mario Ceres

    Mario Ceres New Member

    Joined:
    Mar 3, 2014
    Messages:
    9
    Likes Received:
    0
    Do you need the entire log?
     
  16. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,818
    Likes Received:
    1,565
    Yes please.
     
  17. Mario Ceres

    Mario Ceres New Member

    Joined:
    Mar 3, 2014
    Messages:
    9
    Likes Received:
    0
    Here it is.
     

    Attached Files:

  18. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,818
    Likes Received:
    1,565
    I had a look at the log and to be honest I'm by no means an expert but I failed to find anything not repaired. A lot was done it seems but as long as the actual scan ended saying files were repaired then it should be ok.
    Did you run a chkdsk?
    Have you tried changing USB ports and/or cables. If your using a hub check that hasn't become faulty.
     

Share This Page

Loading...