Skip to content
WindowsBeginner

Windows Stop Code CDFS_FILE_SYSTEM (0x00000026): Meaning, Parameters, and Troubleshooting

Quick Answer CDFS_FILE_SYSTEM is Windows bug check 0x00000026. Microsoft says it indicates a problem in the CD file system. Its documentation lists several p...

BI
Bison Technical Team Enterprise IT specialists
Updated 26 Sep 2026 6 min read 4 total views
Structured technical guidanceSafety notes included where requiredSources listed below

Quick Answer

CDFS_FILE_SYSTEM is Windows bug check 0x00000026. Microsoft says it indicates a problem in the CD file system. Its documentation lists several possible contributors: corrupt file-system data or unreadable sectors, storage-driver problems, and depletion of nonpaged pool memory. The code alone does not establish which one occurred. Microsoft Learn

For a real crash, preserve the dump and note whether an optical disc, mounted disc image, or related device was in use. Examine the call stack and system events. Microsoft documents an exception-context debugging sequence using Arg3 only when CdExceptionFilter appears on the stack. Microsoft Learn

Advertisement

What Is CDFS?

CDFS refers to Windows’ CD file system. Windows includes a CDFS file-system driver for accessing CD file-system content. It is distinct from the NTFS or FAT file system normally used on writable drives. Microsoft Learn

A CDFS_FILE_SYSTEM stop code points to the path in which Windows detected a failure. A damaged disc is one possibility, but a storage driver or lack of kernel memory can also be involved. Avoid assuming that the computer’s main SSD is damaged merely because the name contains “FILE_SYSTEM.” Microsoft Learn

CDFS_FILE_SYSTEM Parameters

Parameter Microsoft’s description How to use it
1 / Arg1 Source-file and line-number information. The high 16 bits identify a source file by its identifier number; the low 16 bits identify the line where the bug check occurred. Helps a debugger locate the reported Windows code path.
2 / Arg2 Address of the exception record, if CdExceptionFilter is on the stack. Interpret conditionally.
3 / Arg3 Address of the context record, if CdExceptionFilter is on the stack. Use with .cxr when that documented condition applies.
4 / Arg4 Reserved. Do not assign it an undocumented meaning.

The condition attached to Arg2 and Arg3 matters. Their meanings should not be assumed for every 0x26 dump. Microsoft Learn

Possible Causes Documented by Microsoft

Damaged file-system data or unreadable sectors

Microsoft says file-system corruption and bad blocks or sectors can induce 0x26. For an optical disc, a read problem might relate to the medium, drive, or path used to access it. Check the dump and device events to distinguish them. Microsoft Learn

Storage-driver problems

Microsoft notes that corrupted SCSI and IDE drivers can affect disk reads and writes. On a particular computer, investigate the actual controller and device path involved rather than assuming it uses either of those driver types. Microsoft Learn

Nonpaged pool depletion

If nonpaged pool memory becomes completely depleted, this bug check can stop the system. Microsoft also describes a low-pool situation during indexing in which another kernel-mode driver requests nonpaged pool and triggers the failure. A driver on the final stack may have encountered the shortage without being the component that consumed all the memory. Microsoft Learn

How to Investigate an Actual 0x26 Crash

1. Record the circumstances

Confirm the complete code 0x00000026 and note what was being accessed when the crash occurred. Record whether an optical disc, external drive, or disc image was mounted and whether the problem repeats with the same medium.

A repeatable crash tied to one disc is a useful lead. It is not, by itself, proof that the disc is the only faulty component.

2. Preserve the crash dump

Keep the dump Windows produced. The bug-check parameters and stack can distinguish an exception path from a memory-shortage or device-I/O investigation.

3. Run the initial WinDbg analysis

Open the dump and enter:

!analyze -v

Record all four arguments and review the call stack and any identified modules. Confirm whether CdExceptionFilter appears.

If it does, and Arg3 is the context-record address described by Microsoft, run:

.cxr <Arg3 address>
kb

Replace <Arg3 address> with the value from the dump. Microsoft recommends .cxr with Parameter 3 followed by kb for this debugging path. Microsoft Learn

4. Check device and system events

Review Event Viewer → Windows Logs → System around the crash for relevant controller, device, or I/O errors. Microsoft’s 0x26 guidance also mentions Autochk messages in the Application log and hardware diagnostics supplied by the computer or device manufacturer. Correlate any event with the device and operation involved in this crash. Microsoft Learn

5. Separate device errors from memory pressure

Evidence Next investigation
Read errors recur with one disc or device. Check the medium, drive, connection, controller, and manufacturer diagnostics.
Several unrelated kernel operations fail while nonpaged pool is low. Investigate pool consumption and the drivers allocating it.
A particular third-party storage or filter driver recurs in dumps. Check that driver’s vendor for an update or supported rollback.

These are evidence-based directions, not guaranteed interpretations of the stop code.

Should You Run CHKDSK?

Microsoft’s 0x26 page includes chkdsk /f /r in its general disk-corruption guidance. Apply that advice to an appropriate writable volume when there is evidence of structural corruption. A conventional read-only CD cannot be repaired in place with CHKDSK in the way a writable FAT or NTFS volume can. For suspected optical-media trouble, check whether the disc can be read in another compatible drive and whether another known-good disc works in the original drive. Microsoft Learn

Do not run a repair command against an unrelated system volume merely because the crash name contains “CD file system.” If important data is on an affected writable drive, preserve it before attempting file-system repairs.

Guidance for Driver Developers

If a relevant driver appears on the stack, inspect the I/O request and exception path around the failure. Check device errors, object lifetime, and cleanup behavior. If nonpaged pool was low, investigate which allocations grew before the stop; adding RAM may relieve genuine capacity pressure, but it will not correct a driver that continually leaks allocations.

Microsoft mentions adding physical memory specifically as a resolution for a nonpaged pool depletion problem. Establish that condition before treating a RAM upgrade as the remedy. Microsoft Learn

Frequently Asked Questions

What does CDFS_FILE_SYSTEM mean?

Windows reported a problem in the CD file system and stopped with bug check 0x00000026. Microsoft Learn

Does it always mean a CD is scratched?

No. Microsoft also lists storage-driver problems and nonpaged pool depletion as possible causes. Investigate the medium and drive alongside the crash evidence. Microsoft Learn

Does it prove my main SSD is failing?

No. The stop-code name and value do not identify a particular failed device. Check the actual I/O path and related system events.

What does Parameter 1 contain?

The high 16 bits identify a source file by number, and the low 16 bits identify the source line where the bug check occurred. Microsoft Learn

Are Arg2 and Arg3 always exception pointers?

No. Microsoft defines them that way if CdExceptionFilter is on the stack. Microsoft Learn

Can I repair a read-only CD with chkdsk /f /r?

No. That command is intended for a volume Windows can check and repair. For a conventional read-only CD, investigate the disc, drive, and read path instead.

Could low nonpaged pool cause this crash?

Yes. Microsoft specifically identifies nonpaged pool depletion as a possible cause. Confirm it from the system’s memory and dump evidence before adding RAM or changing drivers. Microsoft Learn

Summary

CDFS_FILE_SYSTEM (0x00000026) indicates that Windows encountered a problem in its CD file-system path. The documented possibilities include corrupt or unreadable data, storage-driver trouble, and nonpaged pool depletion. Use the dump’s conditional exception parameters, call stack, device events, and memory evidence to choose the right investigation. Microsoft Learn

Sources

 

YOUR FEEDBACK

Was this guide useful?

Your answer helps us keep BISONKB accurate and practical.

THE BISON BRIEF

Practical IT knowledge, once a week.

New troubleshooting guides, scripts and infrastructure notes. No noise.

By subscribing, you agree to our privacy policy. Unsubscribe at any time.