Hypervisor Error BSOD. Please Help!
Solution: I checked my device manager and found two USB devices with problems. I have no idea what they are and I disabled them and everything seems to be working with no more blue screens.
I've been experiencing BSOD errors for the past couple of months. First time I brought it into a shop to fix and found out it was due to a faulty hard drive. I thought that would be all but now I'm getting pretty much exclusive Hypervisor Error BSODs only when playing games. Not sure what's causing it at all. I've included a link to one drive with my dump files for the past few months and my system files.
Here's what I get from WinDbg if it helps:
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.235 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 42
Microsoft (R) Windows Debugger Version 10.0.27704.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\100524-12312-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22621 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff801`2c600000 PsLoadedModuleList = 0xfffff801`2d2134f0
Debug session time: Sat Oct 5 16:23:43.415 2024 (UTC - 4:00)
System Uptime: 4 days 22:20:13.262
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`2ca14fd0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9701`11e0dcb0=0000000000020001
17: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
HYPERVISOR_ERROR (20001)
The hypervisor has encountered a fatal error.
Arguments:
Arg1: 0000000000000011
Arg2: 000000000023f3be
Arg3: 0000000000001005
Arg4: ffffe70000c05ee0
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 218
Key : Analysis.Elapsed.mSec
Value: 2348
Key : Analysis.IO.Other.Mb
Value: 19
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 25
Key : Analysis.Init.CPU.mSec
Value: 125
Key : Analysis.Init.Elapsed.mSec
Value: 62049
Key : Analysis.Memory.CommitPeak.Mb
Value: 91
Key : Analysis.Version.DbgEng
Value: 10.0.27704.1001
Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre
Key : Analysis.Version.Ext
Value: 1.2408.27.1
Key : Bugcheck.Code.LegacyAPI
Value: 0x20001
Key : Bugcheck.Code.TargetModel
Value: 0x20001
Key : Dump.Attributes.AsUlong
Value: 1808
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
Key : Failure.Bucket
Value: 0x20001_11_23f3be_nt!HvlSkCrashdumpCallbackRoutine
Key : Failure.Hash
Value: {2bd6b6ed-2f8f-2ee0-0bc4-8229acc2dfce}
Key : Hypervisor.Enlightenments.ValueHex
Value: 1417df84
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1
Key : Hypervisor.Flags.ApicEnlightened
Value: 0
Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1
Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0
Key : Hypervisor.Flags.CpuManager
Value: 1
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 1
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: 21631230
Key : Hypervisor.Flags.ValueHex
Value: 14a10fe
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: 3f7
Key : Stack.Pointer
Value: NMI
BUGCHECK_CODE: 20001
BUGCHECK_P1: 11
BUGCHECK_P2: 23f3be
BUGCHECK_P3: 1005
BUGCHECK_P4: ffffe70000c05ee0
FILE_IN_CAB: 100524-12312-01.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump
FAULTING_THREAD: ffffc98186fe2040
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff9701`11e0dca8 fffff801`2cb45881 : 00000000`00020001 00000000`00000011 00000000`0023f3be 00000000`00001005 : nt!KeBugCheckEx
ffff9701`11e0dcb0 fffff801`2cab7ee8 : 00000000`00000100 fffff801`2c91769c ffff9701`11e1b3d0 ffff9701`11e0dd30 : nt!HvlSkCrashdumpCallbackRoutine+0x81
ffff9701`11e0dcf0 fffff801`2ca23082 : 00000000`00000100 ffff9701`11e0def0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x1a0d28
ffff9701`11e0dd30 fffff801`2ca22dee : 00000000`00000100 ffff9701`11e0def0 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
ffff9701`11e0de70 fffff801`2c92ff4a : fffff7f2`4001ed50 ffffc981`9443b000 00000000`00989680 00000000`00989680 : nt!KiNmiInterrupt+0x26e
fffffd04`badc7510 fffff801`2c837f87 : 000003df`e3c6ee8b 00000000`00000003 00000000`00000003 00000000`00000000 : nt!HalpLbrResumeRecording+0xa
fffffd04`badc7540 fffff801`2c8377d1 : ffffc981`9443b860 00000000`00000000 ffffffff`ffffffff fffffd04`badc79f0 : nt!PpmIdleExecuteTransition+0x587
fffffd04`badc7990 fffff801`2ca19f94 : 00000000`00000000 00000000`00000000 ffffc981`86fe2040 ffffc981`886f4040 : nt!PoIdle+0x361
fffffd04`badc7b80 00000000`00000000 : fffffd04`badc8000 fffffd04`badc1000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54
SYMBOL_NAME: nt!HvlSkCrashdumpCallbackRoutine+81
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.22621.4249
STACK_COMMAND: .process /r /p 0xfffff8012d348f40; .thread 0xffffc98186fe2040 ; kb
BUCKET_ID_FUNC_OFFSET: 81
FAILURE_BUCKET_ID: 0x20001_11_23f3be_nt!HvlSkCrashdumpCallbackRoutine
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {2bd6b6ed-2f8f-2ee0-0bc4-8229acc2dfce}
Followup: MachineOwner
---------
Windows for home | Windows 11 | Performance and system failures
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.
6 answers
Sort by: Most helpful
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more