BSOD and freezing on new computer

[Introversity]

It just seems to happen randomly, sometimes playing games or blurays or watching YouTube, sometimes just sitting on the desktop.

Computer consists only of new parts, so I can't tell which component is problematic, if any. Running Win7 64bit OEM.

Attached the \minidump file.

Thank you for your help, this is driving me mad.



Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 3081

Additional information about the problem:
BCCode: 101
BCP1: 0000000000000019
BCP2: 0000000000000000
BCP3: FFFFF88002FD3180
BCP4: 0000000000000003
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

 

[yowanvista]

Bugcheck 101 is mainly caused by a defective CPU or outdated BIOS

http://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.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
[COLOR=Red]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.[/COLOR]
Arguments:
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002fd3180, The PRCB address of the hung processor.
Arg4: 0000000000000003, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`046c3478 fffff800`03075453 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`02fd3180 : nt!KeBugCheckEx
fffff880`046c3480 fffff800`030cfde7 : 00000000`00000000 fffff800`00000003 00000000`00002711 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4dfe
fffff880`046c3510 fffff800`03018895 : fffff800`0303d460 fffff880`046c36c0 fffff800`0303d460 fffff880`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`046c3610 fffff800`030c3c33 : fffff800`03241e80 00000000`00000001 fffff880`046c3730 fffff800`030c3347 : hal!HalpHpetClockInterrupt+0x8d
fffff880`046c3640 fffff800`030869e9 : 00000000`00000000 00000000`00000000 00000000`00195d80 00000000`00195d78 : nt!KiInterruptDispatchNoLock+0x163
fffff880`046c37d0 fffff800`033c5568 : 00000000`00000000 fffff880`046c3ca0 fffff800`03057000 00000000`00000000 : nt!KeFlushProcessWriteBuffers+0x65
fffff880`046c3840 fffff800`033c61e5 : 00000000`001861a0 fffff800`033c210e 00000000`00000000 00000000`00000246 : nt!ExpQuerySystemInformation+0x1368
fffff880`046c3be0 fffff800`030c6993 : 00000000`00000000 fffff880`046c3ca0 ffffffff`fffe7960 000007fe`fbb20b48 : nt!NtQuerySystemInformation+0x4d
fffff880`046c3c20 00000000`778f00ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00c9f498 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778f00ba


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_8_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

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