Davinci Resolve Studio Crashes Caused by nvoglv64.dll (Fatal App Exit)

Gaming and Visualization Technologies General Topics and Other SDKs Drivers - Linux, Windows, MacOS
1

Hi everyone,

I’ve been experiencing persistent crashes in DaVinci Resolve Studio 20 Beta while working on GPU-intensive projects involving Fusion effects. After analyzing the diagnostic logs and dump files, I suspect the root cause lies in the NVIDIA GPU driver (nvoglv64.dll) interacting with OpenGL. Below are the details of the issue:

System Specifications:

  • GPU: NVIDIA GeForce RTX 5070 (12GB VRAM)
  • Driver: NVIDIA Studio Driver (531.61)
  • OS: Windows 11 (22H2)
  • CPU: Intel Core i7-14700K
  • RAM: 64 GB (XMP enabled)
  • DaVinci Resolve: Version 20 Beta (20.0.0.23)
  • DirectX: Version 12

Crashes with Fatal App Exit

  • The diagnostic dump revealed that the crash is triggered by the nvoglv64.dll module, which is associated with NVIDIA OpenGL functions.
  • Specific function involved: vk_gr2608GetInstanceProcAddr
  • Exception Code: 0xc0000409 (Stack Buffer Overrun or Security Check Failure)
  • Memory Peak: 764 MB during crash

Logs Analysis

  • Cache timestamp inconsistencies were reported repeatedly in DaVinci Resolve logs. These could indicate conflicts in memory management or cache-related issues.
  • Multiple errors related to GPU memory, including: Nvidia codec insufficient memory

Stack Trace Highlights

  • Repeated function calls within nvoglv64.dll related to DrvPresentBuffers
  • OpenGL rendering or buffer validation seems to be a major factor in triggering the crash

Troubleshooting Steps Taken:

  • Updated to the latest NVIDIA Studio Driver (531.61)
  • Switched from Game Ready Drivers to Studio Drivers to prioritize creative application optimization
  • Cleared DaVinci Resolve cache files and regenerated cache manually
  • Reduced project complexity by splitting Fusion-heavy compositions into separate timelines
  • Monitored GPU resource usage via GPU-Z and HWInfo—observed memory spikes during rendering tasks

Dump Analysis: KEY_VALUES_STRING: 1
Failure.Bucket: FAIL_FAST_FATAL_APP_EXIT_c0000409_nvoglv64.dll
Failure.Exception.Code: 0xffffffffc0000409
Module: nvoglv64.dll

  • Are there known conflicts between DaVinci Resolve Studio Beta 20 and NVIDIA drivers in OpenGL-related tasks?
  • Would disabling OpenGL-specific features (if possible) within the NVIDIA Control Panel help mitigate crashes?

Thank you in advance for any insights or advice—I truly appreciate the time and effort to help me resolve this issue!

Best regards, Javier

2

Hi there @jagv98 and welcome to the NVIDIA developer forums.

Thank you for the detailed write-up! Very much appreciated.

Please check the driver version again. I am not sure the 531.61 even supported the 5070 yet. In any case, the current version is 572.83

{03C08154-A73A-4A61-AF66-A4250641B29F}
{03C08154-A73A-4A61-AF66-A4250641B29F}541×445 26.7 KB

Since We are talking about the “Beta” version of Resolve here, I do not think we have any public incompatibilities or issues to share. At this state Black Magic would contact their developer relations here at NVIDIA in case of bugs they or users encounter. So the best approach would be to let their team know about this.
And just disabling OGL features on trial&error basis will not be helpful.

Try with the newest studio driver first and see if that addresses the issue. If not, please pass this on to BM as well.

Thanks!

1 Like
3

Thank you for your previous response and guidance! I’d like to clarify an error in my initial message and provide additional details.

I am indeed using the latest Studio Driver version 572.83, but I’ve encountered a new, more critical issue while working on GPU-intensive tasks in DaVinci Resolve Studio 20 Beta. My system has rebooted twice with a Blue Screen of Death (BSOD), and each time the issue points to a conflict with DirectX and the driver dxgmms2.sys.

But I will create a new topic so it’s a different thing, for this issue my workaround was to remove the faulting fusion composition in davinci resolve, I hope they will fix this issues soon. Thanks