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.

1. 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.
2. 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.
3. 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)
4. 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 /r from an elevated Command Prompt, allow the restart if prompted, and then check Event Viewer for related storage errors.
5. 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.

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

1. 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.
2. 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.
3. Open Device Manager > DVD/CD-ROM drives. Right-click the optical drive and choose Uninstall device. Reboot so Windows reloads the driver stack.
4. 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.
5. 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.

Are mounted ISOs or virtual drive tools causing the CDFS crash?

If the stop appears after mounting images or installing virtual optical software, remove that variable first. On systems with no active DVD drive, that is still a direct way to trigger the CDFS path.

Fix steps for ISO and virtual-drive conflicts

1. Open File Explorer > This PC, right-click each mounted ISO drive, and choose Eject. Reboot and see whether the crash path changes.
2. Open Settings > Apps > Installed apps on Windows 11, or Settings > Apps > Apps & features on Windows 10. Uninstall Daemon Tools, PowerISO, or other virtual-drive tools. Reboot immediately after removal.
3. Retest with Windows-only ISO mounting by right-clicking an ISO in File Explorer and using the built-in mount option. If built-in mounting works but third-party software crashes, leave the third-party tool removed.
4. If the issue started right after installing backup, antivirus, or disk tools, use msconfig for a clean boot and temporarily disable those utilities one at a time. Officially, virus scanners, backup programs, and disk defragmenter tools are among the items worth disabling during this bug check path.

If that did not work

Go down one layer. At that point, focus on storage drivers, protected system files, and disk health rather than the ISO file alone.

How do you repair storage corruption, cdfs.sys damage, or memory pressure?

Once physical media and ISO tools are ruled out, repair the base Windows and storage layers in order. Start with system file checks, then the component store, then disk structure. After that, shift attention to SCSI or IDE drivers, filter conflicts, and the chance of low nonpaged pool memory.

Fix steps for corruption and driver-stack faults

1. Open Command Prompt (Admin) and run sfc /scannow. Watch the final status message. If it says corrupt files were found and repaired, reboot and retest the same action that caused the blue screen.
2. If SFC cannot repair files or the crash returns, run DISM /Online /Cleanup-Image /RestoreHealth. Reboot after DISM completes, then run sfc /scannow again.
3. Run chkdsk /f /r from an elevated Command Prompt. If it targets the system partition, approve the restart so Windows can scan before full startup. Officially, disk corruption, file-system corruption, and bad blocks can induce this error.
4. Open Device Manager > IDE ATA/ATAPI controllers and Storage controllers. Roll back, uninstall, or update the affected SCSI or IDE controller driver, then reboot. Officially, corrupted SCSI and IDE drivers are a known cause.
5. If crashes happen during heavy indexing, after long uptime, or with no media involved, consider nonpaged pool pressure. A practical check is to note whether a restart temporarily clears the problem and whether it returns during indexing or after additional driver-loaded activity. Officially, depletion of nonpaged pool memory can stop the system, and another kernel-mode driver requiring nonpaged pool memory during indexing can also trigger the error.

Prevention

Avoid stacking multiple ISO tools, old disc utilities, backup filters, and antivirus products on the same machine. Reboot after each storage-stack change so you can see which removal changed the crash path.

What logs should you check after a 0x00000026 blue screen?

The fastest useful logs are in Event Viewer. Look in Windows Logs > System for storage and file-system clues, then compare the timestamps with the blue screen. Patterns matter more than single entries, especially if the machine crashes only during disc access or only during boot.

What to open and what to filter

1. Open Event Viewer > Windows Logs > System. Use Filter Current Log and search around the crash time for SCSI and FASTFAT.
2. Open Event Viewer > Windows Logs > Application and look for Autochk entries after running chkdsk or after an unclean restart.
3. Write down whether the entries appear only when media is inserted, only when ISOs are mounted, or even before login. That timing points you back to the right triage path.

How to read the pattern

SCSI and controller errors before the stop code usually point below CDFS. Autochk entries after chkdsk help confirm whether disk structure issues were found and repaired.

Still not working? Escalation steps for boot loops and repeat crashes

If 0x00000026 keeps happening after the basic path tests, switch from quick fixes to controlled rollback. The goal is to remove recent storage-layer changes, boot with the fewest possible drivers, and decide whether the machine is dealing with software stack damage, failing hardware, or a crash that needs dump-based support.

If Windows boot-loops

1. Boot into Safe Mode. Remove recent virtual-drive, backup, antivirus, or storage software from Settings > Apps, then reboot normally.
2. If the issue began recently, run System Restore from recovery options and pick a restore point from before the first crash.
3. If Safe Mode still crashes, run Reset This PC only after backups are secure and after storage hardware has been checked. This is later in the ladder for a reason.

When to hand it off

Collect a dump when the system crashes with no disc inserted, no ISO mounted, and after SFC, DISM, and chkdsk have all completed. That is also the point to swap the optical drive, test different storage hardware, or move the case to advanced support for dump analysis.

Frequently asked questions

Is 0x00000026 related to the CDFS file system?

Yes. Start by removing any disc, unmounting any ISO, then checking whether the crash still appears. That simple split tells you whether the optical path is the trigger or only where the fault surfaced.

What causes a CDFS_FILE_SYSTEM blue screen?

Officially documented causes include disk corruption, file-system corruption, bad blocks, corrupted SCSI or IDE drivers, and low nonpaged pool memory. Practical checks also include removing discs, unmounting ISOs, and uninstalling third-party virtual-drive tools if the problem began around image mounting.

Can a bad CD or DVD trigger 0x00000026?

Yes. Scratches, dirt, and damaged burns can cause read failures while Windows is trying to interpret disc data. Eject the disc, clean it, test a known-good disc, and if possible try another optical drive. If only one disc crashes, the media is the lead suspect.

How do I fix 0x00000026 with chkdsk or DISM?

Open Command Prompt (Admin), run sfc /scannow, then run DISM /Online /Cleanup-Image /RestoreHealth if SFC reports damage or cannot repair files. After that, run chkdsk /f /r. If Windows says the system partition is in use, approve the restart so chkdsk can run before full startup.

Should I remove virtual drive software for this BSOD?

Yes, if the crash began after mounting ISO files or installing disc-emulation tools. Go to Settings > Apps, uninstall Daemon Tools, PowerISO, or similar software, reboot, and retest with Windows-only mounting. If the crash stops, leave the third-party tool removed.

Can low nonpaged pool memory cause a 0x00000026 crash?

Yes. If the problem appears outside direct disc access, during indexing, or after long uptime, review recent driver and utility installs and check whether the crash pattern changes after a restart, because official guidance lists nonpaged pool depletion and kernel-mode driver activity during indexing as possible triggers.