Hypervisor Error BSOD randomly occurred

Question

Hello, I've gotten a Hypervisor error BSOD three time in the past two or three months, usually when just booting the pc or later on. I usually only have Discord and Mozilla running, maybe Steam. It hasn't occurred during gaming, and usually when I get the error, I have to force shutdown the pc via power button since it won't actually restart itself. I really wish to just fix this since I'm not savvy in the least. I have a crash log to provide as well. It says Windows 10 at the bottom but I actually have Windows 11:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

HYPERVISOR_ERROR (20001)
The hypervisor has encountered a fatal error.
Arguments:
Arg1: 0000000000000028, An internal error was detected in the I/O MMU module.
Arg2: 0000000000000002
Arg3: 6500000000000000
Arg4: 0000000104385380

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

*** WARNING: Unable to verify timestamp for clipsp.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1125

    Key  : Analysis.Elapsed.mSec
    Value: 1287

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 359

    Key  : Analysis.Init.Elapsed.mSec
    Value: 20944

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 85

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29547.1002

    Key  : Analysis.Version.Description
    Value: 10.2602.27.2 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2602.27.2

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x20001

    Key  : Bugcheck.Code.TargetModel
    Value: 0x20001

    Key  : Dump.Attributes.AsUlong
    Value: 0x808

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: 0x20001_28_2_clipsp!unknown_function

    Key  : Failure.Hash
    Value: {db1ff6f3-6610-55ad-105f-4aa1df3ecbf0}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7497cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 38408431

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x24a10ef

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0x3f7

    Key  : Stack.Pointer
    Value: NMI


BUGCHECK_CODE:  20001

BUGCHECK_P1: 28

BUGCHECK_P2: 2

BUGCHECK_P3: 6500000000000000

BUGCHECK_P4: 104385380

FILE_IN_CAB:  053026-10078-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffa609ed168080

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

STACK_TEXT:  
ffffda80`dedcfca8 fffff805`ef986eca     : 00000000`00020001 00000000`00000028 00000000`00000002 65000000`00000000 : nt!KeBugCheckEx
ffffda80`dedcfcb0 fffff805`ef9b4451     : ffffa609`c5506fb0 fffff805`ef9c7390 ffffda80`dedde990 ffffda80`dedcfd30 : nt!HvlSkCrashdumpCallbackRoutine+0x8a
ffffda80`dedcfcf0 fffff805`efab4ec2     : 00000000`00000100 ffffda80`dedcfef0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0xb1
ffffda80`dedcfd30 fffff805`efab4c2e     : 00000000`00000000 00000000`00000100 ffffda80`dedcfef0 00000000`00000000 : nt!KxNmiInterrupt+0x82
ffffda80`dedcfe70 fffff805`7fc5001c     : fffff805`efaa44cb 00000000`00000803 ffffa500`a4a2e6c0 00000000`00000006 : nt!KiNmiInterrupt+0x26e
ffffa500`a4a2e498 fffff805`efaa44cb     : 00000000`00000803 ffffa500`a4a2e6c0 00000000`00000006 fffff805`ef7eec04 : 0xfffff805`7fc5001c
ffffa500`a4a2e4a0 fffff805`ef7b7b48     : 00000000`00000000 ffffa500`a4a2e860 ffffa500`a4a2e680 ffffa500`a4a2e680 : nt!HvlSwitchToVsmVtl1+0xab
ffffa500`a4a2e5e0 fffff805`ef7b6540     : 00000000`00000803 fffff805`f0238c40 00000000`00000000 00000000`00000007 : nt!VslpEnterIumSecureMode+0x3a8
ffffa500`a4a2e6a0 fffff805`ef675c17     : 00000000`00000000 ffffb700`00000000 fffff805`80f90000 00000000`00000011 : nt!VslRemoveProtectedPage+0x5c
ffffa500`a4a2e760 fffff805`ef6b47ce     : ffffa500`a4a2e8b0 00000000`00000000 00000000`00000006 09000001`39b14121 : nt!MiClearPfnImageVerified+0xd7
ffffa500`a4a2e7b0 fffff805`ef6b2f65     : ffffa500`a4a2e8b0 ffffa500`a4a2e870 00000000`00000001 ffffb75b`add6e7f8 : nt!MiProbeLeafPteAccess+0x22e
ffffa500`a4a2e820 fffff805`ef6b2a0f     : 00000000`00000000 00000000`00000002 ffffa500`a4a2ead0 ffffa60a`09659890 : nt!MiProbeAndLockPacket+0x1d5
ffffa500`a4a2e870 fffff805`80e933c7     : fffff805`80f6bdd0 ffffa500`a4a2eb10 00000000`00000000 fffff805`80f6bdd0 : nt!MmProbeAndLockPages+0x7f
ffffa500`a4a2e970 fffff805`80f6bdd0     : ffffa500`a4a2eb10 00000000`00000000 fffff805`80f6bdd0 00000000`00000000 : clipsp+0x33c7
ffffa500`a4a2e978 ffffa500`a4a2eb10     : 00000000`00000000 fffff805`80f6bdd0 00000000`00000000 00000000`00000001 : clipsp+0xdbdd0
ffffa500`a4a2e980 00000000`00000000     : fffff805`80f6bdd0 00000000`00000000 00000000`00000001 00000000`00000001 : 0xffffa500`a4a2eb10


SYMBOL_NAME:  clipsp+33c7

MODULE_NAME: clipsp

IMAGE_NAME:  clipsp.sys

STACK_COMMAND: .process /r /p 0xffffa609e4fce0c0; .thread /r /p 0xffffa609ed168080 ; kb

BUCKET_ID_FUNC_OFFSET:  33c7

FAILURE_BUCKET_ID:  0x20001_28_2_clipsp!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {db1ff6f3-6610-55ad-105f-4aa1df3ecbf0}

Followup:     MachineOwner
---------

Answer 1

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.

Please do not upload a very large Memory.dmp file.

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... etc.), then choose to share those and get a share link.

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

Answer 2

The crash is a HYPERVISOR_ERROR bug check (0x20001). This indicates that the Hyper‑V hypervisor on the system encountered a fatal internal error. In the dump, parameter 1 is 0x28, which the analysis text describes as “an internal error was detected in the I/O MMU module,” and the stack shows Hyper‑V and memory‑management code running when the failure occurred.

For this class of bug check, the documented guidance is:

1. Treat it as a serious kernel/virtualization failure rather than an app issue.
2. Use the Windows debugger and the !analyze extension (which has already been done in the log) to confirm the stop code and parameters.
3. From there, troubleshooting focuses on:
   • Hyper‑V / virtualization features (including any other hypervisors such as third‑party VM or anti‑cheat drivers that rely on virtualization).
   • Device/firmware interactions with the IOMMU (chipset, BIOS/UEFI, virtualization settings, and drivers).

Because this is a Windows 11 home scenario and the error is intermittent, practical next steps are:

1. Make sure Windows and all device drivers are fully updated via Windows Update and OEM tools.
2. If Hyper‑V or other virtualization features are not needed (for example, no VMs, WSL2, or virtualization‑based security features in use), disable them in Windows Features and in UEFI/BIOS (VT‑x/AMD‑V, IOMMU/SVM) and test for stability.
3. If virtualization is needed, ensure firmware (BIOS/UEFI) is up to date and that any overclocking is disabled, then monitor for further crashes.
4. If crashes continue, collect the full memory dump and engage support using the stop‑code troubleshooting flow for Windows 11.

For end users, Microsoft directs troubleshooting of blue‑screen/stop‑code errors, including hypervisor‑related ones, through the general BSOD guidance for Windows 11.

---

References:

• Bug Check 0x20001: HYPERVISOR_ERROR
• "0x20001" Stop error when you start a Linux VM in Windows Server 2008 R2 SP1
• Troubleshooting Windows unexpected restarts and stop code errors