SYSTEM_SERVICE_EXCEPTION is one of the vaguer blue screen messages — it just tells you a system process crashed, without always saying which one. But the pattern of fixes is well established, and the community has beaten this one into submission over the years.

Most of the time, a driver is the villain. Your job is to figure out which one, update or remove it, and repair any damage it left behind. Here’s the order that works.

Why this happens

  • Corrupt or outdated graphics driver. The GPU driver runs deep in the system and is the single most common trigger.
  • Faulty network or Wi-Fi driver. These crash the system when they mishandle packets or power states.
  • Antivirus filter drivers. Deep system hooks from third-party antivirus products can destabilize kernel processes.
  • Corrupted system files. Damage to Windows’ own components makes innocent drivers look guilty.
  • Bad RAM. Failing memory corrupts random drivers, so each crash names a different file.
  • Recent driver or Windows update. A new driver with a bug, or an update that conflicts with an old driver, starts the crashes.
  • Overclocking instability. Unstable CPU, GPU, or RAM overclocks cause exactly this kind of kernel crash.

How to fix it

Work through these in order, from Fix 1 onward, and stop as soon as the crashes stop.

Fix 1: Note the file name on the blue screen

Before changing anything, capture the clue Windows is giving you — it saves hours of guessing.

  1. The next time it crashes, look for text in parentheses after the stop code, like SYSTEM_SERVICE_EXCEPTION (nvlddmkm.sys).
  2. Write down or photograph the exact file name.
  3. Search the file name: nvlddmkm.sys is NVIDIA, atikmdag.sys is AMD, ntfs.sys is the file system, netio.sys points at networking.
  4. If the file name changes every crash, skip straight to Fix 6 (RAM test) — that’s the classic bad-memory pattern.
  5. If it consistently names one driver, prioritize updating or rolling back that specific driver in Fix 2.

Fix 2: Update your graphics, chipset, and network drivers

Cover the three driver families responsible for the vast majority of these crashes.

  1. Press Win + X and open Device Manager.
  2. Update the display adapter first: right-click your GPU, choose Update driver > Search automatically for drivers.
  3. For a truly clean GPU install, download the latest driver from NVIDIA or AMD and choose the clean/custom install option.
  4. Update network adapters the same way, then grab the latest chipset driver from your laptop maker’s support page.
  5. Restart after each major driver and use the laptop normally before moving on — you want to know which update mattered.

Fix 3: Roll back the driver if crashes started after an update

If you can tie the crashes to a specific driver update, undoing it beats any amount of troubleshooting.

  1. In Device Manager, right-click the suspect device and choose Properties.
  2. Go to the Driver tab and click Roll Back Driver if it’s available.
  3. Pick a reason and confirm, then restart.
  4. If Roll Back is greyed out, choose Uninstall device, check Attempt to remove the driver, restart, and let Windows install its older inbox driver.
  5. Pause driver updates temporarily in Settings > Windows Update > Advanced options so the bad version doesn’t come straight back.

Fix 4: Repair system files with SFC and DISM

Damaged Windows components can trigger this stop code even with perfect drivers. Our SFC walkthrough covers this in more depth.

  1. Open Terminal (Admin) from the Win + X menu.
  2. Run sfc /scannow and wait for completion.
  3. Then run DISM /Online /Cleanup-Image /RestoreHealth with an internet connection active.
  4. Restart the laptop.
  5. Run sfc /scannow once more — the second pass should report no integrity violations.

Fix 5: Remove or update third-party antivirus

Antivirus filter drivers are a classic hidden cause because they intercept everything the system does.

  1. Update your third-party antivirus to the latest version and test for a day or two.
  2. If crashes continue, uninstall it fully — use the vendor’s dedicated removal tool, not just Settings, since filter drivers linger otherwise.
  3. Windows Security activates on its own and provides solid protection in the meantime.
  4. Test for several days with only Defender running.
  5. If stability returns, either stay with Defender or reinstall the latest version of your preferred antivirus from scratch.

Fix 6: Test your RAM

Do this especially if the blue screen names a different file each time.

  1. Press Win + R, type mdsched.exe, and choose Restart now and check for problems.
  2. Let the full test complete.
  3. Check results afterward in Event Viewer > Windows Logs > System under the MemoryDiagnostics-Results source.
  4. Any reported errors mean a bad stick — replace it; no software fix exists for faulty RAM.
  5. If you enabled XMP/DOCP in the BIOS, disable it and retest even if the quick test passed.

Fix 7: Clean boot to catch conflicting software

Background utilities — RGB controllers, fan managers, overlays — install drivers that can clash.

  1. Press Win + R, type msconfig, and press Enter.
  2. On the Services tab, check Hide all Microsoft services, then Disable all.
  3. In Task Manager > Startup apps, disable all non-Microsoft entries.
  4. Restart and use the laptop for a day or two.
  5. If it’s stable, re-enable things in small groups until the crashes return, then update or remove the offender.

Fix 8: Undo recent changes with System Restore

If the crashes started days ago and you can’t pin down the cause, rolling back the whole system state is pragmatic.

  1. Press Win + S, type Create a restore point, and open it.
  2. Click System Restore, then Next.
  3. Choose a restore point from before the crashes started.
  4. Click Scan for affected programs to review what will be removed.
  5. Complete the wizard and let the laptop restart — don’t interrupt it.

Closing

SYSTEM_SERVICE_EXCEPTION rewards methodical work: read the file name, update the usual-suspect drivers, repair system files, and check the RAM if the blame keeps shifting. Most cases resolve in the first four fixes. For crashes with no clear pattern at all, the general blue screen of death guide is a good companion read, and Microsoft’s official troubleshooting page covers anything unusual.

Frequently asked questions

What does SYSTEM_SERVICE_EXCEPTION mean?
It means a system process — usually a driver running in kernel mode — tried to do something illegal, like accessing memory it doesn’t own, and Windows stopped everything. The stop code often names the offending file in parentheses, such as ntfs.sys or a driver name, which is your biggest clue. When no file is named, outdated or corrupt drivers are still the most likely cause.
Which drivers most often cause SYSTEM_SERVICE_EXCEPTION?
Graphics drivers top the list, followed by network/Wi-Fi drivers, storage controller drivers, and antivirus filter drivers. Webcam, audio, and Bluetooth drivers show up too. If the crash started after you updated a specific driver, rolling that one back fixes it more often than anything else — which is why noting the timing matters so much.
Can I use Driver Verifier to find the bad driver?
You can, but treat it with respect. Driver Verifier stresses drivers on purpose and will blue screen deliberately when it catches one misbehaving. Only enable it if you’re comfortable booting into Safe Mode to turn it off afterward, and never leave it running permanently. For most people, updating and rolling back drivers solves the problem without needing Verifier at all.
Why does the blue screen name a different file each time?
Different file names across crashes usually point to bad RAM rather than multiple bad drivers. Faulty memory corrupts whatever happens to be loaded at the time, so each crash blames a different innocent driver. If the named file keeps changing, run the Windows Memory Diagnostic before spending more time on drivers.