What SYSTEM_SERVICE_EXCEPTION means

This stop is triggered when a routine crossing from user mode into kernel mode raises an exception. Graphics drivers are a very common source, but any driver, security tool or damaged system file can trigger it, so the file named on screen matters more than the code number.

Common causes

  • A graphics driver problem, particularly just after an update
  • Antivirus or system-utility drivers
  • Corrupted system files
  • Faulty RAM or storage

How to fix SYSTEM_SERVICE_EXCEPTION

Work through these in order and test after each one. Stopping as soon as the crashes stop tells you which change mattered.

  1. Note the file name on the blue screen. If the screen shows a line such as "What failed" followed by a .sys file, write it down. Searching that file name shows which driver it belongs to, which tells you what to update or remove. The named file is the code that crashed, which is not always the root cause.
  2. Reinstall the graphics driver cleanly. Download the latest driver for your exact GPU from NVIDIA, AMD or Intel (or the laptop maker for notebooks), then install it using the vendor's clean-install option. If the newest driver is the one that started the crashes, install the previous release instead.
  3. Repair Windows system files. Open Terminal (Admin) and run sfc /scannow. If it reports damage it could not repair, run DISM /Online /Cleanup-Image /RestoreHealth, restart, and run sfc /scannow once more.
  4. Check security and utility software. Update, or temporarily uninstall, third-party antivirus, disk utilities and system optimizers. Windows Security alone is a reasonable stand-in while you test.
  5. Test the memory. Run Windows Memory Diagnostic (search for it in Start) for a quick check, then MemTest86 for several passes if the crashes continue. Any error points to a faulty stick or slot, or to memory settings the hardware cannot run reliably.
When to stop and protect your data

If the crash happens only during gaming or video playback, concentrate on the GPU driver, temperatures and power delivery.

Not sure this is your code?

The stop code appears as text on the blue screen. If the PC restarted before you could read it, open Event Viewer, then Windows Logs, then System, and look for a BugCheck event with ID 1001. You can also search all stop codes.

Related guides

Other driver errors