none
Hyper-V crash BugCheck 20001

    Question

  • Hello

    There is Windows Server 2016 1607 standart edition with Hyper-V role. Sometimes server crashes with "BugCheck 20001" in dump file. Looks like there are problems with kernel or drivers. I've check memory with memtest, also disks are okay, hardware (MB, lsi controller) was changed.  I have no minidump file, so I can provide part of memory.dmp: Please help me.

    HYPERVISOR_ERROR (20001)
    The hypervisor has encountered a fatal error.
    Arguments:
    Arg1: 0000000000000011
    Arg2: 00000000002401b0
    Arg3: 0000000000001005
    Arg4: ffffe8040024be90

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

    Page 3e00 not present in the dump file. Type ".hh dbgerr004" for details
    Page 3e00 not present in the dump file. Type ".hh dbgerr004" for details
    Page 3e00 not present in the dump file. Type ".hh dbgerr004" for details

    DUMP_CLASS: 1
    DUMP_QUALIFIER: 401
    BUILD_VERSION_STRING:  14393.1066.amd64fre.rs1_release_sec.170327-1835
    DUMP_TYPE:  1
    BUGCHECK_P1: 11
    BUGCHECK_P2: 2401b0
    BUGCHECK_P3: 1005
    BUGCHECK_P4: ffffe8040024be90
    BUGCHECK_STR:  0x20001_11_2401b0
    CPU_COUNT: 38
    CPU_MHZ: 960
    CPU_VENDOR:  GenuineIntel
    CPU_FAMILY: 6
    CPU_MODEL: 4f
    CPU_STEPPING: 1
    CPU_MICROCODE: 6,4f,1,0 (F,M,S,R)  SIG: B000010'00000000 (cache) B000010'00000000 (init)
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  f
    ANALYSIS_SESSION_HOST:  WIN-OAE8EMK0C71
    ANALYSIS_SESSION_TIME:  04-27-2017 13:08:09.0578
    ANALYSIS_VERSION: 10.0.15063.0 x86fre
    LAST_CONTROL_TRANSFER:  from fffff801351bde93 to fffff801351507c0

    STACK_TEXT:  
    ffff8f81`2010d558 fffff801`351bde93 : 00000000`00020001 00000000`00000011 00000000`002401b0 00000000`00001005 : nt!KeBugCheckEx
    ffff8f81`2010d560 fffff801`3518e53c : 00000000`00000000 00000000`00000000 00000000`00000000 fffff801`350cb9c0 : nt!HvlSkNmiCallbackRoutine+0x5f
    ffff8f81`2010d5a0 fffff801`35158f02 : 00000000`00000000 ffff8f81`2010d7b0 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2e8ac
    ffff8f81`2010d5f0 fffff801`35158d49 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
    ffff8f81`2010d730 fffff801`35206d33 : 00075358`57f02d23 00000000`00000046 00000048`468f3ddd ffffbd04`b8ad1010 : nt!KiNmiInterrupt+0x189
    ffff8f81`2007f850 fffff801`35025423 : fffff801`35206d48 fffff801`3512f5b0 ffff8f81`20105e00 00000000`00000009 : nt!PpmIdleGuestExecute+0x17
    ffff8f81`2007f890 fffff801`35024c2a : 00000000`00000000 00000000`00000002 ffffbd04`b8ad10f0 00000000`00000000 : nt!PpmIdleExecuteTransition+0x643
    ffff8f81`2007fb00 fffff801`3515381c : ffffffff`00000000 ffff8f81`20100180 ffff8f81`2010d8c0 ffffbd04`bcf61080 : nt!PoIdle+0x33a
    ffff8f81`2007fc60 00000000`00000000 : ffff8f81`20080000 ffff8f81`2007a000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c

    STACK_COMMAND:  kb
    THREAD_SHA1_HASH_MOD_FUNC:  d541e8ca401d6242a20675209bccbf139f371615
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  871b9b102a7ac608e39dbe57e386849637d56ecd
    THREAD_SHA1_HASH_MOD:  9f457f347057f10e1df248e166a3e95e6570ecfe
    FOLLOWUP_IP:
    nt!HvlSkNmiCallbackRoutine+5f
    fffff801`351bde93 cc              int     3
    FAULT_INSTR_CODE:  48c032cc
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  nt!HvlSkNmiCallbackRoutine+5f
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  58d9f097
    BUCKET_ID_FUNC_OFFSET:  5f
    FAILURE_BUCKET_ID:  0x20001_11_2401b0_nt!HvlSkNmiCallbackRoutine
    BUCKET_ID:  0x20001_11_2401b0_nt!HvlSkNmiCallbackRoutine
    PRIMARY_PROBLEM_CLASS:  0x20001_11_2401b0_nt!HvlSkNmiCallbackRoutine
    TARGET_TIME:  2017-04-22T13:54:18.000Z
    OSBUILD:  14393
    OSSERVICEPACK:  0
    SERVICEPACK_NUMBER: 0
    OS_REVISION: 0
    SUITE_MASK:  272
    PRODUCT_TYPE:  3
    OSPLATFORM_TYPE:  x64
    OSNAME:  Windows 10
    OSEDITION:  Windows 10 Server TerminalServer SingleUserTS
    OS_LOCALE: 
    USER_LCID:  0
    OSBUILD_TIMESTAMP:  2017-03-28 08:11:51
    BUILDDATESTAMP_STR:  170327-1835
    BUILDLAB_STR:  rs1_release_sec
    BUILDOSVER_STR:  10.0.14393.1066.amd64fre.rs1_release_sec.170327-1835
    ANALYSIS_SESSION_ELAPSED_TIME:  274e
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:0x20001_11_2401b0_nt!hvlsknmicallbackroutine
    FAILURE_ID_HASH:  {a5b43b4e-135f-5fe8-d182-74e061b2ff0d}
    Followup:     MachineOwner

    Best regards. Alexey

    Thursday, April 27, 2017 10:16 AM

All replies

  • Have yu checked your system to see that it has the latest drivers for all its devices?  That is one of the first things to check for any crash, as over 90% of the time, that is the cause.

    tim

    Thursday, April 27, 2017 1:48 PM
  • Hello, Tim.

    Thank you for reply. I've tried to check all the drivers. Unfortunately, I have no more idea what causes bsod. There are three identical servers and seems that only one crashes with this bsod.

    Regards

    Wednesday, May 3, 2017 12:48 PM
  • 'Identical' tends to be a euphemism in computers.  Are all systems at the same firmware level?  Have the proper chipset drivers been applied to all systems?  Have you compared the driver versions on all systems to see that they have the same version?  Do all hardware components that have firmware have the same firmware across all systems? 

    The reason I am calling out the driver, besides the fact that over 90% of BSODs are caused by faulty drivers, is that part of the dump you showed even says "WIN8_DRIVER_FAULT".

    A quick way to check drivers is to install the Failover Clustering option on all the nodes (if they are members of the same AD domain).  Installing the option does not require a system reboot, and it does not make the nodes into cluster nodes, so nothing should be impacted.  Then you can run the cluster validation wizard and select all 'identical' nodes.  You can select the specific test, or you can simply let the test run across all things.  You will definitely get errors, because you will not have shared storage and most likely different network configurations.  But one of the tests is to compare driver versions and patch levels of all the nodes.  That part of the report will give you the information.


    tim

    Wednesday, May 3, 2017 10:21 PM
  • From the error you received:

    BUCKET_ID:  0x20001_11_2401b0_nt!HvlSkNmiCallbackRoutine

    Similar error in the following link:

    https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/windows-10-bugcheck-133-seems-to-only-happen/ec6ef803-3a65-4939-91c9-f4825b40de7b

    Can you provide a dump file via a public folder on OneDrive or similar site?

    • Edited by auggyMVP Friday, May 26, 2017 4:50 PM
    Friday, May 26, 2017 4:45 PM