Great advice-- maybe we're a little closer to figuring it out then! For reference, I'm running windows 7 x64. I did a search for "procmon.exe" and ran it. It asked for elevated privileges which I granted. I made sure the logging was running (ctrl e). At first running from an elevated command prompt: xbootmgr -trace hibernate -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\TEMP complained that it could not start the trace file so I disabled all my Otaku software (DeskSpace and TopDesk) and ran the above command in a bat file with ping -n 10 localhost as a delay, enabling by ctrl e the log at the moment the xbootmgr command hit. This probably wasn't necessary-- it probably was the Otaku stuff, but I don't know. I'm putting this all down in case someone else runs into the same problems-- it could be this, or it could be running in a bat file, either is worth a shot. At any case, it hibernated and resumed successfully, so I filtered as you said by duration, with a minimum of 1s. I got back the following So is that right? Searchindexer is the problem? I wonder why that would be the case. In any event, it's very close to my delay.. I will try to disable search and let you know how that goes! Thanks MagicAndrei [Edit] I verified that it does indeed speed up hibernation in a huge way by disabling the Windows Search. This is disappointing because while I don't use the search all the time, when I do need to use it I really need to use it. I wonder if this is a common problem, and if there is a way to optimize this a little bit so I can have a decent hibernation resume and at the same time be able to search efficiently.