Photoshop/ACR June’25 update: GPU error

Jim9

Active member
Messages
88
Reaction score
24
Hi all, Photoshop and ACR was working fine, with AI denoise for raw files (24mp) taking less than 20s. This PC was setup less than 2 weeks ago and everything worked fine.

Now, after the latest June 2025 update, it seems the GPU is having error. Can still use the PC and since it doesn’t have integrated graphics, the GPU is definitely working.

Is it a driver issue? Currently using Nvidia studio driver 576.52 (May’25). The notes for the latest driver 576.80 (June’25) doesn’t mention Photoshop

Anyone having similar problems?

I’m asking on behalf of a friend who doesn’t know much about PCs so I can’t get it updated to the latest Nvidia studio driver yet. Trying to do some research before dropping by his house.

Specs:

AMD Ryzen 3600x

RTX 2070 Super

2x8gb 3000mhz RAM

Windows 11

0c1d2372dffe44e2be330525b0c9a4b7.jpg

39c354ab3fff4d9288fe08f71bf0f342.jpg
 
Last edited:
This may not help at all, but I have no difficulties.

Studio driver 576.80, RTX 4090. PS 26.8.0. ACR 17.4

If it's a driver issue, one thing to try is Display Driver Uninstaller . It wants to run in Safe mode, but I've run it from normal Windows successfully.
 
Nvidia released an update 576.80 on June 17. Restart your system after the update. I had similar issues when I was running an RTX 2080 Ti. I recently upgraded to an RTX 5070 Ti. I'm seeing a 4 to 5 times improvement in AI processing times in Photoshop and ACR.

Morris
 
Updated to the latest studio version.

Photoshop works slower than before.

Some AI features like lens blur causes it to freeze. Sometimes GPU error message appears saying GPU acceleration has been disabled.
 
Updated to the latest studio version.

Photoshop works slower than before.

Some AI features like lens blur causes it to freeze. Sometimes GPU error message appears saying GPU acceleration has been disabled.
In Photoshop /edit/preferences

Under performance restore memory to the default of 70%

Exit Photoshop and start again. If this does not correct it, close Photoshop. The rename GPU and Logs Folders to GPU-old and Logs-old. You can find them In %APPDATA%\Adobe\CameraRaw to force Camera Raw to regenerate them with updated information.

For me this spread things up dramatically and stopped eating all of my video RAM.

Good luck,

Morris
 
GPU stumbles are a chronic Adobe coding problem that has persisted since even the simple numbered versions of PS and their minimal GPU accelerated processes--ask me how I know. Adobe has always blamed the video drivers but it seems more likely due to Adobe not bothering to alpha test its software with nVidia or AMD video drivers.

Adobe's canned response has eternally been to turn off GPU acceleration if you encounter problems, which now renders LR and PS nearly useless, and is calculated to shift the blame away from the real culprit, which is Adobe.

People who have never seen this error, nVidia only slightly less often than Radeon, are either lucky or don't use Photoshop very intensively. The converter, which is very GPU dependent, in my experience is most likely to trigger the error. In my experience this error is becoming more frequent in both Windows (I use recent vintage nVidia and AMD desktop GPUs) and in X86 macOS with an AMD GPU. I haven't seen any significant difference between studio and game-ready drivers, perhaps I am particularly unlucky.

No idea if ARM Apple users are seeing it more, but I will probably shift to an Apple laptop soon so I'll find out up close and personal.

On one side there has always been Microsoft/Apple/nVidia/AMD and on the other side Adobe, yet Adobe has forever said its not their fault or its user error. It has literally been decades.

Rebooting the programs, occasionally the entire machine, should fix the problem until the inevitable next time. Uninstall, reboot and reinstall video drivers if you're desperate.
 
GPU stumbles are a chronic Adobe coding problem that has persisted since even the simple numbered versions of PS and their minimal GPU accelerated processes--ask me how I know. Adobe has always blamed the video drivers but it seems more likely due to Adobe not bothering to alpha test its software with nVidia or AMD video drivers.

Adobe's canned response has eternally been to turn off GPU acceleration if you encounter problems, which now renders LR and PS nearly useless, and is calculated to shift the blame away from the real culprit, which is Adobe.

People who have never seen this error, nVidia only slightly less often than Radeon, are either lucky or don't use Photoshop very intensively. The converter, which is very GPU dependent, in my experience is most likely to trigger the error. In my experience this error is becoming more frequent in both Windows (I use recent vintage nVidia and AMD desktop GPUs) and in X86 macOS with an AMD GPU. I haven't seen any significant difference between studio and game-ready drivers, perhaps I am particularly unlucky.

No idea if ARM Apple users are seeing it more, but I will probably shift to an Apple laptop soon so I'll find out up close and personal.

On one side there has always been Microsoft/Apple/nVidia/AMD and on the other side Adobe, yet Adobe has forever said its not their fault or its user error. It has literally been decades.

Rebooting the programs, occasionally the entire machine, should fix the problem until the inevitable next time. Uninstall, reboot and reinstall video drivers if you're desperate.
About a year ago I had a support call with Adobe. They identified a problem with the Nvidia driver, told me what version to go back to and that mostly resolved the issue. They also worked with Nvidia and Adobe informed me when Nvidia released the corrected driver.

Adobe too ownership of my problem, gave me a workaround and had Nvidia address the issue which helps everyone.

Morris
 

Keyboard shortcuts

Back
Top