Skip to main content
R
radu_3511
Participant
August 18, 2025
Question

Several Camera Raw Issues on AMD Radeon 890M, Windows 11 24H2

  • August 18, 2025
  • 2 replies
  • 605 views

Hello!

I'm encountering some issues while using the Camera Raw Filter in Photoshop. At first it seemed to happen while hovering over the presets (preview), but then it also occurred while adjusting some general sliders or just switching between some masks. The interface becomes unresponsive and/or visually "scrambled", with overlapping or misaligned sections, and in some sessions. Usually the filter freezes entirely. The following error types appeared in the logs (I'll provide further if you let me know what else is needed, it has a good repro rate):

*** Error: Unexpected re-entrancy in RedrawMonitor -- skipping ***
*** Error: Unexpected re-entrancy in RedrawMonitor -- skipping ***
[...repeats]

 

*** Error: GetCorrectionValues - Out of range group index ***
*** Error: GetCorrectionValues - Out of range group index ***

I had the same workflow on an older laptop (7+ years old) with far more modest specs, and surprisingly, the Camera Raw Filter performed better — with no freezes or redraw errors. This leads me to believe the issue is not due to hardware limitations, but possibly a compatibility issue with the GPU or recent software updates. It might also be a bug introduced in a recent Camera Raw or Photoshop version?


My System Specs:

  • Photoshop version & Camera Raw version: latest release (as of today)
  • OS: Windows 11 Pro 24H2, latest updates
  • GPU: AMD Radeon 890M
  • GPU Driver version: 32.0.13022.3006 (the latest on the laptop's vendor site; and that's true for all the drivers)
  • RAM/CPU: 32 GB RAM, AMD Ryzen AI 9 HX 370


Any guidance or workaround would be appreciated. Please let me know if I can provide further diagnostics or test results.


Thanks,
Alexandra

2 replies

M
MHM0D4D
Participant
September 23, 2025

I Have the same problem.

R
radu_3511Author
Participant
November 16, 2025

I still have it too. I hoped that the latest updates will fix something, but no.

D Fosse
Community Expert
D FosseCommunity Expert
Community Expert
November 16, 2025

@radu_3511  @MHM0D4D 

Is this a dual graphics configuration? (most laptops are). In that case you may need to disable the integrated GPU as described here (scroll down):

https://helpx.adobe.com/camera-raw/kb/acr-gpu-faq.html 

 

Dual graphics is a known potential conflict. Unfortunately, there is no way for ACR or Photoshop to control which GPU is being called. That is entirely at the mercy of how the laptop manufacturer has configured the operating system and the two GPU drivers. 

 

BrettN
Community Manager
BrettNCommunity Manager
Community Manager
August 18, 2025

If the issue is caused by a conflict with the video card, the first thing you'll want to do is disable it's use in Camera Raw. You can do this by going to the Camera Raw Preferences (Win: Edit > Preferences > Camera Raw, Mac: Photoshop > Settings > Camera Raw), selecting the Performance section, changing Use Graphics Processor to Custom, and unchecking "Use GPU for image processing." See if that corrects the behavior. 

You can similarly disable GPU usage in the rest of Photoshop by going to its Performance preferences and unchecking "Use Graphics Processor"

CMass
Community Manager
CMassCommunity Manager
Community Manager
August 18, 2025

Hey @radu_3511, 

I'm moving your post to discussions for now. If we find a bug, we'll move it back with all the details needed to reproduce the issue. Thank you! 


^CM

R
radu_3511Author
Participant
August 19, 2025

Thanks, I'll try the next session with with the GPU disabled and will get back with updates. But I’d really appreciate a more long-term solution - this isn't the first mention of that GPU & Ps (similar) issues. Could you clarify whether this is something Adobe is aware of/actively working to find the bug, or if it's related to current AMD driver compatibility? If it's the latter, should I be directing this concern to AMD for potential driver updates? I’d really prefer not to disable a hardware resource permanently just because, and would like to understand what steps (if any) are being taken to address this issue — either on Adobe’s side or in collaboration with AMD. As I already mentioned, if you need some product/system logs or run some scenarios, I'll provide these to help debugging.
Thanks!

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices