Originally Posted by Tonza
I assume you have your GPU overclocked? Any unofficial tool makes this sleep issue, since it messes idle clocks aswell (AB, Trixx etc..). I have readed that issue gets fixed if you overclock with just CCC limits. Im getting also the sleep issues with a twist
If my OC aint stable, and driver crashes -> It wont recover, artifacting continues in every game until i reboot PC. Im gonna myself try today uninstalling all unofficial tools and see if the problem persist. If not, ill let it be, happens so random anyway. Hope you understand what i just wrote, english aint my primary language
No my GPU isn't overclocked at all..
I only have my CPU overclocked, nothing else.
Originally Posted by pharcycle
sorry to labor the point, but did you just reset the clocks or do a complete restore to default for the bios? There are many options that control power management states of the processor which people often set/clear without fully understanding what they do and these can stop the system from resuming. However thats usually only a problem with sleep/resume cycles but thought it worth to check anyway.
When your OS gets in a mess, anything could happen really so its possible, if you have a spare hard drive anywhere you can use to install windows onto it would let you test this.
One thing that may help shed some light onto the problem could be to use a remote desktop application to login your system from a laptop or another PC and see if its just the display that isn't working or if the entire system has come down. If you run win 7 pro, then you just need to enable remote desktop access and use another 7/vista machine from within the same network subnet or failing that you could install TeamViewer and use that from any PC in the world to access your computer remotely. If you get a desktop up you can at least probe the hardware and see what you GPU thinks is going on. You may even be able to wake the computer.
Oh, and one more thought, do you have your keyboard and mouse plugged into a hub in the monitor or in the back of the computer? If the monitor hub, it could just be that when the display goes to sleep it disables the hub therefore never allowing you back onto the computer! If you hit the power button instantaneously to initiate shutdown does the screen come back to life to show the shutdown sequence?
Well, when I first built my PC, it was on a super outdated BIOS version. Version 0906. When I updated the BIOS firmware, I made mental notes of what to set to what and I restored those settings after the BIOS flash. But I'm not sure of what exactly to set to though. Because I bought my PC at a DIY store which they also helped me set up the BIOS and stuff. It's only after I brought it home and tinkered with it that I slowly learn. But I'm still a noob though.
I don't have a spare hard drive but I have reinstalled Windows 8 Pro on this PC quite a number of times while playing around during the stress testing of my OC phase. And this sleep wake problem has mostly been there the whole time. One thing I do notice though is that the chances of it not waking when I am running Prime95 overnight is a lot lower. For the whole past month that I've had my PC, I think the number of times it failed to wake while running prime95 was less than 5.
Using a remote desktop application would have been a good idea, except I just realized this morning that when it fails to wake from idle, the keyboard is unresponsive too. When I press the caps lock or num lock or scroll lock buttons, the respective lights don't change at all. This probably means that the PC has hung, am I right to say that? It's not just the graphics card that isn't responding. The entire PC isn't responding..
I have both my keyboard and mouse plugged directly to the MoBo's I/O at the back. The only connection between my monitor and PC is the single DVI cable. And no, pressing the power button doesn't wake the PC. Nothing does. I have to press and hold the power button till it turns off.. Sigh.
Originally Posted by jellybeans69
Probably a a driver issue/ati issue as i have same thing once in a while on my sapphire 7850 , card itself runs perfectly though.
Did you ever manage to fix it? How does yours happen? When you sleep it or just by leaving it idle like mine?
Originally Posted by connectwise
I don't think it's your graphic card at all. From what I remember before, Asus mobo's had a RMA issue where one of the motherboard voltages was too low or too high it would not wake up from idle. However I don't think this is only an Asus issue where I had the same thing while on a gtx260 from back in the day (and other more recent setups). My issue was solved from tinkering with the bios power option, where I changed it to S1+S3 power options (as far as I can remember) that made my black screen wake up after idle. I could be wrong and my memory's too fuzzy to be precise on the issue. However check and tinker with your bios power options and see if any of the setting change helps.
How long ago was this RMA thing from? Well, apart from this issue, my PC is completely stable no issues with day-to-day use or any hardcore gaming at all. It never crashes once I stabilized the OC, no BSODs, GSODs, graphics card runs fine, everything is fine except for this one problem.. One blood boiling problem..!!
Originally Posted by MrNishi
Im pretty sure its the same as setting hdd to sleep = never but Im at work and cant look at the setting but look under advanced power setting for a "turn power off to hdd" and make sure it is set to never. Pretty sure youve already did it but maybe worth looking in there again.
Yep I've had that set to never from the start. Put to sleep is set to never too. I only set "Turn display off after.." to 10 minutes.
Originally Posted by mickeykool
I just skimmed thru the thread and I had this issue as well. Seemed to work after i just disabled screen saver and let display turn off after XX min.
If no go then try swapping cables? I'm running 3.2 betas and all work fine w/ my settings.
I've never had screen saver enabled! I only have the "Turn display off after XX mins" feature turned on. And nope, I've tried swapping cables, replugging the DVI cables, turning off the monitor's plug. Nothing works.
Does the 13.2 betas fix anything? I'm on 13.1.