Skip to content
PCDecoder
0x0000003BSYSTEM_SERVICE_EXCEPTIONStop codeWidely reported

SYSTEM_SERVICE_EXCEPTION (0x3B): what it means and how to fix it

Updated Oct 2, 2026 · Checked against Microsoft documentation · How this page is made

Quick answer

This error occurs when a system process encounters a critical exception while transitioning between user and system tasks. It is most commonly caused by faulty drivers or corrupted memory. Start by checking for recent driver updates or hardware changes.

What it means

What Windows is telling you

The SYSTEM_SERVICE_EXCEPTION (0x3B) error is a signal that a piece of code running on your computer tried to perform an operation it was not allowed to do. Specifically, it happens when the computer is switching from a standard user task to a privileged system task. During this transition, the system encountered an error it could not recover from, forcing it to stop to prevent further damage to your data.

Why this happens

At a technical level, this error usually stems from a memory access violation. This means a program or driver tried to read or write to a part of the computer's memory that it does not have permission to access, or it tried to access a memory address that does not exist. This is often caused by a "NULL pointer," where the system is told to look for data at an empty or invalid location.

This behavior is frequently triggered by a driver that has become corrupted or is incompatible with your current version of Windows. When a driver passes bad data to the core system, the system crashes to protect itself. While it can be frustrating, the error code is a safety mechanism designed to stop your PC from running with corrupted instructions.

Common causes

  • A faulty or outdated device driver is interacting incorrectly with the system.
  • System memory is corrupted or experiencing hardware failure.
  • A recent change in hardware or software has introduced an incompatibility.
  • Data structures within the system have become corrupted.

How to fix it

Safest and most likely fixes first. Readers' answers to "Did this fix it?" reorder this list over time.

  1. Update your device drivers

    Use this if the error started after installing new hardware or if you suspect a driver is outdated.

    1. Right-click the Start button and select Device Manager.
    2. Look for any devices with a yellow exclamation mark icon.
    3. Right-click the device and select Update driver.
    4. Choose Search automatically for drivers.
    Did this fix it?

  2. Check for recent system changes

    Use this if the error began immediately after you installed a new program or connected a new device.

    1. Disconnect any recently added hardware such as printers, webcams, or USB drives.
    2. Uninstall any software that was installed just before the crashes began via Settings, Apps, Installed apps.
    3. Restart your computer to see if the error persists.
    Did this fix it?

  3. Review the System Event Log

    Use this to identify which specific driver or service is failing.

    1. Type Event Viewer in the search bar and press Enter.
    2. Expand Windows Logs in the left sidebar and select System.
    3. Look for Critical or Error entries that align with the time your computer crashed.
    4. Check the details of these entries for mentions of specific files or drivers.
    Did this fix it?

Is it just you?

25+ Microsoft Q&A threads discuss this, 1 active in the last 30 days. Most recent activity:

Checked Oct 2, 2026. Refreshed automatically every few days.

Sources

Frequently asked questions

Is my computer permanently broken when I see this error?

No, this is a software-level protection mechanism. It usually indicates a driver or memory issue that can be resolved without replacing hardware.

Can I fix this by reinstalling Windows?

You can, but it is rarely necessary. Most instances of this error are caused by a single problematic driver that can be updated or removed.

What does the 0x3B code mean?

It is the internal identifier Windows uses to report that an exception occurred during a system service routine.

More stop codes decoded