BSOD - please advice

w77w · 17 Jun 2011

Please advice. Details below and attached

Is Windows 7 . . .
- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? None
- an OEM or full retail version? OEM
- OEM = came pre-installed on system - No
- Full Retail = you purchased it from retailer - No, self assembled
- What is the age of system (hardware)? less than 2 weeks
- What is the age of OS installation (have you re-installed the OS?) less than 2 weeks

yowanvista · 17 Jun 2011

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)

Go 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                                    *
*                                                                             *
*******************************************************************************

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: fffff88003bd7180, The PRCB address of the hung processor.
Arg4: 0000000000000003, 0.

Debugging Details:
------------------


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  VirtuaWin.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`0a5c20b8 fffff800`02f2d8f9 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`03bd7180 : nt!KeBugCheckEx
fffff880`0a5c20c0 fffff800`02ee04b7 : 00000000`00000000 fffff800`00000003 00000000`00002711 fffff800`02e20552 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`0a5c2150 fffff800`02e17895 : fffff800`02e3d460 fffff880`0a5c2300 fffff800`02e3d460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0a5c2250 fffff800`02ed2233 : 00000000`607e425b fffff800`03048e80 fffffa80`0634f740 fffff800`02f0b2ed : hal!HalpHpetClockInterrupt+0x8d
fffff880`0a5c2280 fffff800`02edb806 : fffff800`03048e80 fffff900`00000001 00000000`00000000 fffff880`0a5c2518 : nt!KiInterruptDispatchNoLock+0x163
fffff880`0a5c2410 fffff800`02ef6061 : 00000000`00000000 00000000`00000001 00000000`00000001 00000000`00000000 : nt!KeFlushMultipleRangeTb+0x266
fffff880`0a5c24e0 fffff800`02ef8aac : 00000000`00000001 fffff880`0a5c2640 fffff900`c1e62000 fffff900`c064d1d0 : nt!MiFlushTbAsNeeded+0x1d1
fffff880`0a5c25f0 fffff800`02ffef86 : fffff880`03a52e00 00000000`000000f7 00000000`00000021 00000000`00000001 : nt!MiAllocatePagedPoolPages+0x4cc
fffff880`0a5c2710 fffff800`030013f6 : fffff880`03a52e00 00000000`000000f7 00000000`00000021 fffff960`0018c0de : nt!MiAllocatePoolPages+0x906
fffff880`0a5c2850 fffff960`00134b68 : 00000000`00000000 00000000`00000000 00000000`ffffffff 00000000`00000000 : nt!ExAllocatePoolWithTag+0x316
fffff880`0a5c2940 fffff960`0014dc92 : fffff900`c24b50a0 fffff900`00000000 00000000`00000000 fffff900`c24b5f18 : win32k!InternalRebuildHwndListForIMEClass+0x38
fffff880`0a5c29b0 fffff960`00134881 : 00000000`00000000 fffff880`0a5c2b60 00000000`00000000 00000000`0008fd20 : win32k!BuildHwndList+0xb2
fffff880`0a5c29e0 fffff800`02ed4f93 : fffffa80`0da7d060 00000000`00000000 00000000`0008e2e8 fffff880`0a5c2a88 : win32k!NtUserBuildHwndList+0x19d
fffff880`0a5c2a70 00000000`749bfd8a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e2c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x749bfd8a


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:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner
---------