Recently I've been using R2R's release to mix some audio tracks and I noticed that at least on W11 is very prompt to crashing under a lot of different circumstances that normally wouldn't be an issue on any other DAW.

• Want to change my audio driver settings while Cubase is open? Crash
• Randomly disconnected from the internet? Crash
• Opened another audio application like audacity while Cubase is running? Crash
• Try to open a project with a different audio driver than the one currently in use? Crash
• Add more than 2 simultaneous Insert FX on a track while playback is active (Pro C2 AND L2 in my case)? Crash
• Wake up my PC from sleep while leaving Cubase open? Crash
• Be just there doing other things while having Cubase open in the background? Crash

The only common symptom between all of these is that the post crash report Cubase shows on startup is that the crash was caused by SYSTEM32/MMDevAPI.DLL and OPENGL32.DLL, and since both of these are based the sys32 folder they can't be tampered with for sec reasons. The official Steinberg forums didn't had anything on crashes similar to these and since my laptop with W10 running the same Cubase version 14.0.32 is not as crash prompt as my PC, I'm starting to suspect it's a W11 problem.

If anyone has lead regarding these errors or found a solution to the same issue, I'd greatly appreciate it.

 

With all respect, if you use it regularly or professionally, pay for it. It is your main Tool where you'll host the others Microtools.

If that's not your case, then only be grateful for what you can try for free.

 

First I would make sure your Graphics Drivers are up to date.
I don't think it will be an issue with Cubase (R2R) as it works perfectly for me on Windows 11.
Next Open CMD Prompt or Terminal (as Admin) and do a scan by typing:
sfc /scannow
and press [enter]
If it finds any files that needs fixing it should fix them and you can repeat scan again to make sure everything is OK.
Scan for Malware using something like Malwarebytes (Free)

Spoiler: Malwarebytes (Free)

https://www.malwarebytes.com/mwb-download

Also make sure you have the latest Microsoft Visual C++ Redistributable installed:

Spoiler

https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170

What audio interface are you using also?
Could possibly be related to Graphics card or an Audio interface driver issue if none of the above fix it.

 

R2Rs Steinberg releases are just as stable as the legit thing, I don't think it would make much difference if you got the real deal.
Ok, Openglide is interesting, as samsum already say that could mean a gpu issue.
Now that gui at the Steinberg forum updated his gfx drivers and got rid of the problem:
https://forums.steinberg.net/t/cubase-11-freezes-safe-mode-says-mmdevapi-dll/749722/7
//edit// windows' own graphics driver often have VERY outdated openglide implementation included. That is because openglide is competition to directx (well... somehow).
You better download gpu drivers from AMD, NVidia or Intel directly.

 

MMDevAPI.DLL is related to Windows Audio devices, or rather devices enumerated by the Windows Audio system. It would help to know what you are using as your audio device.

 

Did this as the first step, it did say that some files were damaged, but the log didn't say if it was one of the dlls that made cubase crash. Repaired the VS C++ redistributable as well.

It's a 3rd Gen Focusrite 8i6 but I only use it if I use my rack synths in a project since I don't have studio monitors (only headphones) that can plug directly to it.

Did this too, although I wasn't exactly that far behind version wise and also checked the thread linked here when I first had these issues, updated my drivers as well then. I have windows updated to the latest version too.

Flexasio when I need audio from my PC 3.5mm speakers and the Focusrite USB driver otherwise.

Edit: I tried to replicate two of the crashes after doing all of this (opening audacity while cubase is open and turning on my audio interface while having the DAW running) and it still crashed citing MMDevApi as the cause, so the issue might be somewhere else.

 

Last edited: Sep 22, 2025

You got a lot going on in terms of variables for troubleshooting purposes. If you get this crash citing the same dll using only the Focusrite and no PC audio whatsoever, including having the Focusrite set as the driver in Audacity when you do, then maybe it's something else.
It's just for that particular dll, which handles device aggregation for WASAPI, to bug out when you're using WASAPI for audio, especially when opening another DAW trying to use the same device, it seems related from the outside looking in. Do have exclusive control enabled in Cubase (Studio Settings > Audio System) or in Windows Sound Properties for the PC audio?

 

Last edited: Sep 22, 2025

This wasn't quite true, someone was getting freezes related to the same dll, a few system updates and it cleared up for them.

 

And what he said wasn't quite true, that's all, had nothing to do with you personally.

 

The PC speakers had exclusive control but disabling it didn't seem to make a difference and regardless of the selected audio driver in cubase it still crashes when I open audacity. The latter doesn't seem to detect the Focusrite driver either, so I don't if it's due to an audio controller conflict.

Will have to do that, but as a secondary resort, as I would have uninstall both cubase plus the silk emu and r2r certificate in order to make room for the legit version but I'll have it in mind too.

 

Update your graphics card drivers....

 

Hi EXpanko,
have you updated the driver of your Focusrite? I've had maior problems with sound and crashes om my win10 after the driver got updated without me knowing... there is a very recent update of Focusrite Control that includes new drivers that are supposed to correct the issues, the driver that got 'pushed' some 2 months ago was faulty!
good luck to us!
Pim

 

SYSTEM32/MMDevAPI.DLL and OPENGL32.DLL

MMDevAPI.DLL Crash – Quick Fix Guide

Spoiler: Source: Grok KI

MMDevAPI.DLL Crash – Quick Fix Guide
MMDevAPI.DLL is a Windows system file in C:\Windows\System32 that manages audio devices (e.g., speakers, microphones). Crashes often occur due to recent Windows updates (like Windows 11 24H2, released late 2024), outdated audio drivers, corrupted system files, or app-specific issues (e.g., OBS Studio, games, or text-to-speech apps). Since today is September 22, 2025, a recent update might be the culprit. Check the Event Viewer (Windows Logs > Application) for errors mentioning MMDevApi.dll to pinpoint the cause.

Steps to Fix the Crash
Try these steps in order, restarting your PC after each one to test if the issue is resolved. Create a System Restore Point first (search for "Create a restore point").


Step Action Why It Helps
1. Update Audio Drivers - Right-click Start > Device Manager. - Expand "Sound, video, and game controllers". - Right-click your audio device (e.g., Realtek, NVIDIA) > "Update driver" > "Search automatically". - If no update found, download the latest driver from the manufacturer’s site (e.g., Realtek, NVIDIA). Fixes driver conflicts, especially after Windows 11 24H2 updates.
2. Run SFC Scan - Open Command Prompt as Admin (search "cmd", right-click > "Run as Administrator"). - Type: sfc /scannow and press Enter. - Wait ~15 minutes for completion. Repairs corrupted system files like MMDevAPI.DLL.
3. Re-register DLL - In Admin Command Prompt: regsvr32 /u MMDevApi.dll (press Enter, then) regsvr32 MMDevApi.dll Re-registers the DLL to resolve loading issues, common in Windows 11 24H2.
4. Update Windows - Settings > Windows Update > Check for updates. - Install all updates, including optional ones. Microsoft patches often fix MMDevAPI.DLL issues.
5. Restart Audio Services - In Admin Command Prompt: net stop AudioSrv net stop AudioEndpointBuilder net start AudioEndpointBuilder net start AudioSrv Resets audio services tied to MMDevAPI.DLL.
6. Workaround for Apps - Run Windows Media Player (or Legacy version) in the background (e.g., pause music). - Disable HDMI audio: Device Manager > "Sound, video, and game controllers" > Right-click HDMI device > Disable. Prevents crashes due to device changes in Windows 11 24H2.
7. App-Specific Fixes - For OBS: Update to the latest version or rollback to 27.1.3. - For games: Set compatibility mode to Windows 10 (right-click EXE > Properties > Compatibility). Addresses app-specific bugs triggering the crash.
If It Persists

• Restore System: Use a System Restore Point from before the issue (pre-Windows update).
• Check Event Viewer: Share specific error details for tailored advice.
• Contact Support: Reach out to Microsoft Support if unresolved.
• Avoid Third-Party DLL Downloads: These risk malware; stick to Windows tools.

Provide details about the app crashing or the error message for more targeted help!

OPENGL32.DLL How to Fix Nvidia OpenGL Driver Error in Windows 10/11 [Steps]
https://techsgizmo-com.translate.go...l=auto&_x_tr_tl=en&_x_tr_hl=de&_x_tr_pto=wapp

Spoiler: Here’s how to fix OpenGL errors in Windows 10

Here’s how to fix OpenGL errors in Windows 10
https://windowsreport.com/opengl-problems-windows-10/#1
Fix OpenGL Not Supported Error in Windows 10 [2021]

Fix Opengl not supported error in windows 10

How To Fix OpenGL Error (For old pc or no graphic card)

How to Fix Nvidia OpenGL Driver Error in Windows 10/11 [Steps]
https://techsgizmo-com.translate.go...l=auto&_x_tr_tl=en&_x_tr_hl=de&_x_tr_pto=wapp

You have to take action yourself and optimize yourself, here is a wealth of links.

Spoiler: Better you use the following links to optimize your computer for music production.

Better you use the following links to optimize your computer for music production.
0.) Don't let audio glitches ruin your performances! www.cantabilesoftware.com/glitchfree/

1.) The Ultimate Guide to Optimize your Windows PC for the Stage
https://gigperformer.com/docs/ultimate-guide-to-optimize-windows-for-stage/index.html

2.) LatencyMon 7.31
The LatencyMon software analyzes and identifies which device, which driver or which service is causing audio dropouts or malfunctions. Real-time audio suitability checker for Windows 10/8.1/8/7/2016/2012/2008 (x86 and x64)
Scroll Down to: System Monitoring Tools https://www.resplendence.com/downloads

3.) Windows Tuning Tips for Audio Processing
https://support.native-instruments....1729-Windows-Tuning-Tips-for-Audio-Processing

4.) PreSonus - Optimizing Your Computer for Audio - Windows 10
https://support.presonus.com/hc/en-...Optimizing-Your-Computer-for-Audio-Windows-10

Optimizing Your Computer for Audio - Windows 11
https://support.presonus.com/hc/en-...Optimizing-Your-Computer-for-Audio-Windows-11

5.) Ableton - Optimizing Windows for Audio
https://help.ableton.com/hc/en-us/articles/209071469-Optimizing-Windows-for-Audio

6.) FL Studio - Optimizing FL Studio performance
www.image-line.com/fl-studio-learning/fl-studio-online-manual/html/app_opt.htm

7.) Windows: How to set up and optimize a Digital Audio Workstation
https://helpcenter.steinberg.de/hc/...t-up-and-optimize-a-Digital-Audio-Workstation

8.) Focusrite - Optimising your PC for Audio on Windows 10
https://support.focusrite.com/hc/en-gb/articles/207355205-Optimising-your-PC-for-Audio-on-Windows-10

9.) Steinberg / Windows: How to set up and optimize a Digital Audio Workstation
https://helpcenter.steinberg.de/hc/...t-up-and-optimize-a-Digital-Audio-Workstation

 

Last edited: Sep 22, 2025

I normally disable my internal motherboard audio in bios but sounds like you are using both swapping between them. I also do not have studio monitors and just have my audio interface running into a normal amp with normal speakers and can use headphones in my audio interface or my amplifier. I wouldn't mix audio devices really especially when using the motherboards audio.
Grab the latest Focusrite for your model and use their ASIO Drivers.
You can use WinDbg to analyze Cubase Crash dumps which you can get from here or the Windows Store:

Spoiler

https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/

For any latency issues or to test current setup this is great free program:

Spoiler: LatencyMon

https://resplendence.com/latencymon

I would first disable internal audio and see if the problem is still there or not just using your Focusrite and Focusrite ASIO Driver and maybe can eliminate issues in steps.
I'm also a legit Cubase owner since Atari ST days but with R2R I get to use much, much more
Let us all know how you get on and we can try help further.

 

Last edited: Sep 22, 2025

Was the first thing I was told and already did so.

In theory yes, Focusrite control technically updates the driver every time you open the app, I currently have firmware 1605 if that's relevant.

I had already done most of the things in this list but for some reason, executing both of these commands result in a calling DllRegisterServer error.

I dont have this option in device manager, probably because of the fact my GPU is connected via DP instead.

Spoiler: Crash report from a few days ago

KEY_VALUES_STRING: 1

Key : AV.Type
Value: Read

Key : Analysis.CPU.mSec
Value: 3843

Key : Analysis.Elapsed.mSec
Value: 42002

Key : Analysis.IO.Other.Mb
Value: 3

Key : Analysis.IO.Read.Mb
Value: 1

Key : Analysis.IO.Write.Mb
Value: 108

Key : Analysis.Init.CPU.mSec
Value: 1125

Key : Analysis.Init.Elapsed.mSec
Value: 54821

Key : Analysis.Memory.CommitPeak.Mb
Value: 108

Key : Analysis.Version.DbgEng
Value: 10.0.27920.1001

Key : Analysis.Version.Description
Value: 10.2506.23.01 amd64fre

Key : Analysis.Version.Ext
Value: 1.2506.23.1

Key : Failure.Bucket
Value: INVALID_POINTER_READ_c0000005_MMDevAPI.dll!CDeviceEnumerator::CallOnPropertyValueChanged

Key : Failure.Exception.Code
Value: 0xc0000005

Key : Failure.Exception.IP.Address
Value: 0x7ffa6025be46

Key : Failure.Exception.IP.Module
Value: MMDevAPI

Key : Failure.Exception.IP.Offset
Value: 0x5be46

Key : Failure.Hash
Value: {519d6dd1-427f-7415-4cbf-979aac11739d}

Key : Failure.ProblemClass.Primary
Value: INVALID_POINTER_READ

Key : Timeline.OS.Boot.DeltaSec
Value: 6317

Key : Timeline.Process.Start.DeltaSec
Value: 4778

Key : WER.OS.Branch
Value: ge_release

Key : WER.OS.Version
Value: 10.0.26100.1

Key : WER.Process.Version
Value: 14.0.32.342


FILE_IN_CAB: Cubase 14.0.32 64bit2025.9.21 14.39.33.039.dmp

NTGLOBALFLAG: 0

CONTEXT: (.ecxr)
rax=00007ffa52a78030 rbx=000000000af74720 rcx=000000000af74710
rdx=0000000017180328 rsi=00000000561dfa40 rdi=0000000017180360
rip=00007ffa6025be46 rsp=000000003799f8f0 rbp=000000003799f9c0
r8=0000000055427b30 r9=000000003799f9a0 r10=00000000005b0000
r11=000000003799f940 r12=0000000000000000 r13=000000003799fa60
r14=0000000055427b30 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206
MMDevAPI!CDeviceEnumerator::CallOnPropertyValueChanged+0x46:
00007ffa`6025be46 488b00 mov rax,qword ptr [rax] ds:00007ffa`52a78030=????????????????
Resetting default scope

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ffa6025be46 (MMDevAPI!CDeviceEnumerator::CallOnPropertyValueChanged+0x0000000000000046)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00007ffa52a78030
Attempt to read from address 00007ffa52a78030

PROCESS_NAME: Cubase14.exe

READ_ADDRESS: 00007ffa52a78030

ERROR_CODE: (NTSTATUS) 0xc0000005

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 00007ffa52a78030

STACK_TEXT:
00000000`3799f8f0 00007ffa`60205e8d : 00000000`0af74710 00000000`17180328 00000000`55427b30 00000000`3799f9a0 : MMDevAPI!CDeviceEnumerator::CallOnPropertyValueChanged+0x46
00000000`3799f970 00007ffa`60228750 : 00000000`59b013a8 00000000`00000000 00000000`17f75018 00000000`17f75010 : MMDevAPI!CDeviceEnumerator::OnPropertyValueChanged+0x1bd
00000000`3799fa00 00007ffa`6021ea91 : 00007ffa`60286fd0 00000000`00000001 00000000`401af060 00000000`00000005 : MMDevAPI!CLocalEndpointEnumerator::OnMediaNotification+0x130
00000000`3799fad0 00007ffa`6a861edd : 00007ffa`6a85fb30 00000000`54fd4650 00000000`54fd4718 00007ffa`6a861d90 : MMDevAPI!CMediaNotifications::OnMediaNotificationWorkerHandler+0x1c1
00000000`3799fbc0 00007ffa`6a872a39 : 00000000`00000000 00000000`00000000 00000000`00000000 00007ffa`6a85b150 : ntdll!TppSimplepExecuteCallback+0x14d
00000000`3799fc00 00007ffa`6990e8d7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!TppWorkerThread+0x819
00000000`3799ff60 00007ffa`6a81c34c : 00000000`00000000 00000000`00000000 000004f0`fffffb30 000004d0`fffffb30 : kernel32!BaseThreadInitThunk+0x17
00000000`3799ff90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x2c


SYMBOL_NAME: MMDevAPI!CDeviceEnumerator::CallOnPropertyValueChanged+46

MODULE_NAME: MMDevAPI

IMAGE_NAME: MMDevAPI.dll

STACK_COMMAND: ~217s; .ecxr ; kb

FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_MMDevAPI.dll!CDeviceEnumerator::CallOnPropertyValueChanged

OS_VERSION: 10.0.26100.1

BUILDLAB_STR: ge_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 10.0.26100.4768

FAILURE_ID_HASH: {519d6dd1-427f-7415-4cbf-979aac11739d}

Followup: MachineOwner
---------

It seems that it was caused due to a change in audio devices from what I interpreter from this report, but I'm sure not why still.

Edit: I disabled a few audio devices that I don't use and that seemed to solve the crash for when audacity is opened while cubase is running but modifying audio driver settings or opening the windows mixer menu still causes it to crash

Tried opening audacity with cubase open with only the Focusrite device enabled in device manager, it still crashed as usual.

 

Last edited: Sep 23, 2025

Agree.
R2R C14 on win11 is the most stable version ever. The problem is probably win11 settings, it takes a whole lot more tweaking compared to win7 for audio work.

 

Tried replicating the crash condition here and it did crash when I went into advanced audio settings as well. Unfortunately, unlike the poster here, I already have windows and my GPU drivers updated to their latest versions as well, so I can't cross that as the cause for the crashes.

 

Spoiler: Source: Grok KI

It sounds like you're dealing with a frustrating audio driver conflict—likely the ASIO driver for your Focusrite interface being "locked" by Cubase, which prevents Audacity from accessing it and causes a crash on launch. This is a common issue on Windows when multiple apps try to use exclusive-mode ASIO devices. Disabling other devices in Device Manager helps isolate things, but it doesn't resolve the app-level lock. Assuming "Szeinber" is a typo for Steinberg (Cubase's developer), I'll focus on practical fixes based on similar reported cases.

Quick Test: Close Cubase Completely

• Before launching Audacity, ensure Cubase is fully closed (check Task Manager > Processes tab for any "Cubase" or "ebr" processes and end them if running).
• Relaunch Audacity and try to record/playback.
• Why this might work: Cubase holds onto the Focusrite ASIO driver even after closing the window, but killing the process releases it.

If that doesn't help, try these steps in order:

1. Switch Audacity to a Different Audio Host (Bypass ASIO)
Audacity defaults to ASIO for low-latency pro audio, but this can conflict with Cubase. Switch to MME or WASAPI for shared access.

• Open Audacity.
• Go to Edit > Preferences > Devices.
• Under "Audio Host," select MME (or Windows WASAPI if available).
• Set "Recording Device" and "Playback Device" to your Focusrite (it should appear as "Focusrite USB Audio" or similar).
• Set the project sample rate to 44.1 kHz or 48 kHz (match Cubase's if possible).
• Close Preferences, then test recording.
• Trade-off: Higher latency than ASIO, but no crashes. If it works, you can use this for quick Audacity tasks while keeping Cubase open.

2. Reinstall Focusrite Drivers and Reset Audacity
Corrupted or mismatched drivers are a top culprit for crashes.

• Download the latest Focusrite drivers from their site (focusrite.com/en/downloads—pick your exact model, e.g., Scarlett Solo/2i2).
• Uninstall old drivers: In Device Manager, right-click your Focusrite under "Sound, video and game controllers" > Uninstall device (check "Delete the driver software").
• Restart your PC, then install the new drivers. Open Focusrite Control app once to initialize.
• For Audacity: Download the latest version (3.6+ as of 2025) from audacityteam.org. During install, check "Reset Preferences" in the setup wizard.
• Relaunch and test with Cubase closed first.

3. Check Sample Rate and Buffer Settings
Mismatched rates can trigger "Error opening sound device" crashes.

• In Audacity: Edit > Preferences > Quality > Set "Default Sample Rate" to 48000 Hz.
• In Windows Sound settings (right-click speaker icon > Open Sound settings): Set Focusrite as default output/input, and ensure sample rate matches (Properties > Advanced).
• In Focusrite Control: Set global sample rate to 48 kHz.
• Increase Audacity's buffer: Edit > Preferences > Devices > Playback/Recording > Latency > Buffer length to 100-200 ms.

4. If Crashes Persist: Run in Compatibility Mode or Check Logs

• Right-click Audacity.exe > Properties > Compatibility > Run as administrator + "Disable fullscreen optimizations."
• Check Windows Event Viewer (search for it in Start menu > Windows Logs > Application) for crash details around the time—look for "Audacity" or "Focusrite" faults. This can point to specific driver errors.
• Test on another PC if possible to rule out hardware (e.g., USB port issues—try a different port or powered hub).

Long-Term Workaround: Use Different Hosts for Each App

• Set Cubase to ASIO (Focusrite USB ASIO) for low-latency tracking.
• Keep Audacity on MME/WASAPI for editing/mixing when Cubase is open.
• If you need both on ASIO, close one before opening the other.

If none of this resolves it, reply with more details: Your OS (Windows 10/11?), Focusrite model, Audacity/Cubase versions, exact crash error message, and if it happens on launch or during recording. We can dig deeper from there!

 

Fixed this one case, check the edit on my previous post.

 

What other problems do you have? A detailed description of the problems would be very helpful.
The Cubase log file is more for Cubase employees.