Photoshop: Solution for amd firepro driver 15.201.2401.0

  • 1
  • Problem
  • Updated 2 years ago
  • Solved
  • (Edited)
I found a solution for amd firepro driver 15.201.2401.0 not recognized by photoshop

if anyone like me installed the 15.201.2401.0 driver, opened photoshop and notice that photoshop is not able to recognize it's firepro driver
the problem it's in the name of the device that amd decided to change
if you'll look at the device manager in windows
you'll see that you graphic card calls AMD Firepro XXXX (FireGL)
i changed back to the old driver that photohsop does recognize
and it worked. so i install back the 15.201.2401.0 driver
open the regedit
searched for my card, in my case W7100
and every time that it was "AMD Firepro W7100 (FireGL)"
I changed it to "AMD Firepro W7100"
after i searched all the registration i logedout of windows,
reboot, and then the problem solved!

hope it'll help someone
sorry for my english=]
Photo of yaron tzarfati

yaron tzarfati

  • 2 Posts
  • 0 Reply Likes

Posted 3 years ago

  • 1
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 813 Reply Likes
Have you contacted AMD about this issue? It sounds like they may need some driver cleanup...

And thanks for letting us know what you found!
Photo of Reto Battaglia

Reto Battaglia

  • 7 Posts
  • 2 Reply Likes
This did not work in my case (W8100). I still doubt that it is a driver problem, because all other CC apps recognize the card correctly (Lightroom, Premiere Pro, AfterEffects, Illustrator). Only PhotoShop (and Speedgrade) do not see the GPU since the latest CC update.

Comes to it that ALL Adobe apps worked before the latest CC update, be it with the older AMD driver (15.20.1045) or with the newest one (15.201.2401). Only since the CC update PS and Speedgrade don't see the GPU anymore, neither with older nor with the newest AMD driver.

Therefore it looks more like a bug in the Adobe apps to me than being a driver issue.

Adobe should work this out fast, if necessary together with AMD.
Photo of MrBoulderLover

MrBoulderLover

  • 2 Posts
  • 0 Reply Likes
I have same problem with my W8100
(driver 15.201.2401-151104a-296716C-Retail_End_User, Win 10 up to date, i7 5930k, Asus X-99-a/USB 3.1, 32GB DRR4 2666 QC Corsair)

Launching sniffer.exe (PS gl info tracker) I see no track of this workaround "(FireGL V)" supposed mistaken label :

GLRenderer is correctly listed as "AMD FirePro W8100"
GLMemoryMB is not correct with 0 ... the mistake should come from here : bad test or bad answer from GC GL driver
CLMemoryMB is correct with 8192 (8GB for OpenCL at least)

in AMD registry parts Hardwareinformation.memorysize and Hardwareinformation.qwmemorysize are not null. I didn't find any field related to memory elsewhere.

You could try bypassing mistaken value on PS side with 8192 if FirePro (w7100/w8100) & 0MB GLMemory answer detected.

However I'm surprised that after 2 PS CC updates there's still no fix for handling pro-grade devices issue (that ruins 10 bits display chain support)...

You can't miss this error if software is launched with such device and you open any project... so correct testing process can't miss it and it has been reported also.

I won't give workaround a try, knowing Reto's comment... and the values up.

Is there any communication from Adobe or AMD about this issue (or between AMD & Adobe ^^) ? I've searched but found nothing.

I am patient but it begins to be truely annoying not seeing anything moving...
This kind of matter is truely efficient turning thousands euros pro hardware (GC + Display) into garbage one ^^

I wish PS and/or AMD will act very quickly now.

Merry XMas & happy new year all.
Photo of MrBoulderLover

MrBoulderLover

  • 2 Posts
  • 0 Reply Likes
I have reported this on amd forum also :

https://community.amd.com/thread/193896

Feel free to comment on the amd subject too.
Photo of JeanYves Pennanguer

JeanYves Pennanguer

  • 1 Post
  • 0 Reply Likes
I got the same problem with a Firepro W2100. It has been fixed with the reinstallation of the preview driver, version 15.200.1062.1004
Photo of Matthieu Foulet

Matthieu Foulet

  • 4 Posts
  • 1 Reply Like
That's great, but where do you find these old drivers?
Photo of Reto Battaglia

Reto Battaglia

  • 7 Posts
  • 2 Reply Likes
First uninstall all AMD-/Firepro-drivers and software. Then run Windows update. It will install the older version 15.200.1062.1004 which is fine.
Photo of Matthieu Foulet

Matthieu Foulet

  • 4 Posts
  • 1 Reply Like
Thanks, I did this, but got errors from atiumdva.dll,
and the W7100 was still not recognized under photoshop.

Had to go back to 15.201.2401.0 to get rid of the error.
Photo of Alberto Bacchin

Alberto Bacchin

  • 1 Post
  • 0 Reply Likes
I have the W4100, I checked the register, it seems all ok, the name I can see is AMD Firepro W4100.

But for examples, when I checked in AMD control center I found the values AMD FirePro W4100 (FireGL V)
Photo of Bob Yourmom

Bob Yourmom

  • 10 Posts
  • 0 Reply Likes
I'm trying to do the windows update method after I remove the newest driver.  I'll update to see what happens.

GPU: Firepro W8100
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 813 Reply Likes
We are working with the GPU vendors and OS vendors. But the problems just aren't that simple to solve, and cannot be solved by Adobe alone.
Photo of Reto Battaglia

Reto Battaglia

  • 7 Posts
  • 2 Reply Likes
Chris Chambers, if you read my previous posts more carefully you will see that they are not about the 10 bit problem at all... And yes, since I use the previous driver version 15.20.1062.1004 everything works fine.
(Edited)
Photo of Douglas Dick

Douglas Dick

  • 2 Posts
  • 0 Reply Likes
Hi, I'm buying a new PC, and was considering the W7100. These posts are a bit concerning to me, as I use Photoshop CC daily. I'm not as computer savvy as some of the other commenters. However, I'm wondering if this issue has been resolved? the posts seem to stop about 1 month ago, so I'm thinking maybe it was? I need a new computer and the W7100 specs look good enough, but I don't want to buy a problem. Thank you. 
Photo of Chris Chambers

Chris Chambers

  • 5 Posts
  • 0 Reply Likes
Douglas, no the issue has not been resolved.  Not even with PS CC 2017 that was recently released.  And as I noted in another post, all the evidence I see points to the problem(s) being in PS and not in the AMD drivers.
Photo of olivier guillemain

olivier guillemain

  • 1 Post
  • 0 Reply Likes
Same problem also for me (W4800)
I can find a previous driver version for PS but I have issue with Premiere and when I find a good version for Premiere it sucks with PS. It's an Adobe issue because all is perfect with GIMP, VLC, Handbrake  and my other GPU using software.