Crash related to out_notsodirect appeared after motherboard upgrade

[madoin]

After MB/CPU upgrade, but still using same external audio device (not the new MB realtek one) latest Wacup started crashing with Next Track click, usually between 2 to 5 clicks it crashes. Before MB upgrade there were no crashes. Only happens with out_notsodirect output. Changed to out_notsowavey and no crashes to date.
Likely something with my system because quite forceful system upgrade without windows reinstall but still maybe good to know that this kind of crash exists.

relevant dump info:
(5274.1940): Security check failure or stack buffer overrun - code c0000409 (first/second chance not available)
Subcode: 0xa FAST_FAIL_GUARD_ICALL_CHECK_FAILURE
For analysis of this file, run !analyze -v
eax=00000000 ebx=00000000 ecx=0000000a edx=00000001 esi=00000001 edi=15e43a80
eip=77e88f30 esp=13d0eee4 ebp=13d0ef10 iopl=0         nv up ei pl zr na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000246
ntdll!RtlFailFast2:
77e88f30 cd29            int     29h

CONTEXT:  13d0f00c -- (.cxr 0x13d0f00c)
eax=00000000 ebx=00000000 ecx=00000001 edx=00df0000 esi=00000001 edi=15e43a80
eip=77e88dfb esp=13d0fabc ebp=13d0fb08 iopl=0         nv up ei pl zr ac pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010256
ntdll!LdrpValidateUserCallTargetBitMapCheck:
77e88dfb 8b1482          mov     edx,dword ptr [edx+eax*4] ds:002b:00df0000=??
Resetting default scope

EXCEPTION_RECORD:  13d0efbc -- (.exr 0x13d0efbc)
ExceptionAddress: 77e88dfb (ntdll!LdrpValidateUserCallTargetBitMapCheck)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00df0000
Attempt to read from address 00df0000

PROCESS_NAME:  wacup.exe

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE_STR:  c0000409

EXCEPTION_PARAMETER1:  0000000a

READ_ADDRESS:  00df0000

FAULTING_THREAD:  ffffffff

STACK_TEXT: 
13d0fabc 77e88dfb ntdll!LdrpValidateUserCallTargetBitMapCheck+0x0
13d0fac0 51cb4062 out_notsodirect+0x4062
13d0fb10 51cb3d86 out_notsodirect+0x3d86
13d0fb58 76f8fcc9 kernel32!BaseThreadInitThunk+0x19
13d0fb68 77e6809e ntdll!__RtlUserThreadStart+0x2f
13d0fbc4 77e6806e ntdll!_RtlUserThreadStart+0x1b

STACK_COMMAND:  .cxr 13d0f00c ; kb ; ** Pseudo Context ** Pseudo ** Value: 1b042e85a90 ** ; kb

SYMBOL_NAME:  out_notsodirect+4062

MODULE_NAME: out_notsodirect

IMAGE_NAME:  out_notsodirect.dll

FAILURE_BUCKET_ID:  INVALID_POINTER_READ_FAIL_FAST_GUARD_ICALL_CHECK_FAILURE_c0000409_out_notsodirect.dll!Unknown

OS_VERSION:  10.0.19041.1

[dro]

Did WACUP's crash reporter get triggered? If it didn't then you'd need to try using the procdump mode (preferences -> advanced -> error reporting -> follow the instructions on that preference page) to try to collect something that is more likely to assist me. As what you've posted doesn't give me anything tangible to work with & from the auto-submitted crash reports since 20202 went up, there seems to have been a spike in notsodirect failures which seem to possibly be triggered by in_mp3 misbehaving but I've so far not managed to replicate it myself.

-dro

[madoin]

Report zip did not appear but also unfortunately error went away when did change in settings: Plug-ins -> Output -> DirectSound -> Output Device -> Primary Sound Driver to Steinberg UR22mkII and back to Primary sound driver. Also then using again out_notsodirect. Bit weird as the Primary and Steinberg device definitely had to be same as only that device has vol > 0 in analog side of cables.
Just in case tried in clean Win VM (so would have no privacy concerns sending full crash dumps) with the same USB sound device redirected there but also no success to get that error again.