 auggyPremium,Mod
join:2001-12-24
Brockville, ON
kudos:15
Microsoft Help
| reply to mm
Re: USB 3 hub causing BSOD's The minidump file shows a CLOCK_WATCHDOG_TIMEOUT (101) stop error from a "hung processor":
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003165180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.
Are you over-clocking the processor?
If so, adding the hub with the processor over-clocked may somehow cause the processor to hang. |
|
 mmI Did It My WayPremium
join:2001-04-07
Summerville, SC
 ·Time Warner Cable
 ·VoicePulse
| said by auggy:The minidump file shows a CLOCK_WATCHDOG_TIMEOUT (101) stop error from a "hung processor":
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003165180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.
Are you over-clocking the processor?
If so, adding the hub with the processor over-clocked may somehow cause the processor to hang.
Nothing is overclocked. |
|
auggyPremium,Mod
join:2001-12-24
Brockville, ON
kudos:15 Host:
Microsoft Help
| Can you provide any more minidump files to see if the error is consistent?
The error is usually hardware related but can sometimes be driver related.
The vmusb.sys, which is a VMware driver may be involved in the crash.
Also, can you see if the same error occurs in Safe Mode? |
|
|
|
 koitsuPremium,MVM
join:2002-07-16
Mountain View, CA
kudos:19 | reply to auggy
Overclocking a CPU would not cause this specific error.
This problem is indicative of either a) a driver that is doing something incredibly broken/wrong (holding clock timer interrupt in suspended state too long), b) a BIOS/UEFI bug of some sort (yep really, could pertain to APIC interrupt configuration), or c) a power saving mode exhibited by the chip (or OS) in which the chip never actually recovers from this PM state in certain situations.
If he had a bad CPU or a "wonky" CPU (i.e. overclocking + overheating), he'd be seeing this behaviour randomly throughout normal operation -- in this case he only sees it when removing a device from a hub, where the hub is attached to a USB 3.0 port driven by the on-board Asmedia USB controller.
One thing I can recommend trying would be to uncheck the checkbox in Windows for the related USB devices (the root hub (Asmedia chip) as well as the USB 3.0 hub itself) "power saving" modes. Windows has never made it easy to figure out the USB topology (what's connected to what), so you may have to try unchecking that on every USB-related device.
If that provides no relief, Asus is the only company that can provide a fix (especially if it's either (a) or (b) listed above).
--
Making life hard for others since 1977.
I speak for myself and not my employer/affiliates of my employer. |
|
