Monitor Tests Forum

Full Version: Monitor resolution changing after sleep
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I didn't notice this until today, but when my computer awakes from sleep, my resolution changes, and colors look washed out. When I put it to sleep, and awaken it again, it goes back. If I restart, it goes back. Not sure what is going on here. I have the most recent drivers.
Is it washed out the same way it was before you disabled the extension block? Do you see separate "HD/SD" and "PC" modes when that happens? Is this with DVI or DisplayPort?
Yes. Exactly like that.

THis is DVI to HDMI
Do you see separate "HD/SD" and "PC" modes when that happens? Does CRU show the extension block is still disabled when that happens?
Okay, So after I restarted the computer, I put it to sleep. When I awakened it, the resolution went back to the washed out resolution. I only saw "PC" in the Nvidia control panel. When I went into CRU, it asked if I wanted it to make changes to my computer, I hit yes, the screen went black, and then back to normal resolution. The extension block wasn't checked when it went back to normal. But I could not check if it was checked when the resolution was washed out because the screen went black.

I am using a DVI to HDMI cable as well.

(04-15-2013 11:31 PM)ToastyX Wrote: [ -> ]Do you see separate "HD/SD" and "PC" modes when that happens? Does CRU show the extension block is still disabled when that happens?

My answer was a little long winded. But no. I don't see the "HD/SD" and "PC" mode separately. I only see "PC". And I could not check to see if extension block was checked when the screen was washed out. But I assume that it was checked. And when windows asked me if I wanted CRU to make changes, it unchecked it. Because when I hit yes, resolution went to normal.
CRU doesn't actually change anything when it starts. What happened was UAC triggered the video driver to redetect displays.

This sounds like a driver bug. For some reason, it's still applying limited range output when waking up from sleep even after disabling the extension block. You can try setting full range with this instead: http://blog.metaclassofnil.com/?p=83
Thank you so much.

So when I run it and it says "Set limited Range 16-235" or "Set full range 0-255" Do I click full range?
Yes, full range, and then you'll probably have to reboot for it to take effect.
Reference URL's