Wednesday, December 18th 2013

AMD Releases the Catalyst 13.12 WHQL Graphics Drivers
After months of Catalyst 13.11 betas AMD has now made available a new WHQL-certified graphics driver, the Catalyst 13.12. This release features support for the Radeon HD 5000, HD 6000, HD 7000, Radeon R7 and R9 Series cards and is available for Windows Vista, 7, 8 and 8.1.
Download: Catalyst 13.12 WHQL 32-bit / Catalyst 13.12 WHQL 64-bit
Feature Highlights
Support for the following new products:
Download: Catalyst 13.12 WHQL 32-bit / Catalyst 13.12 WHQL 64-bit
Feature Highlights
Support for the following new products:
- AMD Radeon R9 290, 280, and 270 Series
- AMD Radeon R7 260, 250, and 240 Series
- Call of Duty: Ghosts (multiplayer component)
- Splinter Cell Blacklist
- Saints Row 4
- Metro Last Light
- XCOM: Enemy Unknown
- Need for Speed Rivals
- Total War: Rome 2
- Battlefield 4
- Saints Row 4
- Splinter Cell Blacklist
- FIFA 14
- Frame pacing ensures that frames rendered across multiple GPUs in an AMD CrossFire configuration will be displayed at an even and regular pace
- Frame pacing is enabled through the AMD Catalyst Control Center, or on a per application basis
- Frame pacing is supported on DirectX 10 and DirectX 11 applications using resolutions up to (and including) 2560x1600 on a single display
- May resolve intermittent black screens or display loss observed on some AMD Radeon R9 290X and AMD Radeon R9 290 graphics cards
- Resolves intermittent crashes seen in legacy DirectX 9 applications
- AMD Radeon R9 290 Series - Power Tune update to reduce variance of fan speed / RPM
- PCI-E bus speed is no longer set to x1 on the secondary GPU when running in an AMD CrossFire configuration
- Resolves incorrect HDMI Audio Driver information being listed in the AMD Catalyst Control Center
- Resolves AMD Steady Video option being grayed out in the AMD Catalyst Control Center
- Resolves intermittent flickering seen on some AMD Radeon R9 270X graphics cards
- Resolves graphics corruption issues found in Starcraft
- Resolves image corruption seen in Autodesk Investor 2014
- Resolves flickering water corruption found in World of Warcraft
- Resolves intermittent black screen when resuming from a S3/S4 sleep-state if the display is unplugged during the sleep-state on systems supporting AMD Enduro Technology
- Resolves intermittent crashes experienced with Battlefield 4 on Windows 8 based systems
- Resolves the display turning green when using Windows Media Player to view HD .avi format video in an extended desktop configuration
- Resolves Metro applications experiencing frame drops during playback of interlaced video content
- Resolves video playback corruption of .wmv format files in Windows Media Player
80 Comments on AMD Releases the Catalyst 13.12 WHQL Graphics Drivers
The problem with AMD is that it's site is a TOTAL ABSOLUTE AMAZING MESS. Couldn't they have just ONE download page? And not just that. I was looking in the past for raid drivers for SB750 (the floppy kind for Windows XP I think) and the driver was there in my face with only one problem. It was saying that it was for SB850 only. :wtf:
Package contains the following graphics drivers and dependent/required software for the products specified in the current version's official release notes for the 64 bit version of Windows 7, Windows 8 and Windows 8.1:
Display Driver ver. 13.251
OpenCL(tm) Driver ver. 10.0.1348.5
Catalyst Control Center ver. 2013.1206.1602.28764
Languages:
If your seeing this in you CCC or GPUZ you have 13.12 Installed .....AMD has had a fault with the beta drivers for the last year with it not reading the proper driver version under WHQL.Give it another 6 months when the next driver WHQL certified is released and it should read it again right.
PS i might also add that you would need to do fresh Windows install to fix it so i just live with it .
Use the old DriverSweeper 3.2.0 version, not the new Treexy Driver Fusion bullshit that they currently have.
Man those AMD Beta drivers ever screw with Windows during an un-install.
This is what I recommend. After you do a complete or full uninstall in the setup.exe file, get Drivefusion or Drive Sweeper to pick up the left over registry files. Before you log off for a restart, go into your device manager, locate your "Video Graphic Array", and uninstall that too. If you have 3 Graphic Cards, then you need to uninstall all three of them in the device manager. Restart your computer once or twice. You can tell it's at default when the resolution is extremely small. Do another drive sweeper sweep again to get any left over registry files listed that were in use earlier. Do a fresh install of the new driver, and it should work properly.
I was going to recommend using AMD_Cleanup_utili_1.2.1.0.exe. It isn't listed on the AMD site anymore, and I don't have any issues with it. I'd also recommend getting CClearner to properly fix your registry unless you have other programs that do the same job like Norton 360, TrendMicro, or something else.
CCleaner can be found at the following website: www.piriform.com/ccleaner/download
The Catalyst 12.10 listed on your Hardware from the Catalyst Client, is probably coming from a registry code that wasn't properly deleted from your previous beta driver installation. If you did a proper uninstall of the previous driver, 12.10, and you did a install of the new one, you'd probably be in the same boat as the rest of us. The Driver Version wouldn't be listed.
I believe it was around version 12.3 or 12.4 of the CCC installers.
Although, it worked fine for me, too.
Amd going to fix this? and do we cross our fingers we don't have a big screw around UN-installing the driver just to update the version?
-or is a Microsoft update going to fix this?
it's not like you're new customers & nvidia does it the same way
it's merely a string... change it if you want, very few things ever use this number (BF3/BF4 minimum driver version check for example)
but seriously, dont you all think you would notice:
- different build number
- different filesize
- bugs fixed
- performance change
- dates of the driver dlls change
- date in the properties of the driver device manager (!? one of you was in device manager i think)
like what :confused: we dont replace a whole tower when a component acts funny, software isnt any differentmy fault for not opening TPU again yesterday, i was actually on it like an hour before this news post, could have saved you so much wasted time & stress
by the way, that build number that changes everytime, dont you notice a date in there? 13.251-131206a-165817C-ATI = december 6, 2013 :respect:
as for WHQL, that's completely useless outside of apps that actually request it (win8 metro apps that use the gpu i hear)
just as i expected, they didnt waste resources building all those betas for vista until the very last one, now i dont have to worry when i get a 290 for my vista installation (i need a base driver at least, still need the partition working with a driver even if i'll migrate things over to a win7 partition or something)
it also looks like the custom cooled 290s launched at the same time as the WHQL+vista driver, it all makes sense really
(EDIT: by the way again, this is not the first time this version number 'issue' has happened, surely there are google results & you might even spot my posts from back then... on guru3d... i should just make a post on my site so people not these forums can stop worrying or reinstalling)