Hi Sonic Charge Team / Magnus,

I am experiencing an instant, fatal crash (0xc0000005 Access Violation) whenever I attempt to load **Synplant 2** or **Microtonic** onto a track in any DAW. This is a massive downer for me, as I am actively trying to purchase the full Sonic Charge bundle, but this issue is completely preventing me from doing so. The crash occurs immediately upon plugin initialization, terminating the DAW's external plugin host process (Broken pipe).

Because my laptop uses a newer **AMD Ryzen AI 9 (Zen 5)** architecture with hybrid graphics, I suspect this may be an OpenGL memory routing collision or SIMD instruction incompatibility on this chipset.

Here are my system specifications, the comprehensive troubleshooting steps I have already completed, and the Windows Event Viewer logs.

System Specifications

• **Laptop Model:** ASUS ProArt PX13
• **Processor:** AMD Ryzen AI 9 (Zen 5 architecture)
• **Graphics (Hybrid setup):** AMD Radeon 890M Integrated + NVIDIA GeForce RTX 4060 Laptop GPU
• **Operating System:** Windows 11
• **DAWs Tested:** Bitwig Studio 6.x (both AVX2 and SSE4.1 host processes) & Reason 14
• **Audio Interface:** Focusrite USB ASIO
• **Plugin Formats Tested:** VST2 (.dll) and VST3 (.vst3) — Synplant 2 (v2.0.2.309) & Microtonic (v3.3.4.1048)

Exhaustive Troubleshooting Steps Already Completed

To rule out local OS, driver, or DAW conflicts, I completed the following system diagnostics (followed by a clean OS reboot and fresh plugin reinstallation), but the crash persists identically:

1. **Audio Driver Isolation:** Removed all third-party audio wrappers (Realtek ASIO, Nahimic, Sonic Studio, A-Volute) from the Windows Driver Registry. Confirmed the DAW is locked directly to my Focusrite USB ASIO hardware driver.
2. **Graphics & Display Hook Removal:** Terminated all background display hooks and overlays (NVIDIA In-Game Overlay, ASUS On-Screen Display / OSD, ASUS OLED Shifter, RivaTuner RTSS, Discord, GameBar).
3. **Virtual Display Drivers:** Disabled headless VR monitors (Meta Virtual Monitor) in the Windows PnP Device tree to ensure OpenGL calls aren't routing to a virtual display.
4. **GPU Binding & OpenGL Fallbacks:** Tested locking the DAW sandbox explicitly to the Discrete NVIDIA RTX 4060 (GpuPreference=2), then integrated AMD Radeon 890M (GpuPreference=1). Also tested injecting software OpenGL environment overrides (LIBGL_ALWAYS_SOFTWARE=1 and QT_OPENGL=software).
5. **C++ Runtimes & Cache Purge:** Cleanly re-installed/repaired Microsoft Visual C++ 2015–2022 x64 Redistributables directly from Microsoft. Completely purged all local cache folders (AppData\Local\Sonic Charge, ProgramData, and HKCU:\Software\NuEdge Development registry keys) to force clean initialization.
6. **CPU Exploit Mitigations:** Temporarily disabled Windows 11 hardware exploit protections (Control Flow Guard / CFG, DEP, and Hardware-Enforced Shadow Stacks) for the DAW sandbox executables.
7. **AVX2 vs SSE4.1 Host Testing:** Swapped Bitwig Studio's native BitwigPluginHost-X64-AVX2.exe for the legacy BitwigPluginHost-X64-SSE41.exe to rule out AVX2 SIMD memory alignment issues on Zen 5 registers.
8. **AI Engine Isolation:** Temporarily renamed the Synplant Genopatch folder to test if the background machine learning module was triggering the crash. The core synth binary still crashed immediately upon loading.

Windows Event Viewer Crash Logs (Event ID 1000)

Both plugins consistently throw an identical 0xc0000005 Access Violation across different DAWs and host formats. Notice the identical fault offsets:

**Synplant 2 (VST3) Crash Log:**
```text
Faulting application name: BitwigPluginHost-X64-AVX2.exe, version: 6.0.11.20070
Faulting module name: Synplant.vst3, version: 2.0.2.309, time stamp: 0x66d0efd9
Exception code: 0xc0000005
Fault offset: 0x000000000002a5f5
Faulting application path: C:\Program Files\Bitwig Studio\bin\BitwigPluginHost-X64-AVX2.exe
Faulting module path: C:\Program Files\Common Files\VST3\Sonic Charge\Synplant.vst3

Microtonic VST3 crash log:
Faulting application name: BitwigPluginHost-X64-AVX2.exe, version: 6.0.11.20070
Faulting module name: Microtonic Multi.vst3, version: 3.3.4.1048, time stamp: 0x63812843
Exception code: 0xc0000005
Fault offset: 0x000000000001ad25
Faulting application path: C:\Program Files\Bitwig Studio\bin\BitwigPluginHost-X64-AVX2.exe
Faulting module path: C:\Program Files\Common Files\VST3\Sonic Charge\Microtonic Multi.vst3

Any insight into whether there is a known OpenGL or SIMD register incompatibility with AMD Zen 5 / Ryzen AI mobile chipsets would be greatly appreciated! I really love what you guys build and am ready to purchase the full bundle the second we can get these plugins running stably on this machine.

Thanks so much,

Mauricio

Bumping, any insight is highly appreciated. I feel like I'm missing out on Synplant and hoping to purchase if I can sort out the issue.

Many thanks again :)

Bumping this again, to be completely honest, I feel pretty left hanging here, which is a massive bummer because I genuinely want to purchase the full bundle the moment this is resolved.

Since this fatal 0xc0000005 crash happens consistently at the exact same offsets across both Synplant 2 and Microtonic on this Ryzen AI 9 / Zen 5 machine, I’m ready to capture and send over a full user-mode memory dump (.dmp) or stack trace to help pinpoint the instruction causing the access violation.

Is there a direct channel, email, or upload link where I can send crash dumps to Magnus or the dev team?

Would really appreciate any guidance so I can get these running and pick up the license.

Thanks! :)

Sorry for this very slow reply.

This doesn’t look like an OpenGL, AVX2, or Zen 5 problem. Both Synplant and Microtonic crash at the same instruction during startup while handling strings, and we have a known issue with file paths that contain characters outside ISO-8859-1 (Western European).

Could you please check the paths shown by %USERPROFILE%, %TEMP%, and %TMP%, and tell us whether any of them contain such characters?

(An easy way: open File Explorer, type each of these into the address bar and press Enter, then click the address bar to see the full path.)