BSOD when running cpu intensive software

[dukeydog]

Hi all

Hope someone can help.
I've had a BSOD for several months, but very infrequently (once every couple of weeks). Stupidly I've just been ignoring it, but I'm trying to render a HD video in Sony Vegas and I now keep getting the BSOD at every attempt.
I also get the same problem when trying to play Mass Effect 2, so I'm assuming it happens when the system is being utilised to its fullest.

I've attached the requierd file. Hope I've done everything correctly, apologies if not.

 

[koolkat77]

Welcome

Go through steps in this thread: http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html. See if it helps in resolving your issue.

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

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff88002f64180, 2}

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

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  VegasMovieStud

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`0a575a48 fffff800`02ee4d5a : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02f64180 : nt!KeBugCheckEx
fffff880`0a575a50 fffff800`02e97ad7 : 00000000`00000000 fffff800`00000002 00000000`00002710 00000000`c2078030 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`0a575ae0 fffff800`03401895 : fffff800`03427460 fffff880`0a575c90 fffff800`03427460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0a575be0 fffff800`02e8a513 : 00000000`fd9a91ef fffff800`03000e80 fffff800`03000e80 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0a575c10 fffff800`02e92dd2 : fffff800`03000e80 fffff880`00000001 00000000`00000000 fffff880`0a575ea8 : nt!KiInterruptDispatchNoLock+0x163
fffff880`0a575da0 fffff800`02ead5f1 : 00000000`00000000 00000000`00000006 00000000`00000001 00000000`0000043b : nt!KeFlushMultipleRangeTb+0x252
fffff880`0a575e70 fffff800`02eb0038 : 00000000`00000006 fffff880`0a575fc0 fffff900`c2212000 00001fa0`02000000 : nt!MiFlushTbAsNeeded+0x1d1
fffff880`0a575f80 fffff800`02fb6f86 : 00000000`000055b0 fffff880`07bfbcc0 00000000`00000021 00000000`0008ca38 : nt!MiAllocatePagedPoolPages+0x4cc
fffff880`0a5760a0 fffff800`02eadd50 : 00000000`000055b0 fffff880`07bfbcc0 00000000`00000021 00000000`00000000 : nt!MiAllocatePoolPages+0x906
fffff880`0a5761e0 fffff800`02fb990e : 00000000`00000000 fffff800`02e96e33 00000000`00000020 00000000`000055b0 : nt!ExpAllocateBigPool+0xb0
fffff880`0a5762d0 fffff960`000d48d9 : fffff900`c021aef8 00000000`00000000 00000000`02050e60 00000000`00000000 : nt!ExAllocatePoolWithTag+0x82e
fffff880`0a5763c0 fffff960`000d5e0c : 00000000`00000000 fffff880`0a576560 fffff960`000e604d 00000000`77721500 : win32k!AllocateObject+0xdd
fffff880`0a576400 fffff960`000acf2c : fffff900`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SURFMEM::bCreateDIB+0x1f8
fffff880`0a5764f0 fffff960`000acaa2 : 00000011`0000013a 00000000`00000011 00000000`01080030 00000000`0000013a : win32k!hsurfCreateCompatibleSurface+0x3bc
fffff880`0a5765c0 fffff800`02e8d253 : fffffa80`0784b8c0 fffff880`0a576720 00000000`00000000 fffff900`c00c0010 : win32k!GreCreateCompatibleBitmap+0x26e
fffff880`0a5766a0 00000000`73b72e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008d3b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73b72e09


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

 

[dukeydog]

Thanks for your help.

I think I've found the problem and thought I would put it on here in case it helps anyone else.
The BSOD was due to the CPU overheating. I cleaned dust from the fan and heatsink and reduced the voltage to the CPU in the BIOS slightly. These two things dropped the temperature considerably and enabled me to render a fairly large video, which worked the CPU hard.

 

[koolkat77]

Thanks for letting us know.