HYPERVISOR_ERROR after Windows update #5288

ad-on-is · 2020-05-29T06:10:46Z

I don't know if this is realted to WSL or not, but since a view Windows versions back, I am getting a green screen when updating Windows. The error message is HYPERVISOR_ERROR.

Althouh, after I force-restart my PC the update finishes successfully and everything works just fine, I'm still worried that something more serious and unexpected might happen in the future.

onomatopellan · 2020-05-29T13:45:17Z

What's the CPU?

ad-on-is · 2020-05-29T13:47:17Z

What's the CPU?

i7-8750H

onomatopellan · 2020-05-29T13:50:35Z

And you see the error only during the build install and then never again until next build install? I guess disabling Virtualization on BIOS would prevent the GSOD but you will need to enable it again for WSL2.

ad-on-is · 2020-05-29T13:57:40Z

@onomatopellan Exaclty, the last reboot of the build install causes the GSOD. Toggeling virtualization in BIOS is not the solution, since I never had this issue before. It started 3-4 builds ago.

onomatopellan · 2020-05-29T14:33:42Z

If it's on last reboot then it could be a driver that crashes with virtualization enabled. You could look at Event viewer if there was some error by that time.

therealkenc · 2020-05-29T23:29:44Z

The error message is HYPERVISOR_ERROR.

I've seen one of these second hand. You can try sending a minidump per the template if have one. Usually (historically) GSODs do sort themselves in forthcoming insider builds eventually (often pretty quick).

Please direct all Windows crashes and security issues to secure@microsoft.com. Ideally, please configure your machine to capture minidumps, repro the issue, and send the minidump from "C:\Windows\minidump".\

ad-on-is · 2020-05-30T07:34:22Z

@therealkenc Automatic memory dump was already enabled in the settings. The MEMORY.DMP is 2GB. I assume, I should change it to Small memory dump, wait until the next GOSOD happens and then provide that 256kb file to Microsoft, right?

BTW: Yesterday I installed 2 builds, the first one resulted in a GSOD, the second one did not.

therealkenc · 2020-05-30T18:21:40Z

and then provide that 256kb file to Microsoft, right?

Yes, if you'd like.

onomatopellan · 2020-05-30T21:23:18Z

I think this is new. Helps to diagnostic faulty installs.
https://docs.microsoft.com/en-us/windows/deployment/upgrade/setupdiag

keesvanbochove · 2020-06-01T09:58:25Z

I have a HYPERVISOR_ERROR GSoD occassionally on build 19041, this happens since I've enabled Windows Insider Program and downloaded this build. I have enabled WSL2 and installed Docker, but I even get the error when Docker is not running. Other people seem to have similar issues (https://www.reddit.com/r/windowsinsiders/comments/gkph4y/gsod_with_hypervisor_error_but_only_for_the_first/). My processor is an AMD Ryzen 9 3950X.

msarson · 2020-06-04T14:45:01Z

I am having the same issue as well for the last few fast ring flight builds. Intel Core i7-9700K, docker running inside WSL2

As reported, the first try at installing a new insider gives the green screen, but you get a successful update on the second attempt.

nithinmohantk · 2020-06-06T11:12:55Z

I am having same issue with Build 19635, it is not updating further as every windows update crashes with BSOD - "HYPERVISOR_ERROR" , I too have docker for Windows with WSL enabled.

Update - I switched the docker from WSL(disable WSL from docker settings, and switch back to default Hyper-V based). This actually helped to get rid off the error. I believe WSL is not ready yet. One time it killed my docker completely, i couldn't get it working. So I had to reinstall windows freshly. WSL is so much unstable with docket on Windows.

ivanmonteiro · 2020-06-09T05:26:28Z

I'm on insiders fast ring build 19640 + wsl 2 + docker desktop. My laptop is a Dell G3 with i7 8750H.
I did NOT have this error while I was on slow ring build 19041.264 + wsl 2 + docker desktop.

I'm having a green screen of death with HYPERVISOR ERROR. It hapens on first boot, right after login screen appears or in the first minutes of usage. After a reboot, the computer works flawlessly without any green screen of death.
So basically it happens on 90% of first boot of a day, and it almost certainly does not hapen on the next couple of boots at the same day. On the next day, however, there is a 90% chance of getting a GSOD on the first boot.

Disabled docker desktop initialization, but keep getting GSOD.
If I would guess, maybe something is running a daily task (or some sort of task) that is causing the crash.

patricknazar · 2020-06-12T06:26:14Z

yes I also have the same issue. First boot of the day, even if i've been up overnight and restart the computer that morning. Windows insiders fast ring 2004 build 19640.1

One way with dealing with this problem is when I see that docker isn't starting, or when it pops up giving me a seemingly different but similar error (can't connect, no response, etc) I just preemptively restart the computer and docker will start upon boot and I won't get the sudden devastation of having my work taken away from me with a GSOD

ad-on-is · 2020-06-12T07:43:26Z

I'm having a green screen of death with HYPERVISOR ERROR. It hapens on first boot, right after login screen appears or in the first minutes of usage. After a reboot, the computer works flawlessly without any green screen of death.
So basically it happens on 90% of first boot of a day, and it almost certainly does not hapen on the next couple of boots at the same day. On the next day, however, there is a 90% chance of getting a GSOD on the first boot.

The only GSOD I see, is, as I already described, while updating. After that, I never experience GSODs again, no matter how often I restart the PC.

patricknazar · 2020-06-13T14:14:30Z

I got one during an update to 19645.1 last night, same error. Luckily the pc wasn't "bricked" and i just had to restart the update upon restart for it to work

ivanmonteiro · 2020-06-13T19:53:06Z

What's the CPU?

i7-8750H

@ad-on-is I have the same CPU on my notebook and I'm also having green screen of death with hypervisor error usually on first boot.

rafaels-dev · 2020-06-14T14:23:48Z

I also have same issue. My processor is i5-4440. The error started after I updated WSL Kernel for use Docker Desktop with WSL2 backend.
I uninstalled docker, but my WSL2 (Ubuntu) become unstable. Terminal freeze on some commands and every time I try to restart WSL using wsl --shutdown command, the green screen appears with HYPERVISOR_ERROR.

rafaels-dev · 2020-06-14T14:43:58Z

I also have same issue. My processor is i5-4440. The error started after I updated WSL Kernel for use Docker Desktop with WSL2 backend.
I uninstalled docker, but my WSL2 (Ubuntu) become unstable. Terminal freeze on some commands and every time I try to restart WSL using wsl --shutdown command, the green screen appears with HYPERVISOR_ERROR.

I did "reset" on my Ubuntu following the procedure described in this article and ubuntu terminal become stable again: https://petri.com/how-to-uninstall-and-reset-windows-subsystem-for-linux-distributions

ivanmonteiro · 2020-06-16T16:47:24Z

I uninstalled docker desktop, all wsl distros installed by the windows store, disabled the windows features of WSL and virtualization plataform.

Previously I had with no success downloaded updated drivers and reinstalled all drivers. Also got the latest version of wsl kernel and same issues persisted.

And I'm testing now re-enabling wsl 2 and installed docker desktop again. I will report back in a couple of days if it SOLVED the Green Screen Of Death for me.

EDIT: No problems so far. Uninstalling all distros and disabling wsl2 then re-enabling it solved it for me! 😁

dparker2 · 2020-07-17T00:19:20Z

I am getting this gsod error as well on build 20161. I do not use docker for windows since I have a home edition. However, I did recently upgrade the WSL 2 kernel, so it may have to do with that.

0nOff · 2020-07-22T05:36:08Z

Disabling the hypervisor helped me (win 10 pro 2004 20161.1000)

Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Hypervisor

therealkenc · 2020-07-22T17:49:13Z

There was some traffic in today's 20175 announce:

That might be us. If folks still experience the HYPERVISOR ERROR GSOD in 20175 or better (but not before) please add a comment to help track whether we can call this nominally addressed. [Noting it is tough to prove a negative.]

ad-on-is · 2020-07-22T20:56:47Z

@therealkenc I just upgraded to 20175 and got the HYPERVISOR_ERROR again. Is this supposed to
happen with this update, while all future updates should be fixed? Or shouldn't it even happen on this update?

therealkenc · 2020-07-22T21:11:18Z

Hmm... I suppose one could be an optimist and plausibly imagine one last GSOD hurrah before the fix was actually applied by the update. But I wouldn't deign to give odds on that until the next roll. Thanks for the feedback: very good to know either way.

ivanmonteiro · 2020-07-23T14:21:41Z

@therealkenc I just upgraded to 20175 and got the HYPERVISOR_ERROR again. Is this supposed to
happen with this update, while all future updates should be fixed? Or shouldn't it even happen on this update?

If hypervisor error persists,
try uninstalling any distros (and docker desktop if you use it) and disabling virtualization platform and wsl on Windows features.
Then restart and install wsl again.
This worked for me.

therealkenc · 2020-07-23T14:46:21Z

This worked for me.

Noting it is tough to prove a negative (an absence of GSOD).

try uninstalling any distros

There is no particular reason why uninstalling especially a distro would have any effect whatso on a kernel bugcheck (it wouldn't). Likewise while you've got nothing to lose (in the hydroxychloroquine sense) by doing a disable/enable Virtual Machine Platform rain dance, there is no particular reasoning to support doing that would actually help (versus whatever the 20175 Windows Update does by itself).

ivanmonteiro · 2020-07-23T16:58:33Z

This worked for me.

Noting it is tough to prove a negative (an absence of GSOD).

try uninstalling any distros

There is no particular reason why uninstalling especially a distro would have any effect whatso on a kernel bugcheck (it wouldn't). Likewise while you've got nothing to lose (in the hydroxychloroquine sense) by doing a disable/enable Virtual Machine Platform rain dance, there is no particular reasoning to support doing that would actually help (versus whatever the 20175 Windows Update does by itself).

You have a point about that.
I'm on older windows version, and what can I say, It worked for me.
I was having daily GSOD with hypervisor_error code and removing distros, disabling WSL on windows features and re-installing it stopped those daily GSODs I was having. This was the only change I made to my system that actually stopped those GSODs.

Remember it will take a while until everybody gets the new build 20175.

patricknazar · 2020-07-26T17:39:24Z

While it would seem I am no longer getting this (I'll update if I do), wsl2 still doesn't work "first boot of the day" and I have to restart the computer. Previously I could tell that the GSOD was coming as nothing wsl2 would start, I'd restart and all was well (for the most part). Now, I still have to restart the computer to get wsl2 working. Docker-desktop gives me stdout: The operation timed out because a response was not received from the virtual machine or container. and Ubuntu just sits in black window i.e. won't start. There is something else going on and it's related to this, somehow.

Update: I left the computer running for a while and it eventually started. It's still broken, and I find it super disruptive, but so far still no GSOD

Update: This doesn't appear to be a problem for me anymore

Windows 10 version 2004 build 20175.1000
AMD Ryzen 7 2700X

rlperez · 2020-10-25T07:00:19Z

Presumably this will be fixed soon? This has gotten worse after I moved to an insider build hoping for a fix as it's been an ongoing issue already but it's been exponentially getting worse. My computer barely runs for 10 minutes before blowing up. I'm going to have to clean install to another operating system since I keep crashing all over the place including in the middle of meetings with this specific problem. First boot of the day is the least of the problems if it crashes by time I get all my software in order. The only time the system is remotely stable (and it's still not on this build perfect as I expected) is if hypervisor is off at a hardware level. Disabling the additional options in the software made no impact. I'm using WSL2. Had to reboot 3 times in the time it took me to type this.

Last boot crashed before I could even finish typing the build number.

Build 20241
AMD Ryzen 5 3600

Woops. Happened again before I could hit send.

alexbond73 · 2021-04-12T06:36:58Z

I have Dev channel preview Windows 10 Pro build 21354.1 installed, to be able to run Hyper-V with AMD Ryzen 5 series CPU.
The VM was created 'version 10', from PowerShell (Admin) as:

New-Vm -VMName "Win10 10" -Version 10.0 -Generation 2 -MemoryStartupBytes 10220MB
Set-VMProcessor "Win10 10" -Count 6 
Add-VMHardDiskDrive -VMName "Win10 10" -Path "Path\VMdisk.vhdx"
Set-VMProcessor "Win10 10" -ExposeVirtualizationExtensions $true

I needed the nested virtualization on, for the sake of running WSL2 linux.
Unfortunately I was getting HYPERVISOR_ERROR and a complete halt of the host machine, with the Green Screen of Death, and 0% progress collecting debug data.
The VM became stable only after switching off the nested virtualization feature.

Set-VMProcessor "Win10 10" -ExposeVirtualizationExtensions $false

cicorias · 2021-05-02T02:32:38Z

hmm, this is happening on a brand new Surface Laptop 4, i7/32gb/1TB 15"...

Be great to get an update. I'm NOT on Insiders

I can provide the minidump files as well, see the !analyze -v output below:


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


Loading Dump File [C:\Windows\Minidump\050121-15734-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 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff804`1c000000 PsLoadedModuleList = 0xfffff804`1cc2a130
Debug session time: Sat May  1 21:58:59.301 2021 (UTC - 4:00)
System Uptime: 1 days 23:53:36.430
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........................................................
Loading User Symbols
Loading unloaded module list
................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`1c3f6cf0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff804`1fad2ca0=0000000000020001
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

HYPERVISOR_ERROR (20001)
The hypervisor has encountered a fatal error.
Arguments:
Arg1: 0000000000000011
Arg2: 0000000000241a42
Arg3: 0000000000001005
Arg4: fffff84c4b651a30

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2468

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 8348

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

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

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


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


DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  20001

BUGCHECK_P1: 11

BUGCHECK_P2: 241a42

BUGCHECK_P3: 1005

BUGCHECK_P4: fffff84c4b651a30

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

BAD_STACK_POINTER:  fffff8041fad2c98

STACK_TEXT:  
fffff804`1fad2c98 fffff804`1c4f3f5b     : 00000000`00020001 00000000`00000011 00000000`00241a42 00000000`00001005 : nt!KeBugCheckEx
fffff804`1fad2ca0 fffff804`1c50da38     : 00000000`00000001 00000000`ffffffff fffff804`1707b180 fffff804`1c520330 : nt!HvlSkCrashdumpCallbackRoutine+0x6b
fffff804`1fad2ce0 fffff804`1c402382     : 00000000`00000001 fffff804`1fad2ef0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0xe8
fffff804`1fad2d30 fffff804`1c402152     : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
fffff804`1fad2e70 fffff804`1c38d96d     : 00000191`765fa87b fffff804`1707b180 00000000`00000000 0000d067`aeff0943 : nt!KiNmiInterrupt+0x212
fffff804`1faadfb0 fffff804`1c2184b6     : 00000000`000030cc 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PpmIdleGuestExecute+0x1d
fffff804`1faadff0 fffff804`1c217274     : ffffffff`ffffffff ffff950a`c0182840 00000000`00405a04 00000000`00000002 : nt!PpmIdleExecuteTransition+0x10c6
fffff804`1faae3f0 fffff804`1c3fa814     : 00000000`00000000 fffff804`1cd26a00 ffff950a`b9b9e0c0 00000000`00000b74 : nt!PoIdle+0x374
fffff804`1faae560 00000000`00000000     : fffff804`1faaf000 fffff804`1faa8000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54


SYMBOL_NAME:  nt!HvlSkCrashdumpCallbackRoutine+6b

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.964

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  6b

FAILURE_BUCKET_ID:  0x20001_11_241a42_STACKPTR_ERROR_nt!HvlSkCrashdumpCallbackRoutine

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {044f697d-6895-07dc-beac-40a8b0f2945a}

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

SimonHofmann1 · 2021-07-19T14:03:43Z

@cicorias I got exactly the same error with my brand new Surface Laptop 4. With or without Hyper-V enabled. All Surface Checks are Fine with the diagnostigs Tool and with the Memtest. I got this BSOD 3 Times dayli .
I tried with the Cloud Reset and Local Wipe&Load with 20H1 and 20H2. Even with windows 11 I got the same error every time.
Did you find a solution? Is there a Case opened by Microsoft?

cicorias · 2021-07-19T16:36:56Z

@cicorias I got exactly the same error with my brand new Surface Laptop 4. With or without Hyper-V enabled. All Surface Checks are Fine with the diagnostigs Tool and with the Memtest. I got this BSOD 3 Times dayli .
I tried with the Cloud Reset and Local Wipe&Load with 20H1 and 20H2. Even with windows 11 I got the same error every time.
Did you find a solution? Is there a Case opened by Microsoft?

I have a problem report open; I have not seen an update nor was there a fix.

I'll follow up and see if they have an update. Give me some time.

totalgaara · 2021-07-26T22:16:05Z

Same issues on Windows 11 with my AMD FX 8320. Already made an issue, craigloewen was kind to try helping me, my bsod have been sent to Hypervisor Teams, they said that my CPU has an internal issue.. but's that not the case, WSL / Hyper -V in general works fine on W10 on my side, so i don't see any issues with my processor...

SimonHofmann1 · 2021-07-30T13:22:43Z

MiniDumps.zip

Hypervisior_Error don't come alone. It's like a BSOD Bingo with the 4 following outputs:

HYPERVISOR_ERROR (20001)
INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.

In the ZIP File are some Minidumps from the last few days.. happens up to 5 Times dayli.
Very frustrating to work with this Surface Laptop 4. It happens on AC/DC, with External LG USB-C Monitor and without External LG Screen. Really a BSOD Bingo, can happens with any circumstances.

Larisho · 2021-07-30T17:16:04Z

@SimonHofmann1 I'm getting the exact same thing except that the screen hangs at 100% and never writes a dump file.

JonathanVQP · 2021-09-12T22:42:01Z

I am running Windows 11 Build 22000.184 for my amd processor and this issue is still not resolved. If you don't enable WSL2 features and hypervisor, this build runs great without it. However, if you do install WSL2 and hypervisor issues, you get the GSOD with the hypervisor error! Even after the error shows up and you reboot, the Windows 11 runs very slow and will crash intermittently. I don't know if this is due to AMD processors specifically or what....!

dhanar10 · 2021-09-17T14:21:42Z

@SimonHofmann1 I'm getting the exact same thing except that the screen hangs at 100% and never writes a dump file.

I believe I experienced the same issue. Windows 10 fully updated as of today on Lenovo laptop with Ryzen CPU.

zx2c4 · 2021-09-30T16:51:21Z

6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

HYPERVISOR_ERROR (20001)
The hypervisor has encountered a fatal error.
Arguments:
Arg1: 0000000000000011
Arg2: 0000000000307cf9
Arg3: 0000000000001004
Arg4: 0000010002005800

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1952

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 1921

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

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

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

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1


DUMP_FILE_ATTRIBUTES: 0x800

BUGCHECK_CODE:  20001

BUGCHECK_P1: 11

BUGCHECK_P2: 307cf9

BUGCHECK_P3: 1004

BUGCHECK_P4: 10002005800

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

BAD_STACK_POINTER:  ffff930036206ca8

STACK_TEXT:  
ffff9300`36206ca8 fffff806`5b3474db     : 00000000`00020001 00000000`00000011 00000000`00307cf9 00000000`00001004 : nt!KeBugCheckEx
ffff9300`36206cb0 fffff806`5b257c36     : 00000000`00000000 fffff806`5b00b05c ffff9300`360fc3c0 ffff9300`36206d30 : nt!HvlSkCrashdumpCallbackRoutine+0x6b
ffff9300`36206cf0 fffff806`5b21eb82     : 00000000`00000000 ffff9300`36206ef0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x24d666
ffff9300`36206d30 fffff806`5b21e903     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
ffff9300`36206e70 fffff806`5b1964cd     : 00000000`00000000 00000000`0ad7d9f2 00000000`00000000 0000006c`fe775d5e : nt!KiNmiInterrupt+0x243
fffff883`5547f510 fffff806`5b0eaa41     : 00000000`0000029c ffff9300`36180100 00000000`00000000 00000000`0000029c : nt!PpmIdleGuestExecute+0x1d
fffff883`5547f550 fffff806`5b0ea256     : 00000000`00000000 fffff806`5b12b07a ffffffff`ffffffb1 fffff806`5b219ced : nt!PpmIdleExecuteTransition+0x661
fffff883`5547f9f0 fffff806`5b216a74     : 00000000`00000000 ffff9300`3618c440 ffffd286`9caad040 00000000`000005f4 : nt!PoIdle+0x3a6
fffff883`5547fbc0 00000000`00000000     : fffff883`55480000 fffff883`55479000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54


SYMBOL_NAME:  nt!HvlSkCrashdumpCallbackRoutine+6b

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  6b

FAILURE_BUCKET_ID:  0x20001_11_307cf9_STACKPTR_ERROR_nt!HvlSkCrashdumpCallbackRoutine

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b3065167-1c4a-54a5-1ca5-d1a56b1755a3}

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

dhanar10 · 2021-10-03T00:18:10Z

By the way, if you are using Lenovo laptop with AMD Ryzen CPU, you might get hit by this issue instead:

https://answers.microsoft.com/en-us/windows/forum/all/legion-5-15arh05h-multiple-bsods-per-day/9b6bb4a9-2329-4907-af42-774e8deeb32f

https://forums.lenovo.com/t5/Gaming-Laptops/Legion-5-15ARH05-constant-abrupt-restarts/m-p/5047613?page=2#5325241

The BSOD message matches this issue.

TLDR There is probably some problems with Lenovo laptop with Ryzen CPU and the workaround is https://www.reddit.com/r/ZephyrusG14/comments/gho535/important_update_to_properly_disable_boosting/fqzjbvm?utm_medium=android_app&utm_source=share&context=3

After implementing the workaround, I can use WSL2 normally without any hypervisor error BSOD. It works at least on my Lenovo laptop with Ryzen CPU.

asvishnyakov · 2023-03-01T01:32:44Z

Does anyone had a chance to solve issue? Looks like issue related to AMD processors

razorbackdb · 2023-03-13T16:21:17Z

After going back to windows 10 it stopped for me, disabling cpu boost in windows 11 solved it too but that means losing a lot of performance for anything else.

microsoft-github-policy-service · 2024-03-14T12:58:29Z

This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request.

Thank you!

microsoft-github-policy-service · 2024-03-14T12:58:29Z

This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request.

Thank you!

craigloewen-msft added bug and removed bug labels Jun 2, 2020

therealkenc added the ntbugcheck label Jul 28, 2020

patricknazar mentioned this issue Jul 30, 2020

"first boot of the day" takes wsl a long time to start #5680

Closed

microsoft-github-policy-service bot closed this as completed Mar 14, 2024

HYPERVISOR_ERROR after Windows update #5288

HYPERVISOR_ERROR after Windows update #5288

Comments

ad-on-is commented May 29, 2020

onomatopellan commented May 29, 2020

ad-on-is commented May 29, 2020 • edited Loading

onomatopellan commented May 29, 2020

ad-on-is commented May 29, 2020

onomatopellan commented May 29, 2020

therealkenc commented May 29, 2020

ad-on-is commented May 30, 2020

therealkenc commented May 30, 2020

onomatopellan commented May 30, 2020 • edited Loading

keesvanbochove commented Jun 1, 2020

msarson commented Jun 4, 2020

nithinmohantk commented Jun 6, 2020 • edited Loading

ivanmonteiro commented Jun 9, 2020 • edited Loading

patricknazar commented Jun 12, 2020

ad-on-is commented Jun 12, 2020 • edited Loading

patricknazar commented Jun 13, 2020

ivanmonteiro commented Jun 13, 2020

rafaels-dev commented Jun 14, 2020

rafaels-dev commented Jun 14, 2020

ivanmonteiro commented Jun 16, 2020 • edited Loading

dparker2 commented Jul 17, 2020

0nOff commented Jul 22, 2020

therealkenc commented Jul 22, 2020

ad-on-is commented Jul 22, 2020

therealkenc commented Jul 22, 2020

ivanmonteiro commented Jul 23, 2020

therealkenc commented Jul 23, 2020 • edited Loading

ivanmonteiro commented Jul 23, 2020

patricknazar commented Jul 26, 2020 • edited Loading

rlperez commented Oct 25, 2020

alexbond73 commented Apr 12, 2021

cicorias commented May 2, 2021 • edited Loading

SimonHofmann1 commented Jul 19, 2021

cicorias commented Jul 19, 2021

totalgaara commented Jul 26, 2021

SimonHofmann1 commented Jul 30, 2021

Larisho commented Jul 30, 2021

JonathanVQP commented Sep 12, 2021

dhanar10 commented Sep 17, 2021

zx2c4 commented Sep 30, 2021

dhanar10 commented Oct 3, 2021 • edited Loading

asvishnyakov commented Mar 1, 2023

razorbackdb commented Mar 13, 2023

microsoft-github-policy-service bot commented Mar 14, 2024

microsoft-github-policy-service bot commented Mar 14, 2024

ad-on-is commented May 29, 2020 •

edited

Loading

onomatopellan commented May 30, 2020 •

edited

Loading

nithinmohantk commented Jun 6, 2020 •

edited

Loading

ivanmonteiro commented Jun 9, 2020 •

edited

Loading

ad-on-is commented Jun 12, 2020 •

edited

Loading

ivanmonteiro commented Jun 16, 2020 •

edited

Loading

therealkenc commented Jul 23, 2020 •

edited

Loading

patricknazar commented Jul 26, 2020 •

edited

Loading

cicorias commented May 2, 2021 •

edited

Loading

dhanar10 commented Oct 3, 2021 •

edited

Loading