Thanks for all the information everyone, I built a 14900k system whilst I dealt with the 13900ks. 14900k has proved to be stable. I had one instance of the problem along with a few crashes after enabling xmp. To avoid the crashes I reduced the ram speed and have had no further issues. So now it’s time to test out the 13900 with adjusted setting. I did all the intel CPU tests and both processors passed so keen to see if the ram speed makes a big impact. Will post back after I get some time free to test it. Cheers.
1 Like
For me, looks like it was solved by updating the new Asus bios, addressing the problem with 13-14000 series cpu. Not a single crash after the bios update! Im glad you figured it out too. Looks like my ram stuff is working as it should. Thanks for the feedback though, really appreciate it!!
Jorgen
lør. 19. okt. 2024 kl. 14:42 skrev fullfacile via Steinberg Forums <notifications@steinberg.discoursemail.com>:
1 Like
Nice! Yeah same here, the CPU and RAM tests were showing ok, but I had to disable XMP and adjust the speeds. Of course, updating the bios helped too. In the end, when ram skips a beat at high load (loooots of tracks and plugins), it’s unforgiving. Glad it worked!!
For sure, the new bios helps with stability, especially at high loads with big projects. The latest latest one helped me for sure. So yeah everyone who sees this in the future:
- Update bios
- Use the intel profile for the power consumption
- Try not to overclock ram and try without XMP
- Ideally, don’t get your CPU usage, RAM and ASIO above 75% for more stability.
Cheers!
Looks like we did figure it out.
Hey all,
I just wanted to update this thread with my latest status on this issue. After updating my motherboard (ASRock Z790 Pro Wifi) BIOS to version 13.01, which includes the 0x12B microcode update from Intel, I didn’t get any more authorization errors nor unexplained crashes in Cubase/Pro Tools, BUT the NVIDIA GeForce graphics driver installer continued to fail (which was apparently a telltale sign that the processor was damaged as a result of the root problem). After going back & forth with Intel customer support for a bit, they sent me a replacement processor (Core i9-13900KS in my case). I just installed it this morning, and now the NVIDIA GeForce driver installer completes and all the errors are still gone. PHEW! Saga complete. 
Thanks again to @daveotero and others for sharing their experience on this issue. Since I’m not a gamer I probably wouldn’t have discovered it otherwise!
Cheers all,
Brian
Nope still crashing here… it disappears sometimes but then reappears when I open older projects that were made during the time it was crashing…
Same plugins in my template, same setup, newer projects don’t crash, old ones do, what’s up? Nuendo was always very stable for me, now it’ll just keep crashing at times incessantly, can’t even boot it up sometimes…
I either get a cannot run because corrupt plugin error - syntax error on Kontakt, or full on serious problem has occurred message.
When rebooting it’ll often just go to initializing and then close itself, or start loading a project and then again, just closes…
Apologies for long silence, after fixing my two PC’s I had a lot of work to catch up on and hadn’t returned to see the continuing conversation. I really do appreciate how well this has worked to find a solution and peace! I can still , with older projects created during the worst of the issue, get the same crash but very rarely and definitely not to the point that I have to stop working with clients like I did before. Thankyou everyone for your knowledge and input.
For those still facing the issue regardless of the bios update and making the ram speed /xmp adjustments I would definitely begin the process of returning the CPU asap. Goodluck!
1 Like
The error message “Plugin cannot run because it is corrupted” typically occurs when a plugin file becomes damaged or incomplete. To resolve this issue with the Yucine download plugin, try the following:
- Reinstall the plugin: Download and install the plugin again from a trusted source.
- Update: Ensure both the plugin and your software are up to date.
- Clear cache: Clear any temporary files that could be causing conflicts.
If the issue persists, consider reaching out to the plugin provider for further assistance.
I’ve started to have this issue myself in the last month or two. Am I understanding this thread correctly in saying that - generally speaking - updating the BIOS + turning off XMP generally has helped?
I don’t know if I’ve ever had to update my BIOS before - excuse the basic question but what’s the best way to do that? Download from the manufacturer? Some sort of utility?
Yes, definitely reduced issue for me but it still occurred in old projects every so often until someone here (thankyou, I can’t recall who atm) mentioned running your ram at the factory base/stock speed for your particular ram not the “advertised” speed. That nailed it for me 
Oh yeah, updating your bios can be done from your motherboard brands website support then finding your exact motherboard model/ operating system downloads. Look for Bios/firmware. Be sure to follow their instructions exactly and or get advice/help from a friend or YouTube. Your MB might even have an app that does it for you.
Hey! So I’ve been getting this exact same error and I use a different DAW (FL Studio). The fix that has been working for me (thus far) has been keeping the iLok License Manager open while I have the session open. Once and a blue moon it crashes when I’m trying to open a project file but never mid-session which was the whole reason that made me want to fix this issue in the first place. I will post updates here and if my current solution stops working, I will set my RAM to base clock as it seems this has worked successfully for some folks here in this thread.
Well, I updated my BIOS, made sure to have the most recent versions of my plugins / iLok, I also got new RAM, disabled XMP, updated Windows, etc etc. and I’m STILL having the issue.
Granted, it’s happening WAY less than before; in the last few weeks only gotten the popup message once. Before this, it was happening multiple times a day on almost every session, old or new, or I was getting weird crashes. The one time this message appeared recently was after closing Nuendo; it did not crash a session or refuse to open a session. The session was already closed, I was just exiting Nuendo for the day. Weird.
I know PACE says it’s not an issue with them, but it does only seem to happen with iLOK plugins, and it seems to happen regardless of Windows/Mac, regardless of DAW (we have now seen examples of Pro Tools, Cubase, Nuendo, and FL Studio), and regardless of Intel / Apple Silicon. Soooooooo???
For me, it’s most often Soundtoys or Liquidsonics, both iLOK.
Do you have an Intel 13th generation processor? You probably need a warranty replacement. PITA for sure, but your processor could be damaged (as mine must have been), so no amount of BIOS updates etc. will cure the problem for you. Since I got a replacement this problem has happened ZERO times, and some other weird crashing/performance issues I’d experienced have also gone away.
Hope this helps and good luck!
Brian