| Previous | Next |
| STATUS_OBJECT_NAME_EXISTS | STATUS_WORKING_SET_LIMIT_RANGE |
STATUS_THREAD_WAS_SUSPENDED
A suspended thread had to be resumed for termination
A suspended thread is not scheduled while its suspend count remains nonzero. This informational status says thread termination collided with that suspended state; Windows resumed the thread as part of allowing termination to proceed. It is therefore evidence about lifecycle ordering, not a request for the caller to resume the thread again.
Record who suspended the thread and who initiated termination. Microsoft documents SuspendThread primarily as a debugger-oriented mechanism and warns that arbitrary suspension can leave synchronization objects held. If termination regularly finds suspended workers, inspect shutdown sequencing and debugger or watchdog logic.
What to inspect
- Trace suspend/resume calls and the thread suspend count.
- Correlate the termination request with debugger, watchdog, or process-shutdown activity.
- Do not issue an extra ResumeThread solely because this informational status was observed.
References
- Microsoft: Suspending thread execution
- Microsoft: SuspendThread
- Microsoft: ResumeThread
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.