No issues in ages, now two BSOD within half an hour

Hi BSOD geeks.

My whole Windows 10 experience has been almost problem free since first Tech Preview October 2014, only had a few crashes which have had logical reasons behind them.

That being said today afternoon I had two times BSOD within half an hour for which I can not find any logical reason. Something common: both BSOD occurred when I was browsing forums with Edge on display 1 (laptop's internal display), using Hyper-V virtual machine to create a new deployment image (host and vm EN-GB PRO build 14971) on display 2 (connected with HDMI), and running Kodi to watch videos on display 3 (wireless Miracast display).

Restarting after first BSOD I opened the same programs, doing the same stuff, so background to both BSOD is identical.

Laptop, Asus X751LD instead of what's told in my system specs, quite low end. DM Log Collector file attached.

Thanks in advance :)

Kari

Hi Kari,

Unfortunately the only useful I can get is that there is a power issue with a driver using a standard USB driver.
This is usually caused by USB devices rather than the USB drivers from the laptop, but I would suggest to check both for driver updates :)

Code:

27-Nov-2016 12:54    Windows Error Reporting    Fault bucket 0x9F_3_IMAGE_UsbHub3.sys, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 6f4d4aec-3164-4e9b-8b30-a047936e49a9

Problem signature:
P1: 9f
P2: 3
P3: ffffc785a1b12530
P4: ffffda012b72dc60
P5: ffffc785a1ff2a60
P6: 10_0_14971
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\112716-27562-01.dmp
\\?\C:\Windows\Temp\WER-116578-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2AC5.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9f_b5f2fe417b17ebfe7affe817740963ce1f15_00000000_cab_0ee7cc37

Analysis symbol: 
Rechecking for solution: 0
Report ID: 50083960-12e8-43b0-9f6e-ee2b7edabdc5
Report Status: 268435456
Hashed bucket:
27-Nov-2016 12:27    Windows Error Reporting    Fault bucket 0x9F_3_UsbHub3!HUBMISC_WaitForSignal, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0ff7a269-0074-4cd5-b22b-a967fb0b22ee

Problem signature:
P1: 9f
P2: 3
P3: ffffc2035cb3b5f0
P4: fffff803747b1c60
P5: ffffc2036a849af0
P6: 10_0_14971
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\112716-47046-01.dmp
\\?\C:\Windows\Temp\WER-92390-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9E73.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9f_b9152be8957134a8e08ed557c9ff3880b05a68_00000000_cab_2264acc3

Analysis symbol: 
Rechecking for solution: 0
Report ID: b60b7e5a-aab0-43fc-a5a0-dd91187e1af6
Report Status: 268435456
Hashed bucket:

Thanks @Martijn.

Any indicator about if this is USB ports on laptop itself or the external USB hub? Is the UsbHub.sys here indicating that it's the hub, or is word hub here used in wider context so that it could also mean internal USB ports?

The thing is I only have two USB3 and one USB2 ports, but I need USB connection for two USB3 and two USB2 devices. I have solved this by attaching a USB2 hub to only available USB2 port, connecting both USB2 devices on this hub.

Windows TP has no public symbols available, this causes that I'm unable to answer your question properly. Anything I try to get more information results in errors caused by lack of symbols.
To answer your question as best as possible, there is no indication to say if it is the USB ports on the laptop or if it is the external USB hub. The WER's posted are currently better than the dumps what says a lot IMO as I usually find WER's not more useful than 25-50% of what a minidump can tell.

USBHub.sys as you know is a Windows driver that is being used between the communication of the USB devices, the USB ports and Windows.
Actually it says here that this driver is a default HUB driver for USB, so I may be a little confused with what Windows Internals says, but this may mean that the external USB HUB is the cause.

Thanks Martijn, very much appreciated. I will mark this as solved.

Kari

You're welcome :)