Hypervisor Error Blue Screen...HELP!

Question

I have been experiencing blue screens with the Hypervisor Error. Here is the latest analysis from the minidump. Please help me figure out what is causing this.

Microsoft (R) Windows Debugger Version 10.0.22621.1778 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\101223-16453-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available WARNING: Whitespace at end of path element Error: Empty Path. WARNING: Whitespace at end of path element Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: WARNING: Whitespace at end of path element Windows 10 Kernel Version 22621 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Edition build lab: 22621.1928.amd64fre.ni_release_svc_prod3.230622-0951 Machine Name: Kernel base = 0xfffff8037ea00000 PsLoadedModuleList = 0xfffff8037f6130c0 Debug session time: Thu Oct 12 13:28:53.422 2023 (UTC - 4:00) System Uptime: 1 days 12:57:16.062 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .......................................... Loading User Symbols Loading unloaded module list ............................ For analysis of this file, run !analyze -v 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* HYPERVISOR_ERROR (20001) The hypervisor has encountered a fatal error. Arguments: Arg1: 0000000000000013 Arg2: 0000000000000000 Arg3: 0000000029b92701 Arg4: ffffe70000005a30 Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1327 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 5466 Key : Analysis.Init.CPU.mSec Value: 1280 Key : Analysis.Init.Elapsed.mSec Value: 152808 Key : Analysis.Memory.CommitPeak.Mb Value: 101 Key : WER.OS.Branch Value: ni_release_svc_prod3 Key : WER.OS.Timestamp Value: 2023-06-22T09:51:00Z Key : WER.OS.Version Value: 10.0.22621.1928 FILE_IN_CAB: 101223-16453-01.dmp TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b BUGCHECK_CODE: 20001 BUGCHECK_P1: 13 BUGCHECK_P2: 0 BUGCHECK_P3: 29b92701 BUGCHECK_P4: ffffe70000005a30 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: ipf_helper.exe STACK_TEXT: ffff9d0054fcdca8 fffff8037ef45371 : 0000000000020001 0000000000000013 0000000000000000 0000000029b92701 : nt!KeBugCheckEx ffff9d0054fcdcb0 fffff8037ee8838c : 0000000000000100 fffff8037ec67b9c ffff9d0054fd63d0 ffff9d0054fcdd30 : nt!HvlSkCrashdumpCallbackRoutine+0x81 ffff9d0054fcdcf0 fffff8037ee20342 : 0000000000000100 ffff9d0054fcdef0 0000000000000000 0000000000000000 : nt!KiProcessNMI+0x2206cc ffff9d0054fcdd30 fffff8037ee200ae : 0000000000000100 ffff9d0054fcdef0 0000000000000000 4a47347bf6611703 : nt!KxNmiInterrupt+0x82 ffff9d0054fcde70 fffff8037ed0804a : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiNmiInterrupt+0x26e ffffd686f7e76b20 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiIpiStallOnPacketTargetsPrcb+0x2a SYMBOL_NAME: nt!HvlSkCrashdumpCallbackRoutine+81 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.22621.2428 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 81 FAILURE_BUCKET_ID: 0x20001_13_0_nt!HvlSkCrashdumpCallbackRoutine OS_VERSION: 10.0.22621.1928 BUILDLAB_STR: ni_release_svc_prod3 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {a3630d9d-0239-bf3a-e873-2ac5f4b4b994} Followup: MachineOwner ---------

Answer 1

Sorry, I was offline.

Your minidump files just indicate memory (RAM) corruption no specific driver is listed

1

The best option is to download the widely available free utility MemTest86, then run a full 4 pass scan with that to test your RAM for physical errors

2

If no RAM errors are found, to try to force Windows 11 show any fault, 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

Before you run Driver Verifier, please create a new System Restore Point

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

---

Note, if you have any difficulty getting into Windows with Driver Verifier enabled:

Start your PC, just as Windows attempts to load (spinning dots), press and hold Power Button for 5 - 10 seconds to perform a Hard Shut Down

Do this twice

On the third start Windows will boot into the Recovery Environment and from there you can access System Repair, Safe Mode, Command Prompt... etc.

Go to Troubleshoot - Advanced Option - Startup Settings and click Restart

Upon restart, press 4 to enter Safe Mode

Open Command Prompt as Administrator and run these two commands, then restart your PC.

verifier /reset

verifier /bootmode resetonbootfail

Answer 2

https://1drv.ms/u/s!An0x0yRMf036gZNqw0NN67s4ZjXYxg?e=S5GSto

Answer 3

Hi, I am Dave, I will help you with this.

Please upload any minidump files you have, I will check those to see if they provide any insight into a potential cause of the system crashes.

Open Windows File Explorer.

Navigate to C:\Windows\Minidump

Copy any minidump files onto your Desktop, then zip those up.

Upload the zip file to the Cloud (OneDrive, DropBox... etc.), then choose to share those and get a share link.

Then post the link here to the zip file, so we can take a look for you.