cancel
Showing results for 
Search instead for 
Did you mean: 

Community Resources

Quasxen
Journeyman III

Waking Monitors Causing GPU Driver Crash and System Reboot

I've seen this issue reported over the years, but nothing related to more recent times, so wanted to add in my situation. I'll put the specs at the end.

 

I use a TV for my main monitor and a regular monitor for my secondary. The TV is plugged in to the single HDMI port and the Monitor is in the DP4 port. Per the card (and during the boot process) the Monitor in DP4 is the primary monitor. Once Windows takes over, the TV is switched to be the primary monitor.

 

After the system is idle for long enough, the monitor and TV will turn off (normal). Now, here's the interesting part, the order in which I wake the screens matters. If I turn the TV back on, wait for it to show "No Signal" then move the mouse to wake the monitor, all is fine. However, if I move the mouse first then turn the TV on, the screens will start to turn on, but then go black and the system reboots. Once the reboot is complete I get a notification that the GPU driver was reset to Default after an unexpected crash.

 

I've tried all the previously posted "solutions" to no avail. This issue has been occurring for months at this point. It's like the system can't handle waking the screens and setting the correct primary screen at the same time

 

SPECS:

Driver - 24.10.1
GPU - 7900xt

CPU - Ryzen 7 5800x3d

OS - Windows 11, 24H2, build 26100.2161

RAM - 32Gb

PSU - 850w

 

 

1 Reply
BigAl01
Volunteer Moderator

If you leave the small monitor as the primary monitor and the TV as the secondary monitor, does the system wake properly with either the mouse move or the TV remote power button?  Is there a reason you can't keep the TV as a secondary monitor?


As Albert Einstein said, "I could have done so much more with a Big Al's Computer!".
0 Likes