Vista Unstable after Resume from Hibernation

When resuming from hibernation state, no new applications launched actually open.

Clicking on IE appears to do nothing. Hitting Ctrl-Shift-Esc fails to launch Task Manager, although, oddly, multiple Task Manager notification icons appears in the taskbar (but no actual Task Manager windows open). Applications that display a splash screen appear to do so but then fail to actually launch their main window.

However, applications that are already open appear to function reasonably properly.

But even more mysteriously, about 1 to 2 hours after resuming, the system suddenly stablizes and all applications that had been attempted to be launched open (including all the multiple iterations of Task Manager).

Performance monitors (if opened before hibernation) don't indicate any applications with extraordinary CPU or RAM utilization.

Vista is updated to SP1 with all the latest drivers (per and most recent BIOS.

My guess is that there's a stuck application somewhere. Any suggestions on how to find it and eliminate it?
Who is Participating?
Davis McCarnConnect With a Mentor OwnerCommented:
Process Explorer will let you drill down through everything
You might also want to check Driver Manager
Your problem sounds as though it is driver related and is being caused by a power management problem.
Davis McCarnOwnerCommented:
Get WinPatrol and use the Startup function to disable startup items (right-click, then disable)  Almost everything is fair game and you can put them back with right-click and Enable.
RedmondGuyAuthor Commented:
Thanks, Davis.

Unfortunately, even after disabling every single startup item (even the hidden ones), AND then going into MMC and disabling every service allowable (and then rebooting, obviously) the problem still persists.

So now I'm thinking maybe it's a driver issue? If it's not an app and it's not a service, what's left?

My first assumption was the GPU -- perhaps preventing applications from creating main windows. It's an NVIDIA GeForce 8400M GS running the latest WHQL-certified release: ForceWare v.174.31. But uninstalling the NVIDIA Driver item in Control Panel has no effect (although it's not clear to me that this actually does remove the driver).

Any other suggestions?
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Davis McCarnOwnerCommented:
Go here and enter your service tag number.  See if there is a BIOS upgrade, especially; but, also look for other drivers.
RedmondGuyAuthor Commented:
Thanks, but as noted above, the BIOS is the latest release and all drivers are entirely up to date.
Davis McCarnOwnerCommented:
If you have the fingerprint reader, another site said you need this for Vista SP1:
I have also seen several Vista systems where the incomplete setup of the reader's software caused interminable security errors in the event viewer.  Do you have any of those?
RedmondGuyAuthor Commented:
I have no security errors in the event viewer but updated to that driver anyway, just in case it was newer than the update on Dell's site that had already been applied.

Unfortunately, the problem still persists.

The oddest part, as I mentioned above, is that about 90 minutes or so after restoring from hibernation, the problem appears to resolve itself and all launched but stalled applications suddenly spring to life. This behavior is 100% consistent.

Are there no profiling tools that can detect an application blocking other apps?
RedmondGuyAuthor Commented:
Thanks for these. I was already using Process Explorer but couldn't really see anything relevant. Driver Manager seems like an interesting utility (same for its sister app, Service Manager). FYI - The download link on the site you reference is broken. Looks like the author let his domain registration lapse. After a few minutes of searching I found a mirror.

Anyway, Driver Manager didn't really help me resolve the problem so I just used brute force to uninstall and reinstall a whole slew of drivers. I'm not entirely sure, but I *think* it might have been the Bluetooth stack.

So, while the suggestions above didn't quite replace good old fashioned hard work at the end of the day -- :-) -- I do appreciate the effort and the help.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.