It crashes pretty reliably the first time I turn on the computer. But generally not reliably or at all after that first reboot. The stop code I'm getting is the 0x101 which in you BSOD list is described as: STOP 0x00000101: CLOCK_WATCHDOG_TIMEOUT (go to top of page) Usual causes:
, BIOS bug, hardware defect (see Significant Posts section below) Knowledge Base Articles:
KB 955076 Stop error message on a Windows Vista or Windows Server 2008-based computer that has multiple processors installed: "STOP: 0x00000101 CLOCK_WATCHDOG_TIMEOUT"
Significant Posts: http://www.sevenforums.com/crashes-debugging/35427-win-7-clock-interrupt-bsod-101-error.html#post356791
These types of error messages are relatively simple, from a certain viewpoint: as frequently happens during normal processing, one core (processor) attempted to get the attention of another core, in order to synchronise their activites with respect to an operation that requires processor coordination. Described using "official" terminology: "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."
The trigger for the crash is the "sender/requestor" processor going "wtf? why is there still no response after almost half a second?!?" Those inter-processor interrupts (IPIs) are some of the most critical activity imaginable, and an unrequited IPI is absolutely lethal - hence the crash.
AMD procs had known issues which manifested themselves in this manner under Vista and Windows 7. There were/are many possible problem permutations, some solved through BIOS updates, and some necessitating fiddling with the "Translation Lookaside Buffer" (TLB), as per torrentg's suggestion to look up 0x101 and AMD and TLB.
Your real aim is to give yourself the best possible chance of discovering a software
cause for the target processor to go unresponsive, and thereby avoid the most obvious conclusion - that the processor is periodically unresponsive because of hardware-level defects
I can confidently tell you that the browsers, apps, and games cannot be the root cause of this problem, even though I don't doubt your observation that the operation of certain software seems to more easily trigger the crash. What you're looking for will be in one of the following categories:
a) BIOS bug
b) a driver whose activity is causing the target processor to lock up
c) a hardware defect (temperature, voltage, dust, RFI, outright borkedness...)
- H2SO4 WinDbg Help File Entry:
The CLOCK_WATCHDOG_TIMEOUT bug check has a value of 0x00000101. This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. Parameters
The following parameters are displayed on the blue screen.
ParameterDescription1Clock interrupt time-out interval, in nominal clock ticks 203The address of the processor control block (PRCB) for the unresponsive processor 40 Cause
The specified processor is not processing interrupts. Typically, this occurs when the processor is nonresponsive or is deadlocked. WinDbg Output Example:
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.
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002f64180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.
At least if it turns out to be a hardware problem, the computer is still under warranty.
My next step is to power down the computer and restart in safe mode to see if it happens there. Then I'll try the driver verify.
I really appreciate all the help in tracking this down. I'd like to figure this out.