B580-Stability Issues with DaVinci Resolve (Missing OpenGL Entry Points & CL_OUT_OF_RESOURCES Error)

[iamdavid]

Hello Intel Support Team and Community,
I am experiencing significant stability issues when using DaVinci Resolve with my Intel Arc B580 graphics card. These issues persist even after extensive troubleshooting, including a full Windows 11 reset, BIOS reset to defaults (which disables ASPM by default on my motherboard), and running with no system overclocks.
System Configuration:


GPU:Intel Arc B580

CPU:Intel Core i7-14700KF

Motherboard: Gigabyte Z790 AORUS ELITE AX (BIOS Version: FK -Latest available as of 6/6/25)

RAM:64GB DDR5-6000 (Crucial Pro UDIMM Kit, CT2K32G60C48U5) - Currently running at JEDEC default speeds after BIOS reset.

Operating System:Windows 11 Home (Build 26100) - Fresh installation.

Intel Graphics Driver Version:32.0.101.6876 (Latest official WHQL downloaded from Intel's website after Windows reset)

DaVinci Resolve Version Tested:


Initially tested with DaVinci Resolve 19.1.4.0011

After Windows reset, tested with DaVinci Resolve 20.0.0.0049 (Latest official public release version)
Problem Description:
DaVinci Resolve frequently encounters errors and becomes unstable, particularly during video playback, editing, or rendering of H.264 and HEVC footage. This often manifests as freezing, playback stuttering severely, visual glitches, and eventually leading to an unrecoverable state requiring the application to be force-closed.
When using DaVinci Resolve, especially with H.264/HEVC files and during standard editing/color grading tasks, I encounter two main categories of critical errors:


Missing OpenGL 4.5 Entry Points (Persistent across driver versions and Resolve versions):
The resolve_graphics_log.txt consistently shows the following errors immediately after Resolve initializes its graphics context:


[Error] missing 4.5 entry point "glGetnTexImage"

[Error] missing 4.5 entry point "glGetnUniformdv"
This indicates an incomplete OpenGL 4.5 implementation in the driver that DaVinci Resolve relies on. These errors occur during the graphics initialization phase and indicate that the driver, despite reporting OpenGL 4.5 support, is failing to provide necessary standard functions within that API expected by Resolve's OpenGL backend.

OpenCL "Out of Resources" Errors (Observed with driver 32.0.101.6876 and Resolve 20):
During longer sessions or more intensive operations, DaVinci Resolve's debug log (ResolveDebug.txt) fills with repeated errors:


DVIP Exception: OpenCL error - API: OpenCL - API Error Code: CL_OUT_OF_RESOURCES (-5)
This indicates a failure in OpenCL operations, likely due to the GPU running out of resources or encountering allocation issues, potentially triggered by activity within Resolve. This points to instability in the driver's OpenCL implementation or resource management under load.


Followed by an "Urgent message: The GPU failed to perform image processing because of an error.||Error Code: -5."

And often associated errors like:


Pinned allocation clEnqueueMapBuffer failed: CL_OUT_OF_RESOURCES

MainPlayer: Failed to get texture, HandleXXXX is unknown.
These errors suggest a severe problem with OpenCL resource management (VRAM or other GPU memory structures) by the driver when used by Resolve.


Follow-up errors often seen after the CL_OUT_OF_RESOURCES errors include:


[UI.GLInterop | ERROR| ... | MainPlayer: Failed to get texture, HandleXXXX is unknown.]
[UI | ERROR| ... | Invalid handle, and failed to get previous texture.]
These are symptomatic of the display/UI system failing to get expected data from the GPU after the OpenCL processing step fails.

Windows Error Reporting (from DxDiag):
My DxDiag report shows multiple LiveKernelEvent errors with Bug Check Code 141 (P1 parameter), indicating repeated graphics driver timeouts or failures. Additionally, there are APPCRASH events for Resolve.exe faulting in ntdll.dll with exception code c0000005 (Access Violation), which often occur subsequent to the driver failures. This system-level error reporting strongly suggests an underlying issue with the Intel graphics driver stability when used with DaVinci Resolve.

Troubleshooting Steps Taken:


Full Windows 11 reset and reinstallation. Used DDU to clean traces of driver before installation.

Reset motherboard BIOS to default settings (ASPM defaults to Disabled on my board).

Ensured no CPU or RAM overclocking (XMP disabled, RAM at JEDEC speeds).

Installed the latest official Intel Arc graphics driver (32.0.101.6876) after the Windows reset.

Tested multiple versions of DaVinci Resolve (currently on 20.0.0.0049, previously 19.1.4.x).

Confirmed DaVinci Resolve preferences are set to use OpenCL for GPU processing, and the Intel Arc B580 is selected.

run (as admin) sfc /scannow, dism /online /cleanup-image /scanhealth, checkhealth, restorehealth - all return no issues.

Virus scan with Windows Defender

Completed Windows Update
Impact:
These issues make DaVinci Resolve highly unstable and unusable for any serious work on my Intel Arc B580 system. Crashes are frequent, or the application becomes unresponsive due to GPU processing failures. The combination of persistent "missing OpenGL entry point" errors and repeated "OpenCL_OUT_OF_RESOURCES" errors, even on a freshly installed Windows system with default hardware settings and the latest drivers/Resolve version, strongly suggests a fundamental issue with the Intel graphics driver's stability and/or API compliance with GPU utilization (both OpenGL for the UI/viewer and OpenCL for compute).
Request:
Could the Intel graphics driver team please investigate these "missing OpenGL 4.5 entry point" errors and the "CL_OUT_OF_RESOURCES" errors when using DaVinci Resolve with the Arc B580? The persistence of the OpenGL API issue across multiple driver versions (I previously had 32.0.101.6874 with the same OpenGL errors) is particularly concerning.
Log Files:
Included are:


resolve_graphics_log.txt (showing the missing OpenGL entry points)

ResolveDebug_2.txt (showing the CL_OUT_OF_RESOURCES errors and other runtime issues)

DxDiag report

Intel SSU report

I can provide the following log files upon request or if there's a preferred method for submission:


DaVinci Resolve Diagnostic Log Bundle (generated via Help - Create Diagnostics Log on Desktop) SIZE IS 1 GB
Please let me know what further information would be helpful.
Thank you for your time and assistance.
Sincerely,

Iamdavid

[iamdavid]

---

@RandyT_Intel wrote:

Hi @iamdavid,

I'm still actively investigating the issue on our end. In the meantime, we’d like to clarify your RMA request. Could you please confirm whether you're using an Intel Branded Card (IBC) or an OEM-manufactured Intel® Arc™ GPU?

• If it’s an Intel Branded Card, we can assist you directly with the warranty process.
• If it’s an OEM card, you’ll need to contact the manufacturer (OEM) for warranty support.

---

Hi @RandyT_Intel ,

The card is made by Gunnir.  Their warranty policy has exclusions and one of them is "Other failures and damages not caused by design, manufacturing, quality and other problems of the product itself."  I think I would have a hard time initiating a return by citing faulty behavior of the Intel driver, as that may be an exclusion and is certainly beyond their control.  If you believe this problem may be specific to the particular manufacturer I would need some evidence of that, and all of the evidence I have reviewed points to the driver.

Thank you

[RandyT_Intel]

Hi @iamdavid @Danyyy3l ,

Thank you for the updates and for providing guidance on how to reproduce the issue. I will proceed with more testing and will report back once my analysis is complete. Thank you for your patience.

Regards,

Randy T.

Intel Customer Support Technician

[Danyyy3l]

Update:
The "versions" way of crashing seems to NOT be only an arc b580 issue.
Im not an expert, i don't know if this means only davinci-resolve can do something about it, or gpu drivers can aswell etc, but here's what they said:

[iamdavid]

Hi @Danyyy3l 

Thank you for providing that video.  That is similar to what I see. There is no specific set of steps that are guaranteed to reproduce the error, but it will eventually happen.  I agree with the Black Magic assessment that it is an OpenGL/OpenGL interop issue.   The driver,  reports OpenGL 4.5 compliance, but, doesn't actually meet that compliance within that API expected by Resolve's OpenGL backend. That is what the logs I submitted point to, e.g.:

(UI.GLInterop | ERROR| ... | MainPlayer: Failed to get texture HandleXXXX is unknown

 DVIP Exception: OpenCL error - API: OpenCL - API Error Code: CL_OUT_OF_RESOURCES (-5)
[UI | ERROR| ... | Invalid handle, and failed to get previous texture],

etc.  

These, combined with the OpenGL entry point errors on startup and "OpenCL_OUT_OF_RESOURCES" errors are symptomatic of the display/UI system failing to get expected data from the GPU after the OpenCL processing step fails.  It fails (or times out, which is why you don't see the app crash every time, it just freezes) from user interaction within the program, usually after some editing.

Check your dxdiag report for the TDR errors (LiveKernelEvent 141 entry). That is when the GPU stops responding and Windows tries to reset the driver.  This suggests the driver isn't using the right language for the Windows kernel or core system libraries, not an application (Davinci Resolve) error.

[RandyT_Intel]

Hi @iamdavid,

I’ve sent you a private message, could you please check on your end and confirm if you received it?

Regards,

Randy T.

Intel Customer Support Technician

[Danyyy3l]

Any updates on this issue?

[RandyT_Intel]

@Danyyy3l @iamdavid I’ve sent you a private message regarding the status of your request.

[Danyyy3l]

I haven't received any private messages.

Can you send again?

[RandyT_Intel]

Hi @Danyyy3l,

The recent post was intended for @iamdavid , apologies for any confusion. I sent the final disposition to him, as I needed to further investigate the issue. It appears the problem is isolated to OpenCL.

Regards,

Randy T.

Intel Customer Support Technician

[Danyyy3l]

Okay, if anything is needed let me know. 

(Also I updated to the latest drivers as of today, but from what I can tell there hasn't been any improvements to this, I still have tons of freezes/slowdowns/crashes)

[Danyyy3l]

Any updates? It's been way too long, I really can't edit like this for any longer, even tho I try my hardest to try to avoid crashes it's just impossible to completely avoid.

@iamdavid  @RandyT_Intel  Was the return of the card possible? Is it possible for me to do it? Mine is the "ASROCK Intel Arc B580 Challenger 12GB OC"

[iamdavid]

Until I initially contacted me and offered to let me return the card to them because of the driver issue but then they changed their mind and told me I need to send it back to the store where I bought it, newegg, which has a 30-day return policy, and Newegg told me to send it back to the manufacturer who is Gunnir.