11.10 WHQL

[The Mac]

I had to do this to play Rage with those drivers. I can't understand why AMD releases a WHQL driver that breaks Rage completely without putting it in big, bold letters in the known issues. People using preview 3 should not "upgrade" to 11.10 final.

However I must say that Battlefield 3 runs flawlessly.

They reverted the OGL driver to 4.1 in the WHQL. Im wondering if that might have been an oversight.

Preview 3 had OGL 4.2, thats why sticking the preview 3 driver in the rage directory fixes it.

You can also drop it in c:\windows\syswow64 for full system use.

 

[hordaktheman]

They reverted the OGL driver to 4.1 in the WHQL. Im wondering if that might have been an oversight.

Preview 3 had OGL 4.2, thats why sticking the preview 3 driver in the rage directory fixes it.

You can also drop it in c:\windows\syswow64 for full system use.

The problem is that the preview driver doesn't seem to work with anything other than Rage.

 

[Bl?n D'?ero]

The problem is that the preview driver doesn't seem to work with anything other than Rage.

Nonsense! I am playing several games, they run normally. BF3 runs great.

 

[hordaktheman]

Nonsense! I am playing several games, they run normally. BF3 runs great.

We're talking about the OpenGL driver. It seems to be limited to Rage while other OpenGL apps crash with it installed.

 

[Ristogod]

Just stop playing rage. It's a terrible game.

 

[hordaktheman]

It's one of the best shooters of recent years, in my opinion.

 

[The Mac]

It's one of the best shooters of recent years, in my opinion.

agreed, i hate shooters mostly...rage was actually fun...a bit short though...2 or 3 more areas would have been nice..

the preview 3 ogl driver doesnt crash any of my other OGL games, so perhaps something else is going on in those systems...

 

[Qamly]

I've had that EXACT SAME stuff happening mainly because I was using driversweeper all the time. It should be run only for extreme cases of screwabunga.
On a fresh system install 6 months ago I decided to stop using it.
The drivers run just fine ever since, only regular uninstall followed by reboot and new installation is needed, no tinkering with folders and cleaners, the installer will do its job smoothly and greet you with a nice green check-mark at the end of the procedure.

STOP USING DRIVER SWEEPER FOR REGULAR DRIVER INSTALLATION.

There is no other way to fix the issue, once this happens, besides using driver sweeper or aticleaner or whatever.
To be clear, I didn't have to use any cleaning program before, it would just work normally. However, this time around, it didn't. Something in the installer screwed up and it wouldn't fix itself. Even multiple attempts didn't help.
Thus, I had to use a cleaning program to fix it, and it did.

All the cleaner programs do is to delete the remaining files and registry keys that the ATI uninstaller don't.

 

[ATi7500]

anyone noticed a decrease in Idle GPU frequencies with this driver? I now have 50MHz on my 6850 in idle, before it was 150MHz.

edit: after a reboot it went back to normal

 

[Lurk]

There is no other way to fix the issue, once this happens, besides using driver sweeper or aticleaner or whatever.
To be clear, I didn't have to use any cleaning program before, it would just work normally. However, this time around, it didn't. Something in the installer screwed up and it wouldn't fix itself. Even multiple attempts didn't help.
Thus, I had to use a cleaning program to fix it, and it did.

All the cleaner programs do is to delete the remaining files and registry keys that the ATI uninstaller don't.

mmm... I have a feeling the problem is infact related to deletion of registry keys which probably SHOULDN'T be deleted. I haven't run into this problem since I re-installed Win7, and stopped using cleaners to wipe out traces of old drivers. Unless you have REALLY never done that before, I still think it might be related to unproper 3rd party cleaning methods.
I don't have the knowledge to delve into this any deeper, glad you could solve it, although I understand it's quite a hassle to go through the entire procedure.

 

[The Mac]

mmm... I have a feeling the problem is infact related to deletion of registry keys which probably SHOULDN'T be deleted. I haven't run into this problem since I re-installed Win7, and stopped using cleaners to wipe out traces of old drivers. Unless you have REALLY never done that before, I still think it might be related to unproper 3rd party cleaning methods.
I don't have the knowledge to delve into this any deeper, glad you could solve it, although I understand it's quite a hassle to go through the entire procedure.

its more than that, there are allot of backup system files, prefetch buffers, and a bunch of junk in the the assembly directory that the sweep proggies clean up.

11.9 was the first time i was forced to use driversweeper in many, many years...

I think a key step most people forget, especially with win7, is to boot into VGA mode after sweeping, not regular mode. this makes sure NOTHING from ati is loaded before running the new cat update.

 

[Lurk]

yeah, I used to skip the safe boot part in the beginning, out of pure laziness.
my personal advice though is to steer away from them sweep proggies as much as possible.
I have a sufficient experience with MS os's to be able to notice that Win7 is able to take care of itself pretty well, this opinion coming from an old time compulsive system tweaker.
I've never had as few 3rd party utilities as in my latest os installment. I really rely only on CCleaner and jv16power tools.
I'm still quite convinced, prove me wrong, that most of driver installation related problems generate behind the keyboard. I've been having no issues with drivers in the past 8 months, coincidentially when I decided to quit with arbitrary deletions and maniacal system cleaning procedures.

But I'm not attempting to hold a lecture here, just my 2¢.

 

[Qamly]

I'm still quite convinced, prove me wrong, that most of driver installation related problems generate behind the keyboard. I've been having no issues with drivers in the past 8 months, coincidentially when I decided to quit with arbitrary deletions and maniacal system cleaning procedures.

But I'm not attempting to hold a lecture here, just my 2¢.

Sorry to burst your bubble, but that isn't the case here.
Take a registry monitor, and install the drivers, and see all the crap it does.
Then do a uninstall, and look at what that does.
Compare.
Notice that they don't match up.

All the cleaning programs do is to undo the install process, no other files are touched, and if they are, it is a bug in the program.

Bottom line is, if you can't install the drivers the 'normal' way, then using a cleaning program is your only option, unless you want to reinstall the OS.

 

[Lurk]

sorry to burst YOUR bubble, but your description of installation procedures seems rather superficial and didn't convince me ONE SINGLE BIT!
Most of the time what you call 'crap' might be there for a reason.
All I can tell you so far from my experience is: no more specific cleaning programs -> smooth sailing.

on a side note: a while ago a version of DriverSweeper completely farked up Win7 SP1 installation for many users, to a point the only way to make it function properly was to completely reinstall os. A full system format as a consequence of 3rd party driver uninstall. I think I made my point.
Nonetheless, I'm glad you eventually solved your issues.

 

[overcast]

I've had that EXACT SAME stuff happening mainly because I was using driversweeper all the time. It should be run only for extreme cases of screwabunga.
On a fresh system install 6 months ago I decided to stop using it.
The drivers run just fine ever since, only regular uninstall followed by reboot and new installation is needed, no tinkering with folders and cleaners, the installer will do its job smoothly and greet you with a nice green check-mark at the end of the procedure.

STOP USING DRIVER SWEEPER FOR REGULAR DRIVER INSTALLATION.

I can't reemphasize this enough. There is absolutely ZERO reason to use those drive cleaner methods. People seriously go to ridiculous lengths with installing these drivers and it has to stop. All you are doing is causing problems for those less educated. I've installed drivers on top of one another for ten years without any issues. At most, uninstall and reinstall new drivers.

 

[Ulysses 31]

Still no v-sync for DX9 stuff in Eyefinity+CF.

 

[Shingo-Y]

Still no v-sync for DX9 stuff in Eyefinity+CF.

V-Sync is also broken in some games, like Sonic Generations.

 

[joe3000]

Call of Duty MW3 is a mess, with 11.10, 11.9...The game runs smooth for a few minutes at 60fps+ and then starts to stutter, texture courption and then CTD

 

[caveman-jim]

on a side note: a while ago a version of DriverSweeper completely farked up Win7 SP1 installation for many users, to a point the only way to make it function properly was to completely reinstall os.

That's not actually true. There was a simple fix, no reinstall of OS necessary.

 

[caveman-jim]

I can't reemphasize this enough. There is absolutely ZERO reason to use those drive cleaner methods. People seriously go to ridiculous lengths with installing these drivers and it has to stop. All you are doing is causing problems for those less educated. I've installed drivers on top of one another for ten years without any issues. At most, uninstall and reinstall new drivers.

There are reasons to use them, for example when you have problems with your drivers not working as expected. It's not necessary to do unless you're experiencing problems, but it can be useful. For most people an install over the top is all that's needed.