Question : BSOD Windows 2008 R2 Hyper-V

Hi Everyone,

I am getting a BSOD on my Win2008 Hyper-V server and have run out of ideas to troubleshoot it. Here is what I have done so far:

Updated all drivers and BIOS

Updated VM Integration services on all guest VM's

Fully updated OS

Here is the dubug log from the dump file:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*C:\windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`01c09000 PsLoadedModuleList = 0xfffff800`01e46e50
Debug session time: Fri May 14 22:24:16.550 2010 (GMT+1)
System Uptime: 7 days 1:21:41.953
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols

Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff88001f3f180, 4}

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: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88001f3f180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

STACK_TEXT:  
fffff800`019daa28 fffff800`01c27443 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`01f3f180 : nt!KeBugCheckEx
fffff800`019daa30 fffff800`01c835f7 : 00000000`00000000 fffff800`00000004 00000000`00002710 fffffa80`0d6d2000 : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff800`019daac0 fffff800`021f0895 : fffff800`02215460 fffff800`019dac70 fffff800`02215460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff800`019dabc0 fffff800`01c773f3 : 00000000`00000000 fffff880`03742ce8 fffff800`01df7b60 00000000`00000002 : hal!HalpHpetClockInterrupt+0x8d
fffff800`019dabf0 fffff800`01c836d2 : fffff800`01df3e80 fffff800`00000001 00000000`00000001 fffff880`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff800`019dad80 00000000`00000000 : fffff800`019db000 fffff800`019d5000 fffff800`019dad40 00000000`00000000 : nt!KiIdleLoop+0x32


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

Any ideas?

Thanks very much!

Dave

Answer : BSOD Windows 2008 R2 Hyper-V

I have found the fix for this incase others are looking. It is a problem with Intel proccessors.

http://support.microsoft.com/kb/975530