Fix SYSTEM_SERVICE_EXCEPTION on Windows 11

Stop code SYSTEM_SERVICE_EXCEPTION means a system thread generated an exception that the error handler didn’t catch. Stop code 0x0000003B. Nine times out of ten the faulting driver is right there on the blue screen next to the stop code — something like win32kfull.sys, nvlddmkm.sys, dxgkrnl.sys, igdkmd64.sys. If you got a driver name, that’s where you start. If the screen just says SYSTEM_SERVICE_EXCEPTION with no filename, you’ll need the crash dump.

GPU drivers own this stop code. More than any other BSOD, this one points at your graphics driver doing something it shouldn’t — trying to access memory outside its allocation, dividing by zero, hitting an unhandled path in the display pipeline. NVIDIA’s nvlddmkm.sys specifically shows up in probably half the SYSTEM_SERVICE_EXCEPTION dumps I’ve looked at.

If it says nvlddmkm.sys: download DDU (Display Driver Uninstaller) from Wagnardsoft, boot into Safe Mode, run DDU to strip out every trace of the NVIDIA driver, reboot, install a fresh driver from nvidia.com. Don’t use GeForce Experience to install it — go to nvidia.com/drivers, pick your card manually, download the driver-only package. GeForce Experience has been the actual cause of SYSTEM_SERVICE_EXCEPTION on two machines I’ve worked on. The overlay hooks into the display pipeline and sometimes conflicts with the driver it’s supposed to manage.

Intel integrated graphics — igdkmd64.sys — crashes this way when Windows Update installs a newer Intel driver that doesn’t play well with the specific hardware revision. Intel 12th gen Alder Lake had a stretch in late 2024 where the Windows-distributed driver caused SYSTEM_SERVICE_EXCEPTION on dual-GPU laptops during video playback. Device Manager, Display adapters, right-click the Intel adapter, Properties, Driver tab, Roll Back Driver. If Roll Back is greyed out, update manually from Intel’s download center with the previous version.

win32kfull.sys and win32kbase.sys

These are Windows kernel-mode display subsystem files. When they show up next to SYSTEM_SERVICE_EXCEPTION, it’s not a third-party driver — it’s Windows itself crashing during graphics rendering. Specific applications trigger this more than anything system-wide. A Surface Pro 9 kept crashing when the owner opened Teams video calls — win32kfull.sys every time, only during video, never at idle. The Intel driver was fine, Teams was fine individually, but the combination of hardware-accelerated video decoding in Teams plus the specific Intel driver version equaled crash. Turned off hardware acceleration in Teams settings and it stopped.

Photoshop, Chrome with hardware acceleration on, DaVinci Resolve, OBS — any app that pushes GPU rendering through the Windows display stack can trigger this. If you notice the crash always happens during a specific application, turn off hardware acceleration in that app’s settings first.

Font corruption also triggers win32kfull.sys crashes. Damaged .ttf or .otf files in C:\Windows\Fonts make the rendering subsystem choke. If you recently installed custom fonts and the crashes started around the same time, remove those fonts. You can also rebuild the font cache — stop the Windows Font Cache Service, delete C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\ contents, restart the service.

When There’s No Driver Name

Sometimes the blue screen just says SYSTEM_SERVICE_EXCEPTION with no file listed. Download BlueScreenView — it reads the minidump files from C:\Windows\Minidump\ and shows you exactly which module caused each crash. The “Caused By Driver” column gives you the filename that the blue screen didn’t show.

If BlueScreenView points at ntoskrnl.exe, that’s the Windows kernel itself — usually means the real culprit is something that corrupted kernel memory. Run sfc /scannow from an elevated Command Prompt. If SFC finds corruption it can’t repair, follow up with DISM /Online /Cleanup-Image /RestoreHealth then SFC again. Our SFC guide covers the full process when the first pass doesn’t fix everything.

Antivirus software causes more SYSTEM_SERVICE_EXCEPTION crashes than people realize. The kernel-mode filter drivers that antivirus products install hook deep into Windows and any bug in them crashes the whole system. If you recently installed or updated Bitdefender, Norton, McAfee, or Kaspersky, try uninstalling it temporarily and running on Windows Defender alone for a few days. If the crashes stop, contact the AV vendor or switch products — Windows Defender is genuinely good enough now that third-party AV causes more problems than it prevents on most machines.

If you’ve been through all of this and the crashes won’t stop — different driver every dump, no clear pattern, SFC clean, no third-party AV — suspect RAM. Bad memory can cause literally any stop code because the corruption is random. Run Windows Memory Diagnostic (mdsched.exe), let it do the extended test, takes about 20 minutes. If it finds errors, you need to figure out which stick — pull one, test, swap, test. Failing that, send us the dump files and we’ll read them properly.