Answered by:
Hyper-V still blue screening

Question
-
I am running identical SuperMicro hardware with the very latest BIOS (2.1a), hardware:
X7DB8 motherboard
Intel Xeon E5420
I have experienced blue screens from the vid.sys memory management issue, which I believe is fixed with SP2? I have experienced the VSS bug (where the writer goes missing), which I believe was fixed in SP2. I have also experienced two other types of BSOD (can't recall the KBs) which were meant to be fixed in SP2.
I have also experienced blue screens related to the "CPU: AAJ69 X Plan Fix An Unexpected Page Fault or EPT Violation May Occur Following the Un-mapping and Re-mapping of a Page." Issue, which I was informed was fixed in the 2.1a BIOS issued by SuperMicro.
In spite of upgrading the BIOS and installing SP2 (which, FYI, resets all the vlanfiltering settings in the registry for Intel NIC drivers) I am still seeing blue screens on a host: The latest dump:
HYPERVISOR_ERROR (20001)
The hypervisor has encountered a fatal error.
Arguments:
Arg1: 0000000000000011
Arg2: 0000000000000000
Arg3: 0000000000001005
Arg4: fffff886002aca60
Debugging Details:
------------------
BUGCHECK_STR: 0x20001_11_0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
PROCESS_NAME: System
CURRENT_IRQL: f
LAST_CONTROL_TRANSFER: from fffffa6003b24792 to fffff80008874450
STACK_TEXT:
fffffa60`01ba29c8 fffffa60`03b24792 : 00000000`00020001 00000000`00000011 00000000`00000000 00000000`00001005 : nt!KeBugCheckEx
fffffa60`01ba29d0 fffff800`088e2f60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hvboot!HbNmiCallbackRoutine+0x6a
fffffa60`01ba2a10 fffff800`088add19 : fffffa60`01ba2bb0 fffffa60`01ba2c30 fffffa60`01b9ca00 00000000`00000000 : nt!KiHandleNmi+0x20
fffffa60`01ba2a40 fffff800`08872447 : 00000000`00000002 fffffa60`01ba2c30 fffffa60`01b9ca00 00000000`00000000 : nt!KiProcessNMI+0xb9
fffffa60`01ba2a70 fffff800`088722b4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x87
fffffa60`01ba2bb0 fffffa60`00f127a2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiNmiInterrupt+0x134
fffffa60`01bc0cd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!C1Halt+0x2
STACK_COMMAND: kb
FOLLOWUP_IP:
hvboot!HbNmiCallbackRoutine+6a
fffffa60`03b24792 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: hvboot!HbNmiCallbackRoutine+6a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hvboot
IMAGE_NAME: hvboot.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49e02553
FAILURE_BUCKET_ID: X64_0x20001_11_0_hvboot!HbNmiCallbackRoutine+6a
BUCKET_ID: X64_0x20001_11_0_hvboot!HbNmiCallbackRoutine+6a
Followup: MachineOwner
- Edited by Hob_Gadling Tuesday, June 23, 2009 5:08 PM
Tuesday, June 23, 2009 10:32 AM
Answers
-
Hi,
Generally speaking, we recommend that you choose hardware which is qualified for the Windows Server 2008 Hyper-V.
The following post discussed the similar issue to yours, it seems that the SuperMicro doesn't compatible with Hyper-V, I recommend that you contact the vendor of SuperMicro for more details.
Supermicro SuperServer 7045A-WTB and Hyper-V
Hyper-V Servers Blue Screening constantly.
In addition, you may try to install Windows Server 2008 R2 to test whether the same issue occur.
Vincent Hu
- Proposed as answer by Ryan Sokolowski (MSFT)Microsoft employee Tuesday, June 23, 2009 7:53 PM
- Marked as answer by Vincent Hu Wednesday, July 1, 2009 8:47 AM
Tuesday, June 23, 2009 2:03 PM
All replies
-
Hi,
Generally speaking, we recommend that you choose hardware which is qualified for the Windows Server 2008 Hyper-V.
The following post discussed the similar issue to yours, it seems that the SuperMicro doesn't compatible with Hyper-V, I recommend that you contact the vendor of SuperMicro for more details.
Supermicro SuperServer 7045A-WTB and Hyper-V
Hyper-V Servers Blue Screening constantly.
In addition, you may try to install Windows Server 2008 R2 to test whether the same issue occur.
Vincent Hu
- Proposed as answer by Ryan Sokolowski (MSFT)Microsoft employee Tuesday, June 23, 2009 7:53 PM
- Marked as answer by Vincent Hu Wednesday, July 1, 2009 8:47 AM
Tuesday, June 23, 2009 2:03 PM -
I'd have to agree with Vincent's assessment. It sure sounds like the SuperMicro hardware you're using isn't fully compatible with Hyper-V requirements.
Ryan Sokolowski | MCT, MCITP x3, MCTS x8, MCSE x2, CCNA, CCDA, BCFPTuesday, June 23, 2009 7:54 PM