Unsolved
This post is more than 5 years old
16 Posts
0
2298
U2415 screen & window re-drawing during wake from screen saver on win 7?
I didn't have this problem on the 2405FPW that was previously connected to this same machine & port. The U2415 is plugged into the same host DisplayPort on a Lenovo M900 running Windows 7. The 2405FPW was connected with a DP-DVI cable. The U2415 is connected with the Dell-supplied DP-mDP cable.
The problem is ALL of the windows are getting redrawn when the windows machine comes out of screensaver blanking. NOT from actual Sleep or Hibernation. The PC is configured to never sleep, nor put any device into any kind of low power mode. Hybrid sleep is also disabled. USB selective suspend is also disabled. The power option is set to "Turn off the display: 20 minutes" and the software screensaver is set to Photo Gallery with a 15 minute wait time. Logon on resume is selected.
The M900 uses an integrated Intel 530 display driver, and as a tiny machine there are no options to change the video card.
What appears to be happening is the display is being "disconnected" from the software and when it's "reconnected" on wake the OS then proceeds to start re-drawing all the windows. This is problematic as some of the windows are getting reloaded (browser sessions).
What's going on?
Should I avoid using the mDP port? If so, why? I can obtain a DP-HDMI cable if necessary.
wkearney99
16 Posts
0
October 12th, 2016 07:00
Anybody? Nobody? bump.
Looking into it further there also seems to be some window resizing going on. The windows appear to be getting resized to 1024x768 and moved to the upper left corner of the screen. As if the monitor resolution was changed and Windows had to readjust them accordingly.
I'm not changing any resolutions here.
I've also switched to using a DisplayPort to HDMI cable and that does not appear to have changed anything. The windows are still getting redrawn and resized when coming out of the screensaver.
wkearney99
16 Posts
0
October 12th, 2016 07:00
This looks interesting:
superuser.com/.../how-can-i-stop-windows-re-positioning-after-waking-from-sleep
wkearney99
16 Posts
0
October 12th, 2016 18:00
The solution was to delete these registry sections:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuration
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Connectivity
Delete all three and all their contents and then reboot. The three sections will be recreated and re-populated with just the detected monitors.
There were a number of entries in there from other monitors and something seems to have be confusing the OS.
It's entirely possible there was a 'virtual monitor' in the setup that may be related to a Splashtop remote access program. Haven't yet tried using that again to see if the problem returns.
wkearney99
16 Posts
0
October 13th, 2016 14:00
Nope, that wasn't entirely the answer.
The problem comes back, however, if you disconnect the monitor.
The OS/driver defaults back to creating this key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuration\NOEDID_8086_1912_00000000_00020000_31063^59443D0DD2FB2E13B124475375FA61A7
Which contains the following:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuration\NOEDID_8086_1912_00000000_00020000_31063^59443D0DD2FB2E13B124475375FA61A7]
"SetId"="NOEDID_8086_1912_00000000_00020000_31063"
"Timestamp"=hex(b):14,5f,73,7f,8c,25,d2,01
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuration\NOEDID_8086_1912_00000000_00020000_31063^59443D0DD2FB2E13B124475375FA61A7\00]
"PrimSurfSize.cx"=dword:00000400
"PrimSurfSize.cy"=dword:00000300
"Stride"=dword:00001000
"PixelFormat"=dword:00000015
"ColorBasis"=dword:00000002
"Position.cx"=dword:00000000
"Position.cy"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuration\NOEDID_8086_1912_00000000_00020000_31063^59443D0DD2FB2E13B124475375FA61A7\00\00]
"Flags"=dword:4101ff87
"VideoStandard"=dword:000000ff
"ActiveSize.cx"=dword:00000400
"ActiveSize.cy"=dword:00000300
"VSyncFreq.Numerator"=dword:03d239c8
"VSyncFreq.Denominator"=dword:00104dc0
"HSyncFreq.Numerator"=dword:0000ba54
"HSyncFreq.Denominator"=dword:00000001
"PixelRate"=dword:03d239c8
"ScanlineOrdering"=dword:00000001
"Scaling"=dword:00000004
"Rotation"=dword:00000001
The two values ActiveSize.cx and ActiveSize.cy are 1024 x 7, along with the PrimSurfSize.cx and PrimSurfSize.cy.
Whereas the data for the actual monitor is:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuration\DELA0BACFV9N67U1GRL_1F_07E0_4D^745AE9559C2DDA5CD5F441ADD30A9C40]
"SetId"="DELA0BACFV9N67U1GRL_1F_07E0_4D"
"Timestamp"=hex(b):a4,25,16,c7,8c,25,d2,01
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuration\DELA0BACFV9N67U1GRL_1F_07E0_4D^745AE9559C2DDA5CD5F441ADD30A9C40\00]
"PrimSurfSize.cx"=dword:00000780
"PrimSurfSize.cy"=dword:000004b0
"Stride"=dword:00001e00
"PixelFormat"=dword:00000015
"ColorBasis"=dword:00000002
"Position.cx"=dword:00000000
"Position.cy"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuration\DELA0BACFV9N67U1GRL_1F_07E0_4D^745AE9559C2DDA5CD5F441ADD30A9C40\00\00]
"Flags"=dword:0101ff87
"VideoStandard"=dword:000000ff
"ActiveSize.cx"=dword:00000780
"ActiveSize.cy"=dword:000004b0
"VSyncFreq.Numerator"=dword:092dda80
"VSyncFreq.Denominator"=dword:00273260
"HSyncFreq.Numerator"=dword:00012136
"HSyncFreq.Denominator"=dword:00000001
"PixelRate"=dword:092dda80
"ScanlineOrdering"=dword:00000001
"Scaling"=dword:00000004
"Rotation"=dword:00000001
Note it has 1920 x 1200 values for the ActiveSize and PrimSurfSize values.
Ok, to the OS or the driver wants to have "something" to fall back on in the event a monitor isn't connected. Which, apparently, is what it thinks is happening when the screensaver goes blank. Which it didn't do before. Likely because the previous monitor wasn't as "thorough" at turning something off so completely as to make the OS think it was gone.
Not sure what the next step in the fix is. Perhaps changing the PrimSurfSize will at least keep it thinking the size of the desktop shouldn't be changed. I'll try that.
DELL-Chris M
Community Manager
Community Manager
•
54.3K Posts
0
October 14th, 2016 08:00
Interesting issue. Apologies that our users did not chime in with their thoughts. The 2405FPW and the U2415 are both 16:10, 1920x1200 60Hz. What resolution is the Lenovo M900 running? Does the U2415 appear in the Windows Device Manager under Monitors? Did you update the Intel driver from Intel itself?
I think you are testing =
Lenovo M900 DP out --> U2415 DP to mDP cable --> U2415 mDP in
Can you test this to see if the same issue happens?
Lenovo M900 DP out --> DP to DP cable --> U2415 DP in
wkearney99
16 Posts
0
October 15th, 2016 12:00
Yes, tried it several ways. DP-miniDP, DP-DP, DP-HDMI. All produce the same result.
The computer is learning 'something' from the display that's convincing it to "logically disconnect" the display when the screensaver kicks in. This does not happen with the 2405FPW.
So, clearly, something between the two is being communicated differently. Enough that the driver on the PC side of things is making assumptions about what to do when the screensaver "turns the display off".
Note, again, I'm not actually putting the OS "to sleep". The OS itself it still running. I'm just looking to let the screensaver do it's thing and not leave the backlight powered on to the display. This does actually happen, it's just the screen-redrawing that's annoying and unwanted.
Right now the "fix" seems to be to manually edit the Registry to force use of the same 1920x1200 resolution for any entries setup as monitors in this registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuration
Both ActiveSize.cx, ActiveSize.cy and PrimSurfSize.cx, PrimSurfSize.cy need to be changed. This seems to prevent the OS from rearranging/redrawing the screens when it turns the display on again.
No doubt there's some blame to pass around here. Between the OS (windows 7 x64 pro), the driver (Intel HD Graphics 530 version 20.19.15.4300) and the monitor, there's something not quite right.
The whole dynamic monitor rearranging scenario is a bit of a hot mess. When it works, it's great. But when things are even slightly off... there's trouble.
DELL-Chris M
Community Manager
Community Manager
•
54.3K Posts
0
October 15th, 2016 18:00
Since still inside the 3 year warranty period, you may initiate a monitor exchange. Test the replacement before sending any monitor back to Dell. If the replacement monitor does not have the issue, keep it and send us the original monitor. If the replacement monitor has the same issue, I doubt that they both could be defective. Send the replacement monitor back to Dell. Something else must be the culprit.