Windows 10: Hypervisor_error BSOD on 1803 while running AVD

I am a developer and I often run AVD (Android Virtual Device) to test programs that I am working on. In the past 2 weeks or so, I've encountered three hypervisor_error BSODs while on windows 1803. After the first BSOD, I went and turned of Hyper-V and Docker but the issue seems to have persisted. Each time, the error happens, it takes a long time before the computer even restarts and most times I don't even get a dump file. The BSODs always happen while AVD is running.

If anyone could help me or point me in the right direction I would appreciate it. I need this to be resolved for the sake of my work and using an alternative like Genymotion is not really an option that I want to explore if I can help it.

Currently on version 1809 amd64 with the latest updates installed. All Drivers seem to be up to date and windows defender does not show any Viruses or malicious software.

:)

 

Windows 10 BSoD HYPERVISOR_ERROR

I originally upgraded my Windows 8.1 Pro with Media Center using the "Media Creation Tool".

I used the Windows "Reset" tool in the "Update & Security" section of settings after receiving a KMODE_EXCEPTION_NOT_HANDLED BSoD that eliminated the possibility of returning to Windows 8.1 Pro with Media Center and also lost the ability to reinstall "Windows
DVD Player" (See "Windows 10 Pro Blue Screen Error" post on 8/15/2015).

I have not had any problems with the system until the HYPERVISOR_ERROR BSoD on 8/25/2015. I have since received the same HYPERVISOR_ERROR BSoD today, 8/26/2015 before receivng your instructions.

I followed your instructions for the HYPERVISOR_ERROR BSoD to uninstall and reinstall the AMD Radeon R9 270 Display Adapter driver to the latest Catalyst 15.7.1 version for Windows10 (64 bit).

I have turned off Windows Defender because I repeatedly get the Windows Update for the same Defender Definition but Windows 10 Pro turns it back on automatically after a restart.

I will let you know if I get the BSoD again since the Display Adapter driver update.

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.

 

7 different BSoD

Hey guys,

I have a serious problem. I make it as short as possible:

• system runs 100 % fine with the 10.12
• updatet to Catalyst 11.1 -> BSoD
• updatet to 11.1 Hotfix -> BSoD
• rollback to 10.12 -> BSoD
• removed ALL AMD files manually, installed 10.12 -> BSoD

• Temps are fine
• no sfc /scannow errors
• no chkdsk errors
• Prime, Furmark all fine
• regardless what driver I install -> BSoD
• I did no hw changes, no OC

Here are my BSoDs I receive:

• 0x0000010e
• 0x1000007e
• 0x0000007e
• 0x0000004e
• 0x0000003b
• dxgmms1.sys
• PFN_LIST_CORRUPT

They all refer to the GPU of course ...

From now on I receive a BSoD every time I try to play a game (especially BC2 and SC II) even if I completely remove the old driver and make a clean install.
Apparently the 11.1 damaged my system irreparable.

Any advice or info would be very much appreciated *Smile