You are fortunate that you happened to build one of the magic platforms (combo of CPU, MB/BIOS, audio interface) that did not experience the issue.SuperG wrote: ↑Tue Jan 31, 2023 7:42 pm Sorry to hear folks having problems.
I have been using Cubase ever since 2018 (when Gibson torpedoed Sonar). Cubase has been good to me. It is not that I cannot get Cubase to stumble occasionally, it is just that I really must push it to get myself into a jam. Usually it is some orchestral project I am working on (with a gajillion tracks); I then wander off part way through to read mail, forget myself, open some other application for a bit (Adobe this, or that...) and then go back to music. More than one media application/memory hog and things could get ugly if I am not paying attention.
My setup is Windows 10 on a first gen i7-6700K. It has only got four *real* cores, but it is sitting on 48 GB ram. (Helps tremendously with VI Pro...) If I had to guess the notable thing about my system's stability is that it is using good-old FireWire (800) for my audio interfaces. Still using Motu interfaces and those things are solid. My only gripe with them is the display's go out after time.
I requested on the steinberg forums and via email support a list of supported hardware and/or BIOS configs, but they refused continuously for over 3 years. I have steinberg *in writing* admitting this problem, and asking me to work with them over the long term to "QA and troubleshoot", but I ran out of patience and time to do this with them years ago. There was no solution offered other than "wait for the industry to change", and that just doesnt work in the face of numerous other brands working this out just fine.
-My wife's MSI laptop from 2015 - an i5 H-series 8th gen with 16GB DDR4 - ran everything perfectly without configuring anything, including ASIO Guard.
-My i7 965extreme 4/8 core with 16GB DDR3 on an x58 motherboard from 2007 (all default) had the issue and I couldnt resolve it with any changes to BIOS or windows runtime.
-My i7 7800x 6/12 core with an x299 motherboard had the issue worse than any other, but had a workaround. I had to fully disable all virtual cores, all power management, and all dynamic clocking to stabilize it, and it would STILL overload internally and pop/click sometimes(rare).
-My i9 10900KF 24 core on a z690 motherboard with 32GB DDR5 works perfectly with all BIOS features enabled. I can do anything while C12 is running - extract large archives, browse web at any capacity, download numerous files at 100MB/sec via our 1200mbit ISP, etc. C12 never glitches, real CPU and internal ASIO never overloads.
And allllllllll this time Steinberg says "there is no issue/the issue is extremely rare and you are basically alone/dont use any new Intel CPUs