Welcome
If you are overclocking any hardware, STOP. Reset any changed values back to default.
Be sure to update your BIOS. See if the problem goes.
Code:
BIOS-versie/datum Phoenix Technologies, LTD 6.00 PG, 9/01/2009
For an insight, go through:
STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {31, 0, fffff88002d63180, 2}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002d63180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0. Let us know your feedback