Skip to content
PCDecoder
0x000000E3RESOURCE_NOT_OWNEDStop codeWidely reported

RESOURCE_NOT_OWNED (0xE3): what it means and how to fix it

Updated Nov 7, 2026 · Checked against Microsoft documentation · How this page is made

Quick answer

The RESOURCE_NOT_OWNED stop code indicates that an active thread attempted to release a system resource that it did not actually own. This is almost always caused by a software defect in a third-party kernel driver or recently installed service. Updating faulty drivers or rolling back recent software changes is the best initial step.

What it means

Windows manages access to shared memory and internal components through resources. When multiple programs, background tasks, or device drivers operate simultaneously, the operating system requires threads to request and acquire ownership of a shared resource before using it. Once the thread finishes its task, it must release that ownership so other components can access the resource.

The RESOURCE_NOT_OWNED bug check occurs when a thread instructs the operating system to release a resource, but Windows verifies its internal records and discovers the requesting thread never owned it in the first place. Releasing an unowned resource risks corrupting data structures, breaking synchronization between tasks, or granting invalid access to hardware.

To prevent silent corruption of memory and unstable system states, Windows halts immediately with this blue screen error. Under the hood, the crash reports four parameters: Parameter 1 provides the memory address of the resource, Parameter 2 identifies the thread that triggered the invalid release, Parameter 3 references the owner table if one exists, and Parameter 4 is reserved.

For standard users, this behavior usually points to driver programming mistakes. A newly installed device driver, peripheral driver, or low-level background service attempted to clear an internal lock improperly, triggering an immediate shutdown.

Common causes

  • A device driver attempted to release a kernel synchronization resource without owning it.
  • A recently installed driver or system service contains a software defect.
  • Newly added peripheral hardware introduced conflicting or outdated drivers.
  • Corrupted system files or driver files causing improper function execution.

How to fix it

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

  1. Check Device Manager for driver errors

    Use this as a first step to see if Windows has flagged any malfunctioning hardware or corrupt drivers.

    1. Right-click the Start button and select Device Manager.
    2. Expand each category and look for any device marked with a yellow exclamation point (!).
    3. Right-click any flagged device and select Properties.
    4. Check the Events tab to review recent driver errors.
    5. Select the Driver tab and choose Update driver to install the latest version from Windows Update or the device manufacturer.
    Did this fix it?

  2. Review the System log in Event Viewer

    Use this to identify which specific driver or service triggered an error right before the crash.

    1. Right-click the Start button and select Event Viewer.
    2. Expand Windows Logs on the left and select System.
    3. Filter or scroll through the log to locate Critical or Error entries timestamped right when the blue screen occurred.
    4. Select the error entry and read the General tab to identify any named driver files (.sys) or services involved.
    5. Update or uninstall the application or driver associated with the identified file.
    Did this fix it?

  3. Remove recently installed drivers, services, or hardware

    Use this if the error started appearing after plugging in a new device or installing new software.

    1. Disconnect any recently attached peripheral hardware such as drawing tablets, external drives, or adapters.
    2. Open Settings and navigate to Apps, then Installed apps.
    3. Sort the list by Date installed to identify recently installed programs or driver utilities.
    4. Select the three dots next to the recent software and choose Uninstall.
    5. Restart the PC and monitor for further stability issues.
    Did this fix it?

  4. Scan for malware and boot-sector infections

    Use this if the crash happens intermittently and driver checks do not reveal an obvious culprit.

    1. Open Windows Security from the system tray or Start menu.
    2. Select Virus & threat protection.
    3. Click on Scan options.
    4. Select Full scan or Microsoft Defender Antivirus (offline scan) to ensure boot records are inspected.
    5. Click Scan now and allow the utility to clean any detected threats.
    Did this fix it?

Is it just you?

25+ Microsoft Q&A threads discuss this. Most recent activity:

Checked Nov 7, 2026. Refreshed automatically every few days.

Sources

Frequently asked questions

What does bug check 0x000000E3 mean?

It means a system thread instructed Windows to release a shared resource, but the operating system detected that the thread did not hold ownership of it.

Can bad hardware cause RESOURCE_NOT_OWNED?

While physical hardware defects are rare causes of this specific bug check, newly connected external devices with buggy driver software frequently cause it.

How do I find the driver causing RESOURCE_NOT_OWNED?

Open Event Viewer and check the System log for errors timestamped at the time of the crash, or inspect crash dump files with a debugging tool to read the faulting thread and driver.

More stop codes decoded