Assigned
Status Update
No update yet.
Comments
rk...@google.com
Thanks for providing all the details we need! We've accepted this issue and will fix this in an upcoming release.
Join our discussion group (
Please note that you have submitted this information with the knowledge that we may use, modify, reproduce, publicly display, and distribute the information in accordance with our open source policies. Please let us know if you did not intend to submit the information for such use.
ti...@googlemail.com
Hi,
thank you for the quick response.
I did a quick test with WHPX enabled and it might have fixed the issue.
At least the emulator runs fine for like 10 minutes now.
If the problem persists, I'll let you know.
Have a nice day!
Am Do., 6. März 2025 um 16:54 Uhr schrieb <buganizer-system@google.com>:
thank you for the quick response.
I did a quick test with WHPX enabled and it might have fixed the issue.
At least the emulator runs fine for like 10 minutes now.
If the problem persists, I'll let you know.
Have a nice day!
Am Do., 6. März 2025 um 16:54 Uhr schrieb <buganizer-system@google.com>:
Description
Hi,
yesterday I experienced a BSOD when running Android Studio.
I updated the copilot plugin and started the emulator right before the BSOD appeared.
I'll attach the .dmp file for you to check out.
I wouldnt have minded about the BSOD, if it didn't make the whole emulator unusable.
Every time I start up an emulator it takes forever to load, often doesn't start at all and just keeps showing the Google icon and then a blackscreen and this can go on for up to 10 minutes. At some point it either works or doesn't but it always leads to a full pc crash. No BSOD, just straight up crash and restart. I've been trying to fix this issue for at least 10 hours yesterday and today and was not able to.
I tried multiple devices, multiple APIs and already uninstalled and reinstalled the emulator and updated my GPU and CPU/Chipset drivers, without any success.
I also checked the .dmp file with BlueScreenView and WinDbg and whilst BlueScreenView just says that ntoskrnl.exe was the culprit, WinDbg clearly states that the "qemu-system-x8" process lead to the original BSOD.
Since the first BSOD I didnt get any other BSOD but only crashes without any real trace whats going wrong. My guess is that something was messed up, caused the BSOD and now silently crashes my pc constantly when trying to use the emulator.
Extra Details to Include:
CPU: AMD Ryzen 7 9800X3D
GPU: GeForce RTX 4070 Ti Super
Emulator Hypervisor: Using Android Emulator Hypervisor Driver for AMD (Hyper-V is OFF)
Tried:
Different API levels & devices
Both hardware and software rendering
No overclocking (CPU and RAM running at stock speeds)
Attached logs from Android Studio
STEPS TO REPRODUCE:
1. Open Android Studio
2. Start any emulator
3. Wait for the pc to crash
ATTACH SCREENSHOTS/RECORDINGS OF THE ISSUE
ATTACH LOG FILES (Select Help > Show Log in Files, or Show Log in Finder on a Mac)
------------------
IMPORTANT: Please read
all required information.
------------------
Studio Build: Android Studio Ladybug Feature Drop | 2024.2.2 Patch 2
Version of Gradle Plugin: 8.5.1
Version of Gradle: 8.7
Version of Java: 21.0.6 (Eclipse Adoptium 21.0.6+7-LTS)
OS: Windows 10 Pro Version 10.0.19045 Build 19045