• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Strange Windows 7 screen saver behavior

Fardringle

Diamond Member
Background info first:
New install of Windows 7 Pro.
Dell OptiPlex 7040 desktop.
Three identical (old) 19" Dell monitors attached to the computer.
Monitor 1 attached to DVI port on AMD Radeon 340X video card.
Monitor 2 attached to Display Port (via DVI adapter) on AMD card.
Monitor 3 attached to Display Port (via DVI adapter) on the motherboard.

In the display settings, 1 is in the middle, 2 on the left, 3 on the right.

All three monitors work perfectly inside Windows. However, when the screen saver kicks in the weirdness starts. This happens with any screen saver that I have tried including all built in Windows 7 screen savers anda couple of third-party screen savers as well. The screen saver animation shows up on monitors 1 and 3, but the desktop stays visible on monitor 2. It seems like Windows is tracking that the screen saver is running on Monitor 2 since it takes about 10 seconds for the Bubbles screen saver to start moving bubbles over to monitor 1 from where they should be starting on the left edge of monitor 2. It just doesn't show the animation on the screen.

If I move monitor 2 to the middle or to the right of 3 in the display settings, then it shows the screen saver animation just like the other screens, but of course that makes it unusable while on the actual desktop since the screens are out of order. Moving it back to the correct position on the left in the display settings makes it stop showing the screen saver again.

I know that I can just physically change the position of the monitors on the desk and reorder them in the display settings to make it work, but I'd like to find a solution to the actual problem since it's bizarre and I don't like it when things don't work the way they are supposed to..
 
The reason it's annoying me so much is that there are literally thousands of similar (and many identical) builds here and this is the first time any of us have seen this particular problem. The fact that this doesn't happen on other machines makes me think the issue in that MS post was resolved some time ago, but I can't figure out why this one machine does it when none of the others in any of our facilities have the same problem, especially when they are all built from the same system image.
 
Back
Top