BSOD due to hypervisor error?

Question

BSOD due to hypervisor error?

Anonymous

Ran into a BSOD while playing game. I was able to generate a bugcheck analysis with the dump file, but that's as far as I can get. I can't understand what's causing such problem. Can someone tell me what the root cause of this issue is by looking at the bugcheck analysis please?

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

HYPERVISOR_ERROR (20001)
The hypervisor has encountered a fatal error.
Arguments:
Arg1: 0000000000000011
Arg2: 00000000002f5af0
Arg3: 0000000000001003
Arg4: ffffe70000c05c40

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 811

    Key  : Analysis.Elapsed.mSec
    Value: 2403

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

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

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

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

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

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

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x20001

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x20001

    Key  : Dump.Attributes.AsUlong
    Value: 1800

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 100

    Key  : Failure.Bucket
    Value: 0x20001_11_2f5af0_win32kfull!xxxTimersProc

    Key  : Failure.Hash
    Value: {fe01e3e0-4d77-9c7c-7d9e-540743202989}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1497cf94

    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: 4a10ef

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

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1

BUGCHECK_CODE:  20001

BUGCHECK_P1: 11

BUGCHECK_P2: 2f5af0

BUGCHECK_P3: 1003

BUGCHECK_P4: ffffe70000c05c40

FILE_IN_CAB:  MEMORY.DMP

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

DUMP_FILE_ATTRIBUTES: 0x1800

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME:  csrss.exe

STACK_TEXT:  
fffff807`10122ca8 fffff807`0cd635a1     : 00000000`00020001 00000000`00000011 00000000`002f5af0 00000000`00001003 : nt!KeBugCheckEx
fffff807`10122cb0 fffff807`0ccce0d8     : 00000000`00000100 fffff807`0cb12dec ffffc580`a82ff340 fffff807`10122d30 : nt!HvlSkCrashdumpCallbackRoutine+0x81
fffff807`10122cf0 fffff807`0cc39e42     : 00000000`00000100 fffff807`10122ef0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x1bb7c8
fffff807`10122d30 fffff807`0cc39bae     : 00000000`00000100 fffff807`10122ef0 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
fffff807`10122e70 fffffacf`d2cbcb9b     : ffffda83`78bb81c0 fffffacf`d193887e ffffda83`78bafca0 00000000`00000000 : nt!KiNmiInterrupt+0x26e
ffffa381`45b2c8a0 fffffacf`d2d8edc4     : 00000000`00000000 ffffa381`45b2ca10 00000000`00000002 00000000`00000004 : win32kfull!xxxTimersProc+0x14b
ffffa381`45b2c910 fffffacf`d19758cd     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000020 : win32kfull!RawInputThread+0xd34
ffffa381`45b2ca50 fffffacf`d1975795     : ffffb408`00000002 ffffa381`459cc900 ffffa381`45b2caa8 00000000`00000018 : win32kbase!xxxCreateSystemThreads+0x11d
ffffa381`45b2ca80 fffffacf`d160a6a1     : 00000000`0000000e ffffb408`65f7e5c0 00000000`00000000 00000000`00000000 : win32kbase!NtUserCreateSystemThreads+0x75
ffffa381`45b2cab0 fffff807`0cc40fe8     : ffffb408`000003cb 00000000`ffffffff 00000266`90804950 00000000`00004f28 : win32k!NtUserCreateSystemThreads+0x15
ffffa381`45b2cae0 00007ffb`05178e14     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000089`71effd48 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`05178e14

SYMBOL_NAME:  win32kfull!xxxTimersProc+14b

MODULE_NAME: win32kfull

IMAGE_NAME:  win32kfull.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  14b

FAILURE_BUCKET_ID:  0x20001_11_2f5af0_win32kfull!xxxTimersProc

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {fe01e3e0-4d77-9c7c-7d9e-540743202989}

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

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

Answer 1

Thanks for sharing the minidump file, JinRong

The minidump files did not name any driver only indicating a hardware issue.

To troubleshoot this issue, kindly try the steps below (Skip a step that you have already tried):

If you are overclocking your PC, try running everything (CPU, GPU, system memory) at their stock speeds. See if the issue is still reproducible. Or, turn off XMP profile or set it to Auto.

Download then install the latest version of BIOS & Chipset drivers from the manufacturer's website.

Test the RAM with the free utility MemTest86, then run a full 8 pass scan to test your RAM for physical errors:

https://www.tenforums.com/tutorials/14201-memte...

If you are comfortable of doing so, take all the system memory sticks out, examine them for any obvious defects, and then reseat them into the sockets. Make sure that they are seated properly in their slots. If you have multiple sticks of system memory installed and you suspect one is faulty, one thing to try is to reproduce the issue with only one stick of memory module at a time. This will help you to isolate the faulty module.

If the issue still persists after the steps above, enable the driver verifier and let the computer crash 3 times then disable it and share the newly created minidump file:

https://www.tenforums.com/tutorials/5470-enable...

Please do not hesitate to ask if you need further assistance.

Stay safe.

____________________________________________________________

Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

Answer 2

Anonymous

Will this do?

https://1drv.ms/f/s!AuvoJgIDK83Ksghi1XhOYkzQuvxQ?e=e07dmh

0 comments

Answer 3

Hi JinRong,

I'm Dyari. Thanks for reaching out. I will be happy to assist you in this regard.

Kindly check C:\Windows\Minidump and copy available minidump files to the desktop then share them via One Drive or Google Drive in order to be analyzed and indicate which file is causing the crash.

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

Also, check C:\Windows and share the MEMORY.DMP file.

Regards,

____________________________________________________________

Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

Share via

BSOD due to hypervisor error?

3 answers