If the BSOD loops and prevents you from accessing your desktop, you must boot into Safe Mode. Safe Mode starts Windows with a minimal set of drivers, allowing you to troubleshoot without the system crashing. Turn off your computer completely.
Type the following command to scan and fix core files, then press Enter: sfc /scannow
If the error is brand new and you just installed new hardware (e.g., RAM), remove it to see if the issue persists. Furthermore, ensure there is sufficient free space on your hard drive. Prevention: Keeping Your System Stable
Download the Windows 11 Media Creation Tool from another computer and create a bootable USB. Boot from the USB and run Setup.exe . Summary Table of Fixes Roll back or reinstall via Device Manager. Corrupted System File Run sfc /scannow and DISM . Bad System Update Uninstall recent updates via Safe Mode. Registry/Bios Changes Use System Restore.
Realtek or Intel Wireless Network Driver. system thread exception not handled new
BIOS/UEFI and firmware
Windows includes built-in tools capable of scanning the system directory and replacing broken or missing files that trigger kernel exceptions. Type cmd into the Windows search bar. Right-click and choose Run as administrator . Execute the deployment imaging tool: DISM.exe /Online /Cleanup-image /Restorehealth Use code with caution.
Navigate to the tab and click Roll Back Driver (if available). Restart your computer. How to Cleanly Reinstall Graphics Drivers
Once the scan reaches 100%, restart your computer to see if the issue is resolved. ⚡ Step 5: Disable Fast Startup If the BSOD loops and prevents you from
sfc /scannow
Locate your primary Windows drive (usually C: or D:). Type C: and press .
At its core, this crash happens when a system process (thread) generates an error that the operating system's exception handler fails to catch. Because the system cannot safely ignore the error, it shuts down to prevent data corruption. The most common triggers include:
Sometimes, even a new PC or a fresh installation of Windows can encounter this error. This is often due to a compatibility issue where a driver is not fully compatible with newer security features, like within Windows Security. A driver that functioned perfectly on an older version of Windows may crash a new installation with enhanced security. If you suspect this, try disabling Memory Integrity temporarily: Go to Windows Security > Device Security > Core Isolation Details and turn off the Memory Integrity toggle. Reboot your system and see if the error persists. If this resolves the problem, you have identified the conflict. You can then choose to either keep the feature off (which is generally not recommended for security) or hunt down an updated driver from the manufacturer that is compatible with Memory Integrity. Type the following command to scan and fix
If Windows identifies a specific driver file on the BSOD screen but you cannot uninstall it via Device Manager, you can manually rename it. Forcing Windows to change the file extension prevents the OS from executing the broken thread upon startup, causing it to generate a fresh, uncorrupted version or skip loading the broken service. Open . Navigate to the Windows drivers directory by typing: cd C:\Windows\System32\drivers Use code with caution.
If you can provide the (e.g., 0x0000001E ) or any filename shown on the BSOD, I can give a more targeted solution.
In Device Manager, right-click the driver, choose Uninstall device , check the box to remove the driver software, and restart. Windows will attempt to reinstall a fresh copy. 2. Uninstall Recent Windows Updates
SEBELUM ANDA MASUK