Windows7 & Server2008 R2 Service Pack1 is available!
Missileman
Orlando, Florida Icrontian
Just got the notification. Geniune Validation is of course required
Link to all versions is here:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c3202ce6-4056-4059-8a1b-3a9b77cdfdda
Link to all versions is here:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c3202ce6-4056-4059-8a1b-3a9b77cdfdda
0
Comments
The previous system shutdown at 10:12:16 PM on ‎2/‎22/‎2011 was unexpected.
followed by
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Nothing seems amiss in my powercfg energy report... I've updated all my drivers... Anything else I'm missing?
Not running an SSD; just a standard SATA3 drive. I have an Asus P7P55D-E LX mainboard, and an i5-760 if that helps at all too.
The system has been rock-solid (and still is, except for this crash when trying to sleep). I'm trying to dig in a bit and see if I can trace what exactly is causing the problem, but these near-shutdown/sleep/hibernate issues are always tricky to pin down..
I would have rolled back to a restore point before SP1 at this point, but somehow they're all gone. Protection was still on for my system drive, but all the restore points were gone and the disk space usage for restore points was set at 0, instead of at 3%, where I'd left it. Ffffffffuuuuuuuuuuuuuuu... Not liking SP1 so far.
I should mention, I tried to run the driver verifier to see if there was something corrupt... Yeah, never do that. It forced my system into a blue screen reboot loop; absolute pain in the ass to fix, but I did. Apparently I'm not the only one who has had that particular issue though, so I mention it here for other people's benefit.
I have the same mother board and the same thing happened to me after I loaded SP1. I have not found a solution for it yet.
I've been going back and forth with MS support now since I posted this. Still no solution. The support person indicated that it was some conflict with the chipset drivers. We're trying to find a work around. I'll let him know that the motherboard does seem to be a factor. Oh, and uninstalling SP1 does make the problem go away.
Thanks for replying though, now I know I'm not alone.