in the lab tested. reviewed. verdictized.
Hypervisor hell with AMD & NZXT
LAB NOTES
One little program that stole multiple days of my life
ZAK STOREY, CONTRIBUTOR
I’m a massive advocate of regularly reinstalling Windows. Whenever anyone asks me for advice on buggy operating systems, it’s my first port of call. Conflicts, bugs, corrupt Windows updates, odd registry keys, they all lead to issues, and most if not all can be fixed with a clean (internetless) install of Windows 11. I personally do it every three to six months.
This time, I decided to do a system swap, too, and move over to last issue’s build (but with tweaks to storage and GPU; I was fed up with Intel and the 14th-gen drama). I swapped the hardware, got Windows installed, and began running through my program installs and updates. Everything was going fine, then bam. Hypervisor error, blue screen of death. Restart, log in, go again, and it was a constant feed of blue screens. I perused the internet for information but with little joy. Hypervisor errors can occur for all manner of reasons, from failed storage sectors, memory instability, and aggressive overclocks, to corrupt drivers. It’s tied to the Hyper-V virtual machine systems on Windows itself.