win 7 pro crashes upon waking from sleep

eight out of ten times when I wake my win 7 pro pc from sleep it'll BSOD within 30 seconds of waking. this didn't happen with the beta or RC, but started immediately upon installing the retail version. only happens when waking from sleep. otherwise the system is rock solid.

I've googled and binged for solutions and have found it's a rather common problem. but no valid solutions other than MS knows about it and don't use sleep mode. (my favorite was "turn off SATA." great solution if you never want to use the pc.) all drivers have been updated, bios updated, ran spinrite on the drive, swapped memory, video cards, etc. inspecting the dump records prove inconclusive on any particular problem driver or error.

anyone else having this problem? if so, any solutions found?

my pc is based on an asus M3A78-CM board w/ an AMD Phenom II X4 965, 3gig ram, 80gig SATA HD, nvidia geforce 9500 GT video. but in my searches it seems a lot of different people with different systems are also experiencing the problem.

thanks for your replies.

...joe

 

Have you tried using the following MS tool for a possible solution ...
Hidden Windows 7 Tool Troubleshoots Sleep Mode Problems

It's original intent was for notebooks, hopefully it will work for your desktop. It may provide some additional clues.
Good luck ... keep us posted.

 

There really shouldn't be any difference hibernating with a laptop or desktop from the OS viewpoint. Each requires a snapshot of all volatile memory states to be written to disk and then recovered at "wake up" time.

HP had a problem with some of its laptops some years ago, when insufficient disk space was allowed in the hibernation partition and it would then overwrite itself, as I recall.

So if you can increase the size of your hibernation partition, try that.

The fact that the bug is intermittent, you say, 8 out of ten times, indicates that certain states are being recovered correctly but others incorrectly. Could be a size problem.

The other trap can be a RAM error. As the image is reloaded, some RAM momentarily fails and you loose your stuff. Same thing can happen with a read error on the hard drive.

Bugger of a problem though, to diagnose, unless you get lucky. Strange MS didn't pick it up in testing if its the OS.

Cheers

 

Hi Codecutter,

Whether or not they did, I know for a fact it was reported to them. There's a whole host of "what the heck!?!" reports all the way from Longhorn to the W7 RC that M$ hasn't seen fit to address. They asked us to test W7, but from what I can tell, I believe it was just a marketing ploy to buy the RTM because I wrote with over a dozen "bugs" (from the user side) that, trolling through other W7 forums, haven't been addressed.

I have, and will continue to do so, advise people to wait until a SP and more tweaking sites come up before they switch. I refuse to take it Uncle Bill's way: I want to Burger King my OS.

 

Hi jpChris & Arie,

Good feedback. To expand on what I said about testing, this is a fault way outside the scope of the end user to diagnose and rectify. It's just one of those things you have to get right, like a driver or a bios.

It'll be some simple dumb problem, like an improperly calculated address, but hell, MS should get cracking and fix it.

Cheers

 

@Arie,

Thanks! Best I've had all day. However, I refuse to "get used to it ". I'll wait for the tweaks, thankyouverymuch.

 

Hi Arie,

AHA! An honest answer!

Actually, what I said about RCs being a ploy (I was being facetious) turns out to be the truth.

I wonder how many thousands\millions of people have to complain before they do something about it — if at all?