BSOD When opening executable (.exe) in Whistler build 2419

Discuss Windows 2000, NT, XP and Windows Server 2000, 2003, SBS 2003.
Post Reply
Whistler2419
Posts: 81
Joined: Wed Jan 20, 2021 7:16 am

BSOD When opening executable (.exe) in Whistler build 2419

Post by Whistler2419 »

Please HELP!
When opening an EXE (Excluding System ones), I get a BSOD. The code is:

*** STOP *** 0xc000021A {FATAL SYSTEM ERROR}
The Windows SubSystem system process has been terminated unexpectedly.

How to get rid of this BSOD?
:?

Fanta Shokata
User avatar
Posts: 323
Joined: Sat Oct 10, 2020 12:48 pm
Location: Tricity, Poland

Re: BSOD When opening executable (.exe) in Whistler build 2419

Post by Fanta Shokata »

Are you using VM or a physical machine???
We stand with Ukraine

Testing
Posts: 10
Joined: Wed Nov 25, 2020 10:56 am

Re: BSOD When opening executable (.exe) in Whistler build 2419

Post by Testing »

Whistler2419 wrote:
Wed Jan 20, 2021 7:34 am
Please HELP!
When opening an EXE (Excluding System ones), I get a BSOD. The code is:

*** STOP *** 0xc000021A {FATAL SYSTEM ERROR}
The Windows SubSystem system process has been terminated unexpectedly.

How to get rid of this BSOD?
:?
There are no way to get rip of this problem. However , you can try to use the application compatibility (earlier version of whistler may be not included this feature). This may be solve the blue screen problem.

Alphis
User avatar
Posts: 63
Joined: Wed Mar 18, 2020 10:21 am
Location: an x360 devkit

Re: BSOD When opening executable (.exe) in Whistler build 2419

Post by Alphis »

if you're using vmware. go back to v12. and try using compat mode if it doesnt work with default 12.x, and vmware tools would give a bsod on 2428, not sure if it happens on 2419 too.
fatal crash intercepted
-says x360

Whistler2419
Posts: 81
Joined: Wed Jan 20, 2021 7:16 am

Re: BSOD When opening executable (.exe) in Whistler build 2419

Post by Whistler2419 »

No, I mean, After 2-5 Seconds after the double click, I am getting the BSOD.
I can't even open Event viewer too! It also has this bug!

Post Reply