Share via

hypervisor error

Anonymous
2021-11-24T07:35:35+00:00

https://1drv.ms/u/s!Anpb_X5YXs6OhuwYDr7NQGOd-55Jbw?e=wBtzNd

Microsoft (R) Windows Debugger Version 10.0.22000.194 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 19041 MP (16 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Edition build lab: 19041.1.amd64fre.vb_release.191206-1406

Machine Name:

Kernel base = 0xfffff80069e00000 PsLoadedModuleList = 0xfffff8006aa2a2d0

Debug session time: Wed Nov 24 16:11:33.527 2021 (UTC + 9:00)

System Uptime: 0 days 0:10:16.283

Loading Kernel Symbols

...............................................................

................................................................

................................................................

..................................

Loading User Symbols

Loading unloaded module list

............

For analysis of this file, run !analyze -v

4: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

HYPERVISOR_ERROR (20001)

The hypervisor has encountered a fatal error.

Arguments:

Arg1: 0000000000000011

Arg2: 000000000028cdd7

Arg3: 0000000000001005

Arg4: ffffe80001ad1bc0

Debugging Details:

KEY_VALUES_STRING: 1 

Key  : Analysis.CPU.mSec 

Value: 3155 

Key  : Analysis.DebugAnalysisManager 

Value: Create 

Key  : Analysis.Elapsed.mSec 

Value: 2881 

Key  : Analysis.Init.CPU.mSec 

Value: 6092 

Key  : Analysis.Init.Elapsed.mSec 

Value: 60739 

Key  : Analysis.Memory.CommitPeak.Mb 

Value: 87 

Key  : WER.OS.Branch 

Value: vb\_release 

Key  : WER.OS.Timestamp 

Value: 2019-12-06T14:06:00Z 

Key  : WER.OS.Version 

Value: 10.0.19041.1

BUGCHECK_CODE: 20001

BUGCHECK_P1: 11

BUGCHECK_P2: 28cdd7

BUGCHECK_P3: 1005

BUGCHECK_P4: ffffe80001ad1bc0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: System

BAD_STACK_POINTER: ffff97019563cc98

STACK_TEXT:

ffff97019563cc98 fffff8006a2f3e0b : 0000000000020001 0000000000000011 000000000028cdd7 0000000000001005 : nt!KeBugCheckEx

ffff97019563cca0 fffff8006a30d8e8 : 0000000000000001 00000000ffffffff ffff970195600180 fffff8006a3201e0 : nt!HvlSkCrashdumpCallbackRoutine+0x6b

ffff97019563cce0 fffff8006a202982 : 0000000000000001 ffff97019563cef0 0000000000000000 0000000000000000 : nt!KiProcessNMI+0xe8

ffff97019563cd30 fffff8006a202752 : 0000000000000001 0000000000000000 4c8d480000024068 7024447f0ff33824 : nt!KxNmiInterrupt+0x82

ffff97019563ce70 fffff8006a18dc6d : 000000016f576a52 ffff970195600180 0000000000000000 000001a247ddd083 : nt!KiNmiInterrupt+0x212

ffffa981392536b0 fffff8006a018346 : 000000000000020e 0000000000000000 0000000000000000 0000000000000000 : nt!PpmIdleGuestExecute+0x1d

ffffa981392536f0 fffff8006a017104 : 0000000000000000 00001f8000000001 0000000000000003 0000000000000002 : nt!PpmIdleExecuteTransition+0x10c6

ffffa98139253af0 fffff8006a1fadc4 : ffffffff00000000 ffff97019560b440 ffffe7019073c080 0000000000000d7b : nt!PoIdle+0x374

ffffa98139253c60 0000000000000000 : ffffa98139254000 ffffa9813924e000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x54

SYMBOL_NAME: nt!HvlSkCrashdumpCallbackRoutine+6b

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 6b

FAILURE_BUCKET_ID: 0x20001_11_28cdd7_STACKPTR_ERROR_nt!HvlSkCrashdumpCallbackRoutine

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {67af35f3-e17d-39ba-23a3-4d20d1dbdc45}

Followup: MachineOwner

windbg> .hh

4: kd> lmvm nt

Browse full module list

start end module name

fffff80069e00000 fffff8006ae46000 nt (pdb symbols) C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\sym\ntkrnlmp.pdb\1F9BB45B28B806E4D18925C06E924B8C1\ntkrnlmp.pdb 

Loaded symbol image file: ntkrnlmp.exe 

Mapped memory image file: C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\sym\ntoskrnl.exe\F05723421046000\ntoskrnl.exe 

Image path: ntkrnlmp.exe 

Image name: ntkrnlmp.exe 

Browse all global symbols  functions  data 

Image was built with /Brepro flag. 

Timestamp:        F0572342 (This is a reproducible build file hash, not a timestamp) 

CheckSum:         00A5EC86 

ImageSize:        01046000 

Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4 

Information from resource tables:

4: kd> kb

RetAddr : Args to Child : Call Site

00 fffff8006a2f3e0b : 0000000000020001 0000000000000011 000000000028cdd7 00000000`00001005 : nt!KeBugCheckEx

01 fffff8006a30d8e8 : 0000000000000001 00000000ffffffff ffff970195600180 fffff800`6a3201e0 : nt!HvlSkCrashdumpCallbackRoutine+0x6b

02 fffff8006a202982 : 0000000000000001 ffff97019563cef0 0000000000000000 00000000`00000000 : nt!KiProcessNMI+0xe8

03 fffff8006a202752 : 0000000000000001 0000000000000000 4c8d480000024068 7024447f`0ff33824 : nt!KxNmiInterrupt+0x82

04 fffff8006a18dc6d : 000000016f576a52 ffff970195600180 0000000000000000 000001a2`47ddd083 : nt!KiNmiInterrupt+0x212

05 fffff8006a018346 : 000000000000020e 0000000000000000 0000000000000000 00000000`00000000 : nt!PpmIdleGuestExecute+0x1d

06 fffff8006a017104 : 0000000000000000 00001f8000000001 0000000000000003 00000000`00000002 : nt!PpmIdleExecuteTransition+0x10c6

07 fffff8006a1fadc4 : ffffffff00000000 ffff97019560b440 ffffe7019073c080 00000000`00000d7b : nt!PoIdle+0x374

08 0000000000000000 : ffffa98139254000 ffffa9813924e000 0000000000000000 00000000`00000000 : nt!KiIdleLoop+0x54

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. DaveM121 891.6K Reputation points Independent Advisor
    2021-11-24T09:15:21+00:00

    Hi moleee, glad to help!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-11-24T09:11:01+00:00

    Thank you.

    Was this answer helpful?

    0 comments
  3. DaveM121 891.6K Reputation points Independent Advisor
    2021-11-24T08:46:38+00:00

    Hi moleee

    Your Memory.dmp file just indicate memory (RAM) corruption no specific driver is listed

    All your drivers and BIOS seem to be up to date.

    To try to force Windows 10 show any faulting drivers, the best option would be to turn on Driver Verifier, let your PC crash 3 times, then you must turn off Driver Verifier, and finally, upload any newly created minidump files

    https://answers.microsoft.com/en-us/windows/for...

    Was this answer helpful?

    0 comments
  5. DaveM121 891.6K Reputation points Independent Advisor
    2021-11-24T08:10:31+00:00

    Hi moleee

    I am Dave, I will help you with this.

    Your Memory.dmp file is 1.7GB in size, please zip up that file to vastly reduce its size and re-upload it, also, please check if there are any minidump files in C:\Windows\Minidump and if so, upload those as a separate download

    I will then analyze those dump files for you.

    Was this answer helpful?

    0 comments