Experts -
I have a new Dell R710 I have had in production for lesss than 48. It has BSOD on me three different times now, and always recoverrs automatically from the reboot. The Server's role is HyperV R2 - but I don't think that makes much of a difference... Here is the dump (all things point to Processor, but I'm not sure how to read this so I am at a loss..) Any help would be appreciated it.. I am banging my head here...
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: 000000000000000d, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002400180, The PRCB address of the hung processor.
Arg4: 000000000000000a, 0.
Debugging Details:
------------------
OVERLAPPED_MODULE: Address regions for 'spsys' and 'USBSTOR.SYS' overlap
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_10_
PROC
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: d
STACK_TEXT:
fffff800`0161a938 fffff800`01882443 : 00000000`00000101 00000000`0000000d 00000000`00000000 fffff880`02400180 : nt!KeBugCheckEx
fffff800`0161a940 fffff800`018de5f7 : fffffa80`00000000 fffff800`0000000a 00000000`00026160 fffffa80`37b048b0 : nt! ?? ::FNODOBFM::`string'+0x4e3
e
fffff800`0161a9d0 fffff800`01825895 : fffff800`0184a460 fffff800`0161ab80 fffff800`0184a460 fffff800`00000000 : nt!KeUpdateSystemTime+0x37
7
fffff800`0161aad0 fffff800`018d23f3 : fffff880`0d5ebf20 00000000`00002000 fffffa80`80a8a658 fffffa80`80d54000 : hal!HalpHpetClockInterrupt
+0x8d
fffff800`0161ab00 fffff800`01838652 : fffff800`018e3a3a 00000000`ffffffed 000027e9`1417802e fffff800`01a5cc40 : nt!KiInterruptDispatchNoLo
ck+0x163
fffff800`0161ac98 fffff800`018e3a3a : 00000000`ffffffed 000027e9`1417802e fffff800`01a5cc40 00000000`00000001 : hal!HalProcessorIdle+0x2
fffff800`0161aca0 fffff800`018de6cc : fffff800`01a4ee80 fffff800`00000000 00000000`00000000 fffff880`03252570 : nt!PoIdle+0x53a
fffff800`0161ad80 00000000`00000000 : fffff800`0161b000 fffff800`01615000 fffff800`0161ad40 00000000`00000000 : nt!KiIdleLoop+0x2c
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
_10_PROC_A
NALYSIS_IN
CONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT
_10_PROC_A
NALYSIS_IN
CONCLUSIVE
Followup: MachineOwner
---------
0: kd> lmvm Unknown_Module
start end module name