A blue screen naming NTFS.sys is Windows telling you the crash happened in its file-system driver — the layer between Windows and your disk. It doesn’t automatically mean your drive is dead, but it does mean something in the read/write path is broken: corrupt file-system structures, bad sectors, a failing drive, or a storage driver misbehaving.

On Acer laptops this crops up most on machines with aging hard drives or the Intel Rapid Storage driver doing something unfortunate. The good news is the diagnosis is straightforward — Windows gives you the exact tools — and logical corruption (the common case) repairs cleanly. Back up first, then work the list.

Why this happens

  • File-system corruption. Improper shutdowns, power cuts, and crashed updates leave the NTFS structures (the master file table, indexes) inconsistent. The next time Windows touches the damaged area — crash.
  • Bad sectors on the drive. A bad sector in a system area means reads fail at the hardware level. On older spinning drives this is wear and tear; on SSDs it can signal worn flash.
  • A failing drive. When bad sectors multiply, corruption recurs no matter how many times you repair it. Recurring NTFS.sys crashes after successful chkdsk runs are the signature of a dying drive.
  • Buggy storage drivers. Intel’s RST driver (iaStorAC.sys) and some third-party disk tools install filter drivers in the storage stack. A bug there crashes NTFS.sys even on a perfectly healthy drive.
  • RAM errors corrupting cached data. Windows caches file data in memory before writing it. Bad RAM flips bits in that cache, and NTFS writes corrupted data — then chokes reading it back. Memory-caused NTFS crashes are real and underdiagnosed.
  • Antivirus file-system filters. Security software hooks into every file operation. A buggy filter update can destabilize the file-system driver, especially right after the antivirus itself updates.

How to fix it

Work through these in order — start with Fix 1 and only move on if the problem is still there.

Fix 1: Back up your data immediately

Do this before any repair touches the disk. Corruption plus repair tools is the riskiest moment for your files.

  1. If Windows boots at all — even into Safe Mode (interrupt boot three times, then Troubleshoot > Advanced options > Startup Settings > Restart, press 4) — copy your important files to an external drive or cloud storage now.
  2. If Windows won’t boot, use the recovery Command Prompt (Troubleshoot > Advanced options > Command Prompt) and copy critical files with xcopy or robocopy to a USB drive.
  3. Prioritize what you can’t replace: documents, photos, work files. Programs can be reinstalled.
  4. Only proceed to disk repairs once the irreplaceable stuff is safe. This ordering has saved more data than any single repair command.

Fix 2: Run chkdsk to repair file-system errors

The primary fix for logical NTFS corruption.

  1. Press Win + X, open Terminal (Admin), and run: chkdsk C: /f /r
  2. The /f flag fixes logical errors; /r locates bad sectors and recovers readable information. If Windows says the drive is in use, type Y to schedule the check for the next restart, then reboot.
  3. Give it time — on large drives with the /r flag, this can take over an hour. Keep the charger plugged in and don’t interrupt it.
  4. When it finishes, note the summary: a handful of repaired errors is normal wear; hundreds of bad sectors is a drive-replacement warning. For context on how disk problems cascade into other crashes, see our Faulty Hardware Corrupted Page guide .

Fix 3: Check the drive’s SMART health

Find out whether the drive itself is healthy or dying.

  1. In Terminal (Admin), run: wmic diskdrive get model,status You want OK next to your drive.
  2. For detail, check your drive maker’s diagnostic tool — most SSD and HDD manufacturers offer free health utilities that read the full SMART data (reallocated sector count, wear level, error rates).
  3. Acer laptops also have built-in diagnostics: tap F2 during startup to enter the UEFI diagnostics and run the storage test.
  4. If SMART shows warnings or the Acer test fails, skip ahead to Fix 7 — no amount of chkdsk will save a drive that’s physically failing, and every boot risks more data.

Fix 4: Update or replace the storage driver

Rule out the Intel RST driver, the classic software cause.

  1. Open Device Manager (Win + X), expand Storage controllers, and note the driver name and version (Properties > Driver).
  2. If it’s an Intel RST driver, get the latest version from Intel’s driver support — several NTFS-related bugs were fixed in newer releases.
  3. Alternatively, switch to the inbox driver: right-click the controller, Update driver > Browse my computer > Let me pick from a list, and choose Standard SATA AHCI Controller.
  4. Restart and test for a few days. If the crashes stop on the standard driver, the Intel driver was your problem — leave the standard one in place or try Intel’s newest release.

Fix 5: Run SFC and DISM

Repair the Windows system files that live on the (now-repaired) file system.

  1. In Terminal (Admin), run sfc /scannow and let it complete.
  2. Then run DISM /Online /Cleanup-Image /RestoreHealth to repair the component store.
  3. Restart. These two catch the system-file damage that file-system corruption often leaves behind — fixing the disk but not the files on it is a half-done job.
  4. If SFC reports it couldn’t fix some files, run it once more after the DISM pass — DISM gives SFC clean sources to work from.

Fix 6: Test the RAM

Bad memory corrupts file data in transit and produces NTFS crashes on a healthy drive.

  1. Press Win + R, type mdsched.exe, press Enter, and choose Restart now and check for problems.
  2. Let the full test complete. Any error means the RAM is suspect.
  3. This matters most when chkdsk finds new corruption every time you run it on a drive with clean SMART data — that’s the fingerprint of memory corrupting data between the disk and the CPU.
  4. If RAM fails, reseat or replace the sticks. Retest NTFS stability afterward — and if your stop codes vary between NTFS errors and memory errors, compare with the PFN List Corrupt guide .

Fix 7: Replace the failing drive

When SMART is bad, bad sectors multiply, or crashes recur after every repair, the drive is done.

  1. With your backup from Fix 1 verified, get a replacement drive — an SSD if you’re still on a spinning disk; it’s the single biggest upgrade an old Acer can get.
  2. Clone the old drive with free cloning software, or do a clean Windows install from a USB created with the Windows 11 download tool — clean installs avoid carrying corruption forward.
  3. If cloning, run chkdsk on the clone afterward to confirm the file system is clean on the new hardware.
  4. After Windows is up on the new drive, the NTFS.sys crashes should be gone permanently. If they somehow persist on brand-new storage, you’re looking at a motherboard storage-controller fault — rare, and a professional repair.

Closing

NTFS.sys crashes scare people because they implicate the disk, and disk problems threaten data — which is exactly why Fix 1 is “back up first” and not an afterthought. But keep perspective: most of these crashes are logical corruption that chkdsk repairs in one pass, on a drive with years of life left. The drives that are actually dying tell you clearly — SMART warnings, multiplying bad sectors, crashes that return after every repair. Listen to what the diagnostics say, act on it promptly, and an NTFS.sys blue screen becomes a maintenance task instead of a data-loss event.

Frequently asked questions

What does the NTFS.sys blue screen mean?
It means Windows crashed inside its NTFS file-system driver — the code that reads and writes your disk. The trigger is usually disk corruption, bad sectors, or a failing drive, but buggy storage drivers can cause it too. Stop codes vary, but NTFS_FILE_SYSTEM (0x24) is the classic one.
Does an NTFS.sys blue screen mean my hard drive is dying?
Not necessarily, but it’s the possibility to rule out first. Logical file-system corruption (fixable with chkdsk) causes the same crash as a physically failing drive. Check the drive’s SMART health — if that’s clean and chkdsk repairs errors, your drive is probably fine.
Can I lose files from NTFS.sys crashes?
Yes, unfortunately. File-system corruption can damage the files being written when the crash happens. Back up your important data as soon as you can boot — even into Safe Mode — before running repairs, because chkdsk can occasionally make damaged files unrecoverable.
Why does this happen more on older Acer laptops?
Older Acers commonly shipped with mechanical hard drives, which develop bad sectors with age, and with Intel RST storage drivers that have a history of NTFS-related bugs. Both factors make NTFS.sys crashes more likely than on a new machine with a fresh SSD.