Photoshop: Solution for amd firepro driver 15.201.2401.0

  • 1
  • Problem
  • Updated 3 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 4 years ago

  • 1
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 845 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 Bob Yourmom

Bob Yourmom

  • 10 Posts
  • 0 Reply Likes
WORKED.  I used the AMD driver uninstall- mini-program to wipe all files and folders of my driver.

...then I went to UPDATE & SECURITY under the Settings window and browsed for new updates.  It installed the driver that was necessary to properly use the GPU features in Photoshop CC 2015

the driver it installed is the: 15.20.1062.1004-150803a-184226E unified Workstation driver
(Edited)
Photo of Reto Battaglia

Reto Battaglia

  • 7 Posts
  • 2 Reply Likes
Hi Bob

Meanwhile AMD-support wrote to me that the ingeneers found the cause of the problems with the latest driver. They will release a new driver in March and recommend that we continue to use the version 15.20.1062.1004 until then.
(Edited)
Photo of Chris Chambers

Chris Chambers

  • 5 Posts
  • 0 Reply Likes
There is a new beta driver out as of March 16, 2016.  It resolved a color matching issue I had, and it re-enabled using Aero with 10 bit color for the first time in a while.  I'm not sure what driver versions had 10 bit working with Aero, but I had seen it before.

As far as 10 bit working in Photoshop, it's still no go.  I'm using the 10 bit ramp.psd file that most people use, and still see banding.  I has this working just fine before with an older version of Photoshop and an AMD FirePro W4800.  I've since upgraded to a W7000, which is of course more powerful.

I can't recall whether I've ever had 10 bit working with Photoshop and the W7000.  I can confirm that the Eizo demo test shows that 10 bit is working in Windows.  I also got a 10 bit readout from "MonInfo".  After trying 4 or more different AMD drivers, and numerous different settings, it appears to me as though the issue is on Photoshop's end.  And to be blunt, the flippant posts from Chris Cox pointing the finger at the display driver are not at all convincing.

One final note that indicates it is a Photoshop issue is that with Aero on and 10 bit on in the AMD driver, PS CC latest version as of right now will not display any pictures with the graphics processor enabled.  Ditto for Camera Raw.  (I've seen this before, and turning off Aero resolves it.)  Meanwhile Bridge will display all pictures with Aeo and 10 bit, and there are no other display issues that I can see.  As soon as you uncheck the box to use the GP on the Performance tab of the prefs and restart PS, the images will show again.  (Or turn off Aero and restart PS.)  Given the other users have also noted that even other Adobe apps seem to work fine with the AMD hardware and drivers, I'm saying Adobe needs to get off their rear ends and fix the Photoshop 10 bit color with AMD problem ASAP.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 842 Reply Likes
I'm sorry you don't like the correct answer.
But the things preventing 10 bit/channel from working are in the OS and drivers.
Photoshop has the code, and it would be working if the OS and drivers said it was allowed.

And yes, the GPU not working with Aero enabled is a driver issue (which I thought they'd fixed ages ago).
Photo of Chris Chambers

Chris Chambers

  • 5 Posts
  • 0 Reply Likes
Well here's the thing.  I'm not paying AMD 10 bucks a month to update their drivers, and neither are the rest of the Photoshop users here.  We are, however, paying Adobe 10 bucks a month or more for Adobe's software to work.  If Adobe is so sure where the problem(s) is(are), why isn't Adobe working with AMD to resolve them??  If 10 bit is working for the NEC demo (not Eizo, sorry), why doesn't PS 10 bit work?

I've read through these forums enough to see this is an ongoing issue.  For years.  PS users should not be waiting even months to get detailed responses as to what Adobe is doing to resolve the issue.  It's not like you have dozens of different graphics card vendors either, such that you have to help debug dozens of different drivers.  Is there anyone but AMD and Nvidia?

How about providing some details on what Adobe is doing to fix this?  While you're at it provide contact info for the people within Adobe who are working on it.  Given Adobe's vast increase in revenue due to the subscription model (which many PS users dislike, BTW), I think it's time Adobe stepped up and addressed the 10 bit issue much more actively.  Simply pointing the finger at AMD doesn't cut it.

P.S.  I'm using Win7 64 bit, which is the same OS where 10 bit was working before back in CS6.  I'm not sure if you're suggesting MS has broken Win7 10 bit for PS only since then, but if they had it would still be Adobe's responsibility to work with MS to resolve issues.  If you're talking Mac when you say OS, and Apple simply refuses to bother supporting 10 bit at all, I would agree it is beyond Adobe to fix that.
Photo of Reto Battaglia

Reto Battaglia

  • 7 Posts
  • 2 Reply Likes
Win 7 is almost 9 years old... 10 bit works perfectly in PS with Win 8.1 and Win 10. Isn't it asking a bit too much that Adobe should fix problems that occur in an OS that has clearly timed out long ago? And with Aero it's the same story: Microsoft dropped it a long time ago for good reasons.  First thing I deactivated back in the old Win7 days was Aero...
(Edited)
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 842 Reply Likes
Photoshop has to have the driver and OS do the right thing in order to use 10 bit/channel display buffers. Photoshop has the capability, but right now the drivers and OS code are not allowing 10 bit/channel display buffers.  That is not something that Adobe can fix or work around -- the OS and driver vendors must once again allow the functionality before applications can possibly use it.

Adobe cannot do anything other than lobby the driver vendors and Microsoft to allow 10 bit/channel display buffers (and we have been).
Photo of Chris Chambers

Chris Chambers

  • 5 Posts
  • 0 Reply Likes
Reto,

Windows 7 was widely released less than 6.5 years ago in October 2009, and remains the most widely used OS.  The extended service end date is January 14, 2020 per MS, so please get your facts straight before commenting.  Most corporate IT departments didn't even consider 8 or 8.1 and they never will, and IT reviews of rolling out Win 10 in the corporate world are probably in the very early stages.  Many home users are also still using Win 7, which is part of the reason why MS is giving it away as a free upgrade.

I believe a couple early comments  here indicate 10 bit issues in Win 10 as well, including one of yours.  Even your comment from one month ago states AMD will be releasing a new driver to fix the problem, so exactly what is your story now?  It works for you or no?

Chris Cox,

Why not a small team of engineers working directly with AMD driver engineers?  And your answer still does not explain either the NEC demo working fine, or the fact that 10 bit worked fine with AMD FirePro hardware and software back in PS CS6. 

And again, are you saying that Windows 7 has changed something such that 10 bit does not work?  Or is it purely on AMD's end?
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 842 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.