I just wanted to post this in case anyone else runs into an issue with any plugins crashing or stand alone versions not opening. I had a hard time finding a solution, so hopefully this helps someone in the future.
I built a new high-end PC last week and was excited to see how well Reaper ran with my existing projects using Gojira X and Parallax X, which ran fine on Windows 10 on an older Intel I7 CPU. On a fresh install of Windows 11 on the new PC, Gojira X stand alone would launch, but Parallax X just spun the cursor for a second, then nothing happened. I’m an IT guy and dug deep for a few days. The tl;dr version is I’m running an AMD Zen 5 architecture CPU (Ryzen 9800x3d) and there is a known bug with that CPU architecture and iLok. To resolve the issue, I had to upgrade the BIOS on my motherboard and now everything works perfectly. Just to throw this in in case someone searches for the codes in the future like I did, I was seeing a couple of errors depending on things I tried to fix in software in the Windows event viewer:
Faulting application name: Parallax X.exe, version: 1.0.0.0, time stamp: 0x667d5c6c
Faulting module name: ntdll.dll, version: 10.0.26100.5074, time stamp: 0x0e967e89
Exception code: 0xc0000005
I was also getting a reference to BEX64 errors if I disabled DEP in Windows while troubleshooting. I have 64GB of RAM as 2 32GB sticks of DDR5 6000 and was worried the plugins were having an issue, but that wasn’t it.
This was all with a fresh install of Windows 11. To determine if it was a Windows issue, I disconnected from the internet, installed Windows 11 and only Parallax X, which crashed. I then ran all updates, all drivers, all Visual Studio runtimes, and verified all products were activated in iLok. I verified it wasn’t iLok directly by disabling the license, running Parallax X stand alone, which prompted me to license it, which I did again, then it would just resume crashing which confirmed it wasn’t a licensing issue. An additional note, I saw the same behavior with GetGoodDrums Smash and Grab, and a few other plugins. They appeared in Reaper under the plugins that failed to scan list where the scan VST button is. I also verified the same happened using only the VST2 or VST3 version. Hopefully this saves someone some frustration.
This is iLok’s statement on the issue. I ended up having one of the motherboards listed as having a fix: