Skip to main content

Could AMD driver curse be back with mysterious RX 6000 failures?

Some of AMD’s RX 6000 graphics cards are giving up the ghost completely, with a bunch of broken GPUs suddenly being brought to our attention by a German repair shop.

That shop, KrisFix, highlighted this problem on YouTube (via Wccftech, with Buildzoid also flagging on Twitter), and the visual evidence provided is worrying indeed.

See more

We’re talking cracked GPUs, no less, and when that happens to the chip, the whole graphics card is an immediate write-off, of course.

KrisFix informs us that over the last three weeks, he has received 61 AMD graphics cards for repair – that’s RX 6900 and 6800 models – and that 48 of those boards had this exact same problem, a cracked GPU.

That’s almost 80% of all those models sent in for repair, a startlingly high percentage it must be said; and all of those he further observes had a shorted SOC rail, shorted memory rail, and a shorted memory controller rail (indicative of a GPU catastrophe). Normally, he would expect to see 10% or so of the graphics cards sent in to be suffering from something as bad as a cracked chip – not 80%.

There was one common thing with the problem boards, though – KrisFix notes that they were all running the same graphics driver, the latest one from AMD.

We’ve reached out to AMD for a comment on what might be going on here, and will update this story if we receive a response.


Analysis: Is mining mayhem a possibility?

As KrisFix points out, it’s difficult to say what might be going on here with any certainty, but given the commonality with the driver, he theorizes that maybe the latest Adrenalin version (released a month ago) is pushing performance a bit harder, and perhaps some RX 6000 GPUs can’t handle this.

At the same time, he makes it very clear that he doesn’t yet have enough information to make that judgement, and it’s pretty obvious we can’t leap to any firm conclusions yet on whether the graphics driver is really at fault here.

At the moment, we just have the word of one German repair outfit, with KrisFix admitting himself that we must be very cautious, and we need further evidence. Indeed, if there really was an issue with RX 6800 and 6900 GPUs, surely we’d be hearing a lot more about this by now, a month after the driver came out?

On the other hand, you could argue about how many folks update their graphics driver regularly. Certainly there are a good many people who stick with the same GPU driver for a while, and definitely don’t take on every single version released.

Another possibility is that the problem is limited to certain graphics cards, and not all of them. Here’s where another suggestion comes into play – that the affected models are ex-mining GPUs. As mining operations threw in the towel last year, they sold off the graphics cards in their farms, and these are GPUs which have literally been flogged almost to death 24/7.

So, it’s not a stretch to think that a good many gamers have picked up second-hand stock of these ex-mining AMD GPUs – quite possibly without knowing they are ex-mining models, as sellers often hide this for obvious reasons – and these have become problematic.

Perhaps the issue is with those ex-mining cards and the new driver. If the latter does indeed push for more performance – which anecdotally, some owners have mentioned getting slight frame rate boosts – maybe this is tipping some GPUs, which were almost dead anyway, over the edge. All of this is just speculation, naturally.

It’s also worth noting that there are scattered reports of coil whine after updating to the latest AMD driver, and of higher hotspot temperatures, which could again point to the GPU being pushed a bit harder. But we really need to wait and see if more reports of this problem with RX 6000 cards come in, now that the purported issue is out in the open.

If there does turn out to be a problem with the graphics driver itself, that won’t be a good look for AMD, considering that 2023 is hardly underway, and Team Red has already undergone a GPU crisis with its new RX 7900 XTX flagship and a problem with the cooling. A second crisis this early in the year would be pretty embarrassing, of course.



Source: TechRadar

Popular posts from this blog

Twitter has hidden the chronological feed on iOS again – and I'm furious

In a controversial move, Twitter has brought back a feature that removes the 'Latest Tweets' view for users on iOS, which is something that many users, including me, hated back in March 2022 – and it's now rolling out. The first time the company decided to do this, 'Home' would appear first in a tab at the top, and there was no way of changing it so that 'Latest Tweets' would be the default view. It was reverted back after the company said it was a 'bug' for iOS users. This time though, it's no bug. Instead, it's 'For You' and 'Following' where you can only swipe between them now, which doesn't make much sense for a platform where you're using the platform to keep up to date with who you follow. It's a bizarre change that makes me ask – who wants this, especially during a time when its new owner, Elon Musk, is bringing in and reversing changes almost every week still? This one change will have big consequenc

This new Linux malware floods machines with cryptominers and DDoS bots

Cybersecurity researchers have spotted a new Linux malware downloader that targets poorly defended Linux servers with cryptocurrency miners and DDoS IRC bots. Researchers from ASEC discovered the attack after the Shell Script Compiler (SHC) used to create the downloader was uploaded to VirusTotal. Apparently, Korean users were the ones uploading the SHC, and it’s Korean users who are targets, as well. Further analysis has shown that the threat actors are going after poorly defended Linux servers, brute-forcing their way into administrator accounts over SSH.  Mining Monero Once they make their way in, they’ll either install a cryptocurrency miner, or a DDoS IRC bot. The miner being deployed is XMRig, arguably the most popular cryptocurrency miner among hackers. It uses the computing power of a victim's endpoints to generate Monero, a privacy-oriented cryptocurrency whose transactions are seemingly impossible to track, and whose users are allegedly impossible to identify. Fo

Port of Lisbon hit by ransomware attack

One of Europe’s busiest seaports, the Port of Lisbon, has been hit with a ransomware attack that knocked some of its digital systems offline. "All safety protocols and response measures provided for this type of occurrence were quickly activated, the situation being monitored by the National Cybersecurity Center and the Judicial Police," a statement shared by the Port of Lisbon Administration (APL) with local media earlier this week said. The incident failed to impact the port’s operations, but did take its official website, portodelisboa.pt, offline. LockBit taking responsibility "The Port of Lisbon Administration is working permanently and closely with all competent entities in order to guarantee the security of the systems and respective data," the statement concludes. While the company doesn’t explicitly say it was targeted with ransomware, the LockBit ransomware operator has added APL to its leaks website, taking responsibility for the hit.  The databas

Code-generating tools could be more of a security hindrance than help

New research by a group of Stanford-affiliated researchers has uncovered that code-generating AI tools such as Github Copilot can present more security risks than many users may realize. The study looked specifically at Codex, a product of OpenAI, of which Elon Musk is among the co-founders.  Codex powers the Microsoft-owned GitHub Copilot platform, which is designed to make coding easier and more accessible by translating natural language into code and suggesting changes based on contextual evidence. AI-coding problems Lead co-author of the study, Neil Perry, explains that “code-generating systems are currently not a replacement for human developers”. The study asked 47 developers of differing abilities to use Codex for security-related problems, using Python, JavaScript and C programming languages. It concluded that the participants who relied on Codex were more likely to write insecure code compared with a control group. Read more > These are the best laptops for progr