Hyper-v Server Blue Screen with bugcheck 101


  • Hi all,

    I have two hyper-v servers (R2) with 2 and 3 guest systems. (Windows Server 2008, Windows Server 2008 SBS, Linux CentOS 5.3 (3x))

    Periodically the Hyper-V servers are Blue Screening and restarting. The event log gives the following:

    The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000101 (0x0000000000000019, 0x0000000000000000, 0xfffff88001e5c180, 0x0000000000000002). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 100809-34491-01.

    I have attempted to analyse the mini dump but am not really sure what I am doing with this or what I am looking for! Any help would be greatly appreciated.

    It makes me think there is something more than a minor glitch as we are getting this multiple times (no idea of a triggering event!) and on two independent servers.

    Thanks in advance.

    Thursday, October 08, 2009 2:55 PM


All replies

  • Hi,


    According to the description, we find it seems to be system crash issue and we need to analyze the crash dump file to narrow down the root cause of the issue. Unfortunately, it is not effective for us to debug the crash dump file here in the forum. Therefore, I would like to suggest that you contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request.


    To obtain the phone numbers for specific technology request please take a look at the web site listed below:




    Hope the issue will be resolved soon.


    Best Regards,

    Vincent Hu


    Friday, October 09, 2009 5:45 AM
  • Thanks for the response Vincent,

    I have analysed the minidump generated and the output from that is below. All I know is that it appears to be a driver fault. 
    All the drivers on the system I believe were installed during the operating system install.
    Does this analysis output mean anything to you?

    0: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    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.
    Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: fffff88001e5c180, The PRCB address of the hung processor.
    Arg4: 0000000000000002, 0.
    Debugging Details:
    BUGCHECK_STR:  0x101
    PROCESS_NAME:  System
    LAST_CONTROL_TRANSFER:  from fffff80001c74443 to fffff80001cc7f00
    fffff800`01a5aa28 fffff800`01c74443 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`01e5c180 : nt!KeBugCheckEx
    fffff800`01a5aa30 fffff800`01cd05f7 : 00000000`00000000 fffff800`00000002 00000000`00026161 fffffa80`045cd278 : nt! ?? ::FNODOBFM::`string'+0x4e3e
    fffff800`01a5aac0 fffff800`01c17895 : fffff800`01c3c460 fffff800`01a5ac70 fffff800`01c3c460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
    fffff800`01a5abc0 fffff800`01cc43f3 : fffffa80`03f4e1b0 ffffffff`ffb3b4c0 fffff800`01e44a20 00000000`00000002 : hal!HalpHpetClockInterrupt+0x8d
    fffff800`01a5abf0 fffff800`01cd06d2 : fffff800`01e40e80 fffff800`00000001 00000000`00000001 fffff880`00000000 : nt!KiInterruptDispatchNoLock+0x163
    fffff800`01a5ad80 00000000`00000000 : fffff800`01a5b000 fffff800`01a55000 fffff800`01a5ad40 00000000`00000000 : nt!KiIdleLoop+0x32
    nt! ?? ::FNODOBFM::`string'+4e3e
    fffff800`01c74443 cc              int     3
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4e3e
    FOLLOWUP_NAME:  MachineOwner
    IMAGE_NAME:  ntkrnlmp.exe
    FAILURE_BUCKET_ID:  X64_0x101_nt!_??_::FNODOBFM::_string_+4e3e
    BUCKET_ID:  X64_0x101_nt!_??_::FNODOBFM::_string_+4e3e
    Followup: MachineOwner


    Thursday, October 15, 2009 10:24 AM
  • Hi Rob,


    I found a post discussed the similar issue with yours, you can refer to:


    Hyperv Server 2008 R2 bluescreen...probably CLOCK_WATCHDOG_TIMEOUT



    If the problem continues, I still recommend that you contact Microsoft CSS via telephone so that a dedicated Support Professional can assist with your request. Thanks for your understanding.



    Best Regards,

    Vincent Hu


    Monday, October 19, 2009 8:11 AM