Solved: FAT FILE SYSTEM (0X00000023) BSOD Crash on Windows 10/11
The FAT_FILE_SYSTEM (0x00000023) Blue Screen of Death (BSOD) is a critical error that can suddenly crash your Windows system, often without warning. This error typically occurs when the operating system encounters a problem with the File Allocation Table (FAT) file system, which is used by older storage devices like USB drives or external hard drives formatted in FAT32 or exFAT. While its less common on modern systems that primarily use NTFS, this BSOD can still appear if youre working with legacy drives or certain hardware configurations.
This guide will help you understand what causes the FAT_FILE_SYSTEM (0x00000023) error, how to troubleshoot it, and provide step-by-step solutions to resolve it. Follow these methods in order, starting with the simplest fixes before moving to more advanced steps.
—
What Causes the FAT_FILE_SYSTEM (0x00000023) BSOD?
The FAT_FILE_SYSTEM error usually appears due to one or more of the following reasons:
- Corrupted file system on a FAT32/exFAT drive: If an external USB drive, SD card, or other storage device is formatted with FAT32 or exFAT and becomes corrupted, Windows may fail to read/write files properly.
- Faulty or incompatible hardware: A failing USB controller, faulty cable, or a problematic external hard drive can trigger this error when accessed.
- Driver issues: Outdated or conflicting drivers (especially for storage controllers) may cause instability when interacting with FAT-formatted drives.
- Malware or disk errors
- Improper ejection of USB devices
: Viruses, bad sectors, or physical damage to the drive can lead to file system corruption.
: Removing a USB drive without safely ejecting it can leave behind corrupted data structures.
Unlike some BSOD errors that affect your main system drive (usually NTFS), this one is often linked to external or secondary storage. However, if the error persists even after removing all external drives, it may indicate a deeper issue with Windows itself.
—
How to Fix FAT_FILE_SYSTEM (0x00000023) BSOD
### Method 1: Check and Repair the Problematic Drive
If you suspect an external drive is causing the error, start by isolating it:
- Disconnect all external drives (USB flash drives, SD cards, etc.) and restart your PC.
- Check if the BSOD reappears. If not, the issue is likely related to one of the disconnected devices.
- If the error persists, proceed to the next steps.
If youve identified a problematic drive, try these repairs:
#### Run CHKDSK to Scan for Errors
pre
chkdsk C: /f /r /x
Note: Replace “C:” with the correct drive letter (e.g., D:, E:) if youre checking an external drive. Run Command Prompt as Administrator to execute this command.
#### Format the Drive (Last Resort)
If CHKDSK doesnt resolve the issue, the drive may be too corrupted for repair. Back up your data first, then:
- Right-click the problematic drive in File Explorer and select Format.
- Choose FAT32 or exFAT (depending on the drives original format) and click Start.
- After formatting, check if the BSOD is resolved.
—
### Method 2: Update or Reinstall Storage Drivers
Outdated or faulty drivers can trigger this error. Update them manually:
- Press Win + X and select Device Manager.
- Expand Disk drives or Universal Serial Bus controllers.
- Right-click each device (e.g., USB Mass Storage Device), then select Update driver > Search automatically for drivers.
- Restart your PC and check for improvements.
If updating doesnt work, try reinstalling the driver:
- Right-click the device again and select Uninstall device.
- Check the box for Delete the driver software for this device and confirm.
- Restart your PC to force Windows to reinstall the driver automatically.
—
### Method 3: Run System File Checker (SFC) and DISM
Corrupted system files can sometimes cause BSODs. Repair them using built-in tools:
pre
sfc /scannow
Wait for the scan to complete, then restart your PC.
If SFC doesnt fix the issue, run DISM (Deployment Image Servicing and Management):
pre
DISM /Online /Cleanup-Image /RestoreHealth
This may take several minutes. After completion, restart your system.
—
### Method 4: Test Hardware for Faults
If the BSOD persists, hardware issues (e.g., failing USB ports or cables) may be to blame:
- Try the suspect drive on another computer to rule out hardware failure.
- Test with a different USB cable or port if using an external drive.
- Check for loose connections inside your PC (if comfortable doing so).
—
### Method 5: Check for Malware and Bad Sectors
Malware can corrupt file systems, leading to BSODs. Run a full scan with:
– Windows Defender (built-in)
– Third-party antivirus like Malwarebytes
For bad sectors on your main drive, use:
pre
chkdsk C: /scan
—
### Method 6: Last Resort Reset or Clean Install Windows
If all else fails and the BSOD occurs even without external drives:
– Perform a Windows reset (keep files) or a clean install to rule out deeper system corruption.
—
FAQ About FAT_FILE_SYSTEM (0x00000023)
Q: Will this error damage my data?
A: The BSOD itself doesnt corrupt your data, but the underlying file system issues may make files inaccessible. Always back up important data before attempting repairs.
Q: Can I prevent this in the future?
A: Yes! Always safely eject USB drives (right-click the drive > Eject) and avoid removing them while in use. Use reliable cables and ports, and scan drives periodically for errors.
Q: Why does this happen on a new PC?
A: New hardware can sometimes have compatibility issues. Update all drivers (especially chipset/storage drivers) and test with minimal hardware to isolate the problem.
Q: Is this related to Windows updates?
A: Rarely, but possible. If the BSOD started after an update, roll back problematic updates via Settings > Update & Security > Windows Update > View update history.
Q: Can I ignore this error if its rare?
A: No. Even occasional crashes can lead to data loss or further corruption. Address the issue promptly, especially if it involves external drives you rely on.
—
Final Notes
The FAT_FILE_SYSTEM (0x00000023) BSOD is usually tied to external storage issues but can sometimes indicate deeper system problems. Start with simple fixes like checking drivers and file system integrity, then escalate to hardware testing if needed. If the error persists after trying all steps, consult a professional for hardware diagnostics.
By following this guide, you should be able to resolve the issue and prevent future crashes.
Last Updated: December 13, 2025
Tested on: Windows 10 (22H2) & Windows 11 (23H2)