Windows 10: Recently getting BSODs while using Emulator Software

I recently encountered BSODs like CRITICAL_PROCESS_DIED and some other stuff while running Nox player and Bluestacks (both latest versions and official) on Win10 20H2 (up-to-date). Tried reinstalling both but didn't work. Hyper-V is disabled and no Virtualisation enabled. I'm on 8gigs memory and HD 630. Any solution?

submitted by /u/aswintvm3
[link] [comments]

:)

 

Recent File List

Remove-ItemProperty -Path "Registry::HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion
\Applets\Paint\Recent File List" -name file1

Remove-ItemProperty -Path "Registry::HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion
\Applets\Paint\Recent File List" -name file2
Remove-ItemProperty -Path "Registry::HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion
\Applets\Paint\Recent File List" -name file3
Remove-ItemProperty -Path "Registry::HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion
\Applets\Paint\Recent File List" -name file4
Remove-ItemProperty -Path "Registry::HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion
\Applets\Paint\Recent File List" -name file5
Remove-ItemProperty -Path "Registry::HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion
\Applets\Paint\Recent File List" -name file6
Remove-ItemProperty -Path "Registry::HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion
\Applets\Paint\Recent File List" -name file7
Remove-ItemProperty -Path "Registry::HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion
\Applets\Paint\Recent File List" -name file8
Remove-ItemProperty -Path "Registry::HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion
\Applets\Paint\Recent File List" -name file9
...

you get the idea. ( too lazy to put it in a for loop and test it.

or just open regedit and remove all the fileX from that key.

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.

 

Android Emulator Causes Windows Crash and goes to BSOD

Hi,

There is an issue with Android Emulator with Visual Studio 2019 as well as Android Studio, that whenever trying to open the emulator the windows crashes and enters BSOD (Status : “clock watchdog timeout”).

This issue has started after a patch update for windows (KB4554354 (OS Build 17763.1132)).

Troubleshooting done so far,

1. We have tried reinstalling the VS 2019 along with Xamarin and freshly created new emulator (x86 processor, API 27/28 etc…)
2. Tried to install android studio and running the newly created emulator.
3. Repair the visual studio 2019.

Nothing works and we are out of help from any source.

We are sure that the patch update was the issue causing the problem.

Thanks,

Prabhakaran K