How to analyse "startup from hibernate"

Question

Note this is NOT a duplicate of:

I care about the time from hibernate, not from boot up. My machine restarts just fine, but returning from hibernation can take up to 15 minutes!

So far I've tried BootRacer, and the Windows Event Logs, but both of these only track data from reboots - not from return from hibernation.

It's not clear to me whether Soluto might do any better, but given that a review I found says ...

Installing Soluto requires a reboot, during which it analyzes your system's boot process

... so I'm not particularly hopeful.

How can I analyse this? Heck, I'll even take "How can I record data about this, without using a stopwatch?" ! All of the data sources only look at reboots :(

Install the WPT (part of the Win10 SDK: https://dev.windows.com/en-us/downloads/windows-10-sdk), run WPRUI.exe, select **First Level**, under Resource select **CPU usage**, **DiskIO**, **FileIO** and under **Performance Scenario** select **Hibernation/Resume**. **Number of iteration** can be set to **1** and click to start. This hibernates the device and resumes it and captures the activity. Zip the large ETL file into zip/RAR file, upload the zip (OneDrive, dropbox, google drive) and post the share link here. — magicandre1981, Nov 17 '16 at 16:29
@magicandre1981 ooh, that sounds promising ... will give it a try, and report back. — Brondahl, Nov 17 '16 at 16:50
ok, if you got the trace share it. if you never used it before you don't see anything in the files. — magicandre1981, Nov 18 '16 at 05:12
Cool, so, file is uploading currently. Could you 'promote' your comment to an answer, since this definitely appears to be the sort of Hibernate performance analysis that I was looking for. Once you've done so, I can edit in the appropriate notes for using the Win 8 version (I already had the Win8 SDK installed, which comes with the same program). I tried opening the log in Event Viewer which failed utterly - it gives me 1000s of blank entries and nothing at all meaningful in the entries that *are* present. For my future reference ... how are you planning to analyse the file? — Brondahl, Nov 19 '16 at 09:49
Ran the cycle twice, and it seems to take ~20-25 minutes each time: #1: https://drive.google.com/open?id=0B0aDHVQY87OedmZUZmxzLUZVMFU #2: https://drive.google.com/open?id=0B0aDHVQY87OeRTZJUGFMWE5lN00 — Brondahl, Nov 19 '16 at 10:03
hm, the trace doesn't show anything useful. you use old Crucial C300 SSDs. Make sure you use the latest firmware. — magicandre1981, Nov 19 '16 at 20:23
That's a shame. Could you let me know what you were using to examine the log files, please? I have other traces from when it's recovering much quicker and I'd like to compare them. — Brondahl, Nov 21 '16 at 22:54
double click on the ETL to open it with WPA. In WPA click on profile->apply->browse catalog and select **Hibernate.wpaprofile** and here it shows Hibernation itself as long part. so no suspend/resume of services/drivers is slow — magicandre1981, Nov 22 '16 at 05:22
WPA = Windows Perf Analyzer = https://msdn.microsoft.com/en-gb/windows/hardware/commercialize/test/wpt/windows-performance-analyzer, right? — Brondahl, Nov 22 '16 at 13:52
Great, thanks. I think this is the best approach available for my problem, so if you want to promote your comment to an answer, then I'll 'Accept' it? — Brondahl, Nov 22 '16 at 16:39

score 1 · Accepted Answer · answered Nov 23 '16 at 05:23

To analyze the HIbernation/Resume, you have to use the Windows Performance Toolkit, which is part of the Windows 10 SDK.

Now run WPRUI.exe, select First Level, under Resource select CPU usage, DiskIO, FileIO and under Performance Scenario select Hibernation/Resume. Number of iteration can be set to 1 and click on start.