The SYSTEM_SERVICE_EXCEPTION error is a Windows Blue Screen of Death (BSOD) that usually appears when Windows encounters an exception while executing privileged system code. The computer stops immediately and normally restarts to prevent further instability or possible data corruption.

The error commonly appears as:

Your device ran into a problem and needs to restart.

Stop code: SYSTEM_SERVICE_EXCEPTION

The corresponding Windows bug check is:

0x0000003B

Although the error may look like a Windows operating-system failure, the actual cause is often a faulty or incompatible device driver, memory corruption, damaged system files, unstable hardware, security software, or a recently introduced software or driver change.

This guide explains what SYSTEM_SERVICE_EXCEPTION means, its common causes, how to diagnose the responsible driver, and the recommended troubleshooting procedure for Windows 11 and Windows 10.

What Is SYSTEM_SERVICE_EXCEPTION?

SYSTEM_SERVICE_EXCEPTION corresponds to Windows bug check:

0x0000003B

Microsoft defines this bug check as an exception occurring while Windows executes a routine that transitions from non-privileged code to privileged code.

In practical terms, Windows encountered an unexpected condition while executing code with kernel-level privileges.

Because kernel-mode code has extensive access to memory and hardware, Windows cannot safely continue after certain exceptions. It therefore stops the operating system and displays the blue screen.

The problem may originate from Windows itself, but third-party kernel drivers are frequently involved.

What Does Bug Check 0x0000003B Mean?

The bug check contains four parameters that can be useful during crash-dump analysis.

Parameter 1: Exception code that caused the crash

Parameter 2: Address of the instruction that generated the exception

Parameter 3: Address of the context record for the exception

Parameter 4: Reserved and normally zero

One frequently encountered exception code is:

0xC0000005 – STATUS_ACCESS_VIOLATION

This indicates that code attempted an invalid memory access.

This does not automatically mean that your physical RAM is defective. Invalid memory access can also result from a defective driver, corrupted data structures, premature memory release, or another software component corrupting memory.

Common Symptoms

A computer affected by SYSTEM_SERVICE_EXCEPTION may show one or more of the following symptoms:

• Random blue-screen crashes
• SYSTEM_SERVICE_EXCEPTION during startup
• BSOD immediately after signing in
• Crash when opening a particular application
• Crash during gaming or graphics-intensive applications
• BSOD after installing Windows updates
• BSOD after installing or updating a driver
• Unexpected restart without warning
• Computer freezing before the blue screen appears
• Repeated crashes several times per day
• SYSTEM_SERVICE_EXCEPTION during shutdown
• SYSTEM_SERVICE_EXCEPTION after waking from sleep
• Boot loop caused by repeated BSODs

Sometimes Windows also displays a .sys filename.

Examples include:

win32kfull.sys

ntoskrnl.exe

nvlddmkm.sys

dxgkrnl.sys

ndis.sys

ntfs.sys

fltmgr.sys

A filename displayed in the crash information is an important diagnostic clue, but it should not automatically be assumed to be the root cause.

For example, ntoskrnl.exe is a core Windows kernel component. If it appears in a crash dump, another driver or hardware problem may have corrupted memory before the kernel finally crashed.

Major Causes of SYSTEM_SERVICE_EXCEPTION

1. Faulty or Incompatible Device Drivers

Device drivers are among the first things to investigate.

Potentially involved drivers include:

• Graphics drivers
• Network drivers
• Wi-Fi drivers
• Bluetooth drivers
• Audio drivers
• Storage controller drivers
• Chipset drivers
• USB drivers
• Printer drivers
• VPN drivers
• Virtualization drivers
• Antivirus filter drivers
• Backup software drivers

A driver may become problematic after Windows Update, a driver update, firmware change, or software installation.

2. Graphics Driver Problems

Display drivers frequently operate at a low system level and interact heavily with memory and the Windows graphics subsystem.

Problems may occur with NVIDIA, AMD, or Intel graphics drivers.

If crashes started immediately after updating the graphics driver, consider rolling back the driver.

Open:

Device Manager → Display adapters

Right-click the graphics adapter and select:

Properties → Driver → Roll Back Driver

If rollback is unavailable, download the appropriate driver from the computer or GPU manufacturer's official support site.

3. Corrupted Windows System Files

Corruption of important Windows files may contribute to system instability.

Windows includes built-in servicing and system-file verification tools that should be used before considering a reinstall.

Open Terminal (Admin) or Command Prompt (Admin).

Run:

DISM /Online /Cleanup-Image /RestoreHealth

After DISM completes, run:

sfc /scannow

Restart Windows after the scan.

DISM repairs the Windows component store used for servicing, while SFC verifies protected system files and replaces damaged copies when possible.

4. RAM or Memory Instability

Memory problems can produce unpredictable BSOD codes, including SYSTEM_SERVICE_EXCEPTION.

Problems may result from:

• Defective RAM
• Poorly seated RAM
• Incompatible memory modules
• Aggressive memory timings
• XMP/EXPO instability
• CPU memory-controller instability
• Motherboard problems
• Overclocking

To run the built-in Windows memory test:

Press:

Windows + R

Enter:

mdsched.exe

Select:

Restart now and check for problems

For persistent unexplained crashes, a longer dedicated memory test can provide more confidence than a quick Windows memory test.

5. Recent Windows or Driver Updates

If the computer worked correctly before an update, establish exactly what changed.

Check:

Settings → Windows Update → Update history

Look for:

• Quality updates
• Driver updates
• Firmware updates
• Definition/security updates
• Optional driver updates

Do not automatically uninstall security updates simply because a BSOD occurred afterward. First investigate whether a driver, firmware, or application incompatibility was introduced at approximately the same time.

If a particular driver caused the problem, rolling back that driver is usually preferable to broadly disabling Windows Update.

6. Third-Party Antivirus and Security Software

Security products often install low-level drivers for:

• File-system filtering
• Web protection
• Network inspection
• Ransomware protection
• Endpoint monitoring

A defective or incompatible filter driver can contribute to kernel crashes.

If SYSTEM_SERVICE_EXCEPTION started immediately after installing or upgrading security software, update the product first.

If necessary, temporarily uninstall the third-party security product as a diagnostic test and determine whether the crashes stop.

Do not leave a production computer permanently unprotected.

7. Storage Problems

SSD/HDD errors, storage-controller problems, firmware bugs, or file-system corruption can also destabilize Windows.

Run:

chkdsk C: /scan

This performs an online scan.

If Windows reports problems requiring an offline repair, you can subsequently use:

chkdsk C: /f

Windows may ask to schedule the check for the next restart.

Also check the health of the SSD or HDD using the storage manufacturer's diagnostic utility when persistent disk-related symptoms are present.

8. BIOS, Firmware, or Chipset Problems

An outdated BIOS/UEFI or chipset package may cause compatibility problems, especially after major hardware or Windows changes.

Check your PC or motherboard manufacturer's support page for:

• BIOS/UEFI updates
• Chipset drivers
• Intel Management Engine components
• AMD chipset packages
• Storage controller firmware
• SSD firmware

Important: BIOS updates should only be performed using the manufacturer's documented procedure. Power interruption or using the wrong firmware can make a system unbootable.

9. Overclocking, Undervolting, XMP, or EXPO

A computer can appear stable during normal use yet crash when a particular kernel workload stresses memory, CPU, or GPU differently.

For troubleshooting, temporarily restore default settings.

Disable or reset:

• CPU overclocking
• GPU overclocking
• CPU undervolting
• GPU undervolting
• XMP
• EXPO
• Manual RAM timings

Then test the computer again.

If the BSOD disappears, reintroduce changes one at a time to identify the unstable setting.

Step-by-Step SYSTEM_SERVICE_EXCEPTION Troubleshooting

Step 1: Record the Exact BSOD Information

Before making changes, record:

• Stop code
• Any .sys filename
• Date and time of crash
• What application was running
• Whether Windows had recently updated
• Recently installed hardware
• Recently installed drivers
• Recently installed security software

This can dramatically reduce troubleshooting time.

Step 2: Check Device Manager

Press:

Windows + X → Device Manager

Look for devices displaying a yellow warning icon.

Pay particular attention to:

• Display adapters
• Network adapters
• Storage controllers
• Sound controllers
• USB controllers
• System devices

Update or reinstall suspicious drivers.

For branded laptops and desktops, OEM-provided drivers may sometimes be more appropriate than generic drivers.

Step 3: Update Critical Drivers

Prioritize:

1. Chipset
2. Graphics
3. Storage controller
4. Network/Wi-Fi
5. Bluetooth
6. Audio
7. USB/Thunderbolt
8. Other hardware-specific drivers

Use drivers appropriate for your exact computer or motherboard model.

Step 4: Roll Back Recently Updated Drivers

If the problem started after a driver update:

Device Manager → Device → Properties → Driver → Roll Back Driver

If rollback is unavailable, uninstall the problematic driver and install a known stable version from the hardware manufacturer's support site.

Step 5: Repair Windows with DISM

Open Command Prompt as Administrator and execute:

DISM /Online /Cleanup-Image /ScanHealth

Then:

DISM /Online /Cleanup-Image /RestoreHealth

Allow the process to complete.

Do not close the window merely because the percentage appears to remain unchanged for some time.

Step 6: Run System File Checker

After DISM completes:

sfc /scannow

Possible results include:

Windows Resource Protection did not find any integrity violations.

This indicates that SFC did not detect corrupted protected system files.

Another possible result is that corrupted files were found and successfully repaired.

Restart the computer afterward.

Step 7: Check Windows Event Viewer

Press:

Windows + R

Enter:

eventvwr.msc

Navigate to:

Windows Logs → System

Check events occurring immediately before and after the BSOD.

Look for:

• Critical events
• Driver failures
• Disk errors
• Storage errors
• WHEA hardware events
• Service failures
• Unexpected shutdown events

Do not assume that every red error is responsible for the crash. Focus on events matching the BSOD timestamp.

Step 8: Use Reliability Monitor

Reliability Monitor provides a useful timeline of system failures.

Press Windows + R and run:

perfmon /rel

Look for:

• Windows failures
• Application failures
• Hardware errors
• Driver installation events
• Windows updates

Select the day of the crash and examine events around the same time.

Step 9: Test RAM

Run:

mdsched.exe

Choose the restart-and-test option.

If multiple RAM modules are installed and crashes continue, advanced troubleshooting may involve testing modules individually.

For example, with two modules:

1. Test both normally.
2. Test module A individually.
3. Test module B individually.
4. Test different motherboard slots if necessary.

This can help distinguish a defective DIMM from a defective slot or memory-channel problem.

Step 10: Check Storage

Start with:

chkdsk C: /scan

If Windows reports that offline repair is necessary:

chkdsk C: /f

For SSDs, also check:

• SMART/health status
• Manufacturer diagnostics
• Firmware availability
• Storage-controller driver

Frequent disk, NTFS, or controller errors in Event Viewer should be investigated carefully.

Step 11: Perform a Clean Boot

A clean boot can help determine whether a third-party service or startup application contributes to the problem.

Press:

Windows + R

Enter:

msconfig

Open the Services tab.

Select:

Hide all Microsoft services

Then choose:

Disable all

Next open:

Task Manager → Startup apps

Disable unnecessary third-party startup applications and restart the computer.

Important: Hide Microsoft services before disabling services. Do not indiscriminately disable Windows services.

If the crashes disappear, re-enable items gradually until the conflicting component is identified.

Step 12: Boot into Safe Mode

Safe Mode loads Windows with a reduced set of drivers and services.

If Windows operates reliably in Safe Mode but repeatedly crashes during normal startup, investigate third-party:

• Drivers
• Services
• Security products
• Startup applications
• Hardware utilities

Safe Mode does not prove that hardware is healthy, but it can significantly narrow the investigation.

Step 13: Examine Windows Minidump Files

Windows may save crash dumps in:

C:\Windows\Minidump

Full or kernel dumps may be stored as:

C:\Windows\MEMORY.DMP

Dump files can reveal:

• Bug check code
• Exception code
• Faulting instruction
• Loaded modules
• Driver stack
• Process active during the crash

For professional troubleshooting, dump analysis is much more reliable than repeatedly changing drivers at random.

Advanced Diagnosis with WinDbg

Microsoft WinDbg can analyze Windows crash dump files.

After opening the dump, one of the most useful initial commands is:

!analyze -v

For SYSTEM_SERVICE_EXCEPTION, Microsoft also documents using the context record associated with bug-check parameter 3.

A debugger may use:

.cxr <address>

followed by:

kb

to examine the stack.

Other useful debugger commands may include:

lm t n

which displays loaded modules.

Experienced technicians should compare several dump files rather than relying on only one crash.

If the same third-party driver repeatedly appears in multiple independent dumps, confidence that it is involved increases considerably.

Understanding Common .SYS Files

ntoskrnl.exe

This is the Windows NT kernel.

Seeing it in a crash report does not necessarily mean Windows itself is defective.

Another driver, unstable RAM, or corrupted memory may have caused the kernel to crash.

nvlddmkm.sys

Normally associated with NVIDIA graphics drivers.

Investigate:

• NVIDIA driver version
• Recent GPU driver update
• GPU temperature
• GPU overclocking
• Graphics-driver corruption

A clean graphics-driver reinstall may be appropriate.

dxgkrnl.sys

Associated with the Microsoft DirectX graphics kernel.

Investigate GPU drivers, graphics hardware, and software interacting with the graphics stack.

ndis.sys

NDIS is part of the Windows networking subsystem.

Do not automatically replace ndis.sys.

Instead investigate components interacting with networking, such as:

• Ethernet drivers
• Wi-Fi drivers
• VPN software
• Firewall products
• Network-filter drivers
• Endpoint-security software

win32kfull.sys

This is part of the Windows graphical/kernel subsystem.

If it appears repeatedly, investigate:

• Graphics drivers
• Display-related utilities
• Third-party kernel drivers
• System-file corruption
• Memory instability

Again, the Microsoft component appearing at the crash point may be the victim rather than the original cause.

Using Driver Verifier

Windows includes an advanced diagnostic utility called Driver Verifier.

Run:

verifier

Driver Verifier intentionally places additional checks and stress on kernel drivers so that faulty behavior becomes easier to identify.

However, this tool should be used carefully.

It can deliberately trigger additional BSODs and can make an already unstable computer difficult to boot.

For this reason, Driver Verifier is best suited to experienced technicians who understand Safe Mode, Windows Recovery Environment, and crash-dump analysis.

Microsoft recommends verifying the smallest practical set of suspected drivers rather than unnecessarily testing everything.

To turn Driver Verifier off from an elevated command prompt:

verifier /reset

Then restart Windows.

What If Windows Cannot Boot?

If SYSTEM_SERVICE_EXCEPTION causes a boot loop, enter the Windows Recovery Environment.

You can then use:

Troubleshoot → Advanced options

Possible recovery options include:

• Startup Settings
• Safe Mode
• Startup Repair
• System Restore
• Uninstall Updates
• Command Prompt

Try Safe Mode first if a recently installed driver or software package is suspected.

Should You Reinstall Windows?

Reinstalling Windows should normally not be the first troubleshooting step.

A clean installation may not fix the problem if the actual cause is:

• Defective RAM
• Failing SSD
• Unstable CPU
• Faulty GPU
• Incorrect BIOS settings
• Defective motherboard
• Problematic driver that is installed again afterward

Analyze the crash before reinstalling Windows whenever practical.

A repair installation or clean installation becomes more reasonable after hardware tests, driver investigation, system-file repair, and dump analysis fail to identify the problem.

Recommended Troubleshooting Order

For most computers, use this sequence:

1. Record the stop code and driver filename

2. Identify what changed before the crashes started

3. Check Device Manager

4. Update or roll back suspicious drivers

5. Install appropriate chipset and GPU drivers

6. Run DISM

DISM /Online /Cleanup-Image /RestoreHealth

7. Run SFC

sfc /scannow

8. Check Event Viewer and Reliability Monitor

9. Test RAM

10. Check SSD/HDD health

11. Return overclock/XMP/EXPO settings to defaults for testing

12. Perform a clean boot

13. Analyze minidump files

14. Use Driver Verifier only when advanced driver diagnosis is necessary

15. Consider System Restore, repair installation, or Windows reinstallation if appropriate

This approach is generally safer and more efficient than randomly reinstalling drivers or immediately reinstalling Windows.

How to Prevent SYSTEM_SERVICE_EXCEPTION Errors

While no procedure can prevent every BSOD, several practices reduce the likelihood of system-service crashes.

Keep Windows and important drivers reasonably current.

Use drivers designed for your exact hardware.

Avoid downloading drivers from unknown third-party driver-download websites.

Maintain sufficient free storage space.

Keep BIOS and firmware current when updates address stability or compatibility problems.

Avoid unstable overclocking or undervolting.

Monitor SSD health.

Test RAM when unexplained BSODs begin occurring.

Avoid running multiple third-party antivirus or endpoint-security products simultaneously unless the products are explicitly designed to coexist.

Create restore points or system backups before major driver, firmware, or system changes.

Frequently Asked Questions (FAQ)

1. What is SYSTEM_SERVICE_EXCEPTION?

SYSTEM_SERVICE_EXCEPTION is a Windows Blue Screen of Death error indicating that an exception occurred while Windows was executing privileged system code.

Its bug check code is:

0x0000003B

2. Is SYSTEM_SERVICE_EXCEPTION a hardware or software problem?

It can be either.

Common software causes include faulty drivers, security software, damaged system files, and driver incompatibility.

Hardware causes may include unstable or defective RAM, storage problems, GPU instability, or other hardware faults.

3. Can RAM cause SYSTEM_SERVICE_EXCEPTION?

Yes.

Defective or unstable RAM can corrupt memory used by Windows or device drivers, resulting in SYSTEM_SERVICE_EXCEPTION and many other BSOD codes.

However, this stop code alone does not prove the RAM is defective.

4. Can a graphics driver cause SYSTEM_SERVICE_EXCEPTION?

Yes.

Graphics drivers operate with significant kernel interaction. Faulty, incompatible, or unstable graphics drivers can contribute to SYSTEM_SERVICE_EXCEPTION.

If the issue started after a graphics-driver update, consider rolling back or cleanly reinstalling the driver.

5. What is SYSTEM_SERVICE_EXCEPTION 0x0000003B?

0x0000003B is the official bug-check value associated with SYSTEM_SERVICE_EXCEPTION.

It indicates that an exception occurred during execution of a system-service routine.

6. What does 0xC0000005 mean with SYSTEM_SERVICE_EXCEPTION?

0xC0000005 means:

STATUS_ACCESS_VIOLATION

It indicates that code attempted an invalid memory access.

This can be caused by a defective driver, memory corruption, corrupted data structures, or hardware instability.

7. Does ntoskrnl.exe mean Windows is corrupted?

Not necessarily.

ntoskrnl.exe is the Windows kernel. It is frequently present in crash stacks because the crash ultimately occurs in kernel mode.

The underlying problem may actually be another driver or unstable hardware.

8. Should I run SFC for SYSTEM_SERVICE_EXCEPTION?

Yes. It is a reasonable troubleshooting step.

Run:

DISM /Online /Cleanup-Image /RestoreHealth

followed by:

sfc /scannow

9. Where are Windows BSOD dump files stored?

Small dump files are commonly stored in:

C:\Windows\Minidump

A larger system dump may be stored as:

C:\Windows\MEMORY.DMP

10. Can antivirus software cause SYSTEM_SERVICE_EXCEPTION?

Potentially, yes.

Third-party security software may install kernel-level file-system or network-filter drivers. A defective or incompatible driver can contribute to BSODs.

11. Can Windows Update cause SYSTEM_SERVICE_EXCEPTION?

The error may begin after an update if the update introduces or exposes an incompatibility with a driver, firmware component, or third-party application.

The timing alone does not prove that the Windows update itself is defective.

12. Can an SSD cause SYSTEM_SERVICE_EXCEPTION?

Storage problems can contribute to Windows crashes.

Check the SSD's health, firmware, storage-controller driver, Event Viewer errors, and file-system integrity if storage problems are suspected.

13. Can overheating cause SYSTEM_SERVICE_EXCEPTION?

Severe CPU, GPU, memory, or motherboard instability caused by heat can result in system crashes.

If BSODs occur primarily during gaming or heavy workloads, check temperatures and cooling.

14. Should I update the BIOS?

A BIOS update can sometimes resolve hardware compatibility and stability problems, but it should not be performed blindly.

Check the computer or motherboard manufacturer's release notes and follow its exact update procedure.

15. Is Driver Verifier safe?

Driver Verifier is a legitimate Windows diagnostic tool, but it intentionally stresses drivers and can trigger BSODs.

It should be used cautiously, preferably by experienced users or technicians.

16. How do I disable Driver Verifier?

Open an elevated Command Prompt and run:

verifier /reset

Restart the computer.

If Windows cannot boot normally, use Safe Mode or Windows Recovery Environment to perform recovery.

17. Will reinstalling Windows fix SYSTEM_SERVICE_EXCEPTION?

It may fix crashes caused by severe Windows or software corruption, but it will not reliably solve defective hardware, unstable RAM, faulty firmware, or a problematic driver that gets installed again.

Diagnose the cause before reinstalling Windows whenever possible.

18. Why does SYSTEM_SERVICE_EXCEPTION happen while gaming?

Gaming increases CPU, GPU, RAM, storage, and driver activity.

Crashes during gaming can therefore expose:

• Graphics-driver problems
• GPU instability
• RAM instability
• Overheating
• Overclock instability
• Power-related hardware problems

Check the crash dump rather than assuming the game itself is responsible.

19. Why does SYSTEM_SERVICE_EXCEPTION keep coming back?

Recurring crashes usually mean that the underlying cause has not been removed.

Analyze multiple crash dumps and look for recurring drivers, modules, exception codes, or patterns.

20. What should an IT technician collect before troubleshooting?

For recurring SYSTEM_SERVICE_EXCEPTION cases, collect:

• Exact stop code
• Screenshot/photo of BSOD
• .sys filename if displayed
• Minidump files
• System Event Log
• Reliability Monitor history
• Hardware configuration
• Driver versions
• Windows version/build
• Recent update history
• Recent hardware/software changes

These details make root-cause analysis substantially more effective.

Conclusion

SYSTEM_SERVICE_EXCEPTION (0x0000003B) is a serious Windows stop error, but it does not automatically mean Windows must be reinstalled.

The most important task is identifying what caused privileged system code to fail.

In many cases, the investigation leads to a faulty or incompatible device driver. Other possibilities include corrupted Windows files, RAM instability, storage problems, graphics-driver issues, security software, firmware incompatibility, or unstable hardware settings.

Start by identifying recent changes and checking drivers. Repair Windows with DISM and SFC, examine Event Viewer and Reliability Monitor, test RAM and storage, and analyze Windows crash dumps when the error continues.

For recurring BSODs, minidump analysis is one of the most valuable diagnostic steps because it can turn a generic SYSTEM_SERVICE_EXCEPTION message into a much more specific driver or subsystem investigation.

Technical note: Microsoft identifies SYSTEM_SERVICE_EXCEPTION as bug check 0x0000003B and documents driver investigation, System event-log review, recently added hardware/software checks, and crash-dump analysis as important troubleshooting approaches.