Skip to content
PCDecoder
0x00000022FILE_SYSTEMStop codeWidely reported

FILE_SYSTEM (0x22): what it means and how to fix it

Updated Oct 13, 2026 · Checked against Microsoft documentation · How this page is made

Quick answer

The FILE_SYSTEM blue screen error (bug check 0x00000022) indicates an unrecoverable failure inside a Windows file system driver. It is an extremely rare crash usually triggered by corrupted storage drivers or failing disk hardware. Running the Windows blue screen troubleshooter and checking your storage drives for errors are the best first steps.

What it means

What bug check 0x22 means

Windows uses file system drivers to organize, read, and write data across your storage drives. Bug check 0x00000022, identified by the symbolic name FILE_SYSTEM, occurs when the Windows kernel encounters an unexpected condition within a file system component that cannot be safely resolved. To prevent silent file corruption or permanent loss of data on attached volumes, Windows halts all operating system activity immediately.

Why this crash happens

According to official documentation, this specific bug check appears very infrequently. When it does occur, the problem points to an issue inside the storage stack. Drivers responsible for managing disk volumes, third-party file system utilities, or storage filters can trigger this crash if they attempt an invalid operation or encounter corrupted memory pointers.

Physical drive defects can also play a role. If a drive fails to return requested data or returns corrupted sector information during an active file system transaction, the driver may enter an unrecoverable state. Because file integrity is critical to system operation, Windows triggers a stop code rather than attempting to write potentially broken data to disk.

Diagnosing the root cause

Determining the exact software component or storage device behind bug check 0x22 typically requires inspecting memory crash dumps. When the crash occurs, Windows captures the machine state into a memory dump file. Debugging tools use the !analyze extension to inspect this dump file, which displays information about the failure and highlights the specific driver or process that provoked the crash. For standard troubleshooting, scanning storage drives and repairing corrupted operating system files help stabilize the file system stack.

Common causes

  • Low-level driver faults or memory conflicts within file system driver components.
  • Hardware problems such as failing storage drives or bad sectors.
  • Damaged Windows system files affecting core storage operations.
  • Third-party disk utilities or volume filter drivers conflicting with system storage.

How to fix it

Safest and most likely fixes first. Readers' answers to "Did this fix it?" reorder this list over time.

  1. Run the Windows Blue Screen troubleshooter

    Use this first if your computer boots into Windows normally.

    1. Open Windows Settings by pressing Windows key + I.
    2. Select System, then click Troubleshoot.
    3. Click Other troubleshooters.
    4. Find and run the troubleshooter for Blue Screen errors, then follow the on-screen prompts.
    Did this fix it?

  2. Check storage drives for file system errors

    Use this to scan and repair potential disk corruption that may trigger file system crashes.

    1. Open File Explorer and click This PC.
    2. Right-click your primary drive (typically C:) and select Properties.
    3. Select the Tools tab.
    4. Under Error checking, click Check to run a scan on the drive.
    Did this fix it?

  3. Run the System File Checker scan

    Use this if damaged Windows operating system components are causing stability issues.

    1. Press the Windows key and type cmd.
    2. Right-click Command Prompt and select Run as administrator.
    3. Type sfc /scannow and press Enter.
    4. Allow the scan to finish and restart your PC if repairs were made.
    Did this fix it?

  4. Inspect crash dump files with debugging tools

    Use this advanced method if the crash recurs and you need to pinpoint the failing driver.

    1. Install the WinDbg application from Microsoft.
    2. Launch WinDbg, click File, and select Open Dump File.
    3. Navigate to C:\Windows\Minidump and choose the latest .dmp file.
    4. Enter !analyze -v into the command prompt at the bottom of the window and press Enter.
    5. Examine the output to identify the specific driver or module listed in the failure bucket.
    Did this fix it?

Is it just you?

25+ Microsoft Q&A threads discuss this, 1 active in the last 30 days. Most recent activity:

Checked Oct 9, 2026. Refreshed automatically every few days.

Sources

Frequently asked questions

How common is bug check 0x22?

Bug check 0x22 (FILE_SYSTEM) is documented by Microsoft as appearing very infrequently on modern systems.

What does the !analyze command do for 0x22 errors?

The !analyze debug extension processes the memory dump file created during the crash to extract detailed diagnostics and point to the root cause.

Can a bad hard drive cause this error?

Physical storage defects like bad sectors can prevent file system drivers from completing input and output tasks, which can result in a crash.

More stop codes decoded