PC Drivers & Software

[bg4m3r]

I just got an MSI branded 6600XT, and a Samsung CRG9 monitor. What is happening is when the screen times out, the monitor goes to standby for about a minute, wakes up (you can hear the connection tone from the computer), checks the input(s), goes back to standby, wakes up, checks the input(s), goes back to standby, ad infinitum until the computer goes to sleep. Once the computer is asleep, it goes to standby. This does not happen connected to my laptop.

I've checked all the cables, in fact, the only one currently connected is the DisplayPort cable that came with the monitor. (I saw this suggestion in another post, and I did have one DP cable that didn't lock in on the monitor side, so I removed it and the HDMI cable, which also came with the monitor)

I am posting this in drivers and software because, at one point in troubleshooting, I did a clean install of the drivers, installed the WHQL driver, and it stopped doing it for about half a day (with all cables connected), then there was a driver crash, and now it's back to doing it. I submitted the crash report via the reporting tool and saved a copy of what it sent if anyone wants to take a look.

The desired setup is to have two DP connections from my computer to the monitor since it can do PBP, which allows me to split the screen into two monitors. Handy since I work in IT and if I need to have a vendor support person remote into my computer, I don't blast them with 5120 x 1440 screen. I don't know if this is a factor, but I don't think so since it's still doing it with only one cable connected.

Any suggestions would be appreciated! Thanks! Spec below for reference

Windows 11 Pro

MSI RX 6600 XT MECH 2X 8G OC

Ryzen 5 3600

MSI B550M PRO-VDH Mobo

16GB RAM

[bg4m3r · Accepted solution]

I've come across an answer, if not a solution, although it comes at the cost of having to completely reset up my system. There seems to be issues with both Windows 11 and the video drivers. I did a clean install of Windows 11. The behavior still happened, even with only the Windows self-installed drivers. Installed Windows 10. The behavior stopped with only the Windows self-installed drivers. Installed the current WHQL AMD driver package and the behavior returned. Uninstalled, and it stopped again. I have not tried the Pro drivers, which are available for this card for some reason, but I'm not sure it's worth the hassle. I don't seem to really use any of the AMD software functions, so going with the Windows-provided driver feels like the best bet right now, unless anyone has any arguments to the contrary.