[SOLVED] Photoshop and Affinity photo crash on opening RAW images

Jan 17, 2020
12
1
15
I have a fresh build and have a problem with Photoshop 2020 and Affinity Photo. They both crash when I open RAW photos. I get often BSOD (with pretty much different error message every time) and Windows 10 automatically restarts. I first thought the problem was Photoshop related and installed Affinity Photo in hope to get around it. No such luck. Affinity Photo crashes too. Any solutions? In Photoshop Preferences -> Performance I removed the tick from Use Graphics Processor. To no avail. I should add that in the first few days of using the new computer when I had only Photoshop it worked good with RAW. Maybe it is related to something I installed down the line, like the Gigabyte App Center and some of the apps in it (EasyTUne, SIV)?

Hardware:
Aorus Ultra X570
Ryzen 7 3800x
PowerColor Radeon RX 5700 XT Red Dragon
TridentZ neo F4-3600C16D-16GTZNEC
Adata Gammix S11 Pro 1tb
 
Last edited:
It's a know issue with some AMD GPU drivers.
Disable Graphics Processor for RAW photos.
Open Adobe Photoshop.
Click Edit>Preferences >Camera RAW...
Click Performance and switch Use Graphics Processor to Off.
Close Photoshop and re open it.

It work fine with older AMD GPUs (e.g. Radeon RX 580 /550)
 
Last edited:
Sorry, I didn't realize replies would come so fast, was adding some more info in my question. Please look again to see what I have added. The Graphics Processor Off solution doesn't work. USAFRet, could you be more specific about the drive problem?
 
Haven't run diagnostics. I have Adata 1tb drive. How should I go about running diagnostics? I am not well versed with computer world, doing this build has been quite a challenge. All other applications run fine, such as the game Wolfenstein New Colossus.
 
Haven't run diagnostics. I have Adata 1tb drive. How should I go about running diagnostics? I am not well versed with computer world, doing this build has been quite a challenge. All other applications run fine, such as the game Wolfenstein New Colossus.
If everything else runs OK, then it might not be the drive.
But see what diagnostic tool ADATA has, and see what it say.s
 
I haven't opened all possible software. But I run diagnostics on the Adata drive with Adata tool and Windows tool and all is fine. I have a little problem with rapidly fluctuating processor mhz, though, it varies from about 3200 to 4600 with the temp and fan speed following these fluctuations. But I have managed to tame this behaviour by clicking in the Gigabyte EasyTune app SmartBoost window the OC icon. This settles the mhz steady just under 3800. Feels kinda strange that OC button steadies it. Then I can click it back to Default and it is stays the same. I have to do this operation every time I start computer to rein in the fluctuating processor. Well, it probably is not related to the RAW photo issue.
 
Sorry, I didn't realize replies would come so fast, was adding some more info in my question. Please look again to see what I have added. The Graphics Processor Off solution doesn't work. USAFRet, could you be more specific about the drive problem?
You did not mention on your post turning the Graphics Processor Off on both settings:
Edit>Preferences >Performance
&
Edit>Preferences >Camera RAW... >Performance
 
You did not mention on your post turning the Graphics Processor Off on both settings:
Edit>Preferences >Performance
&
Edit>Preferences >Camera RAW... >Performance
Oh, sorry about the oversight. I tried now turning it off also from the Camera Raw and got BSOD on opening RAW image.
 
Ok, USAFRet, your suggestion worked. Gigabyte EasyTune and EasyTuneEngineServive seem to have been the source of evil. After removing them, both Photoshop and Affinity Photo open RAW images without causing BSOD. But now as the EasyTune is not there, I got the problem of fluctuating processor speed and, as a consequence, very annoying revving fan. According to HWiNFO, the cores' max speeds are a little over 4500 MHz, min speeds 3100 MHz, the average around 3900-4000 MHz. This fluctuation is happening when system is on idle. Should a new thread be opened on the appropriate forum category for this?
 
Last edited: