| Previous | Next |
| MANUALLY_INITIATED_CRASH | WORKER_INVALID |
RESOURCE_NOT_OWNED
The RESOURCE_NOT_OWNED bug check has a value of 0x000000E3. This indicates that a thread tried to release a resource it did not own.
Important
This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
RESOURCE_NOT_OWNED Parameters
| Parameter | Description |
|---|---|
1 |
Address of resource |
2 |
Address of thread |
3 |
Address of owner table (if it exists) |
4 |
Reserved |
Dump evidence for RESOURCE_NOT_OWNED
For RESOURCE_NOT_OWNED, preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “RESOURCE_NOT_OWNED”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order for RESOURCE_NOT_OWNED
- Run WinDbg
!analyze -v, then inspect the documented meaning of each RESOURCE_NOT_OWNED parameter instead of relying only on the probably-caused-by line. - Find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with resource / owned.
- For RESOURCE_NOT_OWNED, keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.
Do not repeatedly reboot a machine affected by RESOURCE_NOT_OWNED before collecting the dump and event logs. For RESOURCE_NOT_OWNED, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Looking for a different code? Search another status or error code.