Hi all,
I’m getting Windows blue screens (stop code: KERNEL_SECURITY_CHECK_FAILURE) triggered randomly while working in Cubase 15. Sometimes when adding a new MIDI track, sometimes just hitting Play. It has happened repeatedly.
Possibly related graphics behaviour: When HALion launches, it sometimes slows the whole system to a crawl, and a video driver reset (the screen goes black/blinks and recovers) is what brings it back. Given that, plus the random BSODs, I suspect the GPU driver may be involved, but I’d like a second opinion.
Earlier context that may be related: Before the BSODs started, I was also getting a Cubase application crash referencing Groove Agent SE (VST3) — the “A serious problem has occurred” dialog. I understand there’s a known/reported Groove Agent SE crash in Cubase 15, so I’m not sure if these are connected or separate issues.
System:
- Cubase Pro 15 (15.0.30, 64-bit)
- Windows 11 (fresh install, fully updated)
- CPU: Intel i7-10700K
- RAM: 32 GB
- GPU: NVIDIA GTX 1660 Super
- Audio interface: Focusrite 8i6 mk3
What I’ve checked / tried so far:
- Windows 11 is a fresh install and fully up to date both OS and nvidia drivers
- No other apps/games installed, only Cubase and a couple of plugins (all licensed)
- BIOS at defaults, no overclock
Questions:
- Has anyone seen random KERNEL_SECURITY_CHECK_FAILURE with Cubase 15?
- Any known conflicts with this hardware/driver combination and Cubase 15?
I can attach the Windows minidump (.dmp) and the Cubase crash dump if useful. Thanks in advance.
Hi,
Attach the *.dmp files, please.
@faderdude
Have you installed the Intel Chipset drivers? If not you should do so.
I am always installing chipset drivers, MEI, all that stuff. Forgot to mention.
UPDATE: I’ve been “playing” with that error (including checking with Claude) and after testing everything (CPU, RAM, PSU, motherboard), I’ve finally concluded that the problem is the PCI Wi‑Fi card (ASUS PCE‑AX1800), which seems to have faulty drivers. Now as I pulled it out and reinstalled windows the system behaves fine without BSOD. What can I say… get a mac.
Thank you everyone!
That’s not really a fair statement. You can’t build (or for the most part, upgrade) your own mac, and you wouldn’t be installing a WiFi PCIe card in one. So you’re not comparing apples to, erm, apples.
You could also purchase a PC from a DAW builder, or others who cater more to creative/audio/video users.
Pete
Microsoft
Is it solved? How?
I’m also getting these crashes. My “solution” so far has been to switch the audio interface from the Focusrite Scarlett 18i20 2nd gen to the UA Volt. But I don’t know what is causing it. No damp files to attach.
If you’re getting an actual bugchk / bluescreen / black screen, there are .dmp files.
In your event log (search for Event Viewer) under Windows logs and system, scroll down until you find the error for the crash. In that will be the location of the generated dump file.
Pete
Microsoft
Ah, those. I was thinking about crash logs made by Cubase.
These I have (already sent to IT in my company to investigate). I’ll upload it here tomorrow.
I don’t want to argue, but my point is that small thing like faulty driver on Windows took almost a week of unnecessary exploration.
It was pretty tricky to find out the cause. I checked my Windows dump file with WhoCrashed, which only pointed to memory or thermal issues, so I tested those first with dedicated software. Then I disconnected all peripherals and kept running heavy Cubase projects until the BSOD showed up with the Wi-Fi card. Removed it, and everything’s been fine. Worked all day today without a problem. Also with no internet, but that another story 
Oh well, I can’t use that laptop without internet as it’s for remote work 
To make it worse, I have some restrictions made by IT because its company’s laptop which makes bugfixing and diagnosis even more annoying.
But I see that you also have Focusrite interface and I read plenty of reports with this BSOD and Focusrite (they released recently drivers update to fix this). Using another interface works for me so far.
To be honest using a daw with internet = problems i only turn on unless i need to update.. 3rd party wifi card driver issues unless pushed by windows.. been using windows since win 95. Ex IT guy for 20 years .. Macs have there purpose but PC you build how you want it..
After working with IT, 3 suspects were identified:
Wifi
VPN
Focusrite drivers (old MIDI driver)
This actually correlates with what was reported by Focusrite support on one reddit group. They released new driver 3 months ago. Interestingly, I installed full software 2 weeks ago and it installed older driver. I had to install only driver separately.
I still have screenshot from the Focusrite rep/support:
I’m not sure if Wifi is causing BSOD in my case. With UA Volt interface it’s not happening.
From the screenshot, it appears there is a conflict between the Focusrite drivers and the anti‑cheat software that games install on the system.
To be honest, I’ve never had any issues with Cubase 11-13 while using cable internet on Windows 10.
I never like to have my workstation online at all personal preference.. win 10 was great also
I think that the conflict is with more than just that anti-cheat software. I never had it installed, and my interface has been fine for 10 years (4 years on this laptop). BSODs started a few months ago, and the only change I can think of was a Windows update.
Now I don’t feel brave enough to test the new drivers because a BSOD two weeks ago crashed the system completely (failing auto-fixing loop), and I had to reinstall everything. I don’t want to do it 2nd time in just one month 
Definitely would update the driver for your audio card
BSODs are mostly there to protect your apps and data from corruption and from potential exploits.
The BSOD you’re seeing is to protect your system. It’s because it uncovered a problem in the driver, and that problem could potentially be exploited.
That specific BSOD is new, but the driver bug is not. We continuously update the checks in the kernel from month to month.
So the fact that the BSOD didn’t happen in the past means that, instead, the data/etc. corruption potentially happened in the PC. I know it doesn’t seem like it, but the BSOD is actually a good thing. Not as good as a bug fix for the driver, but good for your data.
Pete
Microsoft
