| Previous | Next |
| STATUS_PROFILING_NOT_STARTED | STATUS_COULD_NOT_INTERPRET |
STATUS_PROFILING_NOT_STOPPED
The profile object is still running
This status is the opposite lifecycle mismatch from STATUS_PROFILING_NOT_STARTED. The current profile remains active while the requested operation requires it to be stopped. Native profile objects collect samples into configured buffers and have an explicit start/stop state.
Identify which thread or subsystem owns the active profile and whether a previous stop request failed. Do not close over the state transition in diagnostics: capture the handle and call sequence because two components independently managing one profile can produce intermittent start/stop races.
What to inspect
- Record the complete create/start/stop sequence for the profile handle.
- Check whether another component still owns or expects the active profile.
- Stop the profile through its owning path before performing the incompatible operation.
References
- ReactOS: kernel profile object implementation
- System Informer PHNT: native executive APIs
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.