Hey all,
I'm having the same problem here: I can always successfully stand by at least once after a fresh restart. But usually by the second or third stand by, it progresses to that light blue "Preparing to stand by" screen and just hangs until I do a hard shut down.
I have tried several things fruitlessly:
-Disabling bluetooth radios.
-Turning off wireless before standby.
-Even though I have never received the "nv" error in my Event Viewer, I followed SebastianV's procedure for updating the NVidia drivers, and it seemed to work for a bit--I had a streak of about 15 successful stand bys in a row immediately after the update, but then the stand by failed once, and ever after, my stand by hangs again on the 2nd or 3rd try after a fresh restart.
So I tried something else:
I tried what SebastianV suggested by going to the event viewer (Control Panel -> Administrative Tools -> Event Viewer -> System). I do not receive an "nv" error. Instead, I get an error whose Source is DCOM and whose Event designation is 10010. The error repeats every 2 minutes for the duration of the time I allow the computer to hang on the "Preparing to stand by" screen.
I did some googling about the DCOM error, and followed the instructions on this page:
http://blogs.msdn.com/distributedservices/archive/2009/01/21/dcom-error-10010-in -the-event-logs-and-sluggish-server-performance.aspx
So I created a restore point and then went ahead and edited the permissions on the HKCR\CLSID registry key to look like those presented on the above site. Upon restart, Windows operated absolutely glacially. However, it seemed to fix the standby problem: I managed 5 stand bys in a row without the computer freezing up. Windows was moving so slowly though that it was basically worthless, so I reverted back to the restore point I had created.
After having reverted back to the restore point, the stand by problem occurs just as it did before. Except now, the Event Viewer doesn't log a DCOM error when there's a failed stand by. In fact, now it doesn't log any error at all in association with the failed stand by.
Does this ring a bell with anybody? Do you think I was on the right track by editing those registry permissions?
Thanks much