Bug with initialising a module [SOLVED]

Im stuck with an access violation in utility.cpp, and I have no idea how this happened.
What is the best way to find my mistake? Any ideas on what went wrong? Breakpoints on the Processor or Editor Constructor wont even get hit.
Its too big to share all the code.

Output only says:
Exception thrown at 0x0000000000D40794 in AudioPluginHost.exe: 0xC0000005: Access violation executing location 0x0000000000D40794

thats the disassembly
image

The exeption is thrown in the Message Thread

this is the method that throws the exception
extern "C" bool __cdecl __scrt_initialize_onexit_tables(__scrt_module_type const module_type)

this is a comment to this and other functions:

//-±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±+
//
// On-Exit Table
//
//-±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±+
// When a module uses the Universal CRT DLL, the behavior of _onexit(), atexit(),
// and at_quick_exit() is different depending on whether the module is an EXE or
// a DLL. If it is an EXE, then calls to these functions are passed to the
// Universal CRT DLL and the callbacks are registered with its atexit function
// tables. This way, functions registered by the EXE are called whenever one of
// the exit() functions is called.
//
// If the module is a DLL, it has its own table of registered functions. This
// table is executed when the DLL is unloaded (during DLL_PROCESS_DETACH).
//
// Here, we define the module-local function tables used by DLLs that use the
// Universal CRT DLL. If this module is an EXE or if the Universal CRT is
// statically linked into this module, then these tables will have pointers
// initialized to -1.
//
// The user-callable _onexit(), atexit(), and at_quick_exit() functions then
// either use the module-local function tables or will forward calls to the
// Universal CRT DLL, as appropriate.

Solution: for some unknown reason deleting all vst3 files in the build folder fixed the issue and there is no bug in your code incase you encounter the same issue.