Question BSOD usbhub.sys ?

[laptop_pk]

I've been trying to resolve this BSOD, I've updated BIOS, updated Windows 10, checked drivers, rolled one back, turned off power control to USB, turned on maximum performance in all settings etc. Still getting BSOD with this same error a few times per day, no specific time, sometimes it's while using others when it first turns on. Here's the windmp file

Spoiler: Dump file log

******************************************************************************

* *

* 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: ffffd78fb35ae060, Physical Device Object of the stack

Arg3: ffffba053be37ba0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack

Arg4: ffffd78fb85f4a20, The blocked IRP



Debugging Details:

------------------





KEY_VALUES_STRING: 1



Key : Analysis.CPU.mSec

Value: 5046



Key : Analysis.Elapsed.mSec

Value: 5259



Key : Analysis.IO.Other.Mb

Value: 0



Key : Analysis.IO.Read.Mb

Value: 0



Key : Analysis.IO.Write.Mb

Value: 2



Key : Analysis.Init.CPU.mSec

Value: 1843



Key : Analysis.Init.Elapsed.mSec

Value: 31828



Key : Analysis.Memory.CommitPeak.Mb

Value: 162



Key : Bugcheck.Code.KiBugCheckData

Value: 0x9f



Key : Bugcheck.Code.LegacyAPI

Value: 0x9f



Key : Failure.Bucket

Value: 0x9F_3_IMAGE_usbhub.sys



Key : Failure.Hash

Value: {6e67f518-0887-9d66-a512-212f24e07d60}



Key : Hypervisor.Enlightenments.Value

Value: 0



Key : Hypervisor.Enlightenments.ValueHex

Value: 0



Key : Hypervisor.Flags.AnyHypervisorPresent

Value: 0



Key : Hypervisor.Flags.ApicEnlightened

Value: 0



Key : Hypervisor.Flags.ApicVirtualizationAvailable

Value: 0



Key : Hypervisor.Flags.AsyncMemoryHint

Value: 0



Key : Hypervisor.Flags.CoreSchedulerRequested

Value: 0



Key : Hypervisor.Flags.CpuManager

Value: 0



Key : Hypervisor.Flags.DeprecateAutoEoi

Value: 0



Key : Hypervisor.Flags.DynamicCpuDisabled

Value: 0



Key : Hypervisor.Flags.Epf

Value: 0



Key : Hypervisor.Flags.ExtendedProcessorMasks

Value: 0



Key : Hypervisor.Flags.HardwareMbecAvailable

Value: 0



Key : Hypervisor.Flags.MaxBankNumber

Value: 0



Key : Hypervisor.Flags.MemoryZeroingControl

Value: 0



Key : Hypervisor.Flags.NoExtendedRangeFlush

Value: 0



Key : Hypervisor.Flags.NoNonArchCoreSharing

Value: 0



Key : Hypervisor.Flags.Phase0InitDone

Value: 0



Key : Hypervisor.Flags.PowerSchedulerQos

Value: 0



Key : Hypervisor.Flags.RootScheduler

Value: 0



Key : Hypervisor.Flags.SynicAvailable

Value: 0



Key : Hypervisor.Flags.UseQpcBias

Value: 0



Key : Hypervisor.Flags.Value

Value: 0



Key : Hypervisor.Flags.ValueHex

Value: 0



Key : Hypervisor.Flags.VpAssistPage

Value: 0



Key : Hypervisor.Flags.VsmAvailable

Value: 0



Key : Hypervisor.RootFlags.AccessStats

Value: 0



Key : Hypervisor.RootFlags.CrashdumpEnlightened

Value: 0



Key : Hypervisor.RootFlags.CreateVirtualProcessor

Value: 0



Key : Hypervisor.RootFlags.DisableHyperthreading

Value: 0



Key : Hypervisor.RootFlags.HostTimelineSync

Value: 0



Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled

Value: 0



Key : Hypervisor.RootFlags.IsHyperV

Value: 0



Key : Hypervisor.RootFlags.LivedumpEnlightened

Value: 0



Key : Hypervisor.RootFlags.MapDeviceInterrupt

Value: 0



Key : Hypervisor.RootFlags.MceEnlightened

Value: 0



Key : Hypervisor.RootFlags.Nested

Value: 0



Key : Hypervisor.RootFlags.StartLogicalProcessor

Value: 0



Key : Hypervisor.RootFlags.Value

Value: 0



Key : Hypervisor.RootFlags.ValueHex

Value: 0



Key : SecureKernel.HalpHvciEnabled

Value: 0



Key : WER.OS.Branch

Value: vb_release



Key : WER.OS.Version

Value: 10.0.19041.1





BUGCHECK_CODE: 9f



BUGCHECK_P1: 3



BUGCHECK_P2: ffffd78fb35ae060



BUGCHECK_P3: ffffba053be37ba0



BUGCHECK_P4: ffffd78fb85f4a20



FILE_IN_CAB: MEMORY.DMP



DRVPOWERSTATE_SUBCODE: 3



DRIVER_OBJECT: ffffd78fb26dfe40



IMAGE_NAME: usbhub.sys



MODULE_NAME: usbhub



FAULTING_MODULE: fffff80482f70000 usbhub



BLACKBOXBSD: 1 (!blackboxbsd)





BLACKBOXNTFS: 1 (!blackboxntfs)





BLACKBOXPNP: 1 (!blackboxpnp)





BLACKBOXWINLOGON: 1



PROCESS_NAME: svchost.exe



DPC_STACK_BASE: FFFFBA053BE37FB0



STACK_TEXT:

ffffba05`3be37b68 fffff804`707657d7 : 00000000`0000009f 00000000`00000003 ffffd78f`b35ae060 ffffba05`3be37ba0 : nt!KeBugCheckEx

ffffba05`3be37b70 fffff804`707656f1 : ffffd78f`b2743c80 00000000`00000000 00000000`00000000 00000000`0005ac33 : nt!PopIrpWatchdogBugcheck+0xdf

ffffba05`3be37be0 fffff804`704c1cc2 : ffffd78f`b2743cb8 ffffe781`84e80180 ffffba05`3be37e68 ffffe781`84e80180 : nt!PopIrpWatchdog+0x31

ffffba05`3be37c30 fffff804`704c0d3d : ffffe781`84e80180 81ce7368`00000000 00000000`00000008 00000000`0005ac33 : nt!KiProcessExpiredTimerList+0x172

ffffba05`3be37d20 fffff804`70605d75 : 587aa12d`af358308 ffffe781`84e80180 ffffd78f`ac2c65a0 00000000`00000001 : nt!KiRetireDpcList+0x5dd

ffffba05`3be37fb0 fffff804`70605b60 : fffff804`705f97a0 fffff804`705251fa 0000005f`9c57e8b0 000001b0`2cbeb280 : nt!KxRetireDpcList+0x5

ffffba05`3ccdfa80 fffff804`706052d5 : 00000000`00000001 fffff804`705fff61 00000000`00000008 ffffd78f`00000001 : nt!KiDispatchInterruptContinue

ffffba05`3ccdfab0 fffff804`705fff61 : 00000000`00000008 ffffd78f`00000001 ffffba05`3ccdfb40 ffffd78f`0000104c : nt!KiDpcInterruptBypass+0x25

ffffba05`3ccdfac0 00007ffc`5b557bf8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0xb1

0000005f`9c57e210 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`5b557bf8





IMAGE_VERSION: 10.0.19041.3636



STACK_COMMAND: .cxr; .ecxr ; kb



FAILURE_BUCKET_ID: 0x9F_3_IMAGE_usbhub.sys



OS_VERSION: 10.0.19041.1



BUILDLAB_STR: vb_release



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



FAILURE_ID_HASH: {6e67f518-0887-9d66-a512-212f24e07d60}



Followup: MachineOwner

 

[laptop_pk]

don't recall specifically, there was 4-5 intel drivers. I replaced all USB ones I could find which didn't resolve anything, then i ran the bluescreen view and found the ntoskml.exe errors 3 of them aligned with the dmp file dates, so I did the intel drivers since this led me to believe it was windows and not hardware, they were numbered, 3, 4 and 1 i believe, but the 1 aligned with one not numbered on the device manager. Once that was done it immediately stopped the BSODs and has worked flawlessly since.

 

[ubuysa]

You'd need to upload the actual dump, not just the !analyze -v output. I can identify the device from the dump.

I would not be happy installing drivers for Intel devices from DriverEasy if the Intel Driver and Support Assistant didn't find any. I still advise against using DriverEasy at all...

 

[laptop_pk]

You'd need to upload the actual dump, not just the !analyze -v output. I can identify the device from the dump.

I would not be happy installing drivers for Intel devices from DriverEasy if the Intel Driver and Support Assistant didn't find any. I still advise against using DriverEasy at all...

Which doesn't make any sense, all the feedback received here pointed me to intel and hp which didn't find the problem, I found and reported the problem and the advice is still go back to the place that didn't work. How does that make any sense?

 

[ubuysa]

Which doesn't make any sense, all the feedback received here pointed me to intel and hp which didn't find the problem, I found and reported the problem and the advice is still go back to the place that didn't work. How does that make any sense?

If Intel and HP don't have drivers for an Intel device in an HP laptop then what confidence do you have the some unknown third-party sourced driver is going to be safe , or even right? That it doesn't mean it's the proper driver. I would be researching the device in question and pestering Intel and HP - unless of course it's a device that's no longer supported?

 

[Colif]

curious why op self deleted account before it was finished.

 

[ubuysa]

curious why op self deleted account before it was finished.

Didn't like my answer I guess....

 

[satrow]

Didn't like my answer I guess....

I suspect a shill, "the only thing that fixed it was ... ".

 

[laptop_pk]

Didn't like my answer I guess....

Deleted it because I have no use for it anymore. Reactivated it for you. Computer is fixed, created an account to get help and now it's resolved and working. I answered everyones questions that helped me on what it was, intel drivers not found by the intel tool. Based on the comments seems to me they aren't supporting the device any longer and one of the windows 10 updates installed in the last year broke something.

 

[ubuysa]

Based on the comments seems to me they aren't supporting the device any longer and one of the windows 10 updates installed in the last year broke something.

That's certainly a possibility, but that would mean that whatever driver you are using may not be entirely kosher. You never told us what device it was?

If at all possible I would advise replacing the device with one that is supported, and by Windows 11 because Windows 10 reaches EOL in October 2025. You might think I'm just being pedantic for the sake of it but I am genuinely trying to give you good advice. You leave yourself open to all sorts of malware using unknown drivers to run hardware that's no longer supported - if that is the case of course.

 

[laptop_pk]

That's certainly a possibility, but that would mean that whatever driver you are using may not be entirely kosher. You never told us what device it was?

If at all possible I would advise replacing the device with one that is supported, and by Windows 11 because Windows 10 reaches EOL in October 2025. You might think I'm just being pedantic for the sake of it but I am genuinely trying to give you good advice. You leave yourself open to all sorts of malware using unknown drivers to run hardware that's no longer supported - if that is the case of course.

Sorry, missed that, it was in an earlier post. I appreciate the help, was just at a stopping point, nothing worked and I was going in circles for a few weeks. Device info below. It can't take W11 its an older computer and used as a spare for kids to play games on.

HP EliteBook Folio 1040 G2
4GB RAM
Intel Core i5-5200U
Win 10 version 22H2 - Build: 19041.3930 - All updates applied

 

[Colif]

Driver easy is the last thing I would trust to get the right drivers. 3rd party driver updaters can and will install the wrong drivers, I learned the hard way myself.

usbhub.sys is part of windows, anyone thought to run sfc/dism?

right click start button

choose powershell (admin)

copy/paste this command into window:

Repair-WindowsImage -Online -RestoreHealth

and press enter

Then type SFC /scannow

and press enter

Restart PC if SFC fixes any files as some fixes require a restart to be implemented

First command repairs the files SFC uses to clean files, and SFC fixes system files

SFC = System File Checker. First command runs DISM - https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/what-is-dism?view=windows-11

might not help but worth a try.

drivers running during a recent crash

Dec 09 2015	nfcgpiomanager.sys
May 10 2016	RTKVHD64.sys	Realtek Audio System driver https://www.realtek.com/en/
Jul 21 2016	WirelessButtonDriver64.sys	HP Wireless Button Driver http://www.hp.com/
Nov 17 2016	TeeDriverW8x64.sys	Intel Management Engine Interface driver https://downloadcenter.intel.com/
Jan 25 2017	iaStorA.sys	Intel SATA Storage Device RAID Controller
May 09 2018	RtsPer.sys	Realtek RTS PCIE Reader driver https://www.realtek.com/en/
Jul 10 2018	Smb_driver_Intel.sys	Synaptics SMBus driver http://www.synaptics.com/
Jul 10 2018	SynTP.sys	Synaptics TouchPad Driver http://www.synaptics.com/
Sep 03 2018	Netwtw02.sys
May 13 2019	HpqKbFiltr.sys	HP Compaq Keyboard Filter driver
Jan 22 2020	igdkmd64.sys	Intel HD graphics driver
Jul 10 2020	ibtusb.sys	Intel(R) Wireless Bluetooth(R) Filter driver (Intel Corporation)
Sep 30 2020	e1d68x64.sys	Intel(R) Gigabit Adapter driver

Not sure what the top one is
Netwtw02.sys - Intel Ethernet drivers

If we unsure what new drivers are there
Can you download and run Driverview - http://www.nirsoft.net/utils/driverview.html

All it does is looks at drivers installed; it won't install any (this is intentional as 3rd party driver updaters often get it wrong)

When you run it, go into view tab and set it to hide all Microsoft drivers, will make list shorter.

Can you take a screenshot from (and including)Driver name to (and including)Creation date.

upload to a file sharing website and show link.

 

[laptop_pk]

That's certainly a possibility, but that would mean that whatever driver you are using may not be entirely kosher. You never told us what device it was?

If at all possible I would advise replacing the device with one that is supported, and by Windows 11 because Windows 10 reaches EOL in October 2025. You might think I'm just being pedantic for the sake of it but I am genuinely trying to give you good advice. You leave yourself open to all sorts of malware using unknown drivers to run hardware that's no longer supported - if that is the case of course.

It started again. I ran bluescreenviewer and it says the driver is ntoskrnl.exe causing the crash. Here's the dmp and a screen shot of what bsviewer is showing. Also, ran the SFC scan multiple times finds nothing.

BSOD file dmp and bsv.zip

 

[cwsink]

That dump file shows a power management problem involving a fingerprint reader device. I believe this is the Windows 10 driver/software installer for that device from the US HP support page for your laptop. If you're relying on HP Support Assistant to find and install drivers for your laptop, I doubt it's kept up to date past a few years. I've found I need to go to the product support page and manually download and install drivers for older HP devices.

 

[laptop_pk]

That dump file shows a power management problem involving a fingerprint reader device. I believe this is the Windows 10 driver/software installer for that device from the US HP support page for your laptop. If you're relying on HP Support Assistant to find and install drivers for your laptop, I doubt it's kept up to date past a few years. I've found I need to go to the product support page and manually download and install drivers for older HP devices.

Thank you, I hadn't received that feedback yet and didn't know that. I booted into BIOS and turned off fingerprint reader, I don't know if it worked, it's never been used so no need to try and resolve the issue. It hasn't had a BSOD again since the latest one i uploaded, will have to watch it see what happens.

 

[laptop_pk]

That dump file shows a power management problem involving a fingerprint reader device. I believe this is the Windows 10 driver/software installer for that device from the US HP support page for your laptop. If you're relying on HP Support Assistant to find and install drivers for your laptop, I doubt it's kept up to date past a few years. I've found I need to go to the product support page and manually download and install drivers for older HP devices.

Just got another one two days ago, so turning off the finger print sensor didn't work. Any other suggestions? Should I keep adding drivereasy drivers at this point or is there any other option to fix whatever driver is causing this?

New dmb and bsv

BSOD 2_13_dmp and bsv.zip

 

[cwsink]

I would not use 3rd party driver finder utilities. They are as likely as not to cause problems.

The latest crash is another power management issue where an IRP is getting stuck in a USB driver stack. The device being blamed is a USB device which has a vendor ID of 0424 and product ID of 2532 which shows this at devicehunt.com. So, it's not clear exactly what it is but it's using a Microsoft driver (WinUSB.sys) which makes me suspect it's a USB port or hub driver that probably has a more targeted driver from the laptop product support page. Have you manually gone through the driver installers on the product support page? Not run the tool to see what it finds but manually go through and download driver installers and run the installers.

What does Device Manager look like on your computer? Do you have Unknown devices showing in any nodes? If so, the drivers for those likely need to be manually downloaded from HP and installed. It can be difficult to figure out which installer is for which device but is something I find myself needing to do with older HP devices, unfortunately.

 

[laptop_pk]

I would not use 3rd party driver finder utilities. They are as likely as not to cause problems.

The latest crash is another power management issue where an IRP is getting stuck in a USB driver stack. The device being blamed is a USB device which has a vendor ID of 0424 and product ID of 2532 which shows this at devicehunt.com. So, it's not clear exactly what it is but it's using a Microsoft driver (WinUSB.sys) which makes me suspect it's a USB port or hub driver that probably has a more targeted driver from the laptop product support page. Have you manually gone through the driver installers on the product support page? Not run the tool to see what it finds but manually go through and download driver installers and run the installers.

What does Device Manager look like on your computer? Do you have Unknown devices showing in any nodes? If so, the drivers for those likely need to be manually downloaded from HP and installed. It can be difficult to figure out which installer is for which device but is something I find myself needing to do with older HP devices, unfortunately.

This was helpful info, thank you! I just ran through all usb stuff in the device manager and found this that matched. I attached screen shots showing it. I then deleted the device and rebooted. When i did i got a notification that Atmel maXTouch Digitizer is set up and ready to use. I now have a working touch screen I didn't even know the laptop had. Could this have been causing the BSOD since the hardware IDs matched? Its working now and I'll monitor it for crashes. Let me know what you think. Thank you

USB Device Info.zip

 

[cwsink]

Power management in modern computers is rather complex. Everything must do it correctly for it to work properly. So, if you have a device in the system that needs to perform power management functions but isn't properly installed then you're likely to have problems. Laptops in particular often need customized drivers and the generic Microsoft drivers, for example, may not include all of the functionality needed for the device to work properly.

The screenshot is from before you deleted the device and restarted?

 

[laptop_pk]

Power management in modern computers is rather complex. Everything must do it correctly for it to work properly. So, if you have a device in the system that needs to perform power management functions but isn't properly installed then you're likely to have problems. Laptops in particular often need customized drivers and the generic Microsoft drivers, for example, may not include all of the functionality needed for the device to work properly.

The screenshot is from before you deleted the device and restarted?

Yes that was how I found it in device manager, there wasn't an exclamation point or anything flagging it to look, i was just going down the list looking for the device id you gave me.

 

[cwsink]

Is there now a device in Device Manager with that ID but using a driver other than WinUSB.sys?

 

[laptop_pk]

Is there now a device in Device Manager with that ID but using a driver other than WinUSB.sys?

Interesting, the touch is no longer working again and under device manager it's back to a usb hub for the id and device, but in a diff spot, it is now at the bottom where the other usb hub is but its not showing not installed, its showing fine. I'm guessing if if delete it then it will reinstall correctly again, but I don't know what caused it to move. Computer has only been in sleep mode, no reboots and no BSOD.