Share via

Windows 11 Hypervisor_error BSOD while executing python script

Anonymous
2023-12-31T02:46:15+00:00

I recently upgraded my PC (mother board, CPU and RAM), I did a clean install.

I am receiving regular chrashes and blue screen death errors while executing python scripts on Windows Visual Studio Code! Please help asap!

Below you can see the outcome of minidump results:

Minidump file: https://drive.google.com/file/d/1jrcePwuLraBRzMQk4Y2jgBMGT9FxqBRs/view?usp=sharing

or analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`6b216b00 48894c2408      mov     qword ptr [rsp+8],rcx ss:fffff800`6d325cb0=0000000000020001
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

HYPERVISOR_ERROR (20001)
The hypervisor has encountered a fatal error.
Arguments:
Arg1: 0000000000000011
Arg2: 000000000021d399
Arg3: 0000000000001005
Arg4: ffffe70000005a20

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 500

    Key  : Analysis.Elapsed.mSec
    Value: 1902

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    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_21d399_nt!HvlSkCrashdumpCallbackRoutine

    Key  : Failure.Hash
    Value: {258844d1-0d80-ebff-246a-cb66f43cdc12}

    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

BUGCHECK_CODE:  20001

BUGCHECK_P1: 11

BUGCHECK_P2: 21d399

BUGCHECK_P3: 1005

BUGCHECK_P4: ffffe70000005a20

FILE_IN_CAB:  123123-8796-01.dmp

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

DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  python.exe

STACK_TEXT:  
fffff800`6d325ca8 fffff800`6b344d11     : 00000000`00020001 00000000`00000011 00000000`0021d399 00000000`00001005 : nt!KeBugCheckEx
fffff800`6d325cb0 fffff800`6b2b62da     : 00000000`00000100 fffff800`6b112cac ffff8000`28aff3d0 fffff800`6d325d30 : nt!HvlSkCrashdumpCallbackRoutine+0x81
fffff800`6d325cf0 fffff800`6b224942     : 00000000`00000100 fffff800`6d325ef0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x1a41ea
fffff800`6d325d30 fffff800`6b2246ae     : 00000000`00000100 fffff800`6d325ef0 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
fffff800`6d325e70 00007ffb`665b39d8     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiNmiInterrupt+0x26e
0000000e`811ef630 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`665b39d8

SYMBOL_NAME:  nt!HvlSkCrashdumpCallbackRoutine+81

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.2861

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  81

FAILURE_BUCKET_ID:  0x20001_11_21d399_nt!HvlSkCrashdumpCallbackRoutine

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {258844d1-0d80-ebff-246a-cb66f43cdc12}

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.

0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sakiko 39,235 Reputation points Independent Advisor
    2024-01-01T07:07:22+00:00

    It still shows the same problem.

    Is the problem only when executing Python code?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-12-31T11:41:10+00:00

    Hello, my computer gave 3-4 blue screens as you suggested trying to verify the drivers. In the end, it couldn't load the boot, so it suggested restoring the latest available point. I just see one dump file after the restart. You can see it below, also attached. Which hardware's driver is the problem? Is it memory RAMs? How can I solve this problem?

    Eray

    Link: https://drive.google.com/file/d/1DZwtXsA7pnyp_rkjwKiKeYqCIun_us-_/view?usp=sharing 

    ************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : false
   AllowNugetExeUpdate : false
   AllowNugetMSCredentialProviderInstall : false
   AllowParallelInitializationOfLocalRepositories : true

   -- 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.016 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

Microsoft (R) Windows Debugger Version 10.0.25877.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\123123-6921-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 (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff801`61816000 PsLoadedModuleList = 0xfffff801`624294a0
Debug session time: Sun Dec 31 12:26:03.910 2023 (UTC + 1:00)
System Uptime: 0 days 0:00:13.579
Loading Kernel Symbols
...............................................................
................................................................
....................................................
Loading User Symbols
PEB address is NULL !
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
nt!CmpCheckValueList+0x1cf:
fffff801`61f5308f 0f8505aa1900    jne     nt!CmpCheckValueList+0x19abda (fffff801`620eda9a) [br=1]
0: kd> analyze -v
Couldn't resolve error at 'nalyze -v'
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80161f5308f, The address that the exception occurred at
Arg3: fffff681a07a2e48, Exception Record Address
Arg4: fffff681a07a2660, Context Record Address

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

KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullClassPtr

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 577

    Key  : Analysis.Elapsed.mSec
    Value: 15222

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1000007e

    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: AV_nt!CmpCheckValueList

    Key  : Failure.Hash
    Value: {c646a796-6880-5537-3ad6-4a9f12a046b8}

    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

BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80161f5308f

BUGCHECK_P3: fffff681a07a2e48

BUGCHECK_P4: fffff681a07a2660

FILE_IN_CAB:  123123-6921-01.dmp

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

DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

EXCEPTION_RECORD:  fffff681a07a2e48 -- (.exr 0xfffff681a07a2e48)
ExceptionAddress: fffff80161f5308f (nt!CmpCheckValueList+0x00000000000001cf)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 000000000000011c
Attempt to read from address 000000000000011c

CONTEXT:  fffff681a07a2660 -- (.cxr 0xfffff681a07a2660)
rax=0000000000000004 rbx=fffff681a07a3398 rcx=0000000000000004
rdx=0000000000000004 rsi=fffff681a07a3940 rdi=ffffc28b6b4cd08c
rip=fffff80161f5308f rsp=fffff681a07a3080 rbp=fffff681a07a3159
 r8=0000000000000001  r9=0000000000000004 r10=fffff681a07a30b8
r11=0000000003fef040 r12=0000000000000000 r13=ffffc28b6b4cd000
r14=0000000003fef060 r15=0000000000000007
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050202
nt!CmpCheckValueList+0x1cf:
fffff801`61f5308f 0f8505aa1900    jne     nt!CmpCheckValueList+0x19abda (fffff801`620eda9a) [br=1]
Resetting default scope

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Registry

READ_ADDRESS: fffff80162533470: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 000000000000011c 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  000000000000011c

EXCEPTION_STR:  0xc0000005

STACK_TEXT:  
fffff681`a07a3080 fffff801`61f51573     : ffffc28b`6b4cd000 ffffc28b`6b4cd000 fffff681`a07a3940 00000000`ffffffff : nt!CmpCheckValueList+0x1cf
fffff681`a07a31a0 fffff801`61f539f6     : ffffc28b`6b4cd000 00000000`01590001 ffffc28b`03feeea0 00000000`ffffffff : nt!CmpCheckKey+0xf63
fffff681`a07a32a0 fffff801`61f915a0     : ffffc28b`00000007 ffffc28b`01590001 fffff681`a07a3398 fffff681`00000000 : nt!CmpCheckRegistry2+0xe6
fffff681`a07a3350 fffff801`61ea5f1c     : 00000000`00000000 fffff681`01590001 00000000`00000000 ffffc28b`00010000 : nt!CmCheckRegistry+0x178
fffff681`a07a3420 fffff801`61ea2cc1     : fffff801`624188a8 ffffb00e`cf623001 ffffb00e`01590001 fffff681`a07a36f4 : nt!CmpCreateHive+0x474
fffff681`a07a3680 fffff801`62024147     : ffffb00e`bddeb080 00000000`00000000 00000000`00000101 00000000`0000000f : nt!CmpInitHiveFromFile+0x225
fffff681`a07a3850 fffff801`61b1d167     : ffffb00e`cf6020c0 ffffb00e`cf6020c0 fffff801`62024020 00000000`00000002 : nt!CmpLoadHiveThread+0x127
fffff681`a07a3b30 fffff801`61c31b94     : ffffe481`e5d51180 ffffb00e`cf6020c0 fffff801`61b1d110 00000000`00000000 : nt!PspSystemThreadStartup+0x57
fffff681`a07a3b80 00000000`00000000     : fffff681`a07a4000 fffff681`a079d000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME:  nt!CmpCheckValueList+1cf

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.2861

STACK_COMMAND:  .cxr 0xfffff681a07a2660 ; kb

BUCKET_ID_FUNC_OFFSET:  1cf

FAILURE_BUCKET_ID:  AV_nt!CmpCheckValueList

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c646a796-6880-5537-3ad6-4a9f12a046b8}

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

    Was this answer helpful?

    0 comments
  3. Sakiko 39,235 Reputation points Independent Advisor
    2023-12-31T03:20:13+00:00

    Hello, I'm A&K, here to help.

    The information you have provided indicates a problem with the system kernel, usually caused by a driver, which we need to verify further. Please first create a restore point for your system, then please refer to this article: https://learn.microsoft.com/en-us/windows-hardw... to validate the driver. In the third step select "Automatically select all drivers installed on this computer", wait for a couple of new blue screens and then collect 2-3 copies of the dump file and share the new dump file with me.

    If the computer has any automatic overclocking features enabled (including XMP, PBO, etc.) or manual overclocking, please restore the defaults first.

    Driver verification puts heavy pressure on the drivers in your system to troubleshoot drivers that are in poor condition or misbehaving. It is normal for your computer to run slowly after driver validation is turned on. The computer will also crash more frequently and generate dump files during this process.

    If your system fails to boot after driver verification is turned on, restore the state via a restore point.

    Was this answer helpful?

    0 comments