"Hardware Exception has occured" stopping my DAW setup

[Armonius]

Hello people of WINE! After doing some lurking for a while, I ran into an issue where it made sense to post it on here to see what people think.
I'm trying to setup Reason 12 using bottles as well as configuring my VST plugins and WINEASIO + Cadence for recording purposes. After a week of struggling, I managed to get Reason 12 mostly functional with just one menu screen of text not showing up. WINEASIO gave me a hard time when compiling for a bunch of reasons but i needed to pay more attention to which wine binary it was compiling for as well as where i ran regsvr32.
The issue that is really bothering me now is that my projects from my windows laptop isnt opening up on my linux distro.
A message box stating "A hardware exception has occurred. Reason can still work, but it is recommended you save and close the program" opens and the project just doesn't open up..
I thought it was some memory issue, but after trying to isolate the issue, I realize that the plugin specifically that is causing this is SoundToys Echoboy.. Echoboy works okay when I launch Reason through the terminal, but when i save it in any project, it results in the same hardware exception error with the project and then i cant open it up again. When launched with bottles, it doesn't display the text for the presets at all. I think a font is missing in bottles, but it still stops my projects from opening.
I'm a noob but not a total noob.
I was forced to only use WINEDEBUG channels because wine-dbg wouldn't attach to Reason.exe (Kept saying Cant attach, error 87) so I couldn't really trace anything back.
There's 2 exceptions that i see when using +seh
0024:trace:seh:dispatch_exception code=e06d7363 (EXCEPTION_WINE_CXX_EXCEPTION) flags=1 addr=00006FFFFF463E87
0024:trace:seh:dispatch_exception info[0]=0000000019930520
0024:trace:seh:dispatch_exception info[1]=00000000003E9330
0024:trace:seh:dispatch_exception info[2]=00000001426D14D0
0024:trace:seh:dispatch_exception info[3]=0000000140000000
0024:trace:seh:dispatch_exception rip=00006fffff463e87 rsp=00000000003e91c0 rbp=00000000003e9359 eflags=00000206
0024:trace:seh:dispatch_exception rax=00000000003e9218 rbx=00000001426d14d0 rcx=00000000003e91e0 rdx=0000000000000000
0024:trace:seh:dispatch_exception rsi=00000000003e9330 rdi=0000000019930520 r8=0000000140000000 r9=00000000003e92d0
0024:trace:seh:dispatch_exception r10=0000000140000000 r11=0000000141d18063 r12=00000000003ec740 r13=2aaaaaaaaaaaaaab
0024:trace:seh:dispatch_exception r14=0000000022b1b830 r15=0000000022b06330 mxcsr=00001fa1
0024:trace:seh:call_vectored_handlers calling handler at 0000000140F37800 code=e06d7363 flags=1
0024:trace:seh:call_vectored_handlers handler at 0000000140F37800 returned 0
0024:trace:seh:call_vectored_handlers calling handler at 00000001405F69C0 code=e06d7363 flags=1
0024:trace:seh:call_vectored_handlers handler at 00000001405F69C0 returned 0
0024:trace:seh:call_seh_handlers calling handler 0000000141D19408 (rec=00000000003E91E0, frame=3e94e0 context=00000000003E8CE0, dispatch=00000000003E85C0)
0024:trace:seh:RtlUnwindEx code=80000029 flags=3 end_frame=00000000003E94E0 target_ip=000000014100AE05
and
0024:trace:seh:dispatch_exception code=c0000005 (EXCEPTION_ACCESS_VIOLATION) flags=0 addr=0000000000000000
0024:trace:seh:dispatch_exception info[0]=0000000000000008
0024:trace:seh:dispatch_exception info[1]=0000000000000000
0024:trace:seh:dispatch_exception rip=0000000000000000 rsp=00000000003f8418 rbp=00000000003f8560 eflags=00010202
0024:trace:seh:dispatch_exception rax=00000000003f8628 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000000
0024:trace:seh:dispatch_exception rsi=0000000000000000 rdi=0000000047a54c90 r8=0000000140e4e650 r9=0000000047a54c90
0024:trace:seh:dispatch_exception r10=0000000000000004 r11=00000000409b9180 r12=0000000047a56090 r13=0000000000000013
0024:trace:seh:dispatch_exception r14=0000000000000000 r15=0000000000000000 mxcsr=00001fb7
0024:trace:seh:call_vectored_handlers calling handler at 0000000140F37800 code=c0000005 flags=0
0024:trace:seh:call_vectored_handlers handler at 0000000140F37800 returned 0
0024:trace:seh:call_vectored_handlers calling handler at 00000001405F69C0 code=c0000005 flags=0

I have tried installing many dependencies, dxd_43, dxd9_43, dxd_47, I have tried running it into a virtual desktop, I have tried many different runners and still experience an issue of the sort with this. I even dealt with the headache of getting dotnet40 and dotnet48 installed on my cafe-9.2 and on other wine runners just to see if it would change the outcome and it didnt.
I use soundtoys a lot. Echoboy has a host of different delay styles that I learned creative mixing on. I'm sorta willing to work without it, but i really would like to get to the bottom of why this wont work. I'd really appreciate anyone who has dealt with any problem similar to these so i can get a fresh perspective on how to approach this. I have tried tracking memory addresses to what dll file is causing the issue and the memory range fell within kernelbase for the WINE_CXX_EXCEPTiON

For some context. Im running cachyOS with KDE, as well as using bottles with mfc42, dxvk and vc2015

[Armonius]

Well for whoever may see this dealing with these types of issues, I had to go inside the makefile and change the Prefix variable so that wineasio compiles wineasio.dll specifically for my wine binary. Now, I isolated the issue on what is causing the hardware exception to the soundtoys VSTs. And the dll file specifically that is causing the issue is windowscodecs. I have installed it using wine tricks but it still doesn't pick it up. I will troubleshoot if that is because it's dealing with a 64bit prefix but that is unlikely. I would really like to talk to someone ho knows more about checking dll files through the registry