If you want to do system wide profiling, please don't doit under user-mode sampling data collection (Hotspots, Concurrency, LocksAndWaits analysis), please do it under HW event-based sampling collection - like as lightweight-hotspots, and other predefined analysis types for your running processor.
This is what 'ntstatus.h' Win32 API header file "says" about thecode 4000001f:
// MessageId: STATUS_WX86_BREAKPOINT
// Exception status code used by Win32 x86 emulation subsystem.
#define STATUS_WX86_BREAKPOINT ((NTSTATUS)0x4000001FL)
Sorry, but it isunclear why the exceptionhappened...
Your code is executing 0xcc instruction thus trigerring debugger breakpoint exception.Please post the full call stack.It is unknown why code path is executing int3 instruction.Sometime 0xcc is used as a padding for hot patching at runtime.