Crash when trying to debug application from Visual Studio 19

[elseifthen]

I tried to run Dr. Memory, 64-bit exe, on my application from within Visual Studio 2019 when I got that Dr. Memory internal crash. The thing is: I'm getting very strange crashes in the application I want to debug, in the context of freeing memory/unloading dlls, so I thought maybe there's some mem corruption I can analyze with Dr. Memory. But the strange thing is that this only happens in my Virtual Windows 10 (10.0.19044 Build 19044) machine, not in the virtual machine of a colleague, not on the native Windows installation of another colleague. And now Dr. Memory crashes with some strange output:

 Dr. Memory version 2.5.0
         Running "D:\eclipseWS\something\something_head_exe\exe\Debug\something.exe x/input.inp"
         Using system call file D:\programme\DrMemory\drmemory\logs\symcache\syscalls_x64.txt
<Application D:\eclipseWS\something\something_head_exe\exe\Debug\something.exe (9272).  Dr. Memory internal crash at PC 0x000000007107cf00.  Please report this at http://drmemory.org/issues along with the results of running '-debug -dr_debug'.  Program aborted.
0xc0000005 0x00000000 0x000000007107cf00 0x000000007107cf00 0x0000000000000000 0x0000000000000000
Base: 0x0000000071000000
Registers: eax=0x0000000000000001 ebx=0x0000000000000000 ecx=0x0000000000000000 edx=0x0000000000000000
        esi=0x0000000000000000 edi=0x00000220c2b152b0 esp=0x00000220c2b151f0 ebp=0x00000220c2b15360
        r8 =0x00000220c2b15310 r9 =0x00000000710f4040 r10=0x00000220c2b15312 r11=0x000000007111b2e0
        r12=0x0000000000000000 r13=0x0000000000000000 r14=0x0000000000000000 r15=0x0000000000000000
        eflags=0x0000000000010246
2.5.0-0-(Oct 18 2021 03:01:22) WinVer=105;Rel=2009;Build=19044;Edition=Enterprise
-no_dynamic_options -disasm_mask 8 -logdir 'D:\programme\DrMemory\drmemory\logs\dynamorio' -client_lib 'D:\programme\DrMemory\bin64\release\drmemorylib.dll;0;-visual_studio -logdir `D:\programme\DrMemory\drmemory\logs` -symcache_dir `D:\programme\DrMemory\drmemory\logs\symcache` -lib_blocklist_default `C:\WINDOWS*.d??,C:
0x00000220c2b15360 0x00007ff73b60c308
0x00007ff73b60c313 0x000a0d0079726f6d>


<Starting application D:\eclipseWS\something\something_head_exe\exe\Debug\something.exe (7292)>
<Running on newer-than-this-build "Microsoft Windows 10-2009 x64">
<Initial options = -no_dynamic_options -logdir 'D:\programme\DrMemory\drmemory\logs\dynamorio' -client_lib 'D:\programme\DrMemory\bin64\debug\drmemorylib.dll;0;-visual_studio -logdir `D:\programme\DrMemory\drmemory\logs` -symcache_dir `D:\programme\DrMemory\drmemory\logs\symcache` -lib_blocklist_default `C:\WINDOWS*.d??,C:\Program Files\Common Files\Microsoft Shared*.d??,C:\Program Files (x86)\Common Files\Microsoft Shared*.d??` -resfile 7292 ' -client_lib64 'D:\programme\DrMemory\bin64\debug\drmemorylib.dll;0;-visual_studio -logdir `D:\programme\DrMemory\drmemory\logs` -symcache_dir `D:\programme\DrMemory\drmemory\logs\symcache` -lib_blocklist_default `C:\WINDOWS*.d??,C:\Program Files\Common Files\Microsoft Shared*.d??,C:\Program Files (x86)\Common Files\Microsoft Shared*.d??` -resfile 7292 ' -code_api -probe_api -stack_size 56K -disable_traces -no_enable_traces -max_elide_jmp 0 -max_elide_call 0 -no_shared_traces -bb_ibl_targets -bb_single_restore_prefix -no_shared_trace_ibl_routine -no_enable_reset -no_reset_at_switch_to_os_at_vmm_limit -reset_at_vmm_percent_free_limit 0 -no_reset_at_vmm_full -reset_at_commit_free_limit 0B -reset_every_nth_pending 0 -vm_size 256M -no_early_inject -no_inline_ignored_syscalls -native_exec_default_list '' -no_native_exec_managed_code -no_indcall2direct >
         Dr. Memory version 2.5.0
         Running "D:\eclipseWS\something\something_head_exe\exe\Debug\something.exe x/input.inp"
         Using system call file D:\programme\DrMemory\drmemory\logs\symcache\syscalls_x64.txt
<Invalid opcode encountered>
<intercept_syscall_wrapper: not hooking NtSetContextThread due to conflict @0x00007ffc61d70205>
<intercept_syscall_wrapper: not hooking NtCreateThread due to conflict @0x00007ffc61d6da75>
<intercept_syscall_wrapper: not hooking NtCreateThreadEx due to conflict @0x00007ffc61d6e8c5>
<intercept_syscall_wrapper: not hooking NtTerminateThread due to conflict @0x00007ffc61d6db15>
<intercept_syscall_wrapper: not hooking NtSuspendThread due to conflict @0x00007ffc61d70825>
<intercept_syscall_wrapper: not hooking NtAllocateVirtualMemory due to conflict @0x00007ffc61d6d3b5>
<intercept_syscall_wrapper: not hooking NtAllocateVirtualMemoryEx due to conflict @0x00007ffc61d6df65>
<intercept_syscall_wrapper: not hooking NtProtectVirtualMemory due to conflict @0x00007ffc61d6dab5>
<intercept_syscall_wrapper: not hooking NtMapViewOfSection due to conflict @0x00007ffc61d6d5b5>
<intercept_syscall_wrapper: not hooking NtMapViewOfSectionEx due to conflict @0x00007ffc61d6f325>
<intercept_syscall_wrapper: not hooking NtUnmapViewOfSection due to conflict @0x00007ffc61d6d5f5>
<dr_fragment_app_pc is a DR/client pc>
         ASSERT FAILURE (thread 15512): D:\a\drmemory\drmemory\drmemory\syscall_windows.c:151: opc_is_in_syscall_wrapper(opc) (unknown system call sequence)

Can you make sense of these messages? Is there something wrong with my system?