Windows 7 moves/resizes windows on monitor power cycle

Anonymous
2010-10-08T22:13:48+00:00

I have a new W7 ultimate install on a new PC (AOpen DEX4501 w intel GM45 graphics). I have installed the latest Intel graphics drivers 8.15.10.2202, and all relevant windows updates.

It is connected via HDMI to a Grundig Misuro HD TV. My resolution is set to 1600x900, windows recommended resolution is 1920x1080 but this displays badly so I don't use it.

When Windows sleeps, or I turn off (then later on) the monitor, most windows are moved/resized to the upper left with the lower right at 1024x768.

Firefox, Excel(2003),Explorer windows resize/move, Outlook(2003) did not move/resize.

I have a Samurize (Gadget like) display on the right which someimes get relocated to the top left, but not this morning. The windows resize/move also happens when Samurize is not running.

I have found three other entries related to this;

They don't seem to have been resolved for a long time.

This is a Windows monitor power managment issue, can it be fixed please it is very annoying.

I won't be recommending W7 to others with such issues outstanding.

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2010-10-09T02:55:58+00:00

I have found a work-around.

Using Sysinternals ProcessMonitor I found that Windows was accessing the following Registry path;

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuration

My system had three entries;

DELF003YY7707BR0MUL_30_07D7_6A^9A3774EB79DEE3E3E38496CC7DF4D936

QHD32000001_31_07D6_D5^63E1ABDD175E7871DCAEB710418A0F75

SIMULATED_8086_2A42_00000000_00020000_1010100^CDE365D1B3F0942F0CF38BFB8E127AB4

Under each is a tree called "00" two of the keys are

PrimSurfSize.cx

PrimSurfSize.cy

Under "00" was another branch also called "00" two of the keys are;

ActiveSize.cx

ActiveSize.cy

The first two of the configs (ie DELF00... & QHD3...) the above keys were 1440x900,

so they were not involved.

The third (SIMULATED...) were set to 1024x768.

I changed these to 1600x900 and the problem was solved.

Further I changed resolution (via control panel) to 1920x1080, the moving/resize issue returned,

but the lower right corner was set to 1600x900, ie the SIMULATED... settings.

So for some reason one of the configs does not get set correctly.

I don't know why there are three configs, I have only ever used one monitor.

Hope this helps someone out there...

Was this answer helpful?

400+ people found this answer helpful.
0 comments No comments

236 additional answers

Sort by: Newest
  1. Anonymous
    2015-10-05T00:51:48+00:00

    Hello everyone,

    First off I wanted to thank MichaelAtOz for his post, I have searched everywhere on the internet and posted my problem to several forums to no avail, I have the Samsung U28E590D 4K monitor and the EVGA GeForce GTX 960 2GB GDDR5 PCI Express 3.0 Graphics Card Model: 02G-P4-2968-KR and I have been experiencing this hell to its full extent as well for the past 4 weeks since I purchased this monitor and upgraded to this GPU.

    Not only did my Windows all resized and repositioned themselves to the top left of the screen, but my desktop icons also moved around and Windows also redrew the taskbar and tray icons every time my monitor came back from sleep or when I would simply turned it back on, to add pain to sorrow my IRC client HexChat totally crashed every time the redraw occurred, I was about to return my monitor when I finally found this thread!

    I'm running Windows 10 build 10558 and it has been happening with the previous official builds as well, after applying every fix on this thread such as deleting all the monitor profiles and the two Simulated ones, then shutting down the monitor and fixing the registry key values including the one suggested by turpojurpo to change the Nvidia NV_Modes registry key from 2560x1600 to 3840x2160 (thank you for that too) the issue has been greatly reduced, at this point the only problem still remaining is that the Windows resize a little and still tend to go slightly to the top left of the screen, but after all the mess I had to deal with I find this bearable now.

    I have one question though, I have changed the Stride KEY value to "3840" on the three Registry Keys I have, that is the "NOEDID" one, the one for my "Samsung Monitor" and the "SIMULATED" one, should I change this to "2160" instead? perhaps that's the way to fix my remaining problem?

    Any help or suggestions would be greatly appreciated!  I'm amazed after 5 years this issue continues to be unresolved and it's obviously NOT a Windows 7 ONLY issue at all.

    Was this answer helpful?

    0 comments No comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  3. Anonymous
    2015-10-02T05:49:58+00:00

    Just for people, who use dual-boot (Linux + Windows, boot with grub2) :

    I had in the past 2 monitor connections - DVI + DisplayPort to my ACER ProArt (1920x1080)

    When the grub menu is displayed and the monitor was activated via DisplayPort the cursor moved 2 entries up/down in grub menu. Switching to the DVI connection I could access to all entries of the boot menu.

    After removing the DVI connection I could select all entries of the boot menu.

    So a 2 cable solution might create a new problem.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-10-01T13:15:36+00:00

    I did these changes, and I also changed DwmClipBox settings, rebooted Windows 10, but no luck.

    Maybe you could try the two cable setup that I mentioned earlier (DisplayPort plus HDMI).  This worked for me, but maybe it was just my particular configuration.

    Was this answer helpful?

    0 comments No comments