0

I am trying to measure reboot performance using Windows Performance Toolkit (WPT). The systems I am facing an error on have Windows 10 Threshold 2 on an SSD Drive.

The command I use is: 

xbootmgr -trace rebootCycle -noPrepReboot -postBootDelay 60

The error is as follows: After the reboot the system waits for 60 seconds and then for the next 300 seconds I see "Waiting for prefetcher" on the screen. Then I get an error saying 

"Gave up waiting for virtual prefetcher after 300 seconds. Could not wait for prefetcher."

I DO NOT see this error with the same version of the OS installed on a rotational drive (HDD) but only see it on SSD. I also ran the same command on an earlier version of the OS (Windows 10 RTM 240) and DID NOT face any issue.

I compared the following registry keys as well but there was no difference in the values for the keys: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SysMain

What is causing this error to occur specifically on SSD with Windows 10 TH2 but not on the other mentioned systems?

rkk817
  • 117
  • 1
  • 13
  • enable superfetch service again. It detects the SSD automatically and doesn't prefetch data from SSD (since Win8, changed from Win7). – magicandre1981 Mar 26 '16 at 07:30
  • The superfetch service is enabled (startup type: automatic) already and I'm still facing the issue. – rkk817 Mar 29 '16 at 00:02
  • 1
    have you tried WPRUI and selected here reboot under **Performance scenario**? do this work? – magicandre1981 Mar 30 '16 at 15:44
  • Yes WPRUI works. Thanks for the suggestion. But I'm still looking to resolve this issue for xbootmgr as I want to do this completely from the command line without any manual GUI interaction. I tried using WPR from the command line with the following command: wpr -start GeneralProfile -filemode -onoffscenario RebootCycle -onoffresultspath C:\reboot_Trace but I get an error : WPR.exe should be in the same path as WPRCLI.exe. Error code: 0xc5600601 – rkk817 Mar 30 '16 at 21:10
  • 1
    xperf/xbootmgr are dead and I doubt MS fixes anything. WPR.exe is included in Win10, so use the full path to the WPR.exe from the WPT folder: "C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\wpr.exe" – magicandre1981 Mar 31 '16 at 04:13
  • Yes I realized that silly mistake. I guess I will have to go ahead with WPR then instead of xbootmgr. Thank you for your suggestion. – rkk817 Mar 31 '16 at 18:30
  • so, the full path worked? – magicandre1981 Apr 01 '16 at 04:01
  • Yes. Changed the directory in command prompt to "C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\" and then ran the command successfully. – rkk817 Apr 01 '16 at 21:24
  • I've also asked MS about this issue and the Win10 inbox wpr.exe doesn't support on/off traces. They even expected an invalid argument error, but not this strange one. – magicandre1981 Apr 20 '16 at 17:49

0 Answers0