New Catalyst 'Omega' is Borking my Desktop

[Aquinus]

I'm going back to 14.9. 14.12 (Omega) is worse than Microsoft's generic display driver.

The same thing happened to me when I upgraded in place. You need to run a driver cleaner first as I said earlier.

I had to do a full driver cleaning before installing the drivers worked. I've seen no benefit so far though, granted I'm using 6870s.

 

[Black.Raven]

Do the windows experience index or something, it is in system. after you classify, it shows the aero again. Basicly it doesnt trust your videocard to be able to run it now

 

[URBAN303]

Sometimes having to uninstall graphics drivers and reinstall them that disables the Windows Aero theme by selecting a classic theme. Simply select an Aero theme manually enable Aero.

 

[Ferrum Master]

My first boot with OMEGA ... Hmm nice features... Second boot was normal tough... but still... AMD always makes such surprises...

 

[FordGT90Concept]

http://support2.microsoft.com/mats/aero_effects_not_working

I always turn Aero off on my computer because I want text when hovering on a group and not pictures.

The same thing happened to me when I upgraded in place. You need to run a driver cleaner first as I said earlier.

I'm not going to mess with it anymore. AMD's installer should take care of the previous driver itself and if that is indeed the problem, they should have it fixed by the next release. I'm not going to use third party software to fix a first party problem.

Do the windows experience index or something, it is in system. after you classify, it shows the aero again. Basicly it doesnt trust your videocard to be able to run it now

I suspect if I tried that, it would have foregone the 3D tests because there's no driver installed. In my experience WEI is nothing more than an arbitrary score used for now-defunct Games for Windows Live. Aero is more dependent on having DirectX 9 or newer hardware than anything else.

Edit: Verified. I have a Vista Business 32-bit SP2 machine sitting next to me. It has GMA 3100 (Pixel Shader 3.0/DirectX 9.0c) with an "unrated" WEI score and I was able to enable the Windows Aero theme without problems. Aero is disabled by default.

 

[vgm]

My first boot with OMEGA ... Hmm nice features... Second boot was normal tough... but still... AMD always makes such surprises...

There is no official support for win 10 for CCC Omega because win 10 uses a new kernel revision 10.x as ccc is programed to be aware of only 6.x reversions.
Win10 is showing mashed up of both virtual desktop and original desktop.
Try downgrading to 7/8.1.

 

[Kyle Ragnador]

No Aero:
After new driver installation you have to run WINSAT.exe [Windows Experience Index (WEI)] . So Windows knows your graphicscard power. Otherwise it runs in low spec mode.

Better get Windows 8.1 . Its Faster then xp & vista and even in some parts then 7.


--
--
--

I'm going back to 14.9. 14.12 (Omega) is worse than Microsoft's generic display driver.

Possible:
1. Your Bios has set Primary Videocard to onboard. or
2. You use something like LucidVirtu/GPU Tool which blocks. deinstall them to test. or
3. Due to new features your Overclock is to unstable. or
4. Check compatibility: http://support.amd.com/en-us/kb-articles/Pages/AMDCatalystOmegaWINReleaseNotes.aspx.
If all doesn't help use the AMD Issue Reporting Form.

 

[skline00]

The Omega drivers work well on my rig.

 

[FordGT90Concept]

Possible:
1. Your Bios has set Primary Videocard to onboard. or
2. You use something like LucidVirtu/GPU Tool which blocks. deinstall them to test. or
3. Due to new features your Overclock is to unstable. or
4. Check compatibility: http://support.amd.com/en-us/kb-articles/Pages/AMDCatalystOmegaWINReleaseNotes.aspx.[/COLOR]
If all doesn't help use the AMD Issue Reporting Form.[/FONT]

1. There's only one graphics device in my computer.
2. Nope.
3. Nada.
4. "ATI Radeon™ HD 5000 Series" yup. I should add that AMD pushed this driver to me via pop up notification on boot. I wonder how many people are going to have their computer trashed because of this driver and not know how to revert to 14.9 drivers.

I reported it.

 

[Aquinus]

I'm not going to mess with it anymore. AMD's installer should take care of the previous driver itself and if that is indeed the problem, they should have it fixed by the next release. I'm not going to use third party software to fix a first party problem.

The display driver crashed and caused the machine to BSOD while the driver was installing. My machine was stuck between the old driver and the new one. I had to because stuff went wrong not because it's what you need to do every time you upgrade. Also I think if I uninstalled the display driver first then installed the new one, it probably would have been fine.

 

[FordGT90Concept]

Also I think if I uninstalled the display driver first then installed the new one, it probably would have been fine.

Which AMD and NVIDIA always recommend. XD

 

[Aquinus]

Which AMD and NVIDIA always recommend. XD

90% of the time I can usually install on top of the old install, but the last driver before this was was acting weird. It would occasionally crash when starting a DX11 game, but not all the time and the same thing occurred in the middle of the driver installation. Either way, I wouldn't let cleaning it out stop you from giving them a try regardless of how you think it should work.

 

[INSTG8R]

90% of the time I can usually install on top of the old install, but the last driver before this was was acting weird. It would occasionally crash when starting a DX11 game, but not all the time and the same thing occurred in the middle of the driver installation. Either way, I wouldn't let cleaning it out stop you from giving them a try regardless of how you think it should work.

So with a so called "new driver" you would just run it over top?... Sorry you get what you deserve. I ALWAYS uninstall my old drivers before new. I mean c'mon it's 2 reboots...

 

[Aquinus]

So with a so called "new driver" you would just run it over top?... Sorry you get what you deserve. I ALWAYS uninstall my old drivers before new. I mean c'mon it's 2 reboots...

Versus 3 if it doesn't work right? I'm not too worried about it failing...

 

[Solaris17]

There is no official support for win 10 for CCC Omega because win 10 uses a new kernel revision 10.x as ccc is programed to be aware of only 6.x reversions.
Win10 is showing mashed up of both virtual desktop and original desktop.
Try downgrading to 7/8.1.

That hasn't been implemented in the currently available build so no. and i installed over the betas fine.

 

[GreiverBlade]

only 1 problem for me : tried to activate VSR on a screen who is not meant to be used with it i had to safe mode boot and DDU the driver (safemode also in DDU options) but after that, smooth as butter and less instability in framerates in games (well in the games where i noticed a drop instead of a improvement.)

for the so called borking desktop : user fault at most, when i installed the drivers they prompted me, when i opened CCC, to change the DPI according to my resolution, well i ended with humongous icons.
easy to correct anyway, but if you never used that option previously you might end cursing the driver, afaik a pop up windows who ask you to change your DPI (if you are fine with your desktop : no reason to do so) require a user action, aka: press OK button ... but as i wrote a bit above, if you are fine with your current DPI then no need, so tick the "never show again" box and press cancel.

in practice : you go there.


but then i have a 290 i should try on my R7 240 to see if there is any difference (since my other ATI/AMD card is a 5450 and a 3650 and the 5xxx serie is not supported anymore in the new drivers if i am not mistaken )

 

[Ferrum Master]

There is no official support for win 10 for CCC Omega because win 10 uses a new kernel revision 10.x as ccc is programed to be aware of only 6.x reversions.
Win10 is showing mashed up of both virtual desktop and original desktop.
Try downgrading to 7/8.1.

I didn't ask for help, especially when I know what I am using. Seconds, it has nothing to do with NT10.

 

[FordGT90Concept]

I thought Windows 10 was NT kernel 6.4?

 

[McSteel]

No, Microsoft had a stroke-of-genius idea of bumping up the major version number to 10, so as to distance the new Windows from the previous incarnations as much as possible.

In reality, this kernel is a minor evolution, so 6.4 would've been the correct numbering. Even 7.x might have been acceptable, but 10.x is just plain silly.

 

[FordGT90Concept]

You're confusing the marketing name of the product and the kernel version used for compatibility purposes.

4.0 = NT 4.0

5.0 = 2000
5.1 = XP/Server 2003
5.2 = XP x64/Server 2003 R2

6.0 = Vista/Server 2008
6.1 = 7/Server 2008 R2
6.2 = 8/Server 2012
6.3 = 8.1/Server 2012 R2
6.4 = 10

Wikipedia claims the technical preview is Windows NT 6.4.9879. I have no reason to doubt it.

 

[McSteel]

Yeah, because Wikipedia is infallible.

How about this?

 

[Solaris17]

The real issue here is the TIME FRAME. public windows 10 preview builds are NOT kernel version 10. they ARE 6.4 so this particular problem is not an issue (yet?)

 

[McSteel]

No issues. They're putting an "interceptor" in place. When an application makes a query through legacy API calls, it will get served v6.3, modern apps will get v10.0 as a response.

 

[Solaris17]

No issues. They're putting an "interceptor" in place. When an application makes a query through legacy API calls, it will get served v6.3, modern apps will get v10.0 as a response.

this is even the case when using system information via windows itself? I knew of the interceptor but I believe WMI will report the new kernel version

 

[Ferrum Master]

The real issue here is the TIME FRAME. public windows 10 preview builds are NOT kernel version 10. they ARE 6.4 so this particular problem is not an issue (yet?)

Only Intel drivers had slight problems with new kernel naming scheme... nvidia and AMD are completely safe to us as far Windows Driver Model stuff is the same... That's the reason btw I put this OS, to test my specific professional apps, to alert them to ensure program/driver compatibility as fast they can.

So far none of them has presented WDDM 2.0 driver, that's another story, but compatibility wise, there are no problems in gaming department.