Windows 10 [2014 - 2017]

Status
Not open for further replies.
Hooking up DVI makes monitor power saving work perfectly again, although I don't understand why win10 should care what kind of interface the monitor is connected through; it should be abstracted away via the driver from the part of the OS that handles sleeping and waking the display I would think. Go figure! :p

Win10 does feel a tad rushed, with all the fairly visible bugs. I never had very many issues with past MS OSes; apart from the (infuriating) issue with early Win8 that made it impossible to turn off autocorrect, which made typing in a foreign language all but hopeless. :p
 
Grall said:
Hooking up DVI makes monitor power saving work perfectly again, although I don't understand why win10 should care what kind of interface the monitor is connected through; it should be abstracted away via the driver from the part of the OS that handles sleeping and waking the display I would think. Go figure! :p

Win10 does feel a tad rushed, with all the fairly visible bugs. I never had very many issues with past MS OSes; apart from the (infuriating) issue with early Win8 that made it impossible to turn off autocorrect, which made typing in a foreign language all but hopeless. :p
Click to expand...

It sounds like a the DP on your monitor isn't fully compliant or at least doesn't have an EDID that is PC friendly. This isn't uncommon with some monitors and monitor manufacturers.

For, one, unlike previous connectors DP is fully plug and play. When it is disconnected the computer knows it is disconnected and can safely remove the display. DVI can do that also. But DP can also signal to Windows when it goes into a low power state (like sleep mode or when it is turned off, but not physically disconnected), in this case Windows can and will remove the display. DVI can't do this, as long as it is physically plugged in, Windows must keep the display "active" in Windows. Hence, why even if you turn off a DVI monitor you can still access and navigate to any windows that was on that monitor.

With DP monitors and an OS that properly understands DP, when the monitor is turned off or goes into a really low power state, Windows can remove it and rearrange your desktop such that the DP monitor is no longer accessible. This has some unfortunately side effects however in that windows get resized based on the new display configuration (if it has a lower resolution than the monitor that was turned off) and of course all windows get moved to whatever monitors remain on. Some monitors actually have an option to maintain a connection with the PC even if it is turned off or in a deep sleep mode so that it can emulate the behavior of DVI.

So, what's this have to do with your situation? It sounds like the monitor is properly letting Windows know it is going into sleep mode with DP. But isn't properly accepting the wake up trigger.

What gets frustrating is that many of these DP issues can be resolved by using a custom EDID file rather than using the monitor's hardware EDID. Unfortunately the only way to do that (that I know of) is to use the professional drivers for Quadro (Nvidia) or Fire Pro (AMD) which allow you to use an EDID file to bypass the monitor's EDID.

I wish that existed for consumer video card drivers as it would solve a major issue with my 4k monitor in a multi-monitor setup. I swear if the new AMD drivers include the option to bypass the monitor's EDID like the professional drivers, I'm switching from Nvidia to AMD as soon as it is released.

Regards,
SB
 
@Silent_Buddha my system and monitor sleep worked perfectly fine up until I upgraded to Windows 10. I never had a single issue with my monitor waking up on Windows 7.
 
Windows 8 and Windows 10 instituted proper controls for DP plug and play WRT monitors. Prior to that it was treated as just a different DVI and many of the DP specific EDID features were ignored/not implemented.

Part of it was also how quickly IHV drivers implemented those in their drivers as well. So early on with Windows 8, they didn't have the behavior I described previously, but as the generation went on the driver's started to properly use the DP specific EDID information.

For example, while AMD were getting this all working correctly in their drivers, they had a workaround for bypassing EDID, if there were problems. A lot of people used this early on to avoid the Monitor behavior I described before. Once it was working correctly, they removed the workaround from the catalyst controls. And now you're basically stuck with what I described in my previous post.

One side effect of this is that.

1) With properly configured DP EDID by monitor manufacturers it produces behavior that is correct, but not necessarily desirable by end-users.
2) It exposes incorrect DP EDID configurations in some monitors. Sometimes to the benefit of the consumer (if it avoided the first situation), but sometimes not.

Hence, why there's some monitor manufacturers that put in monitor options that get around some of the PnP DP features for situation [1] to try to bypass features that aren't always desirable for consumers.

This isn't to say that this (case 2) is actually what is happening for you, but it's a possibility as it's something that was experienced by Windows 8.0/8.1 users as graphics drivers matured and correctly implemented DP EDID features.

Regards,
SB
 
Last edited:
I'm running a DP + DVI setup here. I've run a GTX 970 but am currently using a 6970. I've had no sleep problems with Win10 or before.

The only problem I've had is the DP monitor is sometimes slightly blurry on power up, but I think that's a monitor problem. I have to power cycle the monitor a few times. It happens pretty rarely. A few times a month. The monitor is a BenQ BL3200PT.
 
My monitor (Samsung S27A850D, as previously mentioned) is a number of years old now, so it was fairly early with DP support. IIRC, I bought this thing in 2011 or maybe 2012? *shrug* Anyway, it worked perfectly all through my Win8 years, nary any issues whatsoever with it. It was only with 10 that this bullshit started.

Of course, the issue with windows fucking up all the window sizes and positions every time the monitor has to be power cycled is driving me absolutely buggo too. It's not just that it fucks with the sizes and positions, the size and position of windows is random too! Never once do I find my browser window in the same place when powering the monitor back up.

Windows being clever and REMOVING the display is just plain bad. It's the same shit that happened when hotplugging was added with Intel HD audio and windows removing unplugged audio jacks, confusing software in the process. You'd think they would ever friggin learn, but no... :(
 
I have a different problem relating to monitors & sleep mode:
I seem to have about 50:50 chance that my primary monitor blanks but doesn't go into power save when I Sleep the PC, then after a while I get a random noise effect over part of the screen.

Same thing has been happening on multiple OSes XP (?maybe not, can't remember)/XP64/Win7/Win10, across multiple generations of ATI/Radeon cards, different DVI cable/ports.
My former primary monitor (DVI) got wine spilled on it early on & some of its buttons don't work so I always blamed it on that but this monitor has since become my secondary & hasn't had the issue once since.
Primary is now a DP & has same issue.
But I've never heard of anyone else with the same issue so I dunno wth.

I think its some kind of bug in how ATI stuff shuts down the primary port while Sleeping, so the monitor misses the Sleep mode trigger and then the last blank screen held on the monitor corrupts/times out causing the noise.
 
@hoom
The random noise thing sounds similar to HDCP-related finickyness. Except when that happens to me I get it over the whole screen.

The "monitor doesn't power down when told to" bit I've had a couple times over the years with AMD boards. Most recently with recent catalyst drivers on my R290X, up until the point where I nuked my win8->win10 install and re-did it all from scratch. The monitor would appear to enter sleep, then power back up again and show nothing but a black screen (with the backlight shining through faintly, as is the tendency of LCD displays...)
 
Silent_Buddha said:
Windows 8 and Windows 10 instituted proper controls for DP plug and play WRT monitors. Prior to that it was treated as just a different DVI and many of the DP specific EDID features were ignored/not implemented.

Part of it was also how quickly IHV drivers implemented those in their drivers as well. So early on with Windows 8, they didn't have the behavior I described previously, but as the generation went on the driver's started to properly use the DP specific EDID information.

For example, while AMD were getting this all working correctly in their drivers, they had a workaround for bypassing EDID, if there were problems. A lot of people used this early on to avoid the Monitor behavior I described before. Once it was working correctly, they removed the workaround from the catalyst controls. And now you're basically stuck with what I described in my previous post.

One side effect of this is that.

1) With properly configured DP EDID by monitor manufacturers it produces behavior that is correct, but not necessarily desirable by end-users.
2) It exposes incorrect DP EDID configurations in some monitors. Sometimes to the benefit of the consumer (if it avoided the first situation), but sometimes not.

Hence, why there's some monitor manufacturers that put in monitor options that get around some of the PnP DP features for situation [1] to try to bypass features that aren't always desirable for consumers.

This isn't to say that this (case 2) is actually what is happening for you, but it's a possibility as it's something that was experienced by Windows 8.0/8.1 users as graphics drivers matured and correctly implemented DP EDID features.

Regards,
SB
Click to expand...
Understood, thanks for the info @Silent_Buddha. I'm running an LG 34" 21:9 display that's only a year old so I would have hoped all would be kosher!
 
Grall said:
My monitor (Samsung S27A850D, as previously mentioned) is a number of years old now, so it was fairly early with DP support. IIRC, I bought this thing in 2011 or maybe 2012? *shrug* Anyway, it worked perfectly all through my Win8 years, nary any issues whatsoever with it. It was only with 10 that this bullshit started.

Of course, the issue with windows fucking up all the window sizes and positions every time the monitor has to be power cycled is driving me absolutely buggo too. It's not just that it fucks with the sizes and positions, the size and position of windows is random too! Never once do I find my browser window in the same place when powering the monitor back up.

Windows being clever and REMOVING the display is just plain bad. It's the same shit that happened when hotplugging was added with Intel HD audio and windows removing unplugged audio jacks, confusing software in the process. You'd think they would ever friggin learn, but no... :(
Click to expand...

There's a few workarounds for that. If it's just a single monitor then the fix is to set the resolution of the Null display that windows puts in when there is no monitor attached (DP sleep/turned off). You can look it up. If it's multiple monitors it gets more tricky. In those cases you need to figure out a way to either replace the EDID with a EDID file on the computer or put in a virtual VGA monitor and have that mirror the DP monitor. You can either use a VGA dummy plug if you have VGA ports or DVI-I ports (DVI-D will not work). Or you can use software to put in a virtual monitor (iDisplay does this but does not work on Win10).

Regards,
SB
 
hoom said:
I have a different problem relating to monitors & sleep mode:
I seem to have about 50:50 chance that my primary monitor blanks but doesn't go into power save when I Sleep the PC, then after a while I get a random noise effect over part of the screen..
Click to expand...

yup have that exact problem with me but in Intel HD (wont sleep monitor, just blank)
and got the noise issue on my HD 7770 (looks as if the GPU will go kaput, like Xbox 360 when gonna RROD)

but since yesterday its working fine with HD 7770. Has not tried with intel HD though...
 
I posted this over in the Win10 devices thread too, but it probably belongs here... Windows 10 TH2 has some cool new features that you may not know about: http://www.theverge.com/2015/11/13/9727870/microsoft-windows-10-november-update-hidden-features

The most interesting addition for Windows Phone users (such as myself):
If you have a Windows Phone then Cortana gets a lot more useful with the latest Windows 10 update. A new option in Cortana's settings section lets you enable missed call notifications. That's useful if you simply miss a call, but it also lets you reply to calls with text messages. Cortana will use your phone and its number to send the text, and you can even say "text Joe Bloggs" to initiate a text message without having to miss a call.
Click to expand...
Those of you in the Apple ecosystem have enjoyed this feature for years; it's about time Microsoft got around to copying it. :)
 
Guessing it has to do this to perform a kernel swap... I also saw you can pull down the "November ISO" straight from the Win10 media creation tool. All of my Win10 PC's were upgrades; my gaming rig still has a few hardware (storage controller) niggles and my Lenovo laptop has somehow broken the Windows Store icon in a way that I can't seem to fix.

I might just go ahead and wipe + reload them both with the updated ISO and be done with it.
 
I had to reinstall XFi drivers because it did something to them and the Creative apps wouldn't load. Also had some errors from 8gadgetpack and Classic Shell. Some startup apps were removed from startup.

No major problems so far though.
 
yes, it is, WU will download a compressed image of the OS to install.

I had to reinstall gpu, printer, Ethernet and cpu-z (lol)
creative xfi titanium drivers strangely remained untouched...
 
Status
Not open for further replies.

Similar threads

S
High system interrupts usage on windows 8.1 caused by Intel graphics driver
Replies
1
Views
7K
Davros
D
G
Samsung SyncMaster S27A850D Mini-review
Replies
2
Views
8K
Grall
G
A
Holy Wall of Text: My impressions post Playstation 4 (PS4) unveil
2 3 4
Replies
70
Views
20K
(((interference)))
I
Arwin
Official E3 Microsoft Conference Thread 2010
15 16 17
Replies
339
Views
44K
corduroygt
C
O
Unreal creator Tim Sweeney: "PCs are good for anything, just not games”
3 4 5
Replies
91
Views
18K
Mobius1aic
M
Back
Top