I started getting these errors only on large projects with many tracks, plugins, variaudio edits, etc. The plugin is always a random installed plugin and not always one I’m even using in the project. Ten seconds or so after the popup Cubase 12 flash crashes with no recourse. Reinstalling the plugin changes nothing.
I haven’t been able to nail down a specific crash scenario other than large complex projects. CPU usage seems to be unrelated and it happens at random rather than during specific tasks.
Has anyone run into this issue or seen this error popup?
Hi @daveotero , I am having the exact same problem and have completely wiped system and reinstalled, contacted Slate(main plugin offender and Ilok) but no resolution. Did you manage to solve it? I am losing my mind. I’m on Cubase 13, have had problem on windows 10 & 11. Cheers. Andrew
Im having the exact same problem. Random plugin corruption. Nothing helps. I have had to revert back to cubase 12 where everything seems more or less normal. Tried cubnase 13 again today, with the new update, and it took 2 seconds for a VST to get “corrupted”. Could it possibly be related to the bad Intel I9 13900 CPU’s ? I wish Steinberg could come up with a solution.
Yeah, unfortunately this was from bad Intel CPUs, a 13900k and a 14900k. I’ve gone through two of them now and the third one is holding strong only because I’ve under powered it to keep it from damaging itself. There are apparently microcode updates in the newest BIOS versions, so long as your motherboard company has updated them, but this whole thing is a complete disaster.
Anyway, if you manage to make it through the Intel warranty gauntlet, I currently have my short term power limits capped at 250W and my long term power limits capped at 170W. I haven’t noticed any DAW performance degradation, my machine runs cooler (therefore quieter), and this current 14900k has lasted longer than any of the others.
I had this exact problem recently - seemingly out of nowhere. Cubase (version 11.0.41, Windows 11) would issue an Authorization Error dialog with “ cannot run because it is corrupted. Please try reinstalling the product.” where was any number of different plugins - mostly Slate Digital stuff, and things I wasn’t even using in the project. Pro Tools actually issued this error as well, but for the PT application itself (“Pro Tools Ulimate subscription cannot run…”). Happened pretty much immediately after opening a project/session. Made me pretty much dead in the water. Slate and PACE (iLok) support tried to help, but their suggestions so far were only to uninstall/reinstall things, basically (and the problem persisted).
Thankfully I found this thread and @daveotero 's response mentioning the BIOS update possibility. My system is an ASRock Z790 Pro with a Intel Core i9-13900KS, and I don’t think I had ever updated the BIOS. Of course the latest BIOS didn’t work (system wouldn’t start ugh) but after stepping backwards one BIOS version at a time I got to version 7.07 and not only did my system start, but this Authorization Error problem is GONE!
Many thanks again to @daveotero for posting your experience and solution! Glad I didn’t have to replace my CPU. (knocks on wood)
Annnnd I spoke too soon. Within an hour of posting this (and responding to the PACE support guy with “I think I’m good”) both Pro Tools and Cubase issued this error and both crashed. (screen shots below) So I’m back with PACE/iLok hoping they’ve got some ideas…
Unfortunately based on my experience I’m almost positive your CPU is trashed and needs to be replaced. I would go ahead and at least get started with the RMA process through Intel. The BIOS updates are supposed to keep this problem from happening, but once the damage is done it’s irreversible so it’s likely your CPU is damaged beyond repair.
I have seen this happening on an Apple Silicon Mac, so it is unlikely related to any specific Intel generation or CPU issues (though I can’t exclude any, of course).
A reboot sorted it and I never saw that again. As it happens with different plugin vendors and a host, looks definitely worth reporting to PACE/iLok.
Thanks @daveotero , much appreciated. In your experience dealing with Intel, did they provide some kind of “CPU integrity checker” utility that you could run to show them “Yup, it’s got this problem” or was the determination of CPU-gone-bad more a process of elimination?
Love your URM content and Drumshotz pack, BTW - I’ve got your doom hammer snare on everything!
I’ve gone through two RMA replacements with Intel. With the first, I had already replaced the processor with one I bought off the shelf because I had work to do and deadlines to meet so I couldn’t wait around. After explaining my situation, the Intel agent was cool enough to start the exchange process without testing. The next time I knew the signs and started the RMA process early so I was able to download their diagnostic tools and show that some of the test elements were failing.
Since then these issues have become much more widely publicized so I would think that would make the process easier, but who knows.
It was pretty easy to get the conversation started with Intel and I would definitely recommend just doing that ASAP. Be persistent if you need to.
Thanks for picking up the pack! Doomhammer hammers indeed!
Thanks @Fabio_B , good to know. I’ve been in touch with PACE/iLok support about it already, so maybe they’ve got ideas… Would loooove for that to be the case, and not an Intel Core i9-13900KS issue - but we’ll see.
I also had contacted ilok support and they told me that those error pop-ups were not an ilok error. I downloaded a utility to help me determine what process spawned the window since it’s not apparent, and it was a Windows service that I don’t recall the exact name of. Not ilok or cubase specific. I suppose it could be another hardware or software issue, but since you have a 13900 and the two main processors affected by this issue are the 13900 and 14900 I would be fairly certain this is the root of your issues.
Sure could be a 3rd-party tool/API or anything else really… guess it’s rare enough to be a hard nut to crack. I’ve seen it so rarely I can distictly remember all of the cases.
Weird that I got it once and never happened again, I didn’t reinstall iLok Manager or the plugin, didn’t update the OS, and I use that plugin daily.
Actually I thought is was my 14900k, but I think it’s rather the ram speed that was set too high and crashing random plugins. To solve it, I went into the bios, and removed most of the optimizations done by default. So!
I set my RAM to base clock (4800 even if it’s advertized as 6000…having the XMP profile on and the speed set to 6000 by default was 80% of the problem). To fix it, check your ram base clock speed and set it manually to that in bios. You can find the clock speed my entering your ram model in google, and check the specs.
Disabled memory optimization if you see this option
*Next step, if you’re still having problems…Set the power profile to baseline (intel’s one, not the motherboard’s one). Try and find the intel one, or the baseline, but not optimized or Auto. This ensures your motherboard doesn’t try to push too hard.
Finally I’m stable!!!
If you still have problems, those can help too:
Disable “suspend to ram” and try, see if it helped.
If not, the Disable Intel speedstep in the Bios (all of this is in bios)
Disable some more intel turbo stuff, but not too many . Do it one by one.
Clicked on this thread to post that I had this issue years ago in Cakewalk across several reinstalls. Turned out I had a bad stick of RAM. Once I replaced it, I never had the issue again.
(screen shots below) So I’m back with PACE/iLok hoping they’ve got some ideas… 
