System file and kernel errors

RESOURCE_NOT_OWNED (0x000000E3)

Stop code 0x000000E3, also written 0xE3. Here is what it means, what usually causes it, and the safest order to work through fixes on Windows 11 and Windows 10.

In short

A piece of Windows or a driver tried to release a lock it did not hold. It usually points to a driver or file-system component rather than hardware.

What RESOURCE_NOT_OWNED means

Bug check 0xE3 means a thread tried to release a resource, a kind of internal lock, that it did not own. Microsoft’s reference does not list causes, but the meaning implies a driver or component whose lock handling is wrong, such as releasing a lock twice or on the wrong thread. It is an uncommon stop code, so a recent driver, update or low-level program is the most useful place to start.

Common causes

A driver or file-system filter that handles locks incorrectly
A recently installed or updated driver, especially for storage, security or backup software
An outdated component that conflicts with the installed Windows version

How to fix RESOURCE_NOT_OWNED

Work through these in order and test after each one. Stopping as soon as the crashes stop tells you which change mattered.

Undo the most recent change. If the blue screens began after a Windows update, a new driver or new software, remove that change first. Uninstall the update from Settings, Windows Update, Update history, or roll a driver back in Device Manager (right-click the device, Properties, Driver, Roll Back Driver).
Install pending Windows updates. Open Settings, Windows Update and install anything waiting, including optional driver updates from the PC maker. A fixed component may already be available.
Note the file name on the blue screen. If the screen shows a line such as "What failed" followed by a .sys file, write it down. Searching that file name shows which driver it belongs to, which tells you what to update or remove. The named file is the code that crashed, which is not always the root cause.
Check security, backup and disk tools. Antivirus, backup, encryption and disk utilities often install file-system filter drivers. Update or temporarily uninstall the one you added most recently, and retest.
Repair Windows system files. Open Terminal (Admin) and run sfc /scannow. If it reports damage it could not repair, run DISM /Online /Cleanup-Image /RestoreHealth, restart, and run sfc /scannow once more.

Reading the crash evidence for 0xE3

Microsoft’s reference gives the first three parameters as the address of the resource, the address of the thread, and the address of the owner table, if one exists. They are mainly useful to a developer with a debugger, together with the call stack that shows which driver made the release.

For most people, the practical evidence is timing. Reliability Monitor shows when the crashes started, and a driver, update or tool installed at that time is the most likely cause.

Match what you observe to the next check
What you observe	What it may suggest	Next check
The crash began after a driver or software install	That component may mishandle locks	Remove or update it and retest
The crash happens during disk-heavy work such as backup	A file-system filter driver may be involved	Update or disable backup or security tools one at a time
The crash began after a Windows update	An older driver may conflict with the new build	Install the maker’s current drivers

Source: Microsoft Learn: Bug Check 0xE3 RESOURCE_NOT_OWNED ↗

When to stop and protect your data

If the crash repeats with the same driver or program involved, keep the minidump and report it to the maker. A debugger can show the resource and the thread that tried to release it.

Not sure this is your code?

The stop code appears as text on the blue screen. If the PC restarted before you could read it, open Event Viewer, then Windows Logs, then System, and look for a BugCheck event with ID 1001. You can also search all stop codes.

Related guides

Other system file and kernel errors

Frequently asked questions

What does RESOURCE_NOT_OWNED mean?

A piece of Windows or a driver tried to release a lock it did not hold. It usually points to a driver or file-system component rather than hardware. Bug check 0xE3 means a thread tried to release a resource, a kind of internal lock, that it did not own. Microsoft’s reference does not list causes, but the meaning implies a driver or component whose lock handling is wrong, such as releasing a lock twice or on the wrong thread. It is an uncommon stop code, so a recent driver, update or low-level program is the most useful place to start.

What usually causes RESOURCE_NOT_OWNED?

Typical causes: A driver or file-system filter that handles locks incorrectly; A recently installed or updated driver, especially for storage, security or backup software; An outdated component that conflicts with the installed Windows version.

How do I fix RESOURCE_NOT_OWNED (0x000000E3)?

A sensible order is: 1) Undo the most recent change; 2) Install pending Windows updates; 3) Note the file name on the blue screen; 4) Check security, backup and disk tools. If the crash repeats with the same driver or program involved, keep the minidump and report it to the maker. A debugger can show the resource and the thread that tried to release it.

Does RESOURCE_NOT_OWNED mean my hardware is failing?

Not usually. The code describes a lock being released by a thread that did not hold it, which is a software fault. If it appears alongside other stop codes, test memory and storage as well.

Why is so little written about this stop code?

Microsoft’s reference lists the parameters but not specific causes or fixes, so advice is based on what the code means: look at recent drivers, updates and low-level software first.

Use this guidance carefully

A stop code can have several causes, and these steps are general guidance rather than a diagnosis of your PC. If your data matters, back it up before repairs. If the problem continues, a hardware technician can test the parts.

See our testing methodology·Read our editorial policy