Processor Core - Machine Check Exception

Hey Cubase family,

So I get this error intermittently when using Cubase:

Now it happens infrequently, sometimes I’ll go days without seeing it and sometimes it’ll happen within minutes of using the program. I’ve done a memtest86 over a whole weekend (no faults detected), my CPU previously did run a little hot so I switched out the AIO on it - now it runs cool constantly. I never experience this error when doing anything else that is CPU or CPU and GPU intensive, it only happens with Cubase. And it doesn’t necessarily happen with lots of VSTs, or multi tracks going on. Sometimes it can happen with an empty session.
Cubase 14.0.5 64bit2025.3.1 12.48.44.646.dmp (3.2 MB)

I’ve attached my most recent crashdump in hopes that maybe it contains some information that I don’t understand. However, I should note that a lot of times that these crashes happen no updated dump file is created, as I assume the crash happens instantly and there’s no time for a catch operation to write to a dump file.
System information is as follows:

OS Name	Microsoft Windows 10 Pro
Version	10.0.19045 Build 19045
Other OS Description 	Not Available
OS Manufacturer	Microsoft Corporation
System Name	DESKTOP-OI812U2
System Manufacturer	Gigabyte Technology Co., Ltd.
System Model	B550 VISION D
System Type	x64-based PC
System SKU	Default string
Processor	AMD Ryzen 9 5900X 12-Core Processor, 3701 Mhz, 12 Core(s), 24 Logical Processor(s)
BIOS Version/Date	American Megatrends International, LLC. F18d, 9/2/2024
SMBIOS Version	3.3
Embedded Controller Version	255.255
BIOS Mode	Legacy
BaseBoard Manufacturer	Gigabyte Technology Co., Ltd.
BaseBoard Product	B550 VISION D
BaseBoard Version	Default string
Platform Role	Desktop
Secure Boot State	Unsupported
PCR7 Configuration	Binding Not Possible
Windows Directory	C:\Windows
System Directory	C:\Windows\system32
Boot Device	\Device\HarddiskVolume1
Locale	United States
Hardware Abstraction Layer	Version = "10.0.19041.5553"
User Name	*
Time Zone	Mountain Daylight Time
Installed Physical Memory (RAM)	64.0 GB
Total Physical Memory	63.9 GB
Available Physical Memory	51.7 GB
Total Virtual Memory	67.9 GB
Available Virtual Memory	52.6 GB
Page File Space	4.00 GB
Page File	C:\pagefile.sys
Kernel DMA Protection	Off
Virtualization-based security	Running
Virtualization-based security Required Security Properties	
Virtualization-based security Available Security Properties	Base Virtualization Support, DMA Protection, Mode Based Execution Control
Virtualization-based security Services Configured	
Virtualization-based security Services Running	
Device Encryption Support	Reasons for failed automatic device encryption: PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable
A hypervisor has been detected. Features required for Hyper-V will not be displayed.	

Any insights or further trouble shooting ideas?

Cheers,

Krzys

Well it says your crash was in Archetype_Plini_X.vst3.

Do you get crashes in projects without this plug??

The crash dump file contains a crash in the Archetype plugin.

The error you see from the WHEA logger is typically a hardware error pointing to the CPU or even motherboard. You could try to run hardware tests using tools like CPU-Z or HWINFO

Curiosity, what do you use to view dump files?

windbg

Hi @JuergenP ,
can you tell me which line points to the WHEA logger event ID (probably ID 1?)? I’d like to learn more about things like that :wink:

@Grim :

As far as the Archetype Plini plugin, the crash happens even with that plugin not being used in a session. I just experienced another crash right now, but unfortunately the crashdump file wasn’t updated. So it’s looking like maybe some sort of hardware issue.

@JuergenP - I ran a stress test using CPU-Z and that didn’t result in a crash. It didn’t push passed 65 C either on the CPU temps, and was pumping passed 4.3GHZ too.

Appreciate all the suggestions so far, but I’m still in a similar spot to where I was it looks like.

It is right in the header of the first screenshot and also in the parameter list under Source and Event ID.

1 Like

Even if you don’t use the plugin, it still could be loaded. Can you try to move the plugin away temporarily and try it again?

Well, it should not crash running these utilities, that would be really bad. However it is hard to tell what causes the problem.
I think it is the best you take the system to a hardware shop that has experience with low level problems and let them investigate deeper.

Unfortunately even completely uninstalling the Plini X plugin does nothing, the computer still crashes when Cubase is running.

Unfortunately I can’t really take the system anywhere, as I don’t have a spare and I also use it for WFH at my job. I guess I could also try out a different DAW to see if a similar problem happens or not. I struggle to accept that it would be CPU related as this crash only happens when Cubase is running, and I otherwise use some very intensive programs for work and hobbies. But it also seems wild that it would be a software issue causing this. The hunt continues!