| Previous | Next |
| KMODE_EXCEPTION_NOT_HANDLED | KERNEL_APC_PENDING_DURING_EXIT |
SHARED_RESOURCE_CONV_ERROR
Executive resource conversion failure for SHARED_RESOURCE_CONV_ERROR
SHARED_RESOURCE_CONV_ERROR is bug check code 0x0000001F. Executive resources are reader/writer-style synchronization objects used by file systems and other kernel components. This code points at a failure while converting or managing shared/exclusive ownership.
How to read it in a dump
- The stack should show whether a file system, file-system filter, cache manager, or memory manager path owns the resource.
- Look for conversion between shared and exclusive acquisition, recursive acquisition, or release on the wrong path.
- This is a synchronization contract failure, not simply a busy file.
What to check
- Enable verifier deadlock checks for filters and storage/file-system drivers.
- Review paths that upgrade or downgrade resource ownership.
- Check for memory corruption of ERESOURCE or adjacent pool allocations.
References
Dump evidence
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 “this result”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order
- Run WinDbg
!analyze -v, then inspect the documented meaning of each 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 shared / resource / conv.
- 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 this result before collecting the dump and event logs. 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.