Do we really need to know everytime AMD or Nvidia release new drivers? Is it really worthy tech news? (or is it my pre-caffeine 'personality' haha :))

Owen1982Do we really need to know everytime AMD or Nvidia release new drivers? Is it really worthy tech news? (or is it my pre-caffeine 'personality' haha :))

We do :)

To begin with, high idle memory clocks noticed on machines with multiple high-resolution monitors, has been fixed <- can someone from TPU test this?

ixiTo begin with, high idle memory clocks noticed on machines with multiple high-resolution monitors, has been fixed <- can someone from TPU test this?

Mem seems high still - using 3 monitors in a Eyefinity setup

Beta driver, no thanks. 21.10.2 is where its at as far as I'm concerned.

jesdalsWe do :)

Agreed.

jesdals
Mem seems high still - using 3 monitors in a Eyefinity setup

Yep, did you check before upgrading what was the memory clock?

I just installed these drivers on my new AMD laptop. I did "factory reset" so it rebooted, then installed these, Full Install, then I rebooted again. Everything seemed great, then I noticed Windows 11 was updating two updates called AMD Display and some numbers after that, then my new AMD laptop froze, I waited and waited... then had to hold power button down.

Rebooted a couple of times, and now the AMD driver won't load and I keep getting a error "this driver not compatible"

So I uninstall all AMD, pause windows updates for 1 week, then factory reset install of the Full Install option of these newest drivers, and everything is working great...


afraid to turn on updates though for windows... :/ why can it never be simple... I miss consoles for this reason lol

AlwaysHopeBeta driver, no thanks. 21.10.2 is where its at as far as I'm concerned.

If you have looked more into it, you would know that there isn't a difference. WHQL was once a Beta driver, before it was renamed to WHQL with no change.

ixiYep, did you check before upgrading what was the memory clock?

They where identical - one thing more is the automatical zero fan setting - not a fan of that - get much more performance from active fan setting

lynx29I just installed these drivers on my new AMD laptop. I did "factory reset" so it rebooted, then installed these, Full Install, then I rebooted again. Everything seemed great, then I noticed Windows 11 was updating two updates called AMD Display and some numbers after that, then my new AMD laptop froze, I waited and waited... then had to hold power button down.

Rebooted a couple of times, and now the AMD driver won't load and I keep getting a error "this driver not compatible"

So I uninstall all AMD, pause windows updates for 1 week, then factory reset install of the Full Install option of these newest drivers, and everything is working great...


afraid to turn on updates though for windows... :/ why can it never be simple... I miss consoles for this reason lol

Whenever you manually update a driver then Windows decides to update it itself, let it finish and restart if it asks you to. If you get the driver not compatible stuff, just go to Device Manager, right click on the graphics card from Display Adapters -> Properties -> Driver -> Roll back driver.

Then it should work fine and you won't have any more issues.
Hope this helps

Just in a teams meeting but going to install these rights after.

I did experience black screen in some games on my AMD system. I didn't know it was caused by enhanced sync. Now i know. Does AMD do any optimizations whatsoever for older cards or only the latest series?
Also, i noticed that when i play some more demanding games, after i exit the game sometimes core frequency on GPU remains locked to max value. Never experienced so many problems on Nvidia system. Not that green team can't srcrew up.

jesdals
Mem seems high still - using 3 monitors in a Eyefinity setup

Try setting a custom mem clk ~10mhz lower than stock. See if that enables downclock on idle. FWIR, I had a smilar issue with 2x 4k panels & that did the trick.

For me, the latest ones, tend to do well, but the only Navi I have now, is an RX 5500 XT, albeit with 8 GB of VRAM. ("Navi14")
It's an MSI Mech and I actually got it before the MSI Gaming X Radeon RX 5600 XT. It was in a box, since August, 2020 and wasn't opened until at least December 24, 2021.

But I'm currently using my GeForce GTX 1660 Super in my main rig. My RX 5600 XT is a goner.

I was under the impression that the next Drivers release would contain Radeon super resolution or RSR.

Amd drivers become to one of the worst ive ever saw, nearly every day i get a driver timeout.
A few years ago it was a real driver (CCC) not a all in one bug tool like today.


My next second hand gpu will be a Nvidia :laugh:

seth1911Amd drivers become to one of the worst ive ever saw, nearly every day i get a driver timeout.
A few years ago it was a real driver (CCC) not a all in one bug tool like today.


My next second hand gpu will be a Nvidia :laugh:

i've never had a driver timeout on my old RX580 and I used that for like 3+ years also none on my current gpu.

I usually got a driver timeout, because of unstable "SCLK". (GPU core)

seth1911Amd drivers become to one of the worst ive ever saw, nearly every day i get a driver timeout.
A few years ago it was a real driver (CCC) not a all in one bug tool like today.


My next second hand gpu will be a Nvidia :laugh:

Have you checked memory stability? The driver will crap out, if memory is not stable. Other thing you could get is better psu.

Enhanced sync why is this still a thing. Why don’t they just fail to mention it with the next driver. Never worked on my xfx 5600xt.

MysteoaHave you checked memory stability? The driver will crap out, if memory is not stable. Other thing you could get is better psu.

Every time my VRAM crapped out, Windows 10 would give a Cache Hierarchy Error WHEA bugcheck. Sometimes, it was so bad that Windows 10 blacked out and rebooted itself with a Cache Hierarchy Error WHEA bugcheck when the software isn't completely loaded.

For example, Windows 10 would crash with WHEA_UNCORRECTABLE_ERROR with Cache Hierarchy Error as the reason when I just barely started loading of a program.

I traced it to the VRAM that possibly isn't stable at stock clocks, just because of the room being warm.

That's the most ridiculous thing, since my super socket 7 system with an AMD K6-2 450 Mhz and Deer DR-250 ATX power supply, 20 years ago! Where just the room being warm, caused a bunch of totally random Windows 98 SE errors that I never had before. Note that the room wasn't 100 F or 90 F for cryin' out loud! Very ridiculous for a system that wasn't overclocked and overvolted!

MysteoaHave you checked memory stability? The driver will crap out, if memory is not stable. Other thing you could get is better psu.

Yeah its the memory or the psu, but not the driver. :laugh:


CCC 15.7.1 from 2015 and the Crimson 17.9.3 from 2017 work without any issue.

seth1911Yeah its the memory or the psu, but not the driver. :laugh:


CCC 15.7.1 from 2015 and the Crimson 17.9.3 from 2017 work without any issue.

I didn't say it can't be the driver. I have seen some cases of people apologizing that they blame the driver when why had a different PC problem. Most of the time it was unstable RAM. But because of AMD driver bad stigma, everyone is very vocal about it and first blames the driver.

RJARRRPCGPEvery time my VRAM crapped out, Windows 10 would give a Cache Hierarchy Error WHEA bugcheck. Sometimes, it was so bad that Windows 10 blacked out and rebooted itself with a Cache Hierarchy Error WHEA bugcheck when the software isn't completely loaded.

For example, Windows 10 would crash with WHEA_UNCORRECTABLE_ERROR with Cache Hierarchy Error as the reason when I just barely started loading of a program.

I traced it to the VRAM that possibly isn't stable at stock clocks, just because of the room being warm.

That's the most ridiculous thing, since my super socket 7 system with an AMD K6-2 450 Mhz and Deer DR-250 ATX power supply, 20 years ago! Where just the room being warm, caused a bunch of totally random Windows 98 SE errors that I never had before. Note that the room wasn't 100 F or 90 F for cryin' out loud! Very ridiculous for a system that wasn't overclocked and overvolted!

I have heard of similar thing like motherboard not working due to the air humidity and temperature. It's rare, but can happen. For your case, I would blame the board vendor.

Please dont cry :cry:, i wont hurt ure love for AMD :laugh: