AMD Catalyst 12.6 BETA (8.97.100.3 July 3) AMD Legacy Driver

asder00

Enjoy

Follow me on Twitter! @asder00

Downloads:
Win 7/Vista 32BiT
Win 7/Vista 64BiT
Win XP 32BiT
Win XP 64BiT
Linux 32-64BiT

AMD has moved to the AMD Radeon™ HD 2000, AMD Radeon HD 3000, and AMD Radeon HD 4000 Series new driver support model. These updates will focus on resolving application specific issues and critical updates. The reason for the shift in support policy is largely due to the fact that the AMD Radeon HD 2000, AMD Radeon HD 3000, and AMD Radeon HD 4000 Series have been optimized to their maximum potential from a performance and feature perspective.

CERT recently approached AMD with information pertaining to what they believed to be a possible video driver vulnerability exposed by non-default settings of the Microsoft® Enhanced Mitigation Experience Toolkit (EMET). EMET is a security test tool that allows system administrators to create test conditions to validate correct behavior of system components or indicate potential weak points. The presence of an issue does not necessarily mean that this issue can be exploited in regular operation of a system. The default safety settings of the EMET do not cause the issue in question to occur.

The AMD Catalyst 12.6 beta driver for the AMD Radeon HD 2000, AMD Radeon HD 3000, and AMD Radeon HD 4000 Series is designed to resolve a possible video driver vulnerability issue and to minimize the occurrence of system crashes.

Build Info:
DriverVer=07/03/2012, 8.970.100.3000
8.97.100.3-120703a-142008E-ATI

Supported Cards:

Click to show spoiler

SamuelMaki · 07-06-2012, 00:40 | posts: 29 | Location: Espoo, Finland

No windows 8 support?

Espionage724 · 07-06-2012, 03:36 | posts: 619 | Location: Charleroi, PA

Quote:

Originally Posted by SamuelMaki

No windows 8 support?

Try installing it, and then check your WDDM level. If it's 1.2, then there is Win8 support...

joshuaissac · 08-13-2012, 15:18 | posts: 3 | Location: England

Quote:

Originally Posted by Espionage724

Try installing it, and then check your WDDM level. If it's 1.2, then there is Win8 support...

I uninstalled all Catalyst Software and installed this. DXDIAG says 1.1, so I guess it doesn't work on Windows 8, at least for me.

Grabber · 07-06-2012, 08:37 | posts: 194 | Location: The Netherlands

Getting a Virus alert when installing the video drivers, from my Norton Internet Security 2012.

atiumdag.dll (Suspicious.Cloud.7.F)

ipredator · 07-06-2012, 09:38 | posts: 494

Quote:

Originally Posted by Grabber

Getting a Virus alert when installing the video drivers, from my Norton Internet Security 2012.

atiumdag.dll (Suspicious.Cloud.7.F)

Uninstall Norton and get MSE, its free and does a far better job without all the ridiculous false positives.

On a side note, I'd love to see a a new 9.00 driver too

GhostXL · 07-06-2012, 19:19 | posts: 4,916 | Location: PA, USA

Quote:

Originally Posted by Grabber

Getting a Virus alert when installing the video drivers, from my Norton Internet Security 2012.

atiumdag.dll (Suspicious.Cloud.7.F)

Curious as to why you are trying to install these when you have a 5 series card. This is for HD 4 series and below.

SamuelMaki · 07-06-2012, 23:27 | posts: 29 | Location: Espoo, Finland

Quote:

Originally Posted by GhostXL

Curious as to why you are trying to install these when you have a 5 series card. This is for HD 4 series and below.

I have both, 4200 integrated and 5650m. I cannot run the new drivers (I keep getting weird issues, everything works fine if I use some drivers that support both cards...) and I cannot run these drivers because the lack of 5650m driver... Well, I am not sure if I have been just installing "wrong" or having other issues with my windows 8, but with this driver policy, I cannot update my drivers anymore... But I am looking if the coming DNA-drivers supports both my cards...

GhostXL · 07-08-2012, 00:31 | posts: 4,916 | Location: PA, USA

Quote:

Originally Posted by SamuelMaki

I have both, 4200 integrated and 5650m. I cannot run the new drivers (I keep getting weird issues, everything works fine if I use some drivers that support both cards...) and I cannot run these drivers because the lack of 5650m driver... Well, I am not sure if I have been just installing "wrong" or having other issues with my windows 8, but with this driver policy, I cannot update my drivers anymore... But I am looking if the coming DNA-drivers supports both my cards...

Ahh I see, strange dilemma you have going on there. Sorry you seem to be having issues.

mR Yellow · 07-06-2012, 08:40 | posts: 495 | Location: South Africa

When can we get another leaked version of the 9.00 strain?

vejn · 07-06-2012, 09:31 | posts: 523

Thank you!!!
Going to report back if Witcher EE opengl component and Hitman Blood money shaders are fixed.

Benik3 · 07-06-2012, 10:55 | posts: 362

Mobility mod?

vejn · 07-06-2012, 11:35 | posts: 523

So, next legacy release will be 12.9 ?

kevsamiga1974 · 07-06-2012, 12:07 | posts: 704 | Location: England

And still the existing 4870x2 3d clock on 2nd ASIC at idle desktop bootup bug since 12.3. Except it's now worse, clocks can't be reset to video card bios defaults with amd gpu clock tool -i=* -restore anymore from the command line.

The amdclocktool -i=* -restore trick used to reset all the adapters in the system to bios default values of 507/500 1.050V with Catalyst 12.3-12.4 now using 12.6 the same trick to fix the still borked clocks actually puts both clocks to 750/900/1.250V permanently eeek!.

I've had to code a tiny app myself that opens and closes a 3D screen instead in order to fix it since ATI can't be bothered. Available here :

http://www.mediafire.com/?mx7b6d7w3lq2984 35K

Drop in startup folder. All it does is wait 12 seconds after bootup and then opens and immediately closes a low res 3D screen fixing the second clock bug on 4870x2 at least. Only x64 fix.

ARGGGHHHHHH !!!! how long have they had to fix this stupidly obvious bug since february 12.2...yes i know I can open and close a 3d app, but I shouldn't have to everytime I reboot. Not for bloody months on end.

Where is the avivo and hydravision hiding ?

AVT startup popup window needs manually disabling on bootup in registry still.

CCC is crashing...

WEI score has gone down to 7.3 from 7.5 with these no amount of re-runs bring the score back up from 7.3.

What's the point of newer drivers if nothing ever gets fixed despite being told the clock "problem" was supposed to be cured in 8.97, I think it's back to the last decent set where the clocks aint busted wasting electricity and slow cooking the card and where gpu transcoding still works in A's video converter and media espresso....That would be let's see 11.9 WHQL.

This was the highlight funny part from the release notes :

Quote:

The reason for the shift in support policy is largely due to the fact that the AMD Radeon HD 4000, AMD Radeon HD 3000, and AMD Radeon HD 2000 Series have been optimized to their maximum potential from a performance and feature perspective.

Would be nice if these features *actually* worked as they're supposed to instead of half the time being buggy/incomplete/broken/half-assed rolling from one driver to the next letting us play russian roulette across releases.

I won't argue with the performance standpoint, it peaked around 10.5a and then was all downhill from there since Terry Makedon left.

kn00tcn · **Memory**: OCZ 2x2gb 5-4-4-15 840mhz

Quote:

Originally Posted by kevsamiga1974

And still the existing 4870x2 3d clock on 2nd ASIC at idle desktop bootup bug since 12.3. Except it's now worse, clocks can't be reset to video card bios defaults with amd gpu clock tool -i=* -restore anymore from the command line.

The amdclocktool -i=* -restore trick used to reset all the adapters in the system to bios default values of 507/500 1.050V with Catalyst 12.3-12.4 now using 12.6 the same trick to fix the still borked clocks actually puts both clocks to 750/900/1.250V permanently eeek!.

I've had to code a tiny app myself that opens and closes a 3D screen instead in order to fix it since ATI can't be bothered. Available here :

http://www.mediafire.com/?mx7b6d7w3lq2984 35K

Drop in startup folder. All it does is wait 12 seconds after bootup and then opens and immediately closes a low res 3D screen fixing the second clock bug on 4870x2 at least. Only x64 fix.

so.. i should stay on 12.4? i dont mind the clock bug, have geometry wars in startup

can you change your app to use the user's desktop resolution?

maybe put text on it 'oh hai i'm fixin' ur mhz'

maybe i will play with using some of its dlls instead of installing the whole set, there are a few quirks from 12.4 & a little older that i'm curious about (ogl issues, borderlands CF, etc)

kevsamiga1974 · 08-11-2012, 23:17 | posts: 704 | Location: England

Quote:

Originally Posted by kn00tcn

can you change your app to use the user's desktop resolution?

maybe put text on it 'oh hai i'm fixin' ur mhz'

maybe i will play with using some of its dlls instead of installing the whole set, there are a few quirks from 12.4 & a little older that i'm curious about (ogl issues, borderlands CF, etc)

New app uploaded with changes for open in native res and activity message saying it's alive, now included x86 and x64 versions. Let me know if there are any problems since it was just a quick fix for changing in it for what u asked. Just as i suspected the 4870x2 clock fault lies in in the atimpag.sys or atimdag.sys from 12.3 onwards for sure 100% definate from my testing. As does the 2D accelerated rendering fault in all the 12.x drivers for 48xx shown below. And since these are kernal drivers, not so easy to replace on x64 with kernal patch protection. How do I know for sure? I injected 11.12 atimpag.sys and atimdag.sys into the 12.6 driver folder, Disabled the x64 driver integrity checks rebooted with F8 to bypass signature enforcement and as if by magic, both 2D rendering slowdowns and 3D mode boot clock bugs are gone on 2nd gpu so it's not the 3D driver components per se but the kernal ones...Although a more permanent fix would be nice than having to press F8 every time.

http://www.mediafire.com/?539i2u49f1atrud

Source:

; Quick hack to fix Catalyst 12.3+ second GPU 4870x2 clock on boot.

Delay(12000)
InitSprite()
InitKeyboard()
ExamineDesktops()

OpenScreen(DesktopWidth(0),DesktopHeight(0),Deskto pDepth(0),"")
StartDrawing(ScreenOutput(0))
DrawText(DesktopWidth(0)/2,DesktopHeight(0)/2,"4870x2 Clocks Reset",RGB(255,0,0))
StopDrawing()
FlipBuffers()
Delay(10000)
CloseScreen()
End

The polynomial game, at least here as i'm sure many other old opengl issues got fixed along with that for me by extracting and injecting the following Catalyst 12.6 legacy opengl files listed below and replacing them over any driver going back to 10.12 if you don't want the foibles of using 12.6 itself. OpenGL on 12.4 didn't work on the polynomial btw. Neither did it after 10.4 as you probably know already too well Kn00tcn.

With 12.6 legacy games like polynomial work. But for me the 12.6 driver is utterly pants to use on 4870x2 on a daily basis for the games I play, so i'm using a much older driver albeit with 12.6 legacy opengl files injected from 12.6 taking the good bits from it. I simply refuse to use the 12.1-12.6 whql drivers on 4870x2 due to this bug with GPU accelerated rendering on IE9 here :-

http://ie.microsoft.com/testdrive/Pe...g/Default.html

Enjoy the slideshow...11.12 WHQL and below work fine on this test with 4870x2. 12.1-12.6 not. Also mediashow espresso and GPU accelerated transcoding in general has been busted here way back since 11.10+. ;-)

I've been poking around for weeks figuring it all out what works and what doesn't across many driver versions on 4870x2 and stumbled upon things such as games like this using 12.6 dll's became working again quite by accident. Keeping my own notes of all the *many* bugs I come across.

Had to do the same switcheroo replacement with some drivers with the atiumdva.dll and atiumd6a.dll in the past crashing IE flash video to fix them as the WHQL release was broken for me. Think it was 10.10 I replaced with the 10.9 dll's. 10.10 was a half decent driver for 4870x2 apart from the IE flash freezes and BSOD's I had using it.

atig6pxx.dl_
atig6txx.dl_
atigktxx.dl_
atiglpxx.dl_
atio6axx.dl_
atioglxx.dl_

Copy these out of 12.6 package into any unpacked driver you want replacing the same files in the x64 driver folder over the top of any drivers all the way back to 10.12 and then install your unpacked driver using setup. Or alternatively unpack them with the expand command from CMD prompt and copy them into SYSWOW64 after you installed any driver you want. You may get a warning about unsigned driver on x64 but it's ok to continue as it's not a kernal driver replacement like atimpag.sys or atimdag.sys (2D Driver) would be.

Heaven 3.0 is still a slideshow using the opengl mode and crashes after 10.4 still, at least on 4870x2 here, but quake 1, 2 and the polynomial game (maybe more old opengl games) are all working here with 12.6 opengl dll injection into 10.12<>12.4b drivers.

This also works in opposite to some extent, eg. injecting 10.4 versions of the above opengl .dll's into later driver unpacks so old games work, but not entirely...

The games themselves work fine but the opengl version is tied in with OpenCL to some degree, so by doing the 10.4 dll injection into later drivers may lose you one Stream RV770 as well as an OpenCL RV770 device if you want working opengl games at least on 4870x2. Depends if OpenCL is important to you, for me it's not. Having working games however old is...although quite how they took from 10.6 to 11.6 to get around to fixing the BC2 crossfire flickering again is beyond me I digress.

Trouble with fixing games like Borderlands post 11.7 by replacing aticfx32.dll/aticfx64.dll/atidxx32.dll/atidxx64.dll (DX10/11) or atiumdag.dll/atiumd64.dll (DX9) is mostly cutting off a nose to spite your face, one thing is fixed, another is then broken.

It's simlar to me experimenting in the past that you could either have Bad Company 2 or Starcraft 2 working by changing out the .dll's files. Could never get them both working at the same time 100%. Fix one thing by replacing, and then you break another, and therein lies the rub to roll your own hybrid drivers.

It's a pity we even have to resort to these kind of switcheroo tricks and .dll directory dumping in the first place to work around bugs AMD can't or won't acknowledge. Yet it's now believed and the position officially is....that the drivers are optimsed from a performance and feature standpoint for "legacy" cards, hmmmm.....I wonder why the 10.x series performs better for me on MW3 or Sniper Elite V2 in that case. No caps to improve or fix any crossfire performance issues necessary and no stuttering.

Infact using latest caps with much older drivers breaks Unigene tropics and gives me crossfire flickering light rays in Sniper Elite V2. I think something drastically changed in the drivers for older cards around 11.4-11.6 from what I can tell.

kn00tcn · **Memory**: OCZ 2x2gb 5-4-4-15 840mhz

Quote:

Originally Posted by kevsamiga1974

stuff

new app is nice, 64bit is not necessary though since almost every single game is 32bit (& running one fixes the clock)

polynomial is working fine for me on 12.4, borderlands CF you just need atiumdag.dll, so just stick it into the game folder

pretty much everything i do is putting things into the game folder instead of messing with my whole package in system32

btw there are a few things that have always been broken since 10.4, try cities in motion

for IE, i'm still on 8 (does 9 have a compatibility view of 7?), & it's not my primary browser or even secondary

heaven2 last time i tried (few months ago?) it ran ok for opengl, like 75-90% as fast as dx9, CF was scaling, etc

Mikedogg · 07-06-2012, 13:24 | posts: 2,872 | Location: The Freak Show - Earth.

What. No fixes info?

vejn · 07-06-2012, 13:45 | posts: 523

Quote:

Originally Posted by Mikedogg

What. No fixes info?

This is still beta.
Try out then report any issuses and problems so they can fix it in final release.

Miroglu · 07-06-2012, 14:25 | posts: 51 | Location: TURKEY

Thanks asder

pakoo · 07-06-2012, 14:48 | posts: 73 | Location: SPAIN

Fix crossfire in Bad company 2 on 69xx users?.

Thanks.

kevsamiga1974 · 07-06-2012, 15:08 | posts: 704 | Location: England

Read what the title says man...

There's nothing contained in the .inf for above 4xxx series anymore as starting with this driver support has now been sectioned into legacy (I hate that word) and separate >=5xxx branches.

These probably won't install on 69xx series anyhow without modding the .inf file which should in theory still be possible. The question is why would you want to use it as a 69xx series owner, there are already drivers for 5xxx and above with far higher versions than these.

Mikedogg · 07-06-2012, 15:49 | posts: 2,872 | Location: The Freak Show - Earth.

Can't install media codecs, or hydravision.

What a jib!.

Anonizer · 07-07-2012, 02:08 | posts: 4

So is this the best drivers for 4xxx series? Anyone tested?

kevsamiga1974 · 07-07-2012, 08:21 | posts: 704 | Location: England

Best if you like stuck clocks and CCC crashes. Since 12.x they just screwed everything up. Still on 11.9 and I can see me being on them for a long time.