-
Notifications
You must be signed in to change notification settings - Fork 877
Haxm causes Win10 1804 BSOD when i shutting down my computer #55
Comments
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? |
Thanks for responding. Win10 1803 17134.81 64bit |
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. |
I uninstalled the program you mentioned above,then started the x86 avd,bsod. |
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.
We will try to narrow down the cause and find some regular laws, then we are able to locate the root cause. Thanks. |
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). |
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.
Then repeat the steps to see whether the BSOD will be reproduced. We want to find out some clues from our experiments. Thanks. |
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? |
Could you help to check whether high CPU usage when you launched an x86 AVD emulator. Steps are provided below.
If the percentage is high (perhaps over 50%), you may check which process occupies CPU busily. A possible solution you may have a try,
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? |
Thanks for your attention. 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. |
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. |
The guest MSR state area (vcpu_t::gstate::gmsr) is never explicitly initialized, but is only filled with zeros by vCPU initialization code. In some cases, this leads to the wrong MSR being cleared by load_guest_msr() at the first VM entry, which in turn causes SGX to be accidentally disabled, and ultimately a BSOD on recent Windows 10 laptops where SGX is enabled and not supposed to be disabled by third-party software. Explicitly initialize gmsr in vcpu_init(). Also move the logic for initializing the guest IA32_APIC_BASE MSR into this function. Fixes #55, fixes #68.
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.
The text was updated successfully, but these errors were encountered: