• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Catalyst 8.12 Beta

I just encountered huge problems with the 8.12 betas

during install my monitor poped up and said "video mode unsupported" had to restart it, still didnt come up, restarted it and loaded into 640x480 mode only to find it no longer detects the native resolution of 1920x1200 only 1920x1080 of which it wants to set to 30hz interlaced :S

managed to force the resolution to 1920x1200 60hz through CCC but still not good!
 
I just encountered huge problems with the 8.12 betas

during install my monitor poped up and said "video mode unsupported" had to restart it, still didnt come up, restarted it and loaded into 640x480 mode only to find it no longer detects the native resolution of 1920x1200 only 1920x1080 of which it wants to set to 30hz interlaced :S

managed to force the resolution to 1920x1200 60hz through CCC but still not good!



i had simerlar, when i first booted up with new drivers it normally detects 1680x1050 but it ran it at about 800x somthing, and in CCC i couldnt set it to 1680x1050 but if you go into display propertys by rightclicking desktop then you can set it to 1680x1050 from there
 
i had simerlar, when i first booted up with new drivers it normally detects 1680x1050 but it ran it at about 800x somthing, and in CCC i couldnt set it to 1680x1050 but if you go into display propertys by rightclicking desktop then you can set it to 1680x1050 from there

Wouldnt even let me do that, i didnt have anything above 30hz interlaced available to me even with "hide modes this monitor cant display" unticked when selecting hz either

Weird stuff, it works as it is now but i guess ill just have to wait for the official release to get things properly back to normal
 
By default 800x600 defaults to 16bit colour mode, in CCC you need to specify 32bit first then wll you be able to choose higher resolutions.

Normal behaviour for many driver installs.

I've installed on Vista64 on my 4870 and all is perfect. 800x600 to start with but choose 1920x1200 and all is good.
 
just took these off couldnt stop cc crashing even though they gave me 200 points increase in 3d vantage hopefully full fixed release be available shortly
 
Well installed these with no problems. Have not noticed any differince while playing games, but i just hope they have improved my FPS. If they go up by a few % i know i wont be able to tell the differinec.
 
I DID TRY 8.12 !
i think from Guru.

Well, driver is improving games: i have tried on CoD4, Dead Space, Assassins Creed, Crysis, etc.

Tried everything on maximum Crysis, was less lagging ang playing was allmost nice to play.

BUT...when i tried O/C in CCC it was dissaster, my 4870 couuld not even O/C +50mhz ...games were crashing and had to do reboot!

will wait final version from ATI.COM ... maybe there will be better one!
 
This issue does not effect Nvidia cards. I went from an 8800 gts to a 4870 and only had the problem with ATI. Utl x64. Which oddly enough, just manifested itself in a small way just then, the screen blanked for a second, lost Aero and then restarted. This with only one monitor enabled. This is something ATI need to address not Nvidia or MS.

Actually, I have had that issue for quite some time, I've got 2 monitors, and I would occasionally get flickering that would last for about 20 seconds and then result in the display driver restarting.

This is with vista ultimate 64bit. I've been trying out windows 7 build 6801 64bit, and this has completely gone away, this is with the same drivers I was using with vista.

Based on that, I'd say it's more likely that it's vista with the issue and not ATi's drivers. Stability wise, 7 seems extremely stable even in its prebeta state, I've replaced my vista installation with it as I couldn't stand the screen flickering with multiple screens.

MS have done something different, I installed Windows 7 with both monitors and graphics cards, and it automatically installed the graphics drivers and set my monitors to their correct resolution, 1920x1200 and even set them to extended desktop mode.
 
Actually, I have had that issue for quite some time, I've got 2 monitors, and I would occasionally get flickering that would last for about 20 seconds and then result in the display driver restarting.

This is with vista ultimate 64bit. I've been trying out windows 7 build 6801 64bit, and this has completely gone away, this is with the same drivers I was using with vista.

Based on that, I'd say it's more likely that it's vista with the issue and not ATi's drivers. Stability wise, 7 seems extremely stable even in its prebeta state, I've replaced my vista installation with it as I couldn't stand the screen flickering with multiple screens.

MS have done something different, I installed Windows 7 with both monitors and graphics cards, and it automatically installed the graphics drivers and set my monitors to their correct resolution, 1920x1200 and even set them to extended desktop mode.

Nice ;) And with comments like that & others around the net its making it harder for me not to jump on W7 on release because of the high price, even tho i have no issues with Vista.
 
Actually, I have had that issue for quite some time, I've got 2 monitors, and I would occasionally get flickering that would last for about 20 seconds and then result in the display driver restarting.

This is with vista ultimate 64bit. I've been trying out windows 7 build 6801 64bit, and this has completely gone away, this is with the same drivers I was using with vista.

Based on that, I'd say it's more likely that it's vista with the issue and not ATi's drivers. Stability wise, 7 seems extremely stable even in its prebeta state, I've replaced my vista installation with it as I couldn't stand the screen flickering with multiple screens.

MS have done something different, I installed Windows 7 with both monitors and graphics cards, and it automatically installed the graphics drivers and set my monitors to their correct resolution, 1920x1200 and even set them to extended desktop mode.

pretty much a windows/dx problem from all I've heard as well. aero uses directx so if you set your games shortcut to disable visual themes that will disable aero on launch, the second screen will not be trying to use unavailable resources and so you shoudlnt get the crash. same problem with progams with overlays such as teamspeak which used to not disable themes and woudl crash on a single screen.

heard a lot of good things about w7 - thinking of trying the beta in new year.
 
Last edited:
pretty much a windows/dx problem from all I've heard as well. aero uses directx so if you set your games shortcut to disable visual themes that will disable aero on launch, the second screen will not be trying to use unavailable resources and so you shoudlnt get the crash. same problem with progams with overlays such as teamspeak which used to not disable themes and woudl crash on a single screen.

heard a lot of good things about w7 - thinking of trying the beta in new year.

You should try the newest build, it's 6956, I've just thrown it on my laptop. I've heard 6956 is possibly gonna be the beta. :)
 
pretty much a windows/dx problem from all I've heard as well. aero uses directx so if you set your games shortcut to disable visual themes that will disable aero on launch, the second screen will not be trying to use unavailable resources and so you shouldn't get the crash. same problem with programs with overlays such as teamspeak which used to not disable themes and would crash on a single screen.

heard a lot of good things about w7 - thinking of trying the beta in new year.

Is it just a matter of checking the tick box in the icon properties?

Because that didn't work for me in FC2, the shortcut already disabled Aero on the second monitor but I would still get the occasional crash.

Plus even with the betas I've experienced the 'Display Driver stopped responding' issue
 
Last edited:
Back
Top Bottom