cancel
Showing results for 
Search instead for 
Did you mean: 

X570-E Gaming and dual monitor problems

gabriel21st
Level 7
I recently did a fresh build with an AMD processor after being team Intel forever. For the most part, everything works great. One problem I started having was a blue screen during the Windows 10 bootup process with the error VIDEO_MEMORY_MANAGEMENT_INTERNAL. It turns out the Windows "fast startup" option was causing this problem. After disabling, I no longer had blue screens during boot.

However, another problem remained. Every time I boot, my second monitor is not detected by Windows for about 5 minutes. After that time the primary monitor goes dark and Windows makes the notification sound of a device being disconnected. Then either one of two things happen next: the second monitor is finally detected, or it fails to detect and I have to reboot for it to work.

I messed around with various boot options in the BIOS and eventually, as a last resort, disabled fast boot. This actually solved the problem.

This is all happening on a fresh install of Windows and clean-installed NVIDIA drivers (DDU used). Latest BIOS version as well (1407 as of writing).

Anyone have similar experiences? Recommendations to address the issue? Or am I just unlucky?


  • Ryzen 7 3800X (stock)
  • ROG Strix X570-E Gaming
  • Team Force 2x8GB DDR4-3200 (XMP/OC not enabled yet)
  • GIGABYTE GTX 1080 Ti Waterforce
  • Boot drive is Samsung 850 Pro
9,470 Views
15 REPLIES 15

gabriel21st
Level 7
Perhaps you were right... the problem started occurring now even with fast boot disabled. Ran the commands and nothing was changed. My next step is to try a new cable, waiting for it to arrive in the mail. After that I suppose I have no choice but to try another fresh Windows install. This only annoys me so much since this is already a fresh install..

gabriel21st wrote:
Perhaps you were right... the problem started occurring now even with fast boot disabled. Ran the commands and nothing was changed. My next step is to try a new cable, waiting for it to arrive in the mail. After that I suppose I have no choice but to try another fresh Windows install. This only annoys me so much since this is already a fresh install..


try set csm in bios to enable, :cool:

jaunkst
Level 7
Okay, So i am seeing something similar and Its driving me crazy. For me my monitor will eventually receive a signal after some time of rebooting, and power toggling. Once the monitor comes on I do not have any problems with restarts, shutdowns, and power switching.

But, after i dunno 20mins - 1hr or more my PC will return to not wanting to cold boot and send a signal to the monitor.

1. So far i have upped the voltage on my ram a little.
2. Set the XMP profile to 3200
3. Disabled fast boot in the bios
4. Disable fast boot in windows
5. Disabled some power optimizations when system is off
6. Enabled some crap that helps booting the system under extreme low temperatures * doubt this helps but i'm shooting in the dark at this point.

Its madding because no benchmark, or stability test is discovering any issue with this machine. Its just this one very odd and annoying behavior with cold boots after it sits for awhile.

I won't know if I have manage to fix the issue until the morning, because unfortunately this isn't something I can just test without letting the system go completely cold.

jaunkst wrote:
Okay, So i am seeing something similar and Its driving me crazy. For me my monitor will eventually receive a signal after some time of rebooting, and power toggling. Once the monitor comes on I do not have any problems with restarts, shutdowns, and power switching.

But, after i dunno 20mins - 1hr or more my PC will return to not wanting to cold boot and send a signal to the monitor.

1. So far i have upped the voltage on my ram a little.
2. Set the XMP profile to 3200
3. Disabled fast boot in the bios
4. Disable fast boot in windows
5. Disabled some power optimizations when system is off
6. Enabled some crap that helps booting the system under extreme low temperatures * doubt this helps but i'm shooting in the dark at this point.

Its madding because no benchmark, or stability test is discovering any issue with this machine. Its just this one very odd and annoying behavior with cold boots after it sits for awhile.

I won't know if I have manage to fix the issue until the morning, because unfortunately this isn't something I can just test without letting the system go completely cold.



Nope did not work, took 10 mins of rebooting this morning to get anything. i don't think this is a fast boot issue anymore.

jaunkst wrote:
Okay, So i am seeing something similar and Its driving me crazy. For me my monitor will eventually receive a signal after some time of rebooting, and power toggling. Once the monitor comes on I do not have any problems with restarts, shutdowns, and power switching.


Well, I'm a little relieved to hear I'm not the only one. Sounds like you have the exact same problem I do, with the same "remedy" of having to power cycle until things work. Unfortunately I haven't got around to trying a new cable yet, so no progress from me. My gut tells me it's not going to help though..

Siaganmaya wrote:
try set csm in bios to enable, :cool:


Already tried that, no dice.

gabriel21st
Level 7
Many months later.. I hate to thread necro, but I've found a "solution" to the problem.

I guess it's not an issue with fast boot after all, since the effect is the same with it on or off. The solution I've found is to power on both monitors before booting up the PC. Ideally, boot up the PC before the monitors go into sleep mode. Doing this has consistently allowed both monitors to be detected properly without needing to reboot.

Hope this helps anyone else with this annoying issue.