If you’re getting an EXCEPTION_ILLEGAL_INSTRUCTION error or BSOD when launching an app or during use, it usually means the app is trying to use a CPU feature your processor doesn’t support. This can also happen due to a corrupted app install, overclocking, incorrect BIOS settings, or outdated drivers. In rare cases, faulty RAM or CPU may be the cause.
To fix it, try updating or reinstalling the app, check if your CPU supports the required features (like AVX), reset your BIOS to default settings and disable any overclocking, test your hardware, and make sure Windows and all drivers are up to date.
If Windows keeps running CHKDSK every time it starts, you can stop the loop with a few steps. First, open Command Prompt as administrator and run chkntfs /x C: to disable CHKDSK on the C: drive. Next, open the Registry Editor and go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager.
Check that the value for BootExecute is set to autocheck autochk *; if it has anything extra, remove it. You can also run CHKDSK manually once by using chkdsk C: /f /r in Command Prompt and allowing it to run on the next restart.
Finally, to check for system file issues, run sfc /scannow followed by DISM /Online /Cleanup-Image /RestoreHealth.
If you’re seeing the “MicrosoftSecurityApp.exe – Bad Image” error with code 0xc0e90002 on Windows 11, there are a few things you can try. First, open PowerShell as an administrator and run the command Get-AppxPackage Microsoft.SecHealthUI -AllUsers | Reset-AppxPackage to reinstall the Windows Security app. Then, check for any available Windows updates by going to Settings > Windows Update and installing all updates.
If the problem started recently, try uninstalling recent updates from Settings > Windows Update > Update history > Uninstall updates. You can also run a Microsoft Defender Offline scan from Windows Security > Virus & threat protection to check for malware. Lastly, create a new user account to see if the issue is specific to your current profile.
If Secure Boot is greyed out in your BIOS, there are a few simple steps you can try. First, enter the BIOS and disable CSM (Compatibility Support Module)—Secure Boot only works when CSM is off. Next, go to the Secure Boot menu and choose “Install Default Keys” or set Secure Boot mode to Standard. If the option is still locked, try setting a BIOS admin or supervisor password under the Security tab, then reboot and check again.
Hi all,
I’m encountering a crash with the error:
EXCEPTION_ILLEGAL_INSTRUCTION
This happens when I try to launch [specific app or game, if known], or sometimes during general use. It either throws a BSOD or the application just crashes.
Any idea what could be causing this? Faulty CPU instructions? Incompatible software?
Thanks!
Hi everyone,
My Windows system is stuck in a CHKDSK loop during boot. Every time I restart, it runs CHKDSK, finishes, reboots — then does it all over again.
System Info:
OS: Windows 10/11
Drive: SSD/HDD (NTFS)
No recent hardware changes
Any suggestions on how to break this loop or disable CHKDSK without corrupting data?
Thanks!
Hi all,
I’m getting this error on Windows 11:
MicrosoftSecurityApp.exe – Bad Image
Error code: 0xc0e90002
It pops up during startup or when opening the Windows Security app. I’ve tried restarting and running SFC/DISM, but the issue persists.
Anyone else seen this or know how to fix it?
Thanks in advance!
Hi all,
I’m trying to enable Secure Boot on Windows 11, but the option is greyed out in BIOS.
System Info:
OS: Windows 11
Boot Mode: UEFI
TPM 2.0: Enabled
Secure Boot: Disabled (and greyed out)
Any ideas on how to fix this?
Thanks!
Hi all,
I’m trying to enable Secure Boot on Windows 11, but the option is greyed out in BIOS.
System Info:
OS: Windows 11
Boot Mode: UEFI
TPM 2.0: Enabled
Secure Boot: Disabled (and greyed out)
Any ideas on how to fix this?
Thanks!
Just one tip: after resetting, check if your APN (mobile internet settings) auto-configure. Most phones do that now, but in rare cases you might need to re-add those from your carrier’s website.
Just backing up what @Jace said.
The only time you’d lose your number is if you either remove the SIM and toss it or switch to a new carrier without porting your number.
But a plain factory reset? You’re good.
You are indeed right, Lexar had a firmware glitch in late 2024 that caused your corrupted CR3 files, especially with burst mode shooting. If your card is from that batch, it’s best that you replace it immediately to avoid further loss.
Burst shooting can expose card issues if the card struggles with sustained writes or has contact problems.
Pro Tip: Always format your card in-camera before shoots, avoid removing it immediately after bursts, and test with a different card to confirm.
The camera itself doesn’t need much maintenance; otherwise, the card shouldn’t ask to reinsert or format frequently.
Are you sure your card is genuine? Try formatting the card in-camera (not on a computer) to reset its structure. If issues continue, replace the card immediately before your trip.
Your number and plan are related to your SIM, not your phone’s storage. Resetting your phone won’t touch the SIM, number, and even text/call history (that’s stored by your carrier) will still be there.
If you have a physical SIM, just leave it in. If you use an eSIM, most carriers let you re-download the eSIM from your carrier account or app after the reset—just make sure you know your login credentials.
Hoping someone here has been through something similar and can help.
So, my Galaxy A16 just stopped booting properly this morning. It’s stuck in a bootloop and keeps restarting after the Samsung logo. I can’t get it to power on fully, but I can access recovery mode. That’s about it.
The problem is..I have a ton of personal stuff on the phone from the last year or so (photos, work docs, voice notes), and I stupidly never set up Google backup after my last factory reset.
I took it to a local phone repair shop and they said they might need to replace the motherboard to fix the issue..but if they do, all the internal storage data will be wiped. Also tried connecting it to my laptop via USB but it doesn’t detect anything, since the OS doesn’t boot.
Any way at all I can retrieve the data from internal storage without rooting or wiping it clean?