How to Fix SYSTEM_SERVICE_EXCEPTION

SYSTEM_SERVICE_EXCEPTION is a Windows stop error with the bug-check value 0x0000003B, and the most common cause is a faulty or outdated device driver that crosses from user mode to kernel mode improperly. The error also follows corrupt system files, defective RAM, and conflicts from recently installed software such as third-party antivirus. This article explains what SYSTEM_SERVICE_EXCEPTION means, names the common culprits, and gives the step-by-step fixes that resolve it.

Each fix names the exact Windows tool, including the minidump, BlueScreenView, Windows Event Viewer, Device Manager, SFC, DISM, the Windows Memory Diagnostic, and Driver Verifier. The fixes are ordered from the most common, such as identifying and updating the failing driver, to memory tests, software removal, and a controlled Driver Verifier run.

Apply the fixes in order and test stability after each one, because a single driver or corruption source usually accounts for this stop code. A diagnostic table near the end maps each cause to its confirmation method and first fix.

What Does SYSTEM_SERVICE_EXCEPTION Mean?

SYSTEM_SERVICE_EXCEPTION means a process raised an exception while transitioning from user mode to kernel mode through a system service call, so the kernel halted to prevent corrupted execution. The points below explain the common sources, ranked from most to least frequent.

• A faulty or outdated driver. A driver that makes an illegal kernel call or accesses memory incorrectly is the leading cause of this stop code.
• Corrupt system files. Damaged Windows components from a failed update or disk error fail during a service call and trigger the exception.
• Defective RAM. Bad memory cells alter data during a kernel transition, so the exception surfaces under load.
• Conflicting third-party software. Antivirus, virtual drive tools, and low-level utilities that hook system calls cause the exception.
• Graphics and network drivers specifically. Display and network adapter drivers are named in most SYSTEM_SERVICE_EXCEPTION minidumps.

Identify the Failing Driver from the Minidump

Identifying the driver named in the crash file points the fix at one device instead of every driver on the system. Windows writes a minidump to C:\Windows\Minidump after each stop error.

1. Open C:\Windows\Minidump in BlueScreenView after the crash.
2. Read the Caused By Driver column to find the responsible .sys file.
3. Open Windows Event Viewer, expand Windows Logs, and select System to find the matching BugCheck error near the crash time.
4. For deeper analysis, open the dump in WinDbg and run !analyze -v to confirm the failing module.
5. Match the named .sys file to its device in Device Manager, often a GPU, network, or audio driver.

A graphics driver such as nvlddmkm.sys points to the display adapter, while a network driver points to the Wi-Fi or Ethernet adapter. The exact code and its place among the others is covered in the reference on reading BSOD stop codes.

Update or Roll Back the Failing Driver

Updating the named driver, or rolling back a driver that began crashing after an update, resolves the largest share of SYSTEM_SERVICE_EXCEPTION crashes. Graphics and network drivers cause most cases.

1. Open Device Manager and expand Display adapters, Network adapters, and Sound, video and game controllers.
2. Right-click the device that matches the failing .sys file, select Update driver, then Search automatically for drivers.
3. Download the newest driver from the GPU, network, or PC maker if Windows reports none.
4. If crashes began after a driver update, open Properties, select the Driver tab, and click Roll Back Driver.
5. Restart and test stability for several hours after each change.

For a display driver named in the dump, run Display Driver Uninstaller from Safe Mode and then install a freshly downloaded driver to clear leftover files that a normal update leaves behind.

Run SFC and DISM to Repair System Files

Repairing corrupt system files removes a common cause of the exception when no driver is named or crashes occur during boot. SFC and DISM are built-in command-line tools.

1. Right-click Start and open Terminal or Command Prompt as administrator.
2. Run DISM /Online /Cleanup-Image /RestoreHealth and wait for it to finish.
3. Run sfc /scannow to scan and repair protected system files.
4. Restart the computer after both tools report completion.
5. Re-run sfc /scannow once more to confirm no further corruption remains.

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 memory tester, and MemTest86 catches intermittent faults.

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.

Update Windows

Installing the latest Windows updates corrects kernel bugs that cause SYSTEM_SERVICE_EXCEPTION on outdated builds. Quality updates patch the service-call paths that raise the exception.

1. Open Settings, then Windows Update, and select Check for updates.
2. Install every available quality update and feature update.
3. Restart when prompted and allow the update to finish configuring.
4. Open Update history to confirm the updates installed without error.
5. Test stability under normal use after the system is fully updated.

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. The tool ships with Windows and must be reset afterward.

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.

Boot into Safe Mode to Apply Fixes

Safe Mode loads Windows with only essential drivers so repairs run when the system crashes during normal startup. It is reached from the Windows Recovery Environment.

1. Force three failed boots to trigger the Windows Recovery Environment, or hold Shift and click Restart from the sign-in screen.
2. Select Troubleshoot, then Advanced options, then Startup Settings, and enable Safe Mode.
3. Run SFC and DISM from an administrator command line inside Safe Mode.
4. Uninstall the suspect driver, update, or application that preceded the crashes.
5. Restart into normal Windows and test stability.

When Safe Mode cannot resolve the crash, System Restore from Advanced options reverses recent driver and update changes to a point before the first failure.

Disable Automatic Restart to Read the Stop Code

Turning off automatic restart keeps the SYSTEM_SERVICE_EXCEPTION screen visible long enough to record the failing .sys file when the system reboots too fast to read it. The setting sits in System Properties and also confirms minidumps are written.

1. Open System Properties, then Advanced system settings.
2. Under Startup and Recovery, click Settings.
3. Clear the Automatically restart checkbox.
4. Confirm a small memory dump is selected so a minidump is written after each crash.
5. Save changes so the next crash holds the stop code and any file name on screen.

With automatic restart disabled, the file named under “What failed” stays visible to photograph and match against a device in Device Manager.

Update Audio and Webcam Drivers

Updating audio and webcam drivers resolves SYSTEM_SERVICE_EXCEPTION cases that name multimedia or capture devices in the minidump. These class drivers make frequent system service calls and appear often in crash files.

1. Open Device Manager and expand Sound, video and game controllers, and Cameras.
2. Right-click the audio or webcam device, select Update driver, then Search automatically for drivers.
3. Download the newest driver from the laptop or device maker if Windows reports none.
4. Remove a duplicate or generic audio driver left by a virtual audio tool.
5. Restart and test stability with the updated multimedia drivers.

Prevent SYSTEM_SERVICE_EXCEPTION From Returning

Keeping the exception from returning depends on current drivers, intact system files, and a clean set of low-level software. A few routine actions hold the system stable.

• Install drivers from the device maker. Manufacturer graphics, network, and audio drivers avoid the illegal kernel calls that raise the exception.
• Run SFC and DISM periodically. Routine repairs keep system files free of the corruption behind the code.
• Limit low-level utilities. Avoid stacking multiple antivirus tools or virtual drive utilities that hook system calls.
• Keep Windows updated. Quality updates patch the service-call paths that trigger the exception on older builds.

SYSTEM_SERVICE_EXCEPTION Causes and Fixes

Key Takeaways

• The error is a user-to-kernel exception. A process failed a system service call, named by bug-check 0x0000003B.
• Drivers are the leading cause. Read the failing .sys file in BlueScreenView, then update or roll back that driver.
• Repair system files next. Run DISM, then SFC, to fix corrupt Windows components behind the exception.
• Test RAM when no driver is named. Windows Memory Diagnostic and MemTest86 confirm defective memory.
• Remove conflicting software. A third-party antivirus or low-level utility often triggers the crash.

Last Thoughts on SYSTEM_SERVICE_EXCEPTION

SYSTEM_SERVICE_EXCEPTION is resolved by finding the driver or corruption that fails the user-to-kernel transition, because the bug-check 0x0000003B always points to a faulty driver, damaged file, or bad memory. Updating or rolling back the named driver, repairing system files with DISM and SFC, and testing RAM cover the common sources. The full crash workflow and the meaning of every code are covered in the guides to fixing the Blue Screen of Death and reading BSOD stop codes.

Related stop codes are handled in the steps to fix KERNEL_SECURITY_CHECK_FAILURE, fix CRITICAL_PROCESS_DIED, and fix PAGE_FAULT_IN_NONPAGED_AREA. Because outdated drivers lead the causes, the explanation of what drivers are clarifies why keeping them current prevents the exception.