Reoccurring blue screen.

[Jock]

Hello. Sorry my first time visiting this forum so forgive me if I miss information or post this in the wrong place.

Today I was sitting on desktop just listening to Spotify when my PC crashed and gave me a blue screen with a stop code: Hypervisor_error.
I let the system reboot and it blue screened again before I even got to desktop with the same error. After hard rebooting it then went into a never ending cycle of blue screen/reboots but the stop error starting alternating between “hypervisor_error” and “unexpected_kernal_mode_trap”.

It would be safe to assume I have very little knowledge of the intricacies of hardware and software issues, so if anyone can help, that would be great. I have added a screen shot of my spec from my PC specialist account screen.

 

[SpyderTracks]

What are you using hyperV for?

Firstly, create a bootable windows usb direct from Microsoft.

The boot into it, and select "repair this computer"

The go through the following to run startup repair on the system

How to Boot or Repair Windows computer using the Installation Media

Guide to repair Windows 11/10 installation in-place using the bootable Installation USB or DVD without losing data. Repair UEFI or BIOS bootloader.

www.thewindowsclub.com

Hopefully that should get you into windows, if not, then you need to create a bootable Memtest86 USB and do a full scan with that

MemTest86 - Official Site of the x86 Memory Testing Tool

MemTest86 is the original self booting memory testing software for x86 and ARM computers. Supporting both BIOS and UEFI, with options to boot from USB.

www.memtest86.com

 

[Jock]

What are you using hyperV for?

Firstly, create a bootable windows usb direct from Microsoft.

The boot into it, and select "repair this computer"

The go through the following to run startup repair on the system

How to Boot or Repair Windows computer using the Installation Media

Guide to repair Windows 11/10 installation in-place using the bootable Installation USB or DVD without losing data. Repair UEFI or BIOS bootloader.

www.thewindowsclub.com

Hopefully that should get you into windows, if not, then you need to create a bootable Memtest86 USB and do a full scan with that

MemTest86 - Official Site of the x86 Memory Testing Tool

MemTest86 is the original self booting memory testing software for x86 and ARM computers. Supporting both BIOS and UEFI, with options to boot from USB.

www.memtest86.com

I don’t even know what hypervisor is… as I said, I’m pretty dense with computers. As long as it turns on and I can play games, pretty much all I know.

 

[SpyderTracks]

I don’t even know what hypervisor is… as I said, I’m pretty dense with computers. As long as it turns on and I can play games, pretty much all I know.

Do you do any virtualisation? If not, then once you're back in windows we need to disable HyperV as it shouldn't be on.

 

[Jock]

Do you do any virtualisation? If not, then once you're back in windows we need to disable HyperV as it shouldn't be on.

Not that I’m aware of. I literally use it for games and browsing.

 

[ubuysa]

The Windows hypervisor and Hyper-V are two different animals. Windows runs several virtual machines under the Windows hypervisor. Typically this BSOD is either a hardware problem of a configuration problem.

Can you please download and run the SysnativeBSODCollectionApp and upload the resultant zip file to a cloud service with a link to it here. Be sure to make it public (so we don't have to login to download the zip file).

The SysnativeBSODCollectionApp does not collect any personally identifying information, it's perfectly safe, and it#s used by several respected Windows help forums. You can look at the files in the zip file, mostly they are txt files, but please don't change or delete anything. If you want to know what data these files contain there are full details here.

 

[Jock]

The Windows hypervisor and Hyper-V are two different animals. Windows runs several virtual machines under the Windows hypervisor. Typically this BSOD is either a hardware problem of a configuration problem.

Can you please download and run the SysnativeBSODCollectionApp and upload the resultant zip file to a cloud service with a link to it here. Be sure to make it public (so we don't have to login to download the zip file).

The SysnativeBSODCollectionApp does not collect any personally identifying information, it's perfectly safe, and it#s used by several respected Windows help forums. You can look at the files in the zip file, mostly they are txt files, but please don't change or delete anything. If you want to know what data these files contain there are full details here.

Forgive my possible idiocy, but how do I go about downloading and running anything when I blue screen instantly on boot?

 

[SpyderTracks]

Forgive my possible idiocy, but how do I go about downloading and running anything when I blue screen instantly on boot?

Once you're in windows after the first troubleshooting steps.

 

[Jock]

Once you're in windows after the first troubleshooting steps.

Ok I need access to a other machine to follow your steps first then

 

[ubuysa]

Ah, apologies, you didn't make it clear that it BOSDs on boot. Forget the data collection app for now then.

Please run Memtest86 as advised - run it twice so you do 8 iterations of the 13 different tests, this will take a long time. Alternatively, remove one RAM stick and see whether the BSODs stop, then swap sticks.

Can you start Windows in Safe Mode? Use the technique listed under 'From a black or blank screen'. If it boots in Safe Mode then it's a third-party driver causing the problem and we can tell you how to isolate that.

 

[SpyderTracks]

The Windows hypervisor and Hyper-V are two different animals. Windows runs several virtual machines under the Windows hypervisor.

Is this correct? For windows to be able to do any kind of virtualisation, SVM mode would have to be manually enabled on the motherboard (it's disabled by default). Until then, the CPU virtualised cores don't exist, so windows wouldn't have any way of running vm's.

And there are still plenty of CPU's that don't support virtualisation.

Would surprise me if windows defaulted to enabling the service when the majority of systems weren't able to support it if it could lead to instability?

I thought the hypervisor service was only installed when the Hyper-V module was installed through adding windows components. It's certainly not running on my windows pc's that currently don't have hyper V running.

Also, if you were to try to run a second hypervisor platform while having the hypervisor service running, it errors out until you've uninstalled HyperV as you can't run concurrent hypervisors?

 

[Jock]

Ah, apologies, you didn't make it clear that it BOSDs on boot. Forget the data collection app for now then.

Please run Memtest86 as advised - run it twice so you do 8 iterations of the 13 different tests, this will take a long time. Alternatively, remove one RAM stick and see whether the BSODs stop, then swap sticks.

Can you start Windows in Safe Mode? Use the technique listed under 'From a black or blank screen'. If it boots in Safe Mode then it's a third-party driver causing the problem and we can tell you how to isolate that.

I’ve tried swapping ram sticks in and out and into different seats and have the same issue regardless. Also cannot boot in safe mode, tried this and still instant blue screen.

 

[SpyderTracks]

I’ve tried swapping ram sticks in and out and into different seats and have the same issue regardless. Also cannot boot in safe mode, tried this and still instant blue screen.

And the windows repair?

 

[Jock]

running the media creation tool on my external now. Dont have a USB drive so had to find this. And get ahold of a laptop.

 

[ubuysa]

Is this correct? For windows to be able to do any kind of virtualisation, SVM mode would have to be manually enabled on the motherboard (it's disabled by default). Until then, the CPU virtualised cores don't exist, so windows wouldn't have any way of running vm's.

Whilst it's hard to discern exactly how Windows operates at this level (because it's not documented), the Windows Internals book (which is The Bible on Windows internals) indicates that the hypervisor is always present. The block diagram here, very similar to the one from the Windows Internals book, shows that the hypervisor, at minimum, splits the kernel into two 'virtual trust levels', one (VTL0) running Virtualisation Based Security (if active) and kernel device drivers, and the other (VTL1) running the user-mode functions. This is the level of hypervisor functions that is always present on Windows 10/11 - it will be in this area that the 0x20001 hypervisor BSODs happen. Generally they are caused either by hardware or UEFI config configuration mismatches or by real hardware failures.

I’ve tried swapping ram sticks in and out and into different seats and have the same issue regardless. Also cannot boot in safe mode, tried this and still instant blue screen.

If it BSODs starting in Safe Mode then it's almost certainly a hardware (or configuration) problem. @SpyderTracks knows far more about hardwaree than I do, so I will defer to him there.

• Have you made any BIOS changes recently?
• Have you installed any devices/drivers recently?
• Can you also try starting Windows using the 'last known good configuration'?
• Do you hear any more than the single POST beep?

 

[Jock]

Whilst it's hard to discern exactly how Windows operates at this level (because it's not documented), the Windows Internals book (which is The Bible on Windows internals) indicates that the hypervisor is always present. The block diagram here, very similar to the one from the Windows Internals book, shows that the hypervisor, at minimum, splits the kernel into two 'virtual trust levels', one (VTL0) running Virtualisation Based Security (if active) and kernel device drives, and the other (VTL1) running the user-mode functions. This is the level of hypervisor functions that is always present on Windows 10/11 - it will be in this area that the 0x20001 hypervisor BSODs happen. Generally they are caused either by hardware or UEFI config configuration mismatches or by real hardware failures.

View attachment 40637


If it BSODs starting in Safe Mode then it's almost certainly a hardware (or configuration) problem. @SpyderTracks knows far more about hardwaree than I do, so I will defer to him there.

• Have you made any BIOS changes recently?
• Have you installed any devices/drivers recently?
• Can you also try starting Windows using the 'last known good configuration'?
• Do you hear any more than the single POST beep?

Nope, I’ve made no changes to bios or hardware at all. Only one beep too. Running this windows 11 media creation tool is failing on my external too. Great. 😅

 

[ubuysa]

You need to run the Media Creation Tool on a different PC/laptop.

 

[TonyCarter]

I didn't realise SVM was supposed to be OFF by default, and only realised when I was getting some messages on benchmarking tools about results being invalid due to virtualisation. Realised that SVM was enabled on my new build BIOS.

 

[Jock]

You need to run the Media Creation Tool on a different PC/laptop.

I am running it on a different laptop on the external I will plug into my PC but it’s downloading then failing when it comes to the install.

 

[SpyderTracks]

I didn't realise SVM was supposed to be OFF by default, and only realised when I was getting some messages on benchmarking tools about results being invalid due to virtualisation. Realised that SVM was enabled on my new build BIOS.

That’s what I was wondering, it’s very possible that PCS enable it by default.