P: Hundreds of Direct2D Drawbot error. HRESULT: -2005270494

[neilgdabc]

I'm getting hundreds of these errors, and every time they happen the UI freezes for a second or two.

Not entirely sure what build I'm running but it's 25.0. Here is the extremely useful about box:

Any ideas? Thanks!

[Chrisanthi Pel]

hello everyone! 

i updated my premiere to the latest version last week, and this morning, while i am trying to edit a very simple 2 multicam project, i get delay on conforming, on essential sound filter and on top of that, i just got that error message from the events that I never saw before! 

any ideas?

[Christiaan1]

During editing: 

Many interface items of premiere pro not visible anymore.
Many panels have no text.

I have 128 Gb of Ram and 11Gb of video ram. (GTX3080)

[IanB_360]

Hi @Christiaan1 

Welcome to the Premiere Pro forums! We are glad to see you here. We need a few more details to try to help with the issue. Please see, How do I write a bug report ?

Thanks for submitting your bug report. I hope we can help you soon. Sorry for the frustration!

Thanks,

Ian

[Claire H.]

Updating status.

[jamieclarke]

Hi @Christiaan1 - Can you try and navigate to Preferences under General and make sure the checkbox is not selected under "GPU accelerated UI rendering".  Then restart your project.  We are currently not getting reports of this issue in version 25.1

[jamieclarke]

Hi @Chrisanthi Pel - Can you try and navigate to Preferences under General and make sure the checkbox is not selected under "GPU accelerated UI rendering".  Then restart your project.  We are currently not getting reports of this issue in version 25.1

[Aaronz0r]

I started getting this today after updating to version 25.0.0, Build 61
64gb Ram, 24gb VRam
Never got it prior to this update. 

[Ann Bens]

@jamieclarke We are currently not getting reports of this issue in version 25.1

@jamieclarke I recently had one.

[jamieclarke]

Hi @neilgdabc - Thanks for submitting your bug report. We need a few more details to try to help with the

issue. Please see, How do I write a bug report?

Other users have reported this issue as well, can you try and navigate to Preferences under General and make sure the checkbox is not selected under "GPU accelerated UI rendering".  Then restart your project.  We are currently not getting reports of this issue in version 25.1

Sorry for the frustration.

[neilgdabc]

@jamieclarkeThanks for the reply! In 25.1, half the UI just doesn't render - blank boxes everywhere! I've changed that setting, and it seems to have fixed the issue. Although obviously I don't have GPU accelerated UI any more.

And the 'about' box is still empty.

[neilgdabc]

@jamieclarke Actually, I am still getting them in 25.1

[Chrisanthi Pel]

guys, I don't know what is happening, but the worst part is that after I started getting those event messages, Generating peaks is taking forever!! The other day, I was waiting for almost 3,5 hours to generate peaks for 2cam podcast of 1h length. And on top of that, when I added Podcast voice effect from Essential Sound, I waited another 1,5 hours and still nothing! So I ended up editing the podcast at Premiere Pro 24 version and in everything was smooth. Generating Peaks and Essential sound almost in no time. I wasted all my day for nothing. I should stay at Premiere Pro 24 from the begining. 

[Max291794530wtx]

Exact same issue for me. This has been going on with my system for months at this point - should also be noted that the error used to read "Premiere Pro is running low on system memory. Please save your project and proceed with caution." on earlier versions (every iteration of 24). But now since I upgraded to version 25 I get the drawbot error.

[jamieclarke]

Hi @neilgdabc @Chrisanthi Pel @Max291794530wtx - Can you try installing Premiere Pro beta version 25.2.0 build 3 or higher and let us know if it helps your issue?

[Max291794530wtx]

I can't even open my previous projects in Beta 25.2 - it keeps crashing once the project loads.

[jamieclarke]

Hi @neilgdabc - Any updates?

Can you provide the exact steps that lead to this error on your system?  We haven’t been able to reproduce it on our end. If anyone else is experiencing this error, please share the steps to reproduce it, as this will help us investigate further

[Max291794530wtx]

Hi Jamie,

I'm not 100% sure what leads to the Drawbot error, but it seems it becomes more common as the complexity of the Premiere project increases.

I'm pretty fast when it comes to whipping out shortcuts on my keyboard, so if I make edits too fast and Premiere is unable to keep up, sometimes it can trigger the error. My guess is there's a miscommunication between the windows display drivers and Premiere during that time.

[jamieclarke]

Hi @Max291794530wtx - Can you open Task manager and find the details pane in the Column headers, right click "Select Columns" "GDI Objects" is one of the options. Monitoring from there allows for recognizing a growing leak much earlier than when something blows up.  any steps you can reproduce to let us know when the objects start to climb would be very helpful.

[Max291794530wtx]

Good call - curiously, I received the error again right at around 10,000 GDI Objects on Premiere. Technically the number reads 9998, but I observed it reaching 10,000 before going back down. Any time I try to click on something it temporarily brings it back up before going back down to 9998. Strange.

I should also mention I just downloaded the newest set of nvidia studio drivers today, but the error has been consistent with many versions of the same drivers before.

[jamieclarke]

Hi @Max291794530wtx - We have made some updates around this issue in beta, can you try downloading 25.2 and let us know if you are still having issues?

[Max291794530wtx]

Slight update - I see that the default value for GDI Object limit on Windows is actually 10,000 - this may be the issue. I went into the registry and changed it to a higher value and restarted. Let's see if that does the trick.

[Max291794530wtx]

Hi Jamie,

I was able to successfully replicate the error! I changed the 'GDIProcessHandleQuota' value in the Windows Registry to 1000 just to see what would happen, and wouldn't you know it the error popped up like normal as the GDI Objects passed 1000.

If you want to replicate the error too, the pathway is HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows --> GDIProcessHandleQuota

[jamieclarke]

Hi @FilmGuyMax - We have made some updates around this issue in beta, can you try downloading 25.2 and let us know if you are still having issues?

[Dnl13]

Same issue here!
After some time editing, the UI freezes, and on hover, UI elements begin to disappear.
Additionally, the error message "Direct2D Drawbot error. HRESULT" keeps spamming, making the situation even worse.
Restarting Premiere is the only way to keep working.

Could we please get a proper hotfix for this?
Bugs like this should ideally be addressed through targeted hotfixes for the stable release, instead of pushing users to switch to a beta branch.
Beta versions often introduce unfinished features or new bugs, which can make production work even more challenging.

This issue is severely impacting my workflow and productivity. Any manual workaround or an update addressing this bug would be highly appreciated.
Build: 25.0.0. Build 61

Specs: 32GB RAM, 8GB VRAM (RTX 2070 Super), Intel CPU (10 cores/20 threads).
Currently, I can't work for more than an hour without encountering this error and needing to restart Premiere.

[Max291794530wtx]

@Dnl13 let me just say first off, you're my hero for saying all that stuff about the Beta version. Seriously, that shouldn't be the answer.

Second, I think I may have found a workaround for you - the issue revolves around GDI Objects. Windows usually caps them at 10,000 for a single application, and for some reason these new versions of Premiere use up that 10,000 pretty fast (I used to get the Drawbot error within an hour, same as you).

Luckily, you can change this. Go to the search bar in windows and type Registry Editor. Then from there go to HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion \ Windows (make sure to click on Windows to highlight it blue)

Then double click on GDIProcessHandleQuota. Change the 'Base' from Hexadecimal to Decimal. If the number you see is 10,000 change it to a higher number. Apparently windows can handle about 65,000 GDI Objects with no issue, so I set my value to 65,000. Then restart your computer.

Haven't seen that blasted error since. I can work 8-10 hour days without the error popping up once. Hope this helps.