New
#11
You may have a defective CPU, stop any overclocking and follow the steps below
Bugcheck 101 is mainly caused by a defective CPU or outdated BIOS
Details about this bugcheck:
https://www.sevenforums.com/crash-loc...tml#post567135
Win 7 A Clock Interrupt... BSOD (101 Error)
Remove Asus Update or PC Probe
WarningASACPI.sys the old versions are huge cause of BSOD's
Please visit this link: http://support.asus.com/download.aspx?SLanguage=en&m=P7P55D%20LE&p=1&s=32&os=29&hashedid=e7Zic83PvQSr80Lm
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2004-5).
InformationGo to your motherboard's website and check your version of your BIOS. See if there are any problems you are having that are solved by a a later version. I do not often recommend flashing the BIOS because there is a risk involved. If there is problem addressed by a BIOS that applies to your computer, consider flashing your BIOS to the latest version. If you choose to do this, flash you BIOS outside of Windows.
Run Prime 95 again to test your CPU and your ram. Carefully the instructions in this tutorial: CPU - Stress Test with Prime95. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results.
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 101, {61, 0, 807c5120, 1} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) 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: 00000061, Clock interrupt time out interval in nominal clock ticks. Arg2: 00000000, 0. Arg3: 807c5120, The PRCB address of the hung processor. Arg4: 00000001, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_2_PROC CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 1c STACK_TEXT: 8db1f154 832a4e13 00000101 00000061 00000000 nt!KeBugCheckEx+0x1e 8db1f190 832a4462 00002711 00000000 0000b400 nt!KeAccumulateTicks+0x242 8db1f1d0 832a430f 832d097d 0f9d89c1 00000000 nt!KeUpdateRunTime+0x145 8db1f228 832a967f 832cd402 832cd402 000000d1 nt!KeUpdateSystemTime+0x613 8db1f228 832d097d 832cd402 832cd402 000000d1 nt!KeUpdateSystemTimeAssist+0x13 8db1f2c8 83478332 c645a04f 85a893b0 000000b8 nt!KeQueryValuesProcess+0xbb 8db1f350 83476c34 00091cb8 cc756000 c645a0eb nt!ExpCopyProcessInfo+0x116 8db1f3f4 8346d8a6 cc756098 0001ff68 8db1f844 nt!ExpGetProcessInformation+0x115 8db1f874 8346f95c 00000005 00000000 00000000 nt!ExpQuerySystemInformation+0x1086 8db1f890 8327c43a 00000005 cc756098 0001ff68 nt!NtQuerySystemInformation+0x76 8db1f890 8327ae09 00000005 cc756098 0001ff68 nt!KiFastCallEntry+0x12a 8db1f918 8bb9dfdf 00000005 cc756098 0001ff68 nt!ZwQuerySystemInformation+0x11 8db1fc78 8bb7b15e 00000000 00000000 8db1fc98 cng!GatherRandomKey+0x272 8db1fcdc 8bb7b1bf 00000000 8db1fd00 83459b2f cng!ReadExternalEntropyIntoPool+0x1a6 8db1fce8 83459b2f 862c25d0 00000000 85aa8238 cng!scavengingWorkItemRoutine+0x15 8db1fd00 832a703b 85aa8238 00000000 859dca70 nt!IopProcessWorkItem+0x2d 8db1fd50 834479df 00000001 c645ae8f 00000000 nt!ExpWorkerThread+0x10d 8db1fd90 832f91d9 832a6f2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19 STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE Followup: MachineOwner ---------
Last edited by yowanvista; 05 May 2011 at 02:58.