- March 17, 2008
- 1,353
- 306
- Home Country
- Netherlands
Hi all,
I really wanna stay with Windows 7 x64 cause I think it has a lot of good pointers across the whole thing but I cannot for the life of me get S3 sleep working on multiple machines.
Now I know that MS has rewritten this part for the sake of performance so I guess that it's just prone to be buggy because of the rewrite.
But anyways my issue is that entering standby is no problem at all but resuming from standby is another matter. The system will startup everything like fans, hds etc except the screen will remain in a sleep state (so it never receives a signal).
I have tried MCE standby tool and that bit of software actually is really great and solved my desktop's (also win 7) sleep problem but that was something diff. (didnt wanna enter sleep because of realtek onboard audio cr*p).
I'm getting to a point I do not know what to do. There are no pointers what so ever in windows even viewer what's causing all this. The weird thing is that it's incosistent as heck too. I've had it working couple of times but now it just doesn't. So when it stopped working I decided to try a reinstall but then it started happening directly from the start. Well I did install ati vid drivers and some updates but not much more.
Standby always worked beatifully on XP, no probs whatsoever. I skipped vista for the HTPC so I do not have any experience with that one on this machine. I have turned the internet upside down and found several causes;
1) My vertex, heard people reporting that they had issues with the vertex and earlier Win 7 (beta) builds
2) Software settings inside windows. I already tried fiddling with a lot of power settings and disabled stuff like windows defender (reported by some to be the cause and the fix)
3) Believe me or not but even the CMOS battery can be the cause according to some. But I guess that only applies to hybrid sleep, I use pure S3 only
4) I have a couple of Samsung F drives in there, they take a while to spinup. Might take too long for windows, so windows tries to access these drives too soon? I do have windows set to store stuff like the pagefile and temp files on a seperate HD instead of the vertex.
If you guys have anything more for me to try please feel free to post cause I'm getting kinda clueless here.
I really wanna stay with Windows 7 x64 cause I think it has a lot of good pointers across the whole thing but I cannot for the life of me get S3 sleep working on multiple machines.
Now I know that MS has rewritten this part for the sake of performance so I guess that it's just prone to be buggy because of the rewrite.
But anyways my issue is that entering standby is no problem at all but resuming from standby is another matter. The system will startup everything like fans, hds etc except the screen will remain in a sleep state (so it never receives a signal).
I have tried MCE standby tool and that bit of software actually is really great and solved my desktop's (also win 7) sleep problem but that was something diff. (didnt wanna enter sleep because of realtek onboard audio cr*p).
I'm getting to a point I do not know what to do. There are no pointers what so ever in windows even viewer what's causing all this. The weird thing is that it's incosistent as heck too. I've had it working couple of times but now it just doesn't. So when it stopped working I decided to try a reinstall but then it started happening directly from the start. Well I did install ati vid drivers and some updates but not much more.
Standby always worked beatifully on XP, no probs whatsoever. I skipped vista for the HTPC so I do not have any experience with that one on this machine. I have turned the internet upside down and found several causes;
1) My vertex, heard people reporting that they had issues with the vertex and earlier Win 7 (beta) builds
2) Software settings inside windows. I already tried fiddling with a lot of power settings and disabled stuff like windows defender (reported by some to be the cause and the fix)
3) Believe me or not but even the CMOS battery can be the cause according to some. But I guess that only applies to hybrid sleep, I use pure S3 only
4) I have a couple of Samsung F drives in there, they take a while to spinup. Might take too long for windows, so windows tries to access these drives too soon? I do have windows set to store stuff like the pagefile and temp files on a seperate HD instead of the vertex.
If you guys have anything more for me to try please feel free to post cause I'm getting kinda clueless here.