Note the file under “What failed”, then update or remove that driver or app. Uninstall third-party antivirus and virtual-camera or RGB tools, run DISM and sfc /scannow, run chkdsk, and install pending Windows and driver updates.

What SYSTEM_SERVICE_EXCEPTION means

SYSTEM_SERVICE_EXCEPTION (bug check 0x3B) happens during the hand-off from an app to the Windows kernel. Software that intercepts those calls, such as antivirus, anti-cheat, virtual cameras, VPNs and system monitoring tools, can crash there, as can graphics and storage drivers.

Common files on this screen include win32kfull.sys, ks.sys (camera/streaming), netio.sys (network/security filters) and GPU drivers.

Signs of the problem

  • Blue screen: “Stop code: SYSTEM_SERVICE_EXCEPTION”.
  • Crashes while using the webcam, gaming or browsing.
  • Files such as win32kfull.sys, ks.sys or netio.sys listed.

Why SYSTEM_SERVICE_EXCEPTION happens

  • Faulty graphics or webcam drivers.
  • Antivirus, VPN, anti-cheat or monitoring software.
  • Corrupted system files or disk errors.
  • Outdated Windows build with a known driver conflict.

Fixes to try, in order

  1. Act on the named fileMap the file to its software (e.g. ks.sys → camera software, netio.sys → network/security filters) and update or uninstall it. To see which driver crashed, open C:\Windows\Minidump after the next restart and load the newest .dmp file in Microsoft's free WinDbg app (run !analyze -v), or use a dump viewer such as BlueScreenView. The “probably caused by” file names the driver to update or remove.
  2. Remove intercepting softwareUninstall third-party antivirus, virtual camera, RGB and system-monitor apps installed recently.
  3. Update Windows and driversInstall all updates in Settings → Windows Update, including Advanced options → Optional updates → Driver updates, and get GPU drivers from the vendor.
  4. Repair files and diskRun DISM and SFC (commands below), then chkdsk C: /scan.
  5. Test in a clean bootRun msconfig → Services → Hide all Microsoft services → Disable all, restart, and see if crashes stop. Re-enable services in halves to find the cause.

Command

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Run in an elevated Command Prompt (Run as administrator). DISM can take 10–20 minutes; run sfc after it finishes, then restart.

How to tell it worked: No new crashes during the activity that used to trigger them, and no new minidump files.

Prevent it from coming back

Limit low-level utilities (overlays, RGB, monitoring) to those you need and keep them updated.