0x00000023: What It Means and How to Fix This BSOD

0x00000023 is the FAT_FILE_SYSTEM stop code in Windows, and according to official Microsoft documentation it indicates that a problem occurred in the FAT file system. The safest first move is to back up any readable data, disconnect nonessential storage, then run CHKDSK on the affected volume only if the drive does not already show failure signs.

This guide is part of our Windows BSOD stop codes: full list and fixes series.

This is a storage-focused Windows blue screen. Because search results for 0x00000023 can also surface unrelated non-Windows items, stay with Windows storage checks here. (minitool.com)

What usually causes a 0x00000023 blue screen?

Official Microsoft documentation lists disk corruption as one possible cause. It also states that corruption in the file system or bad blocks on the disk can induce this error, that corrupted SCSI and IDE drivers can cause it, and that depletion of nonpaged pool memory is another possible cause.

A practical order is to check the disk and file system first, then review storage-related drivers and logs, then continue with Windows repair steps if the volume is readable and stable.

Likely causes, ranked from most to least common

What to do before repairs

1. Shut down and disconnect nonessential USB storage, docks, card readers, and other recent storage-related peripherals.
2. If Windows boots and the drive is still readable, back up important files first. Copy personal folders such as Desktop, Documents, and Pictures, plus any other needed files, to another drive or cloud storage. If needed, use another PC or recovery media to copy readable files.
3. Note any recent changes such as a storage driver update, antivirus install, backup tool, sync app, encryption tool, or new disk utility.
4. If a new hard drive or controller was added, remove that recent addition first, then retest, as reported by bleepingcomputer.com.
5. If the system can boot, open Event Viewer > Windows Logs > System and Application and look for SCSI, FASTFAT, or Autochk entries after the crash, which Microsoft specifically recommends checking.

According to How to Fix FAT_FILE_SYSTEM 0x00000023 BSOD Error — The FAT_FILE_SYSTEM bug check has a value of 0x00000023. (source)

How do I fix a 0x00000023 BSOD if Windows won’t boot?

If Windows will not boot, enter Windows Recovery Environment first, try Safe Mode only if it is available, then run an offline CHKDSK before SFC or DISM.

Boot into WinRE or Safe Mode

1. If you can reach the sign-in screen, select Power, hold Shift, and choose Restart. If you cannot, interrupt startup three times to trigger recovery, or boot from a Windows installation USB and choose Repair your computer.
2. Go to Troubleshoot > Advanced options > Startup Settings > Restart.
3. Choose Safe Mode with Networking if Windows offers it in Startup Settings.
4. If Safe Mode still fails, return to Troubleshoot > Advanced options > Command Prompt and work from there.

Run an offline disk check first

1. In WinRE Command Prompt, identify the Windows volume letter if needed by checking common letters such as C: and D:.
2. Run chkdsk C: /f first if the drive seems stable.
3. Before running chkdsk C: /f /r, pause if the drive clicks, drops offline, shows SMART warnings, or becomes abnormally slow during reads. Back up readable files first, then consider the drive maker’s diagnostic tool.
4. If CHKDSK reports repeated bad sectors or read errors, stop repair passes and move to the drive manufacturer’s diagnostic tool. If that tool reports failure, replace the drive before more repair attempts.

Microsoft documents disk corruption, file-system corruption, bad blocks, and storage-driver problems as possible causes, so disk checks and storage diagnostics are the first branch to follow.

Should I run CHKDSK or SFC first for 0x00000023?

CHKDSK first in most cases. Microsoft documents this bug check as file-system related, and CHKDSK is the Windows tool used to check a volume for file-system problems. SFC belongs later, after the file system is readable enough for Windows file repair to complete.

When CHKDSK is the right first move

1. If the crash appeared during boot, file copy, install, or external-drive access, open Command Prompt (Admin).
2. Run chkdsk C: /f to fix logical errors. If prompted to schedule on restart, type Y and reboot.
3. Use chkdsk C: /f /r only when bad sectors are a real concern and the data is already protected. Reported by bleepingcomputer.com, CHKDSK /f checks for and fixes file-system errors, while /r checks for bad sectors and attempts recovery of readable data.
4. After restart, check Event Viewer > Windows Logs > Application for Autochk details if Windows boots again, which Microsoft specifically mentions.

When CHKDSK may be a data-risk choice

1. Pause before running /r if the drive clicks, drops offline, throws SMART warnings, or becomes abnormally slow during reads.
2. Back up readable files first, even if that means using another PC or recovery media.
3. Run the drive maker’s diagnostic or SSD vendor tool next.
4. If the vendor test fails, replace the drive before more repair attempts.

If you need the related Windows repair pages, start with CHKDSK, then SFC, then DISM.

Could Windows file corruption be triggering the crash?

Yes. If CHKDSK completes and Windows boots, run SFC first. If SFC finds damage it cannot fully fix, run DISM with RestoreHealth, then run SFC again. If disk errors block either tool, go back to storage checks first.

Run SFC in a bootable system

1. Open an elevated shell, right-click Start and choose Windows Terminal (Admin) in Windows 11, or search for cmd, right-click Command Prompt, and choose Run as administrator in Windows 10.
2. Run sfc /scannow.
3. If SFC reports that it repaired files, restart and test the system.
4. If SFC says it found corruption but could not fix all of it, continue to DISM next.

Run DISM, then SFC again

1. Open Command Prompt (Admin).
2. Run DISM /Online /Cleanup-Image /RestoreHealth.
Advertisement