What's new
Carbonite

South Africa's Top Online Tech Classifieds!
Register a free account today to become a member! (No Under 18's)
Home of C.U.D.

Windows 10 version 1803 killing GPU's DON'T UPDATE

KangarooMike

Well Known Member
Rating - 100%
21   0   0
Joined
Dec 5, 2015
Messages
184
Reaction score
31
Points
2,135
Location
Edenvale
Is the newest version of windows killing AMD RX 5XX GPU's
Current system specs
Ryzen 7 1700, 8GB ram, RX 560 2G
So I updated to the latest version of Windows 10 on 21/05/2018 and it was fine for the first two days. I loaded up games fine and rendered videos as per usual. On Saturday the 26th I launched a game and there were fuzzy hashes all over my screen with the colours being displayed incorrectly and after displaying that for 1-2 minutes windows crashed with no error code. So I reboot and it gets to the desktop then does that again so I remove my RX 560 and swap in my GTX 650 and no problems. So I take it to Matrix warehouse to replace it because it is under warranty, there was no power there so we couldn't test it there so I left it there.

Later that evening I get a message from my friend (He has an RX 580 8G) asking what happened to my card before I took it in to be replaced. I repeated my story to him and he says that it just happened to him. His card has also died.

If this has happened to anyone else please post it in the discussion below with what card you have
 
Im on the latest Win, and don't have any of those problems...
PC runs for hours on end.
Either im lucky or you and your mate just super bad luck.
 
Im on the latest Win, and don't have any of those problems...
PC runs for hours on end.
Either im lucky or you and your mate just super bad luck.
I think it only affects RX 5XX cards because my friends with GTX 10/9XX cards are fine
 
My friend just updated and then his died

And how does that prove anything?

Your graphics card died 5 days after a Windows update and suddenly you're certain that the update is bricking AMD cards, any other reports of this, did the driver have anything to do with graphics, what specifically in the update could cause this etc etc???

You can't jump to conclusions based off no evidence.
 
Bah, mine didn't want to update anyways. Tried twice and failed both times borking WIndows although it managed to recover completely. Now the update has gone missing, it says I am up to date.
 
Doubt it is Windows 1803. I have a RX570 in one rig and an RX580 in another. Both have updated to Windows 1803 about 3 weeks ago and no issues with either.
 
LOL

All i got to say, sorry man but i put no stock in any of this. Dont see how any update could kill your gpu short of a bad flash of its bios
 
I have a Vega 64 and have the update running and no issues here..... the only thing i can think of is u and ur bud are running the same cracked game which had a malware on it that used ur gpu's for mining as that is known virus with cracked games.
 
ALLEGEDLY - Windows 10 version 1803 killing AMD GPU's DON'T UPDATE

There, I fixed it for you :)
 
I am still going to test this out still but i do know for a fact that my 970 dp port after the update.
Been running the gpu for a while on my dual screen setup with no issues, update was downloaded and restarted to install it no dual monitor.

I have already done the ddu uninstall, reinstall latest and older drivers and nothing.
I plan to do a clean install on a different machine to see if my card still works.
 
No chance in hell its PHYSICALLY killing opr harming your GPU. I'll bet you 700 & 22 million, 6 hundred & 27, listen carefully, 100 and 12 , 7teen , hundred.

What I'll bet my ass is happeneing, is that the update has either corrupted your GPU driver or tried to install a new driver and that new driver isn't so lekker. AMD are known for shoddy drivers on a good day.
 
Maybe radeon is just bad cards #GreenTeamFanBoi... Or maybe Nvidia deviced a plan on "killing the enemy" xD.... OR MAYBE ILLUMINATI IS INVOLVED

illuminati.jpg
 
I am still going to test this out still but i do know for a fact that my 970 dp port after the update.
Been running the gpu for a while on my dual screen setup with no issues, update was downloaded and restarted to install it no dual monitor.

@ScorpioMan86 I have already done the ddu uninstall, reinstall latest and older drivers and nothing.
I plan to do a clean install on a different machine to see if my card still works.

This may sound weird, but I promise you its the truth - your DP and DVI port have different BIOS's , I'll assume that in the update, there is some DirectX / nvidia driver that isnt so lekker & isn't playing well with the vBIOS.

"
  1. NVIDIA Source BIOS Version: DP: 84.04.31.00.B3, DD: 84.04.31.00.B2
"
source: GV-N970G1 GAMING-4GD (rev. 1.0/1.1) | Graphics Card - GIGABYTE Global

You need to connect 1 screen, flash BIOS, and then (somehow) flash the other one? Maybe after flashing the currently working one, the other will work (doubtful but worth a try). Might need to flash via Ubuntu.
 
Last edited:
Running an RX 480 8GB here, triple display Eyefinity and on the latest Windows update with no issues. Just wanted to report here if there is indeed a bug. Which, I believe, there isn't.

Cheers :)
 
No chance in hell its PHYSICALLY killing opr harming your GPU. I'll bet you 700 & 22 million, 6 hundred & 27, listen carefully, 100 and 12 , 7teen , hundred.

What I'll bet my ass is happeneing, is that the update has either corrupted your GPU driver or tried to install a new driver and that new driver isn't so lekker. AMD are known for shoddy drivers on a good day.

there are posts all over the net about this update messing with display drivers, specially Intel display adapters which i've personally seen 3 times now.

Lets not take the piss out of him cause he thinks it physically broke the card but he is on to something.
 
there are posts all over the net about this update messing with display drivers, specially Intel display adapters which i've personally seen 3 times now.

Lets not take the piss out of him cause he thinks it physically broke the card but he is on to something.
I remember a few months ago a windows update caused this to happen to my PC, I just had to remove the driver and install what ever the latest AMD driver was at that time, I also thought for a moment my gpu was faulty.
 
Sounds like an AMD vulnerability more than anything else. I updated as soon as it came out, 4 weeks later and it's still fine.
 

Users who are viewing this thread

Latest posts

Back
Top Bottom