0

When I first got the BSOD, BlueScreenView told me it was just ntoskrnl.exe. So, I used Verifier to figure out which driver was causing the problem and it was always related to an Android emulator. I swapped from Leapdroid to LDplayer and it was pretty much the same story. Right now it is pointing at LdBoxDrv.sys. This is a clean Windows 10 1903 install. My specs are i7 7700K and 1080 Ti with virtualization on, HyperV off, and HAXM 7.4.1. I do not believe it is my Windows version even though it is an insider build because before I had the clean install this didn't happen on the same version.

enter image description here

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.