0x00000026 Fixes for CDFS File System BSODs in Windows
0x00000026 usually means a CDFS_FILE_SYSTEM crash. Officially, bug check value 0x00000026 indicates that a problem occurred in the CD file system. The first job is to find the blamed module in the dump and split media damage from ISO-mounter or storage-driver faults. A fast first step is to remove any disc, unmount any ISO, reboot, and then try to reproduce the crash with neither path active.
This guide is part of our Windows BSOD stop codes: full list and fixes series.
What does stop code 0x00000026 mean in Windows?
The stop code is tied to the CD file-system path rather than Windows as a whole. Some third-party writeups also discuss it. (hashroot.com)
Where cdfs.sys fits
cdfs.sys is the CD-ROM file system driver, as it is generally described. It handles reads from CD and DVD media, mounted ISO content presented as optical media, and requests passed down through storage drivers. If it cannot safely read or parse data, the kernel can stop with a blue screen.
Why this still appears on modern Windows
Many current PCs never touch a physical DVD drive, but they still mount ISO files, install backup tools, or run storage-filter drivers. That keeps the old CDFS path alive. In practice, issues can show up during an optical read, a virtual optical mount, or a lower storage or memory problem while CDFS is active.
Boot loop versus access-only crashes
If the machine crashes only when a disc is inserted or an ISO is mounted, the trigger is usually narrow. If it also crashes during boot, after login, or during indexing, look harder at storage corruption, filter drivers, or nonpaged pool pressure instead of blaming the disc alone.
According to Bug Check 0x26 CDFS_FILE_SYSTEM – Windows drivers — The bug check value is 0x00000026. (source)
Likely causes of 0x00000026
Officially documented causes include disk corruption, file-system corruption, bad blocks, corrupted SCSI or IDE drivers, and depletion of nonpaged pool memory. Virtual-drive software, optical media problems, and optical-drive faults are practical possibilities to test first because they directly affect the CD/DVD access path.
- Mounted ISO or virtual drive conflicts. If crashes begin when an ISO is mounted or after disc-emulation software is installed, unmount all ISOs in File Explorer, uninstall the virtual-drive tool from Settings > Apps, reboot, and then retest by right-clicking the same ISO in File Explorer and using Windows’ built-in Mount option.
- Bad disc media or failing optical drive. If the stop happens only while reading a disc, eject it and use the PC with no media inserted. Then inspect the disc under good light, clean it from center to edge, test a known-good disc, and if needed try another drive, including a USB optical drive.
- Storage-driver corruption or filter-driver issues. Officially, corrupted SCSI and IDE drivers can cause this error because they affect the system’s ability to read and write to the disk. Check Device Manager > IDE ATA/ATAPI controllers and Storage controllers for recent driver changes, and roll back or reinstall the affected controller driver if the issue started after an update. (Microsoft Learn)
- Disk corruption or bad sectors. Officially, one possible cause is disk corruption, and corruption in the file system or bad blocks can induce the error. Run
chkdsk /f /rfrom an elevated Command Prompt, allow the restart if prompted, and then check Event Viewer for related storage errors. - Low nonpaged pool memory. Officially, depletion of nonpaged pool memory can stop the system with this bug check, including during indexing when another kernel-mode driver needs that pool. If crashes happen after long uptime, during heavy indexing, or with no media involved, review recent driver or utility installs and check whether the pattern changes after a restart.
Which subsystem failed first? Use this 3-path triage table
The shortest route is to match the crash trigger to the subsystem that was active at the time. If the crash happens only with a disc present, test the physical path first. If it starts after mounting an ISO or adding virtual-drive software, strip that stack first, then run repair commands.
| Crash trigger | Most likely subsystem | First 3 tests | Escalation point |
|---|---|---|---|
| BSOD appears when inserting or reading a CD/DVD | Physical disc or optical drive |
| If several known-good discs fail on one drive but work on another, move to Device Manager driver rollback or uninstall, then hardware replacement. |
| BSOD appears when mounting an ISO or after installing virtual-drive software | Mounted ISO or virtual drive stack |
| If the crash persists with no third-party tool installed, inspect storage drivers and run SFC, DISM, and chkdsk next. |
| BSOD also happens during boot, indexing, or with no disc and no ISO mounted | Kernel memory or storage corruption |
| If the stop code keeps happening, open Event Viewer > Windows Logs > System and check entries at the crash time for SCSI, controller, disk, or FASTFAT errors, roll back any recent storage-controller driver in Device Manager, boot Safe Mode to remove recent virtual-drive or filter software, and gather a dump for advanced support. |
What the dump can tell support staff
For advanced troubleshooting, keep this separate from user repair steps. Official debugger guidance for this bug check is to use the .cxr command with Parameter 3 and then kb to view the stack. That helps support staff working from a dump, but most users should start with trigger-based triage instead of debugger work. (Microsoft Learn)
Did the crash start when reading a CD or DVD?
If the blue screen appears only during disc access, treat the disc and drive as the first suspect. That path is fast to test, cheap to rule out, and keeps you from changing storage drivers when the real problem is a dirty disc, a bad burn, or a weak optical pickup.
Fix steps for physical disc or drive faults
- Shut down any app reading the disc, eject it, and reboot. Then use the PC without any media inserted. If the crash stops, the trigger is likely on the optical path.
- Inspect the disc under good light. Clean it from center to edge, not in circles. Test a known-good pressed disc and then a known-good burned disc if both are available.
- Open Device Manager > DVD/CD-ROM drives. Right-click the optical drive and choose Uninstall device. Reboot so Windows reloads the driver stack.
- If the issue started after a driver update, open Device Manager > IDE ATA/ATAPI controllers or Storage controllers, open the affected controller, and use Driver > Roll Back Driver if available.
- Try another drive, including a USB optical drive. If one drive fails across several known-good discs while another works, replace the failing hardware.
If that did not work
Move to storage repair and log review. Officially, when disk corruption seems to be involved, check Event Viewer for SCSI and FASTFAT in the System log and Autochk in the Application log.
