Windows 10: Monitor keeps going on/off and resetting to 1024x768

I have an HP Monitor pavilion32 and see it in the device manager. However, There are problems with the display adapter, built into the MSI mother board, a Radeon RX 560 series. For some reason as of late, the monitor will constantly connect and disconnect you hear the system beep and eventually may reset to 1024x768. It cannot be changed. The only way to reset it is to deinstall or disable the display adapter Radeon RX 560 and then reinstall/re-enable. That works temporarily. But then this cycle repeats itself randomly. Need help asap as I don't know how to make this stop. What might als

:)

 

HP monitor keeps going to sleep

Hi Ruth,

Incorrect power settings or options can cause your computer's monitor to constantly go to sleep. For us to properly isolate your case, provide more information by answering these questions:

• Which Windows version/build are you using?
• Have you made any significant changes to your device prior to this happening?
• Do you also remember changing or modifying your monitor's default settings?
• Have you recently installed any updates?
• What troubleshooting steps have you done so far to resolve the issue?

Let us know these details so we can move forward to rectifying your concern.

 

Trouble with 2 monitors

Hi Tim,

Thank you for posting your query in Microsoft Community.

I suggest you to change the settings to Extended Monitor and check if it helps.

Please follow below steps:

• Right Click any ware of the Desktop, and launch Personalization.
• Go to dual monitor settings under personalization, and change it Extended Monitor.

Please get back to us for future support, we’ll be glad to assist you further.



Thank you.

 

Display Resolution set to 1024x768 when not using the monitor

I work at a software company. We have three computers with windows10 that share one monitor using a KVM switch. These three computers run automated tests every night (i.e. opening a browser, navigating to our website, and testing various parts of it to make sure it works as we expect).

The problem is that the two machines that are not currently selected on the KVM switch use a resolution of 1024x768, while the one that is selected is using 1920x1080. We want all three machines to be using 1920x1080.

I've read from an answer to a similar question that "Windows creates Simulated monitor with default resolution of 1024 X 768" and I believe this is what we're seeing. I've gone into the registry editor to change the resolution settings for these simulated monitors to be 1920x1080. I see the correct resolution being used when I start the automation test run manually and switch the monitor to a different machine. However, when the three machines restart and begin running the automated tests on their own at the end of the day, I'm still seeing the same problem when I come in the next morning.

There are a few solutions that we know we could do ourselves if there isn't an easy answer:

1. Give each machine its own monitor so we remove the need for the simulated monitor. This is not ideal because space is limited. Additionally, our automation tests are growing in number and we will likely need to get more machines in the future.
   
2. Make our automated tests work on the 1024x768 resolution. Our automation tests should work regardless of resolution, but the software running these tests for us seems to be very finicky when it comes to running tests on a different resolution than they were made on. The tests work sometimes but not consistently. We're planning on updating this automation software soon so it is possible the update will fix this. Another option would be to refactor all of our tests and write them with the resolution 1024x768 in mind. This would be time-consuming and we would have to be using this small resolution on our machines while we write the tests, which in my opinion would be annoying.
   
3. Have a batch file on each machine that runs a script to change the resolution to 1920x1080 before the tests start. The only drawback I'm currently seeing is that we would need to download this script, which runs the risk of getting a virus.
   

We're currently looking into option 3 for solving our issue, but if you guys know of other things I can try, let me know. I can also clarify or provide more details if needed.