SYSTEM_SERVICE_EXCEPTION — the blue screen, explained and fixed

This stop code (0x0000003B) means code running on Windows’ behalf tripped over an exception it couldn’t handle. The blue screen frequently names a file — win32kbase.sys, atikmdag.sys, nvlddmkm.sys and friends — and that name is the biggest clue you’ll get: it points at the graphics stack or whichever driver was involved.

The fix, in order

  1. Read the file name on the blue screen if there is one. nvlddmkm.sys = NVIDIA graphics driver; atikmdag.sys / amdkmdag.sys = AMD graphics; win32k*.sys = Windows’ graphics/windowing core, usually provoked by a display driver or display software.
  2. Clean-install the graphics driver. Download the current driver from NVIDIA/AMD/Intel; for stubborn cases use Display Driver Uninstaller (DDU) in Safe Mode first, then install fresh.
  3. Temporarily remove third-party antivirus using the maker’s uninstall tool and run on Microsoft Defender for a day — security drivers hook deep into system services.
  4. Repair system files: DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow.
  5. Uninstall the latest Windows quality update if the crashes began with it (Settings → Windows Update → Update history → Uninstall updates).

If it still happens

If it crashes only when the camera, a specific USB device, or one app is in use, that device’s driver is the suspect — update or remove it. A minidump viewer confirms which .sys file was on the stack at the crash.

Common questions

The screen says win32kbase.sys. Is Windows itself broken? win32kbase is where the exception surfaced, not necessarily what caused it — display drivers feed it bad data. Clean-install the graphics driver before repairing Windows.

Can overclocking cause SYSTEM_SERVICE_EXCEPTION? Yes — unstable CPU/GPU/RAM overclocks corrupt exactly the kind of work system services do. Return to stock speeds while troubleshooting.

Related errors

IRQL_NOT_LESS_OR_EQUAL · KERNEL_SECURITY_CHECK_FAILURE · CRITICAL_PROCESS_DIED