Bug Or Feature? AMD's Catalyst Doesn't Recognize NB Driver
When installing AMD's current northbridge drivers, the "success" confirmation message, installation log entries, and info in the Device Manager might lead you to believe that everything was installed just fine. Too bad the Catalyst setup says otherwise.
Conclusion And Advice
As a Catalyst user, you should adopt a certain degree of serenity. Some things may seem strange at first, but not all of them are actually signs of serious issues. If you just know certain tricks and workarounds, many inconsistencies can be solved more easily than you'd at first think.
Manually editing the configuration of the Catalyst setup can help solve situations like the one we've just explored. This article's documented steps should benefit less-experienced users, and perhaps suggest a lasting fix to AMD. The more features a software combines in a package, the more complex it gets. Mistakes are almost inevitably made. The real question is how well those mistakes will be addressed and remedied. This should be kept in mind when complaining.
Stay On the Cutting Edge: Get the Tom's Hardware Newsletter
Get Tom's Hardware's best news and in-depth reviews, straight to your inbox.
-
AMW1011 THESE are the type of articles that made Tom's awesome years ago, hopefully you guys will keep them coming.Reply
Thanks, very interesting. -
omoronovo Am I the only one that took note of the fact that the driver version installed was "1.3.3.7"? Maybe Microsoft and ATI/AMD were trying to tell you not to bother :pReply -
This problem has certainly been around for years. I remember posting a question about it on the AMDGame forums.Reply