I'm sorry, my fault - I didn't read it. I will try to use my meager knowledge of English and the help of an translator.
Problems with the RX 480
Hello everyone. Recently, it seems that after updating to drivers 21.3.1 (WHQL), problems with the video card began.
System:
- Intel Xeon e3 1270v2
- Asus P8Z77V-LX
- Sapphire RX 480 8gb NITRO+
- Corsair Vengeance DDR3 16gb 1867mhz
- Сorsair VS650w
- Windows 10 Home x64 20H2, build number 19042.868
- Samsung SyncMasterSA350H 60hz Monitor
How it manifests itself:
During games, periodically, in random moments, there were flickers of the screen (black screen), in the corner of the monitor the inscription HDMI, that is, as if I pulled out and inserted the cable back.
In the browser, when I watched the video and on the desktop, blue dots periodically appeared on different parts of the screen. Sometimes they flickered, sometimes they just lit up. A couple of times, the screen flickered pink.
At this stage, I was sinning on the HDMI cable and on the selected pixel format (the default drivers set YCbCr 4:4:4, I changed to RGB 4:4:4), because when I changed it back and forth, I had these blue dots on the screen, but on YCbCr they were not. This didn't solve the problem: black screens were still appearing, I rebooted to safe mode and removed the AMD cleanup utility drivers. I rebooted, put 21.3.1 (WHQL) again, this time I did not change the pixel format in the settings, but just in case I disabled the "Providing an HDMI connection" and "HDCP" items. That didn't help either. I went to Google with this question and read about the chip dump there. It is useful to check the Furmark video card-it passes without any problems, it warms up to 82 in the peak, no artifacts. Just in case, I pulled out the map, disassembled it, blotted the thermal pads (they were a little runny, but not dry), wiped off the traces of the drips with alcohol, applied a new thermal paste (the last time I changed it six months ago, now it was clear that it was "tired", but not yet dry), and put it back together. Just in case, I changed the HDMI cable to the previous one. Furmark runs smoothly without artifacts with max. with a temperature of 78, the idle temperature is also 4-6 degrees less than before replacing the thermal paste. In the browser, too, everything was quiet for a while, in Warframe I played - everything is fine. It occurred to me that the truth was in the cable and in the funny thermal pads.
Today, a couple of hours ago, I sat down to play Minecraft. For about an hour, everything was fine, then the black screen flashed sharply a couple of times and remained there. The game is running, you can hear it in the background. I restart the PC, the Asus logo is shown, then the black screen. I waited a minute (the system is on the SSD, it should already start), I restart again. After the Asus logo, I get a BSOD with the text "Your PC failed to properly disconnect, the required device is not connected or unavailable, error code 0xc0000225". I reboot, immediately climb into UEFI, it opens and in it, in the dark areas, I already see my favorite blue flickering dots, some blue horizontal stripes have been added to them. I exit UEFI, reboot, and go back to UEFI - there are no blue dots. I reboot and wait for the system to boot, the system does not boot again and gives a BSOD with the same text, I choose to boot in safe mode, google the error code, I understand that because of the driver. In safe mode, everything started without visual problems, I remove the driver using AMD cleanup utility, restart the PC. The system started, Windows in a couple of minutes put some of its driver on my video card (in the device manager, in the video card, version 27.20.1034.6 is written, the development date is 21.08.2020). I Googled, many also had problems with the latest driver. I decided to write here. While I was writing all this, I didn't experience any visual problems. The whole problem is really in the latest version of the driver, or do I still have something with the video card, such as a chip dump?
I bought it in the store at the end of 2016, the warranty has already ended...
