I got a BSOD on a Windows 2008 server running at Amazon EC2, i managed to get the following using windbg. I have no idea what happend exactly (i only found an old hotfix for a similar issue when running a virtual server on a specific processor: http://blogs.msdn.com/b/virtual_pc_guy/archive/2009/10/16/hyper-v-hotfix-for-0x00000101-clock-watchdog-timeout-on-nehalem-systems.aspx) here's the link for the minidump: https://www.yousendit.com/download/MzZIRkJUTStFc0x2Wmc9PQ 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: 0000000000000061, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: fffffa60005ec180, The PRCB address of the hung processor. Arg4: 0000000000000001, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_2_PROC CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP PROCESS_NAME: System CURRENT_IRQL: d STACK_TEXT: fffffa60`01b63948 fffff800`01635390 : 00000000`00000101 00000000`00000061 00000000`00000000 fffffa60`005ec180 : nt!KeBugCheckEx fffffa60`01b63950 fffff800`01672dca : fffff800`01b633c0 fffffa60`01b63a70 00000000`00000000 fffff800`01b633c0 : nt! ?? ::FNODOBFM::`string'+0x2de4 fffffa60`01b63990 fffff800`01b40f04 : 00000000`00000000 00000000`00000000 00000000`00003f5d fffff800`016c2d83 : nt!KeUpdateSystemTime+0xea fffffa60`01b639c0 fffff800`0167258d : 00000000`176810c5 00000000`00000000 00000000`00000008 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8c fffffa60`01b639f0 fffff800`0168498d : 00000000`00000000 fffffa60`01b63be8 00000000`00000001 00000000`00000007 : nt!KiInterruptDispatchNoLock+0x14d fffffa60`01b63b80 fffff800`01640a47 : fffff800`01792cf0 00000000`00000004 fffffa60`01b63ce0 000fce15`ec565e8f : nt!KeFlushMultipleRangeTb+0xdd fffffa60`01b63bc0 fffff800`01640559 : 00000000`00000000 fffff800`016b8800 fffff800`01792cf0 00000000`06655cb9 : nt!MmOutPageKernelStack+0x57 fffffa60`01b63ca0 fffff800`016b88d0 : 00000000`00000000 00000000`00000080 00000000`00000000 006f0072`00500000 : nt!KiOutSwapKernelStacks+0x159 fffffa60`01b63d10 fffff800`01883f57 : 00650044`00630076 00200020`00630073 00200020`00200020 003d0020`00200001 : nt!KeSwapProcessOrStack+0x58 fffffa60`01b63d50 fffff800`016b6656 : fffff800`01792680 fffffa80`05dec720 fffff800`01797b80 00000000`00000000 : nt!PspSystemThreadStartup+0x57 fffffa60`01b63d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 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_2_PROC_ANALYSIS_INCONCLUSIVE BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE Followup: MachineOwner --------- any help would be appreciated!

Threr can be 2 issues 1)if its a Nehlem processor ( Install the Hotfix ) or 2) Dell hardware with C1E and C-States enabled in the bios http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/77bcc073-b2ff-4f47-a7dc-1aa79e5b1333 http://www.virmansec.com/blogs/skhairuddin