I don’t think that’s correct. Windows 11 is only available as 64-bit OS, there is no 32-bit version. Strangely though, the 64-bit DLLs are located in C:\Windows\System32 while the 32-bit ones required for 32-bit applications are located in C:\Windows\SysWOW64.
The error message is probably caused by another issue, like an incompatible or outdated driver.
no - its not an incompatible or outdated driver - Nuendo 12 running perfectly is a clue that it’s Nuendo 13 at fault.
Further testing today at my end, including fresh windows installation and ONLY nuendo 12 and 13 yeilded the same results. So I delved deeper…The interesting thing is, by cutting down the number of processor cores in the bios or in windows, from 36 to 32, I am able to run both versions of Nuendo perfectly - on the new windows installation and the original installation.
The problem lies with how Nuendo 13 handles core count over 32 cores.
Bump the core count up to use all 36 cores and the problem returns to N13 and I can only run N12…
That is good to know. In the “ancient times”, running another very popular DAW, once they began utiilizing both their proprietary CPUs and Native CPUs, it was well known that one had to keep ONE Native CPU processor out of the DAW processing chain, so that the computer could run the operating system and other non-DAW tasks. Otherwise, the computer would be erratic, with random crashes and sometimes no crash report. Weird behavior. This is eerily familiar.
I would recommend for now, only assigning 32 cores for DAW work, and reserving the other 4 for the operating system. You should be fine with that.
Glad you are getting to the bottom of this issue. Sorry I cannot be of more help.
I wasn’t successful using a script/command prompt to allocate the limited number cores to Nuendo 13, but have all cores available on the system for non-nuendo 13 activites.
I was only successful limiting the cores thru the BIOS or using msconfig - which required rebooting and having windows only use the alloted cores for its entire operation.
Yes - I remember somthing like that about that processor/core allocation in ancient times.
I got a similar spec and got this thread as a recommendation to check regarding my own issues.
Brand new Dell Precision tower with 128GB RAM & intel Xeon
I don’t know for sure, because I don’t have Cubase, only Nuendo, but from what I understand from tech support, the issue affected version 13 of both Nuendo and Cubase and therefore as Nuendo 14 is fixed, Cubase 14 is likely fixed too.
