Yes, System not freezing.
Had today the idea to test with a remote desktop connection.
When installing the driver, screen goes black and fan stops, but the remote desktop connection stays active. I can even reinstall the microsoft basic driver from the session and as soon as it is installed, the fan starts spinning again. For the image to come active again I still have to restart though.
What I didn't tried: Old drivers. There are too many. Has someone a good hint where to start from?
I suspect your GPU is faulty, but try drivers from 3 months ago or even older.
i tried 17.7.3, 17.4.4, 17.2.1 and 17.8.1 (least directly from gigabyte).
Always did the "select /amd/package/driver/ in the device manager" and always removing the driver with DDU before trying the next.
To no avail (poor SSD, so much unnecessary writing)
One thing: The autoinstallers of 17.4.4 and 17.2.1 say "error 182 - cant correctly identify graphiccard"
should i go to a friend and try another PSU, the card in another computer, a not HDMI monitor or does it looks like a hopeless case for return?
(recently, when softreseting after failed driver install, the next time windows comes up it returns to microsoft basic driver by itself)
Try another system/psu if you can.
Okay, you probably won't believe what I tell you now.
I said before, that remote desktop(RDP) was no problem, even with installed amd driver. Yesterday I made some more test and were even able to run FurMark over RDP. I thought it was strange.
Today I borrowed a HDMI projector. With DVI Monitor also connected I plugged the projector in (Windows Basic Driver) and ... nothing. Windows said there is nothing and the projector said: no signal on HDMI.
Okay I thought, install the driver. Same as all the time: GPU Fan stops, Monitor goes black .... wait, did the "no signal" message just disappeared. 3 seconds later I had my screen on the projector.
what the heck.
So either the DVI port doesnt work with all the tested drivers, or the (old, nameless) monitor can't work with win10+that driver by dvi.
Well, wanted to buy a new one anyway...
Verified it with HDMI and DVI monitors of a friend. both worked fine with the AMD driver.
For everyone who doesn't want to buy a new monitor / whos monitor is rather new: "google for "restore EDID" or similar.I won't try it though, as I planned to buy a new monitor anyway.
have a nice weekend