@david_d
Good day David,
Hopefully this reply finds your problems behind you! If not, here is a list of items to look at (I’ve been at this for over 20yrs, built/bought/sold plenty of IT companies/studios).
1 - What was the exact error(s) thrown in the BSOD?
2 - Cubase/Nuendo BSOD 99% of the time is caused by the things you have already been informed by Steinberg Support (drivers, hardware, virus, performance, etc).
3- Head over to the following help center link and verify your system is properly updated with OEM drivers and you have performed all the recommended tweaks. I personally regard the tweaks as principle items that should never be overlooked. Every system we build has every tweak in it. And every system we build rarely (if ever) has an issue like yours. https://helpcenter.steinberg.de/hc/en-us/articles/360008589880
5 - Make sure your Windows 10 system default audio playback device is not the same ASIO/Audio interface you are using in Cubase.
6 - Make sure you are on the latest OEM ASIO drivers for the audio interface, and ASIO4All is not installed. It can be very problematic having this running a professional audio interface card, or installed along side an OEM ASIO driver.
7 - If you are running an nvidia GPU, make sure the Studio version of the driver is installed and not the gaming/performance NVidia GPU drivers (this is crucial). And just as crucial, also mentioned in the help center article, uninstall/shut down any NVidia software that is not a driver (Broadcast, Experience Center, etc)
8 - Treat this as a standalone audio workstation, if you are not already doing so, and back-out any performance and overclocking tweaks (typical to gamers).
9 - Download Autoruns from Microsoft, it will give you a complete view of everything that is installed/running at startup/running as a service/installed drivers/on and on. Caution, if you have never used this tool, do not run it in administrator mode (that’s an option in the menu when you launch it), only use to it look around, not manage your machine. Autoruns for Windows - Sysinternals | Microsoft Learn
10 - Perform a memory test on your system using Toms Hardware Guide: How to Test RAM: Make Sure Bad Memory Isn't Crashing Your PC | Tom's Hardware
11 - Its possible you have some corruption at the HD level with something that is critical to Cubase (i.e. dll, exe, partition information). Work this problem from the bottom up. First check the hard drive for issue by running CHKDSK, see: How to Scan & Fix Hard Drives with CHKDSK in Windows 10 - Second, reinstall Cubase 11 on a different drive, preferably an eNVM drive, or minimally SSD.
12 - In the meantime while you figure this out: Disable all tracks before closing the Cubase project. Stating the obvious: Its best practice to do this for any project you are not actively working on.
Best of luck!!
For future generations, please let us know how you solve the problem.
-michael clendening