Solaris17Can you confirm this with a screen shot? You don't exhibit any of the odd readings we do? Does your Oc program detect a driver? Mine does not. i'm using after burner.

Looking at it closely, I can confirm that MSI AB 3.0.0 Beta 17 and ROG Techpowerup GPU-z 0.7.4, isn't indicating a driver version. I'm not going to put a picture up to confirm this. On MSI AB, Driver Version is blank. There's nothing listed. In my GPU-Z where it say "Driver Version," the following is listed: atiumdag 13.251.0.0/Win7 64. In SK-1's screenshot, there should be a "(driver version)" in between the 0.0 and /Win7 64. It's not there, and I am not worried about it to be honest.

This is why I will never buy another Amd product. It takes month and months of beta drivers to get to this. Good thing I went nvidia this time around.

pr0fessorAre you serious AMD? I bought Windows 8, because I thought you do not support Vista anymore. Well, Windows 8 isn't that bad.

support.amd.com/en-us/download

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:

If those don't fix the CrossFireX crashes in COD:Ghost, that's it for me with AMD.

Description:
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 .

H82LUZ73Description:
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 .

I seriously doubt a fresh windows install would fix it. Its a missing registry string.

When you guys did a clean install, do you mean you used the clean install option during the driver installation or did you do the "DriverSweeper clean up, restart then driver install" method?

Use the old DriverSweeper 3.2.0 version, not the new Treexy Driver Fusion bullshit that they currently have.

CheeseballWhen you guys did a clean install, do you mean you used the clean install option during the driver installation or did you do the "DriverSweeper clean up, restart then driver install" method?

Use the old DriverSweeper 3.2.0 version, not the new Treexy Driver Fusion bullshit that they currently have.

Uninstall of old driver package, reboot, install new driver package, reboot, should normally do the trick.

Generally it should, however I've found a couple of ati*.dll files being left over (no leftover registry entries though), so I made it a habit to use DriverSweeper to completely clean out any leftover files.

ClassicEnergyThis is why I will never buy another Amd product. It takes month and months of beta drivers to get to this. Good thing I went nvidia this time around.

Take your AMD hate post to a relevant thread of equally juvenile users. Your comment is not in the slightest useful to anyone, and merely detracts away from the topic, and altogether makes me all flustered when i read such ill-thought-out posts.

Here's what I show after 30 min of pissn around..

Man those AMD Beta drivers ever screw with Windows during an un-install.

they're broken, doesn't work with my 5830, Resident Evil 6 crashes on load and shutter in menus, i haven't tried other games though. I reverted on 13.9 and everything is nice now, wtf, AMD???

Can anyone tell me why I am having Catalyst as 12.10 ? I did a clean install (uninstall old beta completely)

I'm not even gonna touch this update with all the wacky screenshots of different driver versions after install. It may not be a big deal, but it makes you wonder what else AMD forgot while making this driver...

_larry.... it makes you wonder what else AMD forgot while making this driver...

They forgot to give a $hit about, that's all....

I've seen the "not updating version" issue before. These drivers are working fine here.

AnasHSNCan anyone tell me why I am having Catalyst as 12.10 ? I did a clean install (uninstall old beta completely)

Something tells me you didn't do a complete or full uninstall. There may have been left over files in the AMD folder. You just did a complete uninstall, or what you thought was one, and just installed the new WHQL into the original folder.

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.

erockerI've seen the "not updating version" issue before. These drivers are working fine here.

Yep, there was a thread way back about the whql not updating the "catalyst_version" entries in the registry when you updated from the betas.
I believe it was around version 12.3 or 12.4 of the CCC installers.

Although, it worked fine for me, too.

I miss the days when the driver came every month. Even without any update within. Never mind like nVidia. Finally 8.1 is officially supported and my HDMI output signal is back to normal.

So wth?

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?

guys... i cant believe you're falling for 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 different

my 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)

Anyone else having random crashes in Ass Creed 3, mainly on naval battles?

BF4 is such a noob and still reports me having 13.4. Oh well. At least I know I actually updated.

CCC driver 13.10bv2 is still the best looking and running driver imo!

63jaxthey're broken, doesn't work with my 5830, Resident Evil 6 crashes on load and shutter in menus, i haven't tried other games though. I reverted on 13.9 and everything is nice now, wtf, AMD???

Seriously I also have a old card and.........these drivers offer no new fixes for it, so I am not going to install them and then complain when my system runs perfect without updating to a driver package optimized for GCN and NOT VLIW.