Android Studio AVD emulator starts and runs fine for a few mins then becomes unresponsive and causes BSOD

Whenever I run the AVD Emulator on my laptop, it works great for a few minutes, its very responsive and doesn’t lag etc. But after a few minutes it just stops working and clicking on anything has no effect, eventually becomes not responding and ends up crashing my laptop and causing a BSOD with error code "UNEXPECTED KERNEL MODE TRAP". I’ve had a look into this and apparently this could be a RAM issue, so I ran the Windows Memory Diagnostic and it came back with no issues. I’ve reinstalled Android Studio, reinstalled Intel HAXM, tried getting a new Android System image, also found some solution to run the command bcdedit /set hypervisorlaunchtype off in cmd as admin, tried that but it still doesn’t work. Does anyone have any ideas what the issue could be or how to fix it? I’m including Android Studio logs and Windows Event Viewer logs in case there is anything in there that I’ve missed.

In Android Studio logs, these are the last logs it shows:

2021-10-20 01:11:33,479 [ 416852]   INFO - manager.EmulatorProcessHandler - Emulator: emulator: INFO: boot completed 
2021-10-20 01:11:33,479 [ 416852]   INFO - manager.EmulatorProcessHandler - Emulator: emulator: Increasing screen off timeout, logcat buffer size to 2M. 
2021-10-20 01:11:33,479 [ 416852]   INFO - manager.EmulatorProcessHandler - Emulator: emulator: Revoking microphone permissions for Google App. 
2021-10-20 01:13:33,484 [ 536857]   WARN - n.process.BaseOSProcessHandler - Process hasn't generated any output for a long time.
If it's a long-running mostly idle daemon process, consider overriding OSProcessHandler#readerOptions with 'BaseOutputReader.Options.forMostlySilentProcess()' to reduce CPU usage.
Command line: C:Usersw_matAppDataLocalAndroidSdkemulatoremulator.exe -netdelay none -netspeed full -avd Pixel_2_API_29 
java.lang.Throwable: Process creation:
...

And in Event Viewer (there’s a bunch, just pasting in the ones that aren’t repeated, apart from the power management capabilities one as thats repeated a few times):

The description for Event ID 4 from source IntelHaxm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
The driver DriverWudfRd failed to load for the device PCIVEN_8086&DEV_1903&SUBSYS_381F17AA&REV_07&11583659&0&20.
Processor 0 in group 0 exposes the following power management capabilities:

Idle state type: ACPI Idle (C) States (3 state(s))

Performance state type: ACPI Collaborative Processor Performance Control
Nominal Frequency (MHz): 2304
Maximum performance percentage: 173
Minimum performance percentage: 34
Minimum throttle percentage: 4
The description for Event ID 2 from source MEIx64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
Windows cannot store Bluetooth authentication codes (link keys) on the local adapter. Bluetooth keyboards might not work in the system BIOS during start-up.
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
 and APPID 
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
 to the user <my user> SID (S-1-5-21-2691420795-189460331-426176001-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007f (0x0000000000000008, 0xffff910011f3fe50, 0xfffffe0537410f70, 0xfffff80316293524). 

Can anyone see anything wrong with any of these, or know what the solution to this may be?

Source: Windows Questions

LEAVE A COMMENT