Quick Answer
Run chkdsk /f /r from an admin command prompt, then update your storage drivers (especially Intel RST or NVMe drivers). If that doesn't work, uninstall recent Windows updates or do a system restore.
The SYSTEM_SERVICE_EXCEPTION error with ntfs.sys is a Windows blue screen that appears when the NTFS file system driver crashes. This usually happens because of a corrupt disk, a faulty storage driver, or a recent change to your system like a Windows update or new software. I've seen this error on machines with failing hard drives, but it's also common after a driver update goes sideways. The key is to figure out which one is causing it on your machine.
Fix Steps (Do These in Order)
Step 1: Check Your Disk for Errors
Start with the disk check because if your drive is physically failing, nothing else will help. Open a command prompt as administrator (search for “cmd”, right-click, and select “Run as administrator”). Then type:
chkdsk C: /f /rYou'll likely see a message saying the disk is in use and asking if you want to schedule it for the next restart. Type Y and press Enter, then restart your PC. The check will run before Windows boots. If it finds bad sectors or file system errors, let it finish. This can take a while—sometimes a few hours on a large drive. After it completes, see if the blue screen still appears.
Step 2: Update Your Storage Drivers
If the disk is fine, the next suspect is the driver that talks to your hard drive or SSD. On many machines, that's the Intel Rapid Storage Technology (RST) driver, or a specific NVMe driver for M.2 SSDs. Open Device Manager (right-click the Start button and select “Device Manager”), expand “Storage Controllers”, and look for any device with a yellow warning icon. Right-click it and select “Update driver”, then “Search automatically for drivers”. If Windows finds nothing, go to your PC manufacturer's website and download the latest chipset and storage drivers. For example, if you have a Dell, search “Dell [your model] storage driver”. Installing the wrong one can cause more issues, so stick to the manufacturer's own page.
Step 3: Uninstall Recent Windows Updates
If the error started after a Windows update, that update could be the culprit. Windows 10 and 11 both let you roll back recent updates. Go to Settings > Update & Security (or Windows Update in Windows 11) > View update history > Uninstall updates. Look for the most recent updates sorted by date. Uninstall the most recent one, restart, and see if the error goes away. If it doesn't, uninstall the next one down and try again. I've seen a bad cumulative update cause exactly this error, so it's worth checking.
Step 4: Run System File Checker and DISM
Corrupted system files can trigger this error too. Run the System File Checker first. From an admin command prompt, type:
sfc /scannowLet it finish. Then run the Deployment Image Servicing and Management tool:
DISM /Online /Cleanup-Image /RestoreHealthThis can take 15-20 minutes. Both will repair corrupted files. After they finish, restart your PC and test.
Step 5: Check Your RAM
Bad RAM can cause random blue screens, and it often points to files like ntfs.sys even though the RAM itself is the problem. Windows has a built-in memory diagnostic tool. Type “Windows Memory Diagnostic” in the Start menu, select the first result, and restart. Let it run the standard test. If it finds errors, you'll need to replace the bad RAM stick. This is less common than disk issues, but I've seen it.
Alternative Fixes If the Main Steps Don't Work
If you're still getting the blue screen, try these. They're less common fixes but have worked for some people.
System Restore
If your system has a restore point from before the error started, you can roll back to it. Type “Create a restore point” in the Start menu, click “System Restore”, and follow the prompts. Pick a point before the error began. This doesn't touch your personal files, but it will uninstall any drivers or updates installed after that point.
Disable Fast Startup
Windows has a “Fast Startup” feature that can cause weird issues with drivers and file systems. To turn it off, go to Control Panel > Power Options > Choose what the power buttons do > Change settings that are currently unavailable. Scroll down to “Turn on fast startup (recommended)” and untick it. Restart your PC. Some users report that this alone stops the error, especially on laptops.
Check for Third-Party Antivirus Conflicts
If you have a third-party antivirus program (like Norton, McAfee, or Avast), it can interfere with file system operations and trigger this error. Temporarily uninstall it completely (not just disable it), then test. If the error stops, you'll need to switch antivirus or update to a newer version. Windows Defender is actually solid, so you might not need third-party software at all.
Prevention Tips
Once you've fixed the error, here's how to keep it from coming back. First, back up your data regularly. If the disk is failing, a backup is your only safety net. Use an external drive or a cloud service. Second, keep your drivers updated, but don't install them the second they release. Wait a week and see if others report problems. Third, run chkdsk every few months on your system drive, especially if you notice files getting corrupted or apps crashing randomly. Finally, if you're using an older hard drive (spinning disk), consider replacing it with an SSD. SSDs are faster and less likely to develop bad sectors, which cuts down on ntfs.sys errors significantly.