Blue Screen with BugcheckCode 131073

Question

Blue Screen with BugcheckCode 131073

Vượng Vũ 15

I have had my PC crash several times since I first got it with an issue regarding BugcheckCode 131073, or a Hypervisor error. I have uploaded the dump (.dmp) file to Google Drive. Please find the link below. I would appreciate it if someone could review it and help identify the root cause.
https://drive.google.com/file/d/1krmvOt5gG0fIqKB718aB5HeXFaazeEmD/view?usp=sharing

2 answers

Your answer

Answer 1

Jonathan Deives 68,395 Independent Advisor

The minidump file do not indicate any driver or hardware causes, only memory corruption.

Do you have more minidump files ?

Vượng Vũ 15

Here it is
https://drive.google.com/file/d/1js8REwxc0jSOwnX6qaE0cgfHE6HdPctm/view?usp=sharing
And i see

Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............
Loading User Symbols

Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff8040b629527, The address that the exception occurred at
Arg3: fffff8040be60060, Parameter 0 of the exception
Arg4: 0000000000000006, Parameter 1 of the exception

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2296

    Key  : Analysis.Elapsed.mSec
    Value: 4974

    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: 312

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29507.1001

    Key  : Analysis.Version.Description
    Value: 10.2511.5.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2511.5.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1e

    Key  : Bugcheck.Code.TargetModel
    Value: 0x1e

    Key  : Failure.Bucket
    Value: 0x1E_C000001D_nt!NtCallEnclave

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff8040b629527

    Key  : Failure.Exception.IP.Module
    Value: nt

    Key  : Failure.Exception.IP.Offset
    Value: 0x429527

    Key  : Failure.Hash
    Value: {e7b503cf-dc1f-d5a2-3142-80890ddc6510}

    Key  : Faulting.IP.Type
    Value: Paged

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x1497cf94

    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: 4853999

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x4a10ef

    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  : SecureKernel.HalpHvciEnabled
    Value: 1

    Key  : Stack.Pointer
    Value: PRCBException

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1


BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc000001d

BUGCHECK_P2: fffff8040b629527

BUGCHECK_P3: fffff8040be60060

BUGCHECK_P4: 6

FILE_IN_CAB:  020826-24203-01.dmp

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


FAULTING_THREAD:  ffffc50670f95040

EXCEPTION_PARAMETER1:  fffff8040be60060

EXCEPTION_PARAMETER2:  0000000000000006

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  afafafafafafafaf -- (.trap 0xafafafafafafafaf)
Unable to read trap frame at afafafaf`afafafaf
Resetting default scope

IP_IN_PAGED_CODE: 
nt!NtCallEnclave+57
fffff804`0b629527 1e              ???

STACK_TEXT:  
ffff9100`29b320e8 fffff804`0b74971a     : 00000000`0000001e ffffffff`c000001d fffff804`0b629527 fffff804`0be60060 : nt!KeBugCheckEx
ffff9100`29b320f0 fffff804`0b6298d2     : ffff9100`29b32900 ffff9100`29b321c0 fffff804`0b200000 fffff804`0b6231f4 : nt!HvlpVtlCallExceptionHandler+0x22
ffff9100`29b32130 fffff804`0b4a3f93     : ffffd80b`c7d4fa50 ffffd80b`c7d4f398 fffff804`0b6231f4 fffff804`0b2edb24 : nt!RtlpExecuteHandlerForException+0x12
ffff9100`29b32160 fffff804`0b50cc6e     : ffffffff`ffffffff ffffd80b`c7d4f440 ffffd80b`c7d4f440 ffff9100`29b32900 : nt!RtlDispatchException+0x2f3
ffff9100`29b328d0 fffff804`0b61f452     : afafafaf`afafafaf afafafaf`afafafaf afafafaf`afafafaf afafafaf`afafafaf : nt!KiDispatchException+0x1ae
ffff9100`29b32fb0 fffff804`0b61f420     : fffff804`0b634275 ffffd80b`c7d4f278 00000000`00000000 ffffd80b`c7d4f398 : nt!KxExceptionDispatchOnExceptionStack+0x12
ffffd80b`c7d4f258 fffff804`0b634275     : ffffd80b`c7d4f278 00000000`00000000 ffffd80b`c7d4f398 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
ffffd80b`c7d4f260 fffff804`0b62d442     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x135
ffffd80b`c7d4f440 fffff804`0b629527     : fffff804`0b6c51ee 00000000`4b5fc06b 00000000`00989680 00000000`00000002 : nt!KiInvalidOpcodeFault+0x342
ffffd80b`c7d4f5d8 fffff804`0b53528f     : fffff804`0b4c67af 00000000`00000000 00000000`00000003 00000000`00000001 : nt!NtCallEnclave+0x57
ffffd80b`c7d4f608 fffff804`0b4c67af     : 00000000`00000000 00000000`00000003 00000000`00000001 ffff9100`29b11180 : nt!MiClearPfnImageVerified+0x77
ffffd80b`c7d4f610 fffff804`0b4c529a     : ffffc506`79bd1e1c 00000000`00000000 ffffc506`79bd1e24 00000000`00000000 : nt!PpmIdleExecuteTransition+0x14bf
ffffd80b`c7d4fa50 fffff804`0b6231f4     : 00000000`00000000 ffffc506`70f95040 ffffc506`8d1c0080 ffffc506`8c486080 : nt!PoIdle+0x76a
ffffd80b`c7d4fc40 00000000`00000000     : ffffd80b`c7d50000 ffffd80b`c7d4a000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54


SYMBOL_NAME:  nt!NtCallEnclave+57

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.6199

STACK_COMMAND: .process /r /p 0xfffff8040bf49f40; .thread 0xffffc50670f95040 ; kb

BUCKET_ID_FUNC_OFFSET:  57

FAILURE_BUCKET_ID:  0x1E_C000001D_nt!NtCallEnclave

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {e7b503cf-dc1f-d5a2-3142-80890ddc6510}

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

Vượng Vũ 15 Reputation points

2026-02-08T16:39:36.65+00:00

Here https://drive.google.com/file/d/1js8REwxc0jSOwnX6qaE0cgfHE6HdPctm/view?usp=drive_link
Jonathan Deives 68,395 Reputation points Independent Advisor

2026-02-08T19:41:26.6366667+00:00

The minidump files do not indicate any driver or hardware causes, only memory corruption.

Try forcing Windows to show failed drivers and produce minidump files, enable Driver Verifier for this.

Before running Driver Verifier, create a new system restore point.

Click on start menu and type "verifier".

Select "Create custom settings (for code developers)" > "Next".

Check all options except "DDI compliance checking" and "Randomized low resource simulation".

Click Next > Select "Select driver names from a list".

Next Select all drivers NOT provided by Microsoft. > Next > Finish.

Restart the system until the BSOD occurs 3 times and minidump files are generated.

If you have problems starting Windows after enabling Driver Verifier, follow these steps:

Start your PC, as soon as Windows tries to load (spinning dots appear), press and hold the power button for 5 to 10 seconds to perform a forced shutdown

Do this three times.

Windows will boot into the Recovery Environment.

Go to Troubleshoot > Advanced Option > Startup Settings and click Restart.

When restarting, press 4 to enter safe mode.

Open command prompt as administrator, run these two commands and restart your PC.

verifier /reset

verifier /bootmode resetonbootfail
Vượng Vũ 15 Reputation points

2026-02-09T07:53:56.9866667+00:00

Hello, I encountered an issue when booting Windows after enabling Driver Verifier. It forced the system into Automatic Repair with the message: “Windows couldn’t load correctly. System Restore can try to restore your PC to an earlier point in time when it worked correctly…” After that, I entered Safe Mode and disabled Driver Verifier. I checked and there is only one dump file. Below is that dump file. If this is not sufficient, I can try reproducing the issue again.
https://drive.google.com/file/d/1R6Fi8odLozDtI4ANSxmfvE4GsVj5lwq6/view?usp=sharing
Jonathan Deives 68,395 Reputation points Independent Advisor

2026-02-09T18:17:36.6566667+00:00

The minidump indicate "vgk.sys", which is Vanguard as the cause of the BSOD, try temporarily uninstalling to see if the problem persists.
Vượng Vũ 15 Reputation points

2026-02-14T06:08:56.58+00:00

My computer shuts down automatically because of this error, and there is no blue screen displayed.
https://drive.google.com/file/d/1-0fFN2OtkhbHpeVMmNgc0zR9k2fNIlre/view?usp=sharing
I also ran verifier /standard /all to test the drivers for about 10 minutes, and the system was still running normally.

Answer 2

Bugcheck Code 131073 typically indicates a hypervisor error, which can be caused by various factors, including issues with virtualization settings, drivers, or hardware conflicts. Here are some steps you can take to troubleshoot this issue:

Check Virtualization Settings: Ensure that virtualization is enabled in your BIOS/UEFI settings. Sometimes, incorrect settings can lead to hypervisor errors.
Update Drivers: Make sure all your drivers, especially those related to virtualization (like chipset and graphics drivers), are up to date. Outdated or incompatible drivers can cause system instability.
Run Hardware Diagnostics: Use the built-in diagnostic tools provided by your PC manufacturer to check for hardware issues. This can help identify if there are any failing components.
Check for Windows Updates: Ensure that your Windows installation is fully updated, as updates often include important fixes for stability and performance.
Analyze the Dump File: If you are familiar with debugging tools, you can analyze the dump file using WinDbg to get more specific information about what caused the crash. This can provide insights into whether a specific driver or hardware component is at fault.
Review Event Viewer Logs: Check the Event Viewer for any critical errors or warnings that occurred around the time of the crashes. This can help pinpoint the source of the issue.

If the problem persists after trying these steps, consider seeking assistance from a professional or the manufacturer's support team for a more in-depth analysis.

References:

Share via

Blue Screen with BugcheckCode 131073

2 answers

Your answer