So I have to ask but how has AMD not scrapped their driver team? I read these threads all the time and it's pretty much always the same thing. Killer hardware that they can't get to work.
Printable View
So I have to ask but how has AMD not scrapped their driver team? I read these threads all the time and it's pretty much always the same thing. Killer hardware that they can't get to work.
The installation process for 9.11 Beta, 9.11 full release and 9.12 Beta is FUBAR. There seems to be some kind of issue with the version of Visual C++ 2005 that CCC installs (CCC relies on C++ to run), meaning that on a fairly high percentage of machines, installing any of the above packages often either fails outright, causes crashes/BSODs, or fails to install CCC while successfully installing the rest of the driver package (ie. the display driver, AVIVO, HDMI audio drivers etc), with this last being most common. Aside from the obvious, this results in an error popup whenever Windows is started complaining about "MOM implementation".
I managed to work around it by running the 9.12 installer and selecting only the drivers, not CCC or Visual C++, and thus not installing CCC, and then using a 9.10 installer to install CCC.
9.11 working great here. Ran 3D'06, Stalker CoP Benchmark (Aug'09 Dx9 required).
9.11 has problems with Call Of Duty - United Offensive.:down:
9.10 FTW:up:
And I thought it was just me. I kept having the same issue, it would lock up mid install. I thought something was wrong with my system. Did a restore and tried it again and same thing. Did an uninstall and then a reinstall and that seemed to work, but talk about being in a panic mode. I just went back to water cooling from phase and thought I had screwed something up. Glad to know it is probably the driver.Quote:
Originally Posted by Mayke
Can't be the driver when everyone else got it to install fine. I installed the 9.11's a few nights ago without any issues on the first try.Quote:
Originally Posted by Utnorris
Quote:
Originally Posted by SoulsCollective
http://drivercleaner.net/download.php
Works like a champ if you really need to clean up old drivers and seem to be having problems with the standard uninstaller. Otherwise I would just use the standard install/uninstall utility in Windows.
I've already got that installed, and I fail to see the relevance to the problem :confused:Quote:
Originally Posted by Blkout
The 9.11 and later Catalyst releases simply have issues with installing CCC on certain systems. Check the AMD forums, there are quite a few people complaining about it. It's got nothing to do with an improperly installed/uninstalled old package - for the record, this was the second thing I tried after using the Cat Install Manager to express uninstall all trace of existing drivers, and made no difference.
Quote:
Originally Posted by Utnorris
It's not just you Utnorris, plenty of folks are having issues with this release.Quote:
Originally Posted by Blkout
The relevenace is that CCC is part of the driver package, but I figured you knew that. Every forum has people complaining about something, it doesn't make it a widespread problem. Almost all cases are usually on a case by case basis.Quote:
Originally Posted by SoulsCollective
A half dozen or dozen of people out of thousands of sucessful installs doesn't tell me it's a faulty driver issue. It tells me its a case by case issue.Quote:
Originally Posted by SoulsCollective
I installed the 9.10 drivers, then I uninstalled them. (I also used the driversweeper program to delete the files and registry entries being left after the uninstall) And installed the 9.11 version afterwards. Both intallation processes went ideally without any problem.
9.10 worked fine. 9.11 Beta, 9.11, and 9.12 Beta do not work fine. My system has not changed, therefore the issue is with the driver package, no?Quote:
Originally Posted by Blkout
:rolleyes:
Whether the problem is widespread or not is a separate issue, but in this particular case I'd say it is - there are a number of threads on this issue and posters complaining around the interwebs, here and elsewhere, and folks are having problems ranging from the installer locking up their machine (uncommon, severe) to simply failing to install CCC (common, moderate severity). That's a driver release bug. Obviously it does not affect all systems, as in that case it would never have made it through AMD QC, but that doesn't mean the problem exists.
I have no intention of arguing this point with you, as it's going to turn into quibbling over degrees and semantics - I'm simply posting in the thread dedicated to the 9.11 release to warn prospective installees of the issues the driver package may cause them (BSODs, CTDs, lockups, or CCC failing to install and giving error messages on every boot), and a solution that may fix the problem (installing the driver only from this release, and the CCC app from an earlier release).
Yeah, I wasn't saying it was widespread, but a few have had the issue. I don't know if it's a driver issue, I doubt, but more of a software conflict. Until we are able to compare systems of the ones that did have the problem we are just guessing at it. It could be a simple thing like turning off anti-virus while installing or not installing part of the package. Could be an issue with the hardware, don't know, but it's something and we should try and figure out what it is.
I very much doubt anti-virus would affect things.Quote:
Originally Posted by Utnorris
For those folks having the CCC failing to install properly, checking error logs seems to point to issues with Visual C++. On the AMD forums, some users report being able to install the 9.11 package once they removed all Visual C++ installations (2005 and 2008), rebooted, and allowed the driver package to install its own bundled version (which differs from the latest available builds from MS). This wasn't an option for me, as I need it for other things - but perhaps it could be as simple as ATi writing CCC in this older version (although they'd have to have done something wrong for a simple version update to break their program)? Or the driver installer not handling detection of a later, more updated version of VC++ properly and crashing out?
Given that I doubt most users have VC++ installed for anything beyond installation of new Catalyst packages and don't bother to update it from MS, could the problems could simply be down to this?