| Previous | Next |
| STATUS_AUDIT_FAILED | STATUS_CONNECTION_COUNT_LIMIT |
STATUS_TIMER_RESOLUTION_NOT_SET
The process has no matching timer-resolution request to release
Windows timer-resolution APIs maintain request state that must be balanced by the component that established it. This status indicates that the current process or call path attempted to undo a resolution setting that was not active in the expected scope. It is a lifecycle mismatch rather than a hardware timer failure.
Timer resolution affects power use, scheduling granularity, and system behavior, so libraries should not issue unmatched cleanup calls. Multiple components can request resolutions independently; one component must not assume that a system-wide observed value proves it owns a corresponding request.
What to inspect
- Log every begin/set and end/unset call with process, module, requested period, and return value.
- Balance requests in the same abstraction that owns initialization and teardown.
- Do not infer ownership from the current global timer resolution.
- Check duplicate shutdown, failed initialization, and DLL detach paths for unmatched release calls.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: timeBeginPeriod
- Microsoft Windows SDK metadata: ntstatus.h
- Microsoft: pooled threads and callback environments
Looking for a different code? Search another status or error code.