How to fix the SYSTEM_SERVICE_EXCEPTION (0x0000003B) blue screen
This stop code means a driver or system service passed bad data to the kernel as it crossed from user mode. Graphics and system drivers are the usual cause. Jump to your situation below or work through the methods in order.
By Neeraj Singh ~11 min Updated Jun 2026 88% found this helpful
Error message
SYSTEM_SERVICE_EXCEPTION. Stop code 0x0000003B. An exception happened while executing a system service routine.
Summary
SYSTEM_SERVICE_EXCEPTION (stop code 0x0000003B) happens when an exception is raised while a system service routine runs, typically as a driver crosses from user mode into the kernel with bad data. In practice the most common culprit is a graphics driver, followed by other system drivers, corrupt system files, and occasionally a misbehaving low-level application or bad RAM. The fix is to update the graphics and other system drivers (or roll them back if the crash started after an update), repair system files with SFC and DISM, remove any recently installed software or driver that coincided with the crashes, and test memory if it persists. The minidump usually names the driver involved, which makes the fix direct.
What this error means
System service routines are the entry points drivers use to ask the kernel to do work. This stop code means one of those calls hit an exception, usually because a driver handed the kernel data it could not process, so Windows halted.
Graphics drivers are the frequent offenders because they are complex and constantly crossing that boundary. Corrupt system files and rough third-party software produce the same effect. Updating the drivers and repairing the system files clears the large majority.
Common causes
An outdated or buggy graphics driver.
Another faulty system driver.
Corrupt system files.
Recently installed software interfering at a low level.
A driver update that introduced a bug.
Bad or failing RAM.
A misbehaving virtualisation or security tool.
Expert insight
“SYSTEM_SERVICE_EXCEPTION is the one I associate with graphics drivers more than anything. A driver hands the kernel something it cannot digest as it crosses into kernel mode, and over it goes. So I clean-install the GPU driver first, roll it back if the crashes started after an update, then run SFC and DISM to rule out corrupt system files. The minidump usually names the driver, so I let it tell me where to look rather than guessing.”
Manager, Tech Support & Operations · 19+ years fixing Windows and system errors
✓ How to fix it
Method 1
Identify the driver from the crash
1Open the minidump in C:\Windows\Minidump with BlueScreenView, or note any module on the screen.
2It usually names the driver that raised the exception.
3Target that driver below.
Method 2
Update or reinstall the graphics driver
1Update the graphics driver from the GPU maker, doing a clean install.
2If the crashes began after a GPU driver update, roll it back in Device Manager.
3Graphics drivers are the most common cause of this stop code.
Method 3
Remove recently installed software
1Uninstall any software or driver added just before the crashes started, especially security, virtualisation or system tweak tools.
2Test after removing each suspect.
3Reinstall current versions if needed.
Method 4
Repair system files
1Run DISM /Online /Cleanup-Image /RestoreHealth then SFC /scannow from an elevated prompt.
2This repairs corrupt system files that can trigger the stop code.
3Reboot and watch for the crash.
Method 5
Test your memory
1Run Windows Memory Diagnostic or MemTest86.
2Replace any failing module.
3Rule memory out if the driver fix does not hold.
Method 6
Boot into Safe Mode if it keeps crashing
1If the PC will not stay up, let it fail twice so it enters the Recovery environment, then choose Troubleshoot, Advanced options, Startup Settings, and pick Safe Mode with Networking.
2Safe Mode loads only basic drivers, so you can work on the fix without the crash recurring.
3From there, update or roll back drivers and run the repairs below.
SYSTEM_SERVICE_EXCEPTION points at drivers, with graphics drivers the prime suspect, so clean-install or roll back the GPU driver first and let the minidump name any other culprit. Repair system files with SFC and DISM, and remove software that coincided with the crashes. Test RAM only if drivers and system files are clean.
Frequently asked questions
What does SYSTEM_SERVICE_EXCEPTION mean?
Stop code 0x0000003B means an exception occurred while a system service routine ran, usually because a driver passed bad data to the kernel. Graphics and system drivers are the common cause.
Which driver usually causes it?
The graphics driver most often, followed by other system drivers. The minidump in C:\Windows\Minidump, read with BlueScreenView, usually names the exact driver.
How do I fix it?
Clean-install or roll back the graphics driver, repair system files with SFC and DISM, remove recently installed low-level software, and test RAM if it persists.
It started after a Windows or driver update
Roll back the driver that was updated, or uninstall a recent update. A driver update that introduced a bug is a common trigger for this stop code.
Could software cause this blue screen?
Yes. Low-level software such as security, virtualisation or tweak tools can trigger it. Uninstall anything added just before the crashes began and test.
Do I need to test my RAM?
Test it if updating drivers and repairing system files does not stop the crash, since failing memory can also cause this stop code.
Still not working?
If drivers and system files are clean but it still crashes, enable Driver Verifier on third-party drivers to force the offender into the next dump, then disable it once identified. As a check, a clean boot that disables all non-Microsoft services and startup apps can confirm whether software is involved. You can also submit your error to us for a tailored fix.
