Camera Raw GPU errors: “out-of-memory” and “unrecoverable” — how to fix? (RTX 5070)

[thebestpic]

Camera Raw GPU errors: “out-of-memory” and “unrecoverable” — how to fix? (RTX 5070 | Photoshop 26.11 | ACR 17.5.1 | Bridge 15.1.2.737)

Hi everyone,

When I launch Camera Raw from either Adobe Bridge or Photoshop, I often get one of these two errors:

1. “The graphics processor has encountered an out-of-memory error. Due to a run-time error, GPU acceleration has been reverted to Limited for the remainder of the session.”

2. “The graphics processor has encountered an unrecoverable error. Due to a run-time error, GPU acceleration has been disabled for the remainder of the session.”

Sometimes I get only one, sometimes both in sequence.

My setup:

• GPU: NVIDIA RTX 5070 (Studio Driver ver. 32.0.15.8157 )

• Photoshop Version: 26.11

• Adobe Camera Raw Version: 17.5.1

• Adobe Bridge Version: 15.1.2.737

• OS: Edition Windows 11 Pro
  Version 25H2
  Installed on ‎18-‎10-‎2025
  OS build 26200.6901
  Experience Windows Feature Experience Pack 1000.26100.253.0

I’ve already tried updating GPU drivers, adjusting GPU preferences in both Camera Raw and Photoshop, and confirming that GPU acceleration is correctly enabled. The issue still happens intermittently.

Has anyone encountered this or found a stable configuration that works with this setup? Any advice or confirmed solutions would be greatly appreciated!

[Kevin Stohlmeyer · Accepted solution]

hi @thebestpic try resettings your Camera Raw prefs: 

Hold down the Ctrl key (Win) or Cmd key (Mac) while opening Photoshop/Settings/Camera Raw... and then click "Yes" when prompted to delete them.

[thebestpic]

Hi Kevin,

Thanks for your suggestion. I tried the Ctrl + Win shortcut, but it didn’t seem to trigger the reset. However, using Alt + Shift on launch worked correctly and reset the preferences.

I also noticed that Camera Raw disables GPU acceleration only when presets are being toggled ...otherwise, GPU acceleration stays active.

Would you like me to share the logs or any diagnostic reports to help further with the issue?

Thanks again for your time and help!

So, as of now the issue not sorted yet.

[thebestpic]

Sorry my bad..holding the ctrl key didn't work.