Blue Screen UsbHub3.sys DRIVER_POWER_STATE_FAILURE (9f) on brand new Acer Nitro 5 AN515-54 NH

Pawel82
Pawel82 Member Posts: 5

Tinkerer

Hi,

A few days ago i bought brand new Acer Nitro 5 AN515-54 NH. I installed the latest Windows 10 Pro, then all the drivers from Acer website, the newest bios and latest Nvidia drivers from nvidia website. I also installed the latest 3D Mark, relal temp, and occt to check component temperatures under stress. I turned on the 3d mark a couple of times, (occt only for temp monitoring) all right and great results, not hight temperatures, but after that, (3D Mark closed) on iddle, leaving the laptop turned on for an hour, I saw a login screen. I guessed a reset took place, and found data for the blue screen. What is the cause?

I seems to be: DRIVER_POWER_STATE_FAILURE (9f) related to UsbHub3.sys

Memory dump:

https://1drv.ms/u/s!AgoDJjna9sBfgZJOoua2svV9rVGuaQ?e=U3r5SB


Microsoft (R) Windows Debugger Version 10.0.19041.685 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff804`32200000 PsLoadedModuleList = 0xfffff804`32e2a4b0
Debug session time: Sat Feb  6 22:39:15.633 2021 (UTC + 1:00)
System Uptime: 0 days 1:12:09.365
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......................
Loading User Symbols

Loading unloaded module list
...............................
For analysis of this file, run !analyze -v
4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffbd898861e720, Physical Device Object of the stack
Arg3: fffff307cfe5f750, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffbd89900999e0, The blocked IRP

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 3

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-P4RH87M

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 22

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 75

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffbd898861e720

BUGCHECK_P3: fffff307cfe5f750

BUGCHECK_P4: ffffbd89900999e0

DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  UsbHub3.sys

MODULE_NAME: UsbHub3

FAULTING_MODULE: fffff80436ac0000 UsbHub3

BLACKBOXACPI: 1 (!blackboxacpi)


BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

STACK_TEXT:  
fffff307`cfe5f718 fffff804`3275f487 : 00000000`0000009f 00000000`00000003 ffffbd89`8861e720 fffff307`cfe5f750 : nt!KeBugCheckEx
fffff307`cfe5f720 fffff804`3275f3a1 : ffffbd89`8d9de6b0 fffff804`324735d6 00000000`00000000 00000000`00028538 : nt!PopIrpWatchdogBugcheck+0xdf
fffff307`cfe5f790 fffff804`32444f12 : ffffbd89`8d9de6e8 ffffe200`8fd60180 fffff307`cfe5fa18 00000000`00000000 : nt!PopIrpWatchdog+0x31
fffff307`cfe5f7e0 fffff804`32406eed : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00028538 : nt!KiProcessExpiredTimerList+0x172
fffff307`cfe5f8d0 fffff804`325f95ee : ffffffff`00000000 ffffe200`8fd60180 ffffe200`8fd6b240 ffffbd89`8d4a5280 : nt!KiRetireDpcList+0x5dd
fffff307`cfe5fb60 00000000`00000000 : fffff307`cfe60000 fffff307`cfe59000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


IMAGE_VERSION:  10.0.19041.264

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x9F_3_ACPI_IMAGE_UsbHub3.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {047903fc-cc2a-99ae-aec6-814c458e15ac}

Followup:     MachineOwner
---------

4: kd> lmvm UsbHub3
Browse full module list
start             end                 module name
fffff804`36ac0000 fffff804`36b63000   UsbHub3    (pdb symbols)          C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\sym\usbhub3.pdb\FEB0212F8C4FD77DDEEBF0678FB00EA21\usbhub3.pdb
    Loaded symbol image file: UsbHub3.sys
    Image path: \SystemRoot\System32\drivers\UsbHub3.sys
    Image name: UsbHub3.sys
    Browse all global symbols  functions  data
    Image was built with /Brepro flag.
    Timestamp:        FDA30E83 (This is a reproducible build file hash, not a timestamp)
    CheckSum:         000AC346
    ImageSize:        000A3000
    File version:     10.0.19041.264
    Product version:  10.0.19041.264
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    Information from resource tables:
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     usbhub3.sys
        OriginalFilename: usbhub3.sys
        ProductVersion:   10.0.19041.264
        FileVersion:      10.0.19041.264 (WinBuild.160101.0800)
        FileDescription:  USB3 HUB Driver
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
4: kd> !blackboxacpi
4: kd> !blackboxbsd
Version: 176
Product type: 1

Auto advanced boot: FALSE
Advanced boot menu timeout: 30
Last boot succeeded: TRUE
Last boot shutdown: FALSE
Sleep in progrees: FALSE

Power button timestamp: 0
System running: TRUE
Connected standby in progress: FALSE
User shutdown in progress: FALSE
System shutdown in progress: FALSE
Sleep in progress: 0
Connected standby scenario instance id: 0
Connected standby entry reason: 0
Connected standby exit reason: 0
System sleep transitions to on: 0
Last reference time: 0x1d6fcccec19e032
Last reference time checksum: 0x48b7ddf6
Last update boot id: 16

Boot attempt count: 1
Last boot checkpoint: TRUE
Checksum: 0x7f
Last boot id: 16
Last successful shutdown boot id: 15
Last reported abnormal shutdown boot id: 15

Error info boot id: 0
Error info repeat count: 0
Error info other error count: 0
Error info code: 0
Error info other error count: 0

Power button last press time: 0
Power button cumulative press count: 0
Power button last press boot id: 0
Power button last power watchdog stage: 0
Power button watchdog armed: FALSE
Power button shutdown in progress: FALSE
Power button last release time: 0
Power button cumulative release count: 0
Power button last release boot id: 0
Power button error count: 0
Power button current connected standby phase: 0
Power button transition latest checkpoint id: 0
Power button transition latest checkpoint type: 0
Power button transition latest checkpoint sequence number: 0
4: kd> !blackboxntfs

NTFS Blackbox Data

0 Slow I/O Timeout Records Found
0 Oplock Break Timeout Records Found
4: kd> !blackboxpnp
    PnpActivityId      : {00000000-0000-0000-0000-000000000000}
    PnpActivityTime    : 132571169140230880
    PnpEventInformation: 3
    PnpEventInProgress : 0
    PnpProblemCode     : 24
    PnpVetoType        : 0
    DeviceId           : SW\{96E080C7-143C-11D1-B40F-00A0C9223196}\{3C0D501A-140B-11D1-B40F-00A0C9223196}
    VetoString         : 

 

Answers

  • AnhEZ28
    AnhEZ28 ACE, Member Posts: 4,464 Pathfinder
    1. Make sure that your windows is up to date
    2. Your BIOS is on version 1.32
    3. You can try to update both Nvidia and Intel GPU drivers.

    Please remember to include @AnhEZ28 when you want to reply back to my comment so that I can check your response.
    Thank you and have a nice day!