Windows 7: My BSOD On server (probly printers)

DeWinter · 26 Jul 2011

Windows 7 64Bit Full retail
3 Month old hardware
3 Month old OS

**yowanvista** · 26 Jul 2011

The msinfo32 file is missing from the attachment, did you remove it?

Seems that there is a problem with the CPU itself

Run Prime 95 to test your CPU. 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

According to your dump file the issue is with your Processor. This occurs when the processor is non-responsive or is deadlocked.

Possible Solutions :

a) BIOS bug
b) a driver whose activity is causing the target processor to lock up
c) a hardware defect (temperature, voltage, dust

But its mainly caused by a defective CPU or outdated BIOS

Details about this bugcheck:
http://www.sevenforums.com/crash-loc...tml#post567135

Win 7 A Clock Interrupt... BSOD (101 Error)

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

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  OUTLOOK.EXE

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`0c8d5658 fffff800`02c3a473 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`009ea180 : nt!KeBugCheckEx
fffff880`0c8d5660 fffff800`02c94de7 : 00000000`00000000 fffff800`00000001 00000000`00002710 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4d8e
fffff880`0c8d56f0 fffff800`03202895 : fffff800`03227460 fffff880`0c8d58a0 fffff800`03227460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0c8d57f0 fffff800`02c88bf3 : 00000000`47ef4723 fffff800`02e06e80 00000000`00000000 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0c8d5820 fffff800`02c9a610 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`0c8d59b0 fffff800`02ca4881 : fffff900`c2861001 00000000`00000003 00000000`00000001 fffff800`02c8b953 : nt!KeFlushMultipleRangeTb+0x260
fffff880`0c8d5a80 fffff800`02cb79bb : 00000000`00000003 fffff880`0c8d5c00 fffff900`c2861000 fffff960`000dbf34 : nt!MiFlushTbAsNeeded+0x1d1
fffff880`0c8d5b90 fffff800`02dbdceb : 00000000`00002330 00000000`00002330 00000000`00000021 fffff960`0011ae2c : nt!MiAllocatePagedPoolPages+0x4bb
fffff880`0c8d5cb0 fffff800`02c9f070 : 00000000`00002330 fffff880`08a80cc0 00000000`00000021 00000000`01ff0000 : nt!MiAllocatePoolPages+0x8e2
fffff880`0c8d5e00 fffff800`02dc0bfe : 00000000`00000000 fffff880`0c8d65b0 00000000`00000020 fffff880`08a80cc0 : nt!ExpAllocateBigPool+0xb0
fffff880`0c8d5ef0 fffff960`00102df1 : ffffffff`850512e0 00000000`00000000 fffff900`c0aa1020 00000000`00000000 : nt!ExAllocatePoolWithTag+0x82e
fffff880`0c8d5fe0 fffff960`0010431f : fffff900`c01cccf0 fffff880`0c8d6160 fffff880`0c8d60e8 00000000`04011252 : win32k!AllocateObject+0xdd
fffff880`0c8d6020 fffff960`000678df : fffff900`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SURFMEM::bCreateDIB+0x1fb
fffff880`0c8d6110 fffff960`001e1097 : fffff900`c01cccf0 ffffffff`850512e0 00000030`0000002c fffff900`c00c3010 : win32k!hbmCreateDriverSurface+0xef
fffff880`0c8d61a0 fffff960`00b163f0 : fffff900`c01cccf0 fffff900`c221dcd0 ffffffff`850512e0 fffff900`c0105020 : win32k!EngCreateBitmap+0x27
fffff880`0c8d61f0 fffff960`000db35e : fffff900`c01cccf0 00000030`0000002c 00000000`00000001 00000000`00000001 : RDPDD!DrvCreateDeviceBitmap+0x150
fffff880`0c8d6270 fffff960`000db096 : 00000030`0000002c 00000000`00000030 00000000`6e081070 00000000`0000002c : win32k!hsurfCreateCompatibleSurface+0x1fe
fffff880`0c8d6340 fffff800`02c8b953 : fffffa80`0f31e260 fffff880`0c8d64a0 00000000`00000000 fffff900`c00c3010 : win32k!GreCreateCompatibleBitmap+0x26e
fffff880`0c8d6420 00000000`74f22dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0022cd68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74f22dd9


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

Windows 7: My BSOD On server (probly printers)

My BSOD On server (probly printers) problems?