Nice setup! Lots of screens indeed ![]()
I am glad you had 2 days without crash, hope it carries on.
If you got more, try disable Nahimic.
Best of luck !
If anybody helps: Without Izotope Ozone 11 Elements NO CRASH…and now…one session no crashes uninstalling Bonjour, NO CRASH with Ozone 11 Elements activated!
I think it’s solved. 1 XMP I profilefor the ram for XMP II (less agressive with times, and volts…
It solved estability with the plugins like ozone or universal audio…The 1d2d.dll: the vga with long clable and adaptador doesn’t goes to the stability…changed by hdmi monitor…Then 2 diferen’t problems solved…at the moment.
Now 6 monitors running well. 4 x in the rx580 and 2 from uhd770 (integrated in th MB)
Not solved yet….Is fustrating
I trien Witsel default settings in the BIOS, using only hd770 intel integrated one monitor, and only the rx580 only one monitor….still crashes
New graphic card asus nvidia rtx5060…still crashing. BIOS in load defaults.
Nuendo 14.0.32 64bit2025.7.2 13.40.36.898.dmp (1.9 MB)
I think the relevant bits of this one are:
STACK_TEXT:
00000000`00000000 00000000`00000000 Nuendo14.exe!heap_corruption+0x0
00000000`00000000 00000000`00000000 unknown![~0s]+0x0
00000000`0014db80 00007ffb`349f538d ntdll!RtlFreeHeap+0x0
00000000`0014dc70 00007ffa`9254b3f0 iZOzone11Elements+0x0
00000000`0014dc78 00000000`00520000 unknown!unknown+0x0
00000000`0014dc80 ffffffff`00000000 unknown!unknown+0x0
00000000`0014dc88 3ff00000`00000000 unknown!unknown+0x0
00000000`0014dc90 ffffffff`ffffffff unknown!unknown+0x0
00000000`0014dc98 00000000`0014dda8 unknown!unknown+0x0
00000000`0014dca0 00007ffa`90b4b775 iZOzone11Elements+0x0
00000000`0014dca8 ffffffff`ffffffff unknown!unknown+0x0
This looks like it’s being caused by iZOzone11Elements.
I think most (if not all) of your previous crash dumps also pointed to Windows system components, but related to video. With a new video card, and the ntdll reference, this sure seems like a system-based issue in general, though the culprit in this case was Ozone11 Elements.
Have you performed a full system wipe and reinstall yet? Also, is this a user-build system? Not sure if that part has been discussed yet, but ensuring you have the latest drivers from the manufacturer for all motherboard/system components is important. Thought I’m pretty sure from the way you’ve been describing this issue you’ve already done all that.
Subject: Nuendo 14 Crashing with Dedicated GPU — Stable Only with iGPU (Tested with NVIDIA & AMD)
Dear Steinberg Support,
I’m experiencing a consistent and reproducible crash in Nuendo 14, which only occurs when the system is running a dedicated GPU. Here are the full system details and the testing steps I’ve taken:
System Configuration:
- CPU: Intel Core i9-14900K
- Motherboard: ASUS Z790-P WiFi (BIOS defaults loaded)
- RAM: 32GB DDR5 Corsair Titanium
- GPU(s) Tested:
- NVIDIA RTX 5060 (latest drivers)
- AMD RX580 (tested with Adrenalin drivers v21 and v25)
- iGPU: Intel UHD Graphics (integrated)
- Audio Interface (in Nuendo): RME Fireface 800 (ASIO)
- Audio Interface (in Windows): Digidesign Mbox 2 (legacy driver)
- Monitors: Multi-monitor setup (up to 4)
- OS: Windows 11 Pro
Issue Description & Behavior:
- Nuendo 14 crashes reliably with certain projects when any discrete GPU is active.
- Tested with both NVIDIA and AMD GPUs, using multiple driver versions.
- System voltages and temperatures are identical in both cases (iGPU vs dGPU).
- When I disable the discrete GPU (via Device Manager or physical removal) and rely solely on the integrated Intel UHD graphics, the exact same project runs smoothly and without any crashes.
This leads me to rule out:
- GPU hardware faults (3 cards tested, different vendors)
- GPU driver incompatibility (both AMD and NVIDIA)
- ASIO driver issues (Nuendo uses RME Fireface 800, not the legacy Mbox 2)
Conclusion:
The issue appears to lie in the way Nuendo 14 interacts with dedicated GPUs, perhaps related to:
- GPU acceleration or display context switching
- PCIe resource conflicts
- ASIO performance under multi-GPU/multi-monitor environments
The fact that the crashes are entirely absent with the iGPU suggests a software-level incompatibility rather than faulty hardware or overheating.
Please let me know if this is a known issue or if there are any recommended settings (in Nuendo or the OS) to force software rendering or bypass GPU acceleration. I’m happy to provide logs, system dumps, or run additional diagnostics if needed.
Thank you for your support.
Kind regards,
Jordi
Nuendo 14.0.32 64bit2025.7.2 23.16.44.063.dmp (1.7 MB)
Nuendo 14.0.32 64bit2025.7.2 16.31.06.801.dmp (2.1 MB)
Yestarday at night news, it seem that windows + Nuendo + Float windows in nuendo like ozone or fabfilters or supervision…it doesn’t matter, with realtime movement…with diferent refresh monitor, it is not stable, it seem to work, but finally crashes, may be the composicion in one monitor with float windows from windows and nuendo is not stable either. Today I return to AMD RX580 with all monitor at 60Hz. with and without superpositioning windows… I’m going to explain you if it works or not.
multifactor: it seem solved. but i’m going to wait a time. to see if really solved:
vga withadappador dp-vga…long vga cable…refresh rate different in all monitors…it seem to be the problem…xmp memory…but vga long cable difeerent refresh monitors seem to be the most significant. now 6 monitor with dp and hdmi, refresh all at 60hz…still working.
I hope it’s fixed. You’ve had a heck of a time with this!
yes… now a I have 120hz 120hz 100hz 100hz in the RX580 and 60Hz 60Hz iGPU…and working…with superposition windows…I think tha the VGA with adaptor DP doesn’t work 100% with floating plugins…well Today I have musical mix with several plugins…will see.
I’m still having crashes with d2d1.dll and another but I begin to think thats a Supervision Problem. but I don’t know…
Nuendo 14.0.32 64bit2025.7.14 17.34.30.219.dmp (1.7 MB)
Nuendo 14.0.32 64bit2025.7.14 17.30.40.824.dmp (1.9 MB)
Nuendo 14.0.32 64bit2025.7.12 20.03.59.754.dmp (1.3 MB)
Nuendo 14.0.32 64bit2025.7.12 18.01.07.047.dmp (1.3 MB)
chat gpt:
ertainly! Here’s a technical crash report summary in English based on the data you provided:
Crash Report Summary for Nuendo 14.0.32
Date: July 14, 2025
Process: Nuendo14.exe
Version: 14.0.32.342
Operating System: Windows 10 (build 26100.1, ge_release branch)
Debug Engine Version: 10.0.27871.1001
Exception Details
- Exception Code: 0xC0000005 (Access Violation)
- Exception Description: Attempt to read from invalid memory address
0xFFFFFFFFFFFFFFFF - Faulting Module: d2d1.dll
- Faulting Function: WidenLine
- Instruction Pointer: 0x7ff8bf2acafe
- Exception Offset: 0x16cafe in d2d1.dll
Context
- The crash occurred due to an invalid pointer dereference within the Direct2D rendering library (d2d1.dll) during a drawing operation (
WidenLinefunction). - The instruction attempted to read from a null or invalid memory address, resulting in an access violation.
- The stack trace indicates the failure happens inside Direct2D device context rendering code when drawing lines.
Performance & Resource Usage
- CPU Time (Analysis): 281 ms
- Elapsed Time (Analysis): 273 ms
- Memory Peak: 319 MB committed
- I/O: 1 MB read, 114 MB written
- Process Start Delay: 140 seconds after OS boot
Additional Notes
- The fault address is outside any loaded module’s address space, indicating a probable null or corrupted pointer use.
- The failure bucket classifies this as an
INVALID_POINTER_READ. - This kind of error might be related to graphical driver issues, corrupted application state, or a bug in the rendering pipeline.
Have you tried uninstalling graphics card driver in safe mode using DDU ?
That fixed it for me on my MSI Z790-A with a 4060 graphics card.
Now I decided to reinstall all the system only withs the rtx 5060 drivers…I ve tried a clean uninstall drivers cleanup amd or similar…but the same result.


