Haxm causes Win10 1804 BSOD when i shutting down my computer

[aztechnoob]

BSOD dmp info "Probably caused by : memory_corruption ( nt!MiDeleteEnclavePages+96 )".
It seems have relation with intel sgx.
I have updated both sgx driver and haxm,no use.
I have disabled sgx driver,start up a android studio virtual device(use haxm),bosd remain.
Please help.

[wcwang]

Could you please provide the detailed information of PC and the reproduced steps to BOSD? E.g., Windows versions, OS bits, HAXM version, AVD information, etc. Have you tried other Android virtual device other than the current one?

[aztechnoob]

Thanks for responding.

Win10 1803 17134.81 64bit
CPU: i5-8250u
HAXM 7.2.0,6.2.1 both caused bsod
Android device: Name: Nexus_5X_API_24 CPU/ABI: Google APIs Intel Atom (x86) caused bsod,
and this one is ok:Name: Nexus_10_API_24 CPU/ABI: ARM (arm64-v8a).
avd's other settings remain default.
dmp files are here:links: https://pan.baidu.com/s/1FWYcafMP8irBO_GVF1tDCg password: a6yx

[wcwang]

Thank you for providing the detailed core dump files for analysis. All of three core dump files points to a same process from user space, i.e., MBAMessageCenter.exe. Could you help to check your system environment to see whether there is such an application running in background? If so, you may try to terminate it firstly and see whether the BSOD is disappeared.
As for the last dump file WATCHDOG-20180522-1511.tmp, the dump information is quite different from other dump files. From the dump file, it is caused by a system driver igdkmd64.sys, which is an Intel graphics kernel mode driver and related to DirectX graphics.
From the initial analysis, both types of BSOD are not relevant to HAXM. You may attempt the solution and tell us about the result later.

[aztechnoob]

I uninstalled the program you mentioned above，then started the x86 avd，bsod.
Also，I uninstalled the software and intel video card driver,then started the x86 avd，bsod again.
Finally，I installed vs emulator for android（used hypver-v not haxm）,no bsod，everything is fine.
Maybe it has som compatibility issues with intel sgx(FAILURE_BUCKET_ID: 0x1a_18011544_nt!MiDeleteEnclavePages) or the Noble Bug10 RS4。I also contacted with the engineer of the manufactor of computer，they updated the program，I updated too，BSOD remain。
This is the full dump file，links: https://pan.baidu.com/s/1DW943YIk7949MUeyZf0aKw，password: 22a4,hope they could help。Thanks.

[wcwang]

Thanks for your update and analysis. We have analyzed the crash dump files you provided. We found this time a suspicious service related to the crash, maybe a fingerprint recognition service for authentication or some image recognition.
Could you help us to provide the service list in your machine? The detailed steps are as below.

1. Start -> Type "Services", enter
2. In Services menu -> Action -> Export List... -> Save as Tab delimited txt file

We will try to narrow down the cause and find some regular laws, then we are able to locate the root cause. Thanks.

[aztechnoob]

Thanks for your hard working。I uploaded the service list to the folder:bsod full dump(links: https://pan.baidu.com/s/1DW943YIk7949MUeyZf0aKw，password: 22a4).
Before I created this issue,I tried to reinstall the OS (win10 1803 10.0.17134.1) and installed android studio before installing drivers.I started the x86 avd with software GLES-2.0,it was no bsod,but after i tried serveral times,it crashed,even coudn't start the avd.Please help,thank you.

[wcwang]

After we checked the service list you provided, there is only one service related to the BSOD information, i.e., Windows Biometric Service. Is there any real fingerprint or face scanner on your computer? Were they used for logging in Windows? Could you try to disable the service and see what will happen then? The operations can be as below.

1. Open 'Services';
2. Double click 'Windows Biometric Service';
3. Make sure the 'Service status' is 'Stopped' and change the 'Startup type' to be 'Disabled'.

Then repeat the steps to see whether the BSOD will be reproduced. We want to find out some clues from our experiments. Thanks.

[aztechnoob]

Thanks for your advice.I disabled the service 'Windows Biometric Service' as you said above,BSOD remain.And Then I uninstalled the fingerprint driver and disabled it in device manager.NO BSOD happened.But when a x86 avd was running, I tried to start 'Windows Biometric Service' ,the system crashed,BSOD happened.How does it happened?How could this problem be solved?And to whom should i give feedback?

[wcwang]

Could you help to check whether high CPU usage when you launched an x86 AVD emulator. Steps are provided below.

1. Open 'Task Manager';
2. Click 'More Details', the column 'CPU' shows the percentage.

If the percentage is high (perhaps over 50%), you may check which process occupies CPU busily.

A possible solution you may have a try,

1. Open 'Device Manager';
2. Find 'Biometric devices' -> 'Fingerprint Reader';
3. Capture the 'General' and 'Driver' tab pages from the 'Properties' and paste the screenshots onto GitHub;
4. Try to 'Update Driver...' or 'Roll Back Driver...';
5. Restart your computer.

Another thing needs to be confirmed with you, you said the BSOD occurred immediately this time when you started 'Windows Biometric Service', rather than on shutting down, right?
By the way, could you help to take photos of your screen when BSOD occurs? We can learn more information from the crash text description. Thanks.

[aztechnoob]

Thanks for your attention.
1.In the progress of starting a x86 avd,at first studio.exe occupies CPU busily,about 40%,then is openJDK platform binary,over 30%,last is qemu-system-i386.exe ,even over 60%.Here is the progress in gif:

2.The finger print driver is up-to-date,and the old version causes bsod too.Here is the screenshots:

3.Yes,bsod immediately when i started the 'Windows Biometric Service'service,BSOD screen showed"stop code:MEMORY_MANAGEMENT",same as accoured on shutting down .QR link is:https://support.microsoft.com/zh-cn/help/14238/windows-10-troubleshoot-blue-screen-errors.

[wcwang]

Thanks for your information again. From the above detailed information from the crash dump file and your latest description, the problem should be raised to the manufacturer of the Goodix fingerprint SPI device, and they are supposed to reproduce this BSOD issue easily according to your information. During this problem is being resolved, a workaround approach is to stop the service temporarily. If you need any information or analysis from us, please give your feedback further. Thanks.