| Previous | Next |
| STATUS_NET_WRITE_FAULT | STATUS_NOT_SAME_DEVICE |
STATUS_PROFILING_AT_LIMIT
The active profile-object limit has been reached
The native profiling subsystem limits how many profile objects can be active at the same time. Once that limit is reached, another profile cannot be started. This is distinct from an undersized sample buffer or a single profiler consuming excessive CPU.
Inventory active profiling sessions and the components that created them. Leaked profile handles or failure to stop profiles after a diagnostic run can exhaust the limit. Because several profiling tools may coexist, correlate the failure with ETW, debugger, performance, and vendor diagnostic activity on the machine.
What to inspect
- List profilers or diagnostic agents active when the failure occurs.
- Audit native profile create/start/stop cleanup and leaked handles.
- Stop unused profiling sessions before starting another one.
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.