New Catalyst 'Omega' is Borking my Desktop

[FordGT90Concept]

Yeah, because Wikipedia is infallible.

How about this?

I find that very hard to believe. I think I'll keep my aluminium hat on until Microsoft officially releases a build that has a number other than 6.4,

 

[D007]

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

This is the same problem I had on my gf's computer. But apparently I'm just too stupid to install a driver according to people on these forums..lol..

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

I keep seeing you in multiple topics trying to defend this driver. Why?
People are having issues with it and people like you seem intent on nothing else but discrediting them.
Does that make you happy or something? I spent hours trying to get this to work.
It's not working and it is not our fault.. You get that I hope..

A decent driver knows how to install it's self without making you take extra steps.
Your comments are giving me a headache.

Also 2 reboots? lol.
Only with ATI..

Telling people who are having issues "you get what you deserve" because you won't accept the FACT that they are having valid and widespread issues?
Talking to them in a condescending tone as if you are sooo intelligent, because your display driver installed correctly? roflmfao..
Only on the internets..

And for the umtinth time. NO MATTER HOW MANY TIMES WE REBOOT WE ARE HAVING THE SAME PROBLEMS OVER AND OVER AGAIN, PLEASE GET THAT.

 

[Solaris17]

I find that very hard to believe. I think I'll keep my aluminium hat on until Microsoft officially releases a build that has a number other than 6.4,

http://www.windowscentral.com/microsoft-confirms-nt-kernel-version-windows-10-will-go-100

http://msdn.microsoft.com/en-us/library/ie/hh869301(v=vs.85).aspx

http://arstechnica.com/information-...ion-6-any-more-and-why-it-will-probably-work/

https://www.google.com/search?q=mic...i57.9284j0j7&sourceid=chrome&es_sm=0&ie=UTF-8

 

[Ferrum Master]

I find that very hard to believe. I think I'll keep my aluminium hat on until Microsoft officially releases a build that has a number other than 6.4,

It already stated, they will do it and did it. There are already further builds past 9888.

The most sad thing, there is the slight IE11 update, I need it because of one active x control... and the only page that needs it, that I must use for work... and it does not work... the winner is supplychain.microsoft.com

 

[OneMoar]

I would take me 15m over team viewer to fix your 'Problems' with this driver
seriously the installer automatically logs any problems try reading them ...

 

[FordGT90Concept]

http://msdn.microsoft.com/en-us/library/ie/hh869301(v=vs.85).aspx

This is the only one that matters and specifically the line within:

Developers preparing for Windows 10 should note that the Windows NT value in the UA string will change from 6.4 to 10.0 with the new release. If you have code that depends on the version number, we advise that you update to allow for the new value.

It's legit which means Microsoft intends to change a whole lot more than just bolting a start menu on to it and updating things like DirectX. WDDM 2.0 is not only plausible, but likely although I don't know what changes are made that require foundational changes.

I would take me 15m over team viewer to fix your 'Problems' with this driver
seriously the installer automatically logs any problems try reading them ...

The install is fine in my case, it's the loading of the driver that catastrophically fails upon reboot.

 

[Ferrum Master]

This is the only one that matters and specifically the line within:

It's legit which means Microsoft intends to change a whole lot more than just bolting a start menu on to it and updating things like DirectX. WDDM 2.0 is not only plausible, but likely although I don't know what changes are made that require foundational changes.


The install is fine in my case, it's the loading of the driver that catastrophically fails upon reboot.

Well mate, they actually must do something to gather moar money... instead of fixing and renaming it Vista Mk.4

There are actually noticeable under the hood changes, a bit reminds Longhorn times, that were most fun actually.

About that driver, just use DDU.

Simple AMD uninstall is rubbish, it even removes creative drivers lol. It is designed to some specific previous version, not all beta versions that one may had. So far DDU seems to be most robust and up to date database of each driver specific mess that is left in the OS.

 

[erocker]

Going from the latest beta's to this driver, I had no issues. I used this method as usual: http://www.techpowerup.com/forums/threads/how-to-reinstall-video-drivers-quick-guide.52502/

 

[Steevo]

Windows Update KB3004394

Does you has it?

If yes, uninstall it.

 

[Batou1986]

KB3004394

Bingo I installed the omega driver and started getting signature errors which would cause the driver to not load, figured it was the driver.
So I tried installing 14.4 and still got driver signature errors.

"KB 3004394 modifies the Windows Root Certificate checker so that it looks for bad root certificates daily"

Removing now will report back

 

[FordGT90Concept]

Windows Update KB3004394

Does you has it?

If yes, uninstall it.

Yes, I have it. Installed yesterday infact. I'll wait for Batou1986 before trying myself.

 

[McSteel]

Windows Update KB3004394

Does you has it?

If yes, uninstall it.

Yeah, bad root certs would make every driver seem unsigned, which is a disaster for 64-bit Windoze.

 

[FordGT90Concept]

I'm not seeing any issues on my system other than the Omega driver install.

 

[OneMoar]

bcdedit /set testsigning on

 

[Steevo]

bcdedit /set testsigning on

Do that and you will see the "test mode" BS in the lower right of your desktop. I have to run software on windows 8 that requires it since I signed it and I'm not official enough.

 

[Batou1986]

Reporting back
KB3004394 was the issue, 14.12 works fine after removing that update.

bcdedit /set testsigning on

Why disable driver signing completely when you can just un install the update that breaks it

Yeah, bad root certs would make every driver seem unsigned, which is a disaster for 64-bit Windoze.

Exactly this, when I tried 14.4 windows gave a popup for every file related to the driver saying the signature was unable to be verified which was different from the usual unsigned driver dialog.
Strangely the 14.12 driver seems to suppress these warnings

 

[Solaris17]

Do that and you will see the "test mode" BS in the lower right of your desktop. I have to run software on windows 8 that requires it since I signed it and I'm not official enough.

just call up microsoft and tell them to PM me. Maybe they work off a vouch system ill be like "yeah Steevos a total bro he won't malware anybodys shit."

 

[FordGT90Concept]

Reporting back
KB3004394 was the issue, 14.12 works fine after removing that update.



Why disable driver signing completely when you can just un install the update that breaks it

Exactly this, when I tried 14.4 windows gave a popup for every file related to the driver saying the signature was unable to be verified which was different from the usual unsigned driver dialog.
Strangely the 14.12 driver seems to suppress these warnings

Which begs the question: why did AMD not get these drivers signed?

 

[Steevo]

just call up microsoft and tell them to PM me. Maybe they work off a vouch system ill be like "yeah Steevos a total bro he won't malware anybodys shit."

LOL, did you get issued a licensed certificate for signing? If so what did you have to do?

Which begs the question: why did AMD not get these drivers signed?

They are, its an issue with windows itself AFAIK. Only some users have the issue.

 

[Batou1986]

Which begs the question: why did AMD not get these drivers signed?

They are signed, the problem is the KB3004394 changes something with signatures and their expiration criteria and thinks all drivers have invalid or expired signatures so even previously working drivers wont load.

This new signature check only seems to trigger when new drivers are installed, currently installed drivers remain unaffected.

 

[FordGT90Concept]

Considering there's an answers.microsoft.com topic that's only 2 days old and has over 130 pages pretty much puts this in the Microsoft "fail" column. They screwed up last month by letting XP's Microsoft Update certificate expire too. They got that fixed last week or the week before. It triggered a similar response to what KB3004394 is.

I don't think I'll bother with Omega nor KB3004394 though. I'm not having any problems with 14.9 nor KB3004394 (excepting Omega drivers).

 

[Batou1986]

Considering there's an answers.microsoft.com topic that's only 2 days old and has over 130 pages pretty much puts this in the Microsoft "fail" column. They screwed up last month by letting XP's Microsoft Update certificate expire too. They got that fixed last week or the week before. It triggered a similar response to what KB3004394 is.

I don't think I'll bother with Omega nor KB3004394 though. I'm not having any problems with 14.9 nor KB3004394 (excepting Omega drivers).

if you have KB3004394 you will not be able to update any drivers until microsoft fixes the problem

 

[Gmr_Chick]

Heh, my one little puff of smoke (read: problem) suddenly turned into a huge shit cloud it seems.

On a more serious note, I said screw it and uninstalled everything relating to the latest driver, reinstalled my GPU driver directly from Sapphire (HD 7790), then went back to CCC version 14.9... And whaddaya know - no more problems.

While some people are reporting no problems here, I'm going to go out on a limb and say that I think Omega needs a bit more polishing.

 

[OneMoar]

the watermark from using test mode can be removed with this
I run test mode on all my x64 systems it saves a lot of hassle
http://cl.ly/YwDq

 

[ThE_MaD_ShOt]

I couldn't be more pleased. The Omegas actually work great for my rigs.