What is the stop code SYSTEM_SERVICE_EXCEPTION in Windows 11 and what causes it?

The stop code SYSTEM_SERVICE_EXCEPTION (0x0000003B) appears when a kernel-mode process executes an illegal or unexpected instruction that Windows cannot recover from. The most common causes are corrupt or outdated device drivers (especially graphics, network, and audio drivers), corrupt Windows system files, faulty RAM, third-party security software interfering with kernel operations, and virtualization software conflicts (particularly VMware Tools). The faulting module listed in the crash dump — such as nvlddmkm.sys, win32k.sys, or dxgkrnl.sys — usually identifies the specific culprit.

How do I fix the blue screen SYSTEM_SERVICE_EXCEPTION in Windows 11 when I can't boot into Windows?

If Windows 11 won't boot, restart your PC and interrupt the boot three times in a row (hold the power button) to enter the Windows Recovery Environment (WinRE). From there, go to Troubleshoot > Advanced Options > Command Prompt and run: 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth'. You can also try Startup Repair from the same Advanced Options menu. If a restore point exists, use System Restore. As a last resort, perform an in-place repair upgrade using Windows 11 installation media, choosing to keep your files and apps.

Why does SYSTEM_SERVICE_EXCEPTION BSOD happen in Windows 11 VMware virtual machines?

This BSOD in a VMware VM is most commonly caused by outdated or corrupted VMware Tools, particularly the vmci.sys or vsock.sys drivers included with VMware Tools. Other causes include running an older VMware Workstation version that lacks full Windows 11 support (version 17+ is recommended), incorrect VM firmware settings (should be UEFI for Windows 11), and missing virtualization-based security compatibility flags in the .vmx configuration file. Fix it by fully uninstalling and reinstalling the latest VMware Tools, updating VMware Workstation, and adding Hyper-V compatibility flags to the VM's .vmx file.

Can antivirus software cause SYSTEM_SERVICE_EXCEPTION on Windows 11?

Yes. Antivirus and endpoint security software operate at the kernel level using drivers that intercept system calls. If these drivers are outdated, incompatible with a recent Windows 11 update, or have a bug, they can cause a SYSTEM_SERVICE_EXCEPTION BSOD. Common culprits include McAfee, Norton, Avast, Bitdefender, and Webroot. To test if your antivirus is the cause, boot into Safe Mode with Networking (which prevents most third-party drivers from loading) and observe whether the BSOD recurs. If stable in Safe Mode, temporarily uninstall your antivirus and test in normal mode. Always replace it with an updated version.

How do I find which driver is causing SYSTEM_SERVICE_EXCEPTION in Windows 11?

The most reliable method is to analyze the minidump file created at the time of the crash. Navigate to C:\Windows\Minidump\ and open the most recent .dmp file using WinDbg Preview (free from the Microsoft Store). Run the command '!analyze -v' inside WinDbg. The output will show the faulting module (e.g., 'nvlddmkm.sys' for NVIDIA, 'ataport.sys' for storage, 'netio.sys' for networking). Alternatively, open the Windows Event Viewer, navigate to Windows Logs > System, and look for Critical events around the time of the crash. The 'BlueScreen' source entries show the stop code and often the faulting driver filename.

SYSTEM_SERVICE_EXCEPTION Windows 11: Complete BSOD Fix Guide (Stop Code 0x0000003B)

Fix SYSTEM_SERVICE_EXCEPTION BSOD on Windows 11. Step-by-step guide covering driver updates, SFC scans, VMware fixes, and registry repairs. Resolve stop code 0x

Last updated: March 1, 2026

Last verified: March 1, 2026

2,300 words

Key Takeaways

Root Cause 1: Corrupt, outdated, or incompatible device drivers (most commonly graphics, network, or antivirus drivers) triggering a kernel-mode exception that Windows cannot recover from, resulting in stop code 0x0000003B.
Root Cause 2: Corrupt system files, faulty RAM, or conflicting third-party software (including VMware tools, VPN clients, and security software) causing illegal system service calls in privileged kernel mode.
Quick Fix Summary: Run 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth' in an elevated Command Prompt, update or roll back suspect drivers via Device Manager, check RAM with Windows Memory Diagnostic, and boot into Safe Mode to isolate third-party software conflicts.

Fix Approaches Compared
Method	When to Use	Time	Risk
SFC + DISM Scan	System files are corrupted; BSOD occurs randomly without a clear driver culprit	15-30 min	Low
Driver Rollback / Update	BSOD started after a Windows Update or new hardware installation	5-15 min	Low
Windows Memory Diagnostic	System crashes under load or after multiple random BSODs	30-60 min	Low
Clean Boot / Safe Mode	BSOD appears to be triggered by third-party software or startup apps	10-20 min	Low
VMware Tools Reinstall	BSOD occurs only inside a VMware virtual machine running Windows 11	10-20 min	Low
Check Disk (CHKDSK)	Disk errors or failing storage device suspected	30-90 min	Low-Medium
System Restore	BSOD began after a recent change and a restore point exists	20-40 min	Medium
In-Place Upgrade Repair	All other methods fail; OS integrity severely compromised	60-120 min	Medium
Full Windows 11 Reinstall	Hardware is healthy but OS is unrecoverable	2-4 hours	High (data loss risk)

Understanding the SYSTEM_SERVICE_EXCEPTION Error on Windows 11

When Windows 11 encounters a SYSTEM_SERVICE_EXCEPTION blue screen (stop code 0x0000003B), it means the operating system detected an exception while executing a routine in privileged kernel mode that could not be handled gracefully. Rather than risk data corruption, Windows immediately halts all operations and displays the BSOD.

The exact screen you will see reads:

Your PC ran into a problem and needs to restart.
Stop code: SYSTEM_SERVICE_EXCEPTION

In some cases Windows also displays a secondary parameter, such as:

SYSTEM_SERVICE_EXCEPTION (nt!KiSystemServiceCopyEnd+0x13)
SYSTEM_SERVICE_EXCEPTION (win32k.sys)
SYSTEM_SERVICE_EXCEPTION (nvlddmkm.sys) — NVIDIA graphics driver
SYSTEM_SERVICE_EXCEPTION (dxgkrnl.sys) — DirectX kernel
SYSTEM_SERVICE_EXCEPTION (vmci.sys) — VMware connectivity

The file name listed in parentheses is your single best diagnostic clue. It identifies which driver or system component triggered the crash.

Step 1: Capture and Read the Minidump File

Before fixing anything, collect data. Windows 11 writes a minidump to C:\Windows\Minidump\ after every BSOD.

Open File Explorer and navigate to C:\Windows\Minidump.
Note the most recent .dmp file (e.g., Mini121524-01.dmp).
Open WinDbg (download from the Microsoft Store as "WinDbg Preview") or use the command-line tool:

windbg -y "srv*c:\symbols*https://msdl.microsoft.com/download/symbols" -z "C:\Windows\Minidump\Mini121524-01.dmp"

In WinDbg, type !analyze -v to get the full crash analysis, including the faulting module.

If you cannot boot into Windows normally, boot to the Windows Recovery Environment (WinRE) by holding Shift while clicking Restart, then go to Troubleshoot > Advanced options > Command Prompt.

Step 2: Run SFC and DISM to Repair System Files

Corrupt Windows system files are a leading cause of this BSOD. Run these commands as Administrator in sequence:

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

After DISM completes, run sfc /scannow once more. Restart when prompted. If SFC reports it cannot fix files, you may need to run it from WinRE or perform a repair upgrade.

Step 3: Update or Roll Back Problem Drivers

If the minidump named a specific .sys file, target that driver directly.

To roll back a driver:

Press Win + X → Device Manager.
Expand the relevant category (e.g., Display Adapters for nvlddmkm.sys).
Right-click the device → Properties → Driver tab → Roll Back Driver.

To update a driver:

Visit the manufacturer's website directly (NVIDIA, AMD, Intel, Realtek, etc.).
Download and install the latest WHQL-certified driver.
Avoid using Windows Update drivers for graphics cards — always prefer manufacturer packages.

To uninstall a problematic driver completely (e.g., GPU):

pnputil /delete-driver oem27.inf /uninstall /force

Use Display Driver Uninstaller (DDU) in Safe Mode for GPU drivers to ensure a completely clean state before reinstalling.

Step 4: Check RAM with Windows Memory Diagnostic

Faulty RAM can cause unpredictable kernel exceptions.

Press Win + R, type mdsched.exe, press Enter.
Choose Restart now and check for problems.
The tool runs two passes by default. Press F1 to enable extended tests (recommended).
After reboot, check Event Viewer → Windows Logs > System and filter for source MemoryDiagnostics-Results.

If errors are found, run MemTest86 (bootable USB) for a more thorough test. Faulty RAM must be reseated or replaced.

Step 5: Check for Disk Errors

chkdsk C: /f /r /x

This schedules a disk check on next reboot. The /r flag locates bad sectors. On SSDs, bad sectors are less common, but logical file system errors still occur. Allow the check to complete fully before evaluating results.

Step 6: Isolate Third-Party Software with Clean Boot

Antivirus software, VPN clients, and virtualization tools frequently conflict with Windows 11's kernel.

Press Win + R, type msconfig, press Enter.
On the Services tab, check Hide all Microsoft services, then click Disable all.
On the Startup tab, click Open Task Manager and disable all startup items.
Restart and test. If the BSOD stops, re-enable services in batches to find the culprit.

Common offenders include: McAfee, Norton, Avast, Bitdefender kernel drivers, Cisco AnyConnect, GlobalProtect VPN, OBS virtual camera, and audio processing software like Nahimic or Sonic Suite.

Step 7: Fix SYSTEM_SERVICE_EXCEPTION in VMware

If Windows 11 is running as a VMware virtual machine, the BSOD is almost always caused by:

Outdated VMware Tools (especially vmci.sys, vsock.sys)
Incorrect VM hardware version
Missing Hyper-V compatibility settings

Fix steps:

Inside the VM, open VMware Tools installer from the VM menu → Reinstall VMware Tools.
Uninstall VMware Tools completely, reboot, then reinstall the latest version from the VMware website.
In VMware Workstation, edit the VM settings → Options > Advanced > Firmware type — ensure it matches the Windows 11 requirement (UEFI).
Add the following lines to your .vmx file to improve compatibility:

hypervisor.cpuid.v0 = "FALSE"
mce.enable = "TRUE"
vhv.enable = "TRUE"

Ensure your VMware Workstation version is 17+ for full Windows 11 support.

Step 8: Use System Restore or Perform a Repair Upgrade

System Restore (if a restore point exists):

Boot into WinRE → Troubleshoot > Advanced options > System Restore.
Choose a restore point dated before the BSOD began.

In-place repair upgrade (last resort before reinstall):

Download the Windows 11 ISO from Microsoft's official site.
Mount the ISO and run setup.exe.
Choose Keep personal files and apps.
This reinstalls Windows 11 system files while preserving your data.

Additional Tips

Disable Fast Startup: Go to Control Panel > Power Options > Choose what the power buttons do > Turn off fast startup. Fast startup can cause driver state issues on resume.
Update BIOS/UEFI firmware: An outdated BIOS can cause hardware-level exceptions. Visit your motherboard manufacturer's support page.
Check Windows Update: Some BSOD variants are fixed by cumulative updates. Go to Settings > Windows Update > Check for updates.

Frequently Asked Questions

bash

# ============================================================
# Windows 11 SYSTEM_SERVICE_EXCEPTION Diagnostic & Fix Script
# Run all commands in an ELEVATED (Administrator) Command Prompt
# or PowerShell. Commands marked [PS] require PowerShell.
# ============================================================

# --- STEP 1: Check system file integrity ---
sfc /scannow

# --- STEP 2: DISM image health check and repair ---
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

# Run SFC again after DISM completes
sfc /scannow

# --- STEP 3: Schedule disk check on next reboot ---
chkdsk C: /f /r /x
# Type Y when prompted to schedule on next restart, then reboot

# --- STEP 4: View recent minidump crash details [PS] ---
# Install WinDbg from Microsoft Store, or use this PowerShell snippet
# to list recent minidump files by date:
Get-ChildItem "C:\Windows\Minidump\" | Sort-Object LastWriteTime -Descending | Select-Object -First 5

# --- STEP 5: Check Event Log for BSOD entries [PS] ---
Get-WinEvent -LogName System | Where-Object { $_.LevelDisplayName -eq 'Critical' } | Select-Object -First 10 | Format-List TimeCreated, Message

# --- STEP 6: List all installed third-party drivers [PS] ---
# Helps identify non-Microsoft drivers that may be causing the crash
Get-WmiObject Win32_PnPSignedDriver | Where-Object { $_.Manufacturer -ne 'Microsoft' } | Select-Object DeviceName, DriverVersion, Manufacturer | Sort-Object DeviceName | Format-Table -AutoSize

# --- STEP 7: Export driver list to CSV for review [PS] ---
Get-WmiObject Win32_PnPSignedDriver | Select-Object DeviceName, DriverVersion, Manufacturer, DriverDate | Export-Csv -Path "$env:USERPROFILE\Desktop\drivers_export.csv" -NoTypeInformation

# --- STEP 8: Check for driver verifier issues ---
# Enable Driver Verifier to catch faulty drivers (WARNING: may cause more BSODs temporarily)
# Only enable if you have identified a specific suspect driver.
verifier /standard /driver <suspect_driver.sys>
# To reset Driver Verifier after diagnosis:
verifier /reset

# --- STEP 9: Roll back a specific driver (example: NVIDIA) ---
# Find the OEM INF number for the driver first:
pnputil /enum-drivers
# Then uninstall using the identified OEM number:
# pnputil /delete-driver oem27.inf /uninstall /force

# --- STEP 10: Check RAM via Windows Memory Diagnostic ---
mdsched.exe
# Select "Restart now and check for problems"
# After reboot, view results in Event Viewer:
# Path: Event Viewer > Windows Logs > System > Source: MemoryDiagnostics-Results

# --- STEP 11: Disable Fast Startup via registry [PS] ---
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Power" -Name HiberbootEnabled -Value 0

# --- STEP 12: Check Windows Update status [PS] ---
Get-WindowsUpdateLog
# Or trigger update check:
Start-Process "ms-settings:windowsupdate"

# --- STEP 13: VMware-specific fix (run inside the VM) ---
# Check VMware Tools service status:
sc query VMTools
# Restart VMware Tools service:
net stop VMTools && net start VMTools
# If VMware Tools is broken, reinstall from VMware menu:
# VM menu > Reinstall VMware Tools

# ============================================================
# After each fix step, restart the PC and monitor for BSODs.
# Use the minidump analysis to confirm the fix worked.
# ============================================================

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SRE specialists, and Windows systems administrators with a combined 40+ years of experience diagnosing kernel panics, BSODs, and system-level failures across enterprise and consumer environments. Our guides are grounded in real crash dump analysis, Microsoft documentation, and hands-on lab testing. We specialize in translating cryptic stop codes into actionable, step-by-step remediation procedures for both developers and general users.

Sources

Explore More windows Guides

Acer Aspire Blue Screen of Death Fix: How to Stop BSOD Crashes on Acer Laptops

Fix Acer Aspire Blue Screen of Death errors fast. Step-by-step guide covering driver updates, RAM checks, overheating, and Windows repair commands.

Acer Aspire Blue Screen of Death Fix: Step-by-Step Troubleshooting Guide (BSOD Errors Solved)

Fix Acer Aspire blue screen of death errors fast. Covers MEMORY_MANAGEMENT, DRIVER_IRQL, KERNEL_SECURITY_CHECK and more. Step-by-step commands included.

Acer Aspire Blue Screen of Death Fix: Stop Codes, Causes & Complete Solutions

Fix Acer Aspire Blue Screen of Death errors fast. Covers MEMORY_MANAGEMENT, DRIVER_IRQL, KERNEL_SECURITY_CHECK_FAILURE & more with exact commands.