How to Fix SYSTEM_SERVICE_EXCEPTION

SYSTEM_SERVICE_EXCEPTION is a Windows stop error with the bug-check value 0x0000003B. It fires when a program raises an exception while crossing from user mode into kernel mode through a system service call, and the leading cause is a faulty or outdated device driver, most often a graphics or network driver. Corrupt system files, defective RAM, and conflicts from recently installed software such as third-party antivirus account for the rest.

What Causes SYSTEM_SERVICE_EXCEPTION?

SYSTEM_SERVICE_EXCEPTION is caused by something failing the controlled transition from user mode to kernel mode during a system service call. Four sources account for almost every case, ranked here from most to least common:

The error sits among a family of kernel-mode stop codes. The full list and how to read each one is covered in the guide to BSOD stop codes, and the broader recovery workflow lives in how to fix the Blue Screen of Death.

How Do You Fix SYSTEM_SERVICE_EXCEPTION?

Work through the fixes in order and test stability after each one, because a single driver or corruption source usually accounts for the whole stop code. Start by reading the minidump so the rest is aimed at one device instead of the entire system:

• Update or roll back the failing driver. Match the .sys file from the minidump to its device in Device Manager (usually under Display adapters or Network adapters), then update it, or open the Driver tab and choose Roll Back Driver if crashes began after an update. For a graphics driver, run Display Driver Uninstaller in Safe Mode and install a fresh download.
• Repair system files with DISM, then SFC. Open Terminal as administrator and run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. DISM rebuilds the component store that SFC draws from, so running it first raises SFC’s success rate. Restart and re-run sfc once to confirm.
• Uninstall recent software or antivirus. In Settings > Apps > Installed apps, sort by install date and remove any antivirus, virtual drive tool, or system utility added just before the crashes. Use the vendor removal tool to fully clear an antivirus, then test on Microsoft Defender alone.
• Read the minidump module. If you skipped it, open C:\Windows\Minidump in BlueScreenView and read the Caused By Driver column, or load the dump in WinDbg and run !analyze -v. A named module points the whole fix at one device.
• Test the RAM. Run Windows Memory Diagnostic, and MemTest86 from a USB drive for several passes to catch intermittent faults. Reseat modules and test one stick at a time to isolate a bad one. Update Windows and run Driver Verifier (verifier) as a last step when no driver is ever named, then reset it with verifier /reset.

The audio and webcam class drivers (the file ks.sys is the usual name) make frequent service calls and appear often in these dumps, so update them from the device maker if they are named. Because outdated drivers lead the causes, the explanation of what drivers are shows why keeping them current prevents the exception.

Test the RAM with Windows Memory Diagnostic

Testing memory confirms or rules out defective RAM, which corrupts data during the kernel transition that produces this exception. Windows includes a built-in tester, and MemTest86 catches the intermittent faults it can miss.

1. Type Windows Memory Diagnostic in Windows Search and open it.
2. Select Restart now and check for problems, and let every pass complete.
3. Read the result in Event Viewer under the MemoryDiagnostics-Results source.
4. Run MemTest86 from a USB drive for several passes to confirm an intermittent fault.
5. Reseat each module and test one stick at a time to isolate a failing module.

Confirm the installed modules match the board specification before replacing them, as covered in the guide to how RAM works.

Uninstall Recent Software and Resolve Antivirus Conflicts

Removing recently installed software and a conflicting third-party antivirus fixes crashes that began after the program was added. Low-level utilities that hook system calls are a frequent trigger.

1. Open Settings, then Apps, then Installed apps, and sort by install date.
2. Uninstall any antivirus, virtual drive tool, or system utility added shortly before the crashes began.
3. Use the vendor removal tool to fully clear a third-party antivirus, then rely on Microsoft Defender to test stability.
4. Restart and confirm the crash is gone before reinstalling a current, supported version.

Run Driver Verifier to Find an Unnamed Driver

Driver Verifier forces an immediate crash when any third-party driver misbehaves, naming the offender when the minidump alone is inconclusive. It ships with Windows and must be reset afterward, so do not enable it unless you can turn it off.

1. Create a System Restore point before enabling Driver Verifier.
2. Type verifier in Windows Search and open Driver Verifier Manager.
3. Select Create standard settings, then Select driver names from a list.
4. Check all non-Microsoft drivers, click Finish, and restart.
5. After the next crash, read the named driver in the minidump, then run verifier /reset to turn it off.

If the system cannot boot with Driver Verifier active, enter Safe Mode from the Windows Recovery Environment and run verifier /reset to disable it.

SYSTEM_SERVICE_EXCEPTION Causes and Fixes

This table maps each likely cause to the way you confirm it and the first fix to apply, so you can move from the minidump to a targeted repair:

Last Thoughts on SYSTEM_SERVICE_EXCEPTION

SYSTEM_SERVICE_EXCEPTION is resolved by finding the one driver or corruption source that fails the user-to-kernel transition, because bug-check 0x0000003B always points to a faulty driver, a damaged system file, or bad memory rather than a vague system fault. Reading the minidump first turns the fix into a single targeted step: update or roll back the named driver, repair system files with DISM and then SFC, remove a conflicting antivirus, and test the RAM when no driver is named. Apply one change at a time and test stability after each, and the stop code clears for almost every case.

This error is one of a family of kernel stop codes that share the same diagnostic method. Related fixes are covered in the steps to fix CRITICAL_PROCESS_DIED and the wider workflow in how to fix the Blue Screen of Death. For every other common Windows fault, the hub on common PC problems connects the full set of troubleshooting guides.

Key Takeaways:

• The error is a user-to-kernel exception. A program failed a system service call, reported as bug-check 0x0000003B.
• Drivers are the leading cause. Read the failing .sys file in BlueScreenView, then update or roll back that driver. Graphics and network drivers cause most cases.
• Read the minidump first. The named module in C:\Windows\Minidump points the whole fix at one device instead of every driver.
• Repair system files next. Run DISM, then SFC, to fix corrupt Windows components when no driver is named.
• Test RAM and remove low-level software. Windows Memory Diagnostic confirms bad memory, and a conflicting antivirus or utility often triggers the crash.
• Keep drivers, files, and Windows current. Manufacturer drivers, periodic SFC and DISM runs, and the latest updates stop the exception from returning.

Frequently Asked Questions (FAQs)