Dorico 6.1.10.6078 Crashing/Freezing - Screen Goes White and sometimes beeps

I’ve been having so many crashes with Dorico 6 right now. I’m running an RTX 4090, Noteperformer 5.1.2 and 4 Roli M’s for MIDI entry. I don’t get crashes at all on my laptop using the Rolis.

I’m thinking it may have something to do with the NVIDIA driver but not sure.
Here is a link to download diagnostics: https://drive.google.com/file/d/1Uy7uEwYdR7O9AmrX95REoAgotOViILy-/view?usp=sharing

I have an update. The crashing was making it completely unusable and I decided to try going into Nvidia control panel and just turning everything off that could be turned off. I’ve been working for about 30 minutes with no crashes but the screen will flash off on and on if I move the score around a lot.

It’s looking like this is a graphics card/driver issue. Please advise and fix soon. I really need this to work. Looks like I might have a workaround but the flashing screen gets annoying.

Hi @Tony_DeSare , if it is a graphics card/driver issue, then there is nothing that we can do about it, it is simply not in our hands.
You can try to update your driver to the latest available one and hope that that solves your problem, but other than that there is no other advice I can give, except for changing the graphics card.

Just for nostalgia’s sake: I remember the bad old days when practically every issue in Finale could be corrected just by updating video drivers. That became the standard first response from everyone on CompuServe. :zany_face:

Carry on…

I maybe have found the solution for those having a similar issue. I was still crashing even with the NVIDIA control panel stuff shut off. I turned back on the GSync and it stopped the flashing. I also turned off HDR in the app specific settings in Windows, not the NVIDIA control panel and so far no crashes. It also seems that maybe my LG 4K monitor might be involved. My theory is that it’s being cause by the HDR on the monitor interacting with Windows HDR. Time will tell.

Including this for anyone else that might have an issue. If this doesn’t end up solving the issue, I will report back.

From Gemini:

HDR (High Dynamic Range) settings, particularly in Windows and on certain Mac configurations, can cause significant issues with Dorico, ranging from video playback problems to interface rendering errors. HDR, which expands the color and brightness range, can conflict with the Standard Dynamic Range (SDR) environment in which most notation software operates, leading to display issues.

  • Video Playback Issues: HDR video files (such as those recorded on iPhones in HEVC format) can cause Dorico’s video window to not function, display a green screen, or fail to load, as the video engine may struggle to handle the metadata.

  • Screen Flicker: Users on M1 Mac Minis with 4K monitors have reported screen flickering during playback in Dorico, often appearing after the monitor wakes from sleep.

  • Washed-Out Colors: When Windows HDR is enabled, SDR applications like Dorico may appear washed out, with incorrect colors and contrast.

  • Audio Engine Failures: In some cases, external monitors (like LG HDR 4K/5K displays) can cause, or be related to, failures in connecting to the audio engine, particularly on macOS.

  • Performance Lag: Changes in the Qt application framework (used by Dorico 5) can cause input lag on certain systems, which may be exacerbated by high-resolution/HDR display settings.

Potential Solutions and Workarounds:

  • Disable Windows HDR: Turn off Windows HDR when working in Dorico to avoid washed-out colors and interface issues.

  • Convert Video Files: If video files are not working, convert them from HDR/HEVC to SDR/H.264 before importing into Dorico.

  • Adjust Monitor Settings: If using a 4K monitor, check if HDR settings can be adjusted, or disable it specifically for that display in the operating system.

  • Reopen Project: For flickering issues on Mac, closing and reopening the project may resolve the issue, as suggested by some users.

  • Disconnect External Displays: If experiencing audio engine failures, try disconnecting the external HDR display to see if it resolves the issue.

Ok, so an update. Nothing I’ve tried works. The crashes happen completely randomly. Sometimes I could be fine for a half hour. Sometimes it’s every five minutes. I’ve literally scoured the Internet and the official Steinberg forum solution said I have to replace my $2000 video card, which I can’t do because I also use it for video editing and gaming. Every other program on this computer runs 100% flawlessly.

It never crashes except for Dorico. I have two other computers that I use Dorico on (one in my recording studio and one on my travel laptop and Dorico does not crash). But my main rig won’t stop just crashing, then goes to a white screen, and then I close it, reboot and start all over again at least a few times an hour. There must be someone out there that can diagnose the issue. I have the crash report attached above but I don’t know how to interpret it.

I’m sorry it’s just so frustrating especially since I rely on being able to use Dorico for my living and to be constantly interrupted and then constantly saving after everything I write is driving me crazy. I love Steinberg. Longtime Cubase user and Dorico is an amazing program when it works.

You’ve know idea whether what Gemini says is actually true, or how relevant it is.

I would start by disabling or removing as much “non-default” stuff as possible – such as your external audio speakers; additional VST plug-ins, etc – to test whether it works ok without them. Then add them back one by one.

Hi @Tony_DeSare , could you upload a new diagnostic report, please? Thanks

Another update, I may have solved the problem. I’ve been using Dorico for a couple of hours with no crashes. I uninstalled my Oculus VR software which I noticed in the event viewer of Windows was crashing with the video driver. Time will tell but hopefully this has fixed it.

Can confirm uninstalling the Oculus Meta software stopped Dorico from crashing. The process running in the background that seems to be the problem is OVRServer. The screen now doesn’t go white and make the program crash. I’m just restating this for people with the same problem to find.