none
xperf and xbootmgr registry locations used for boot tracing RRS feed

  • Question

  • This is a somewhat unusual request, but I have a system that essentially 'snaps back' to a known state on reboot. This obviously defeats the boot tracing done through xbootmgr, however I can handcraft exceptions to what is snapped back. Generally I would use procmon to indentify what needs to be preserved, however xbootmgr reboots the platform rather quickly and I'm just too slow to find out what it did. The idea is to analyze boot times on this platform using xperfs excellent analytic capabilities, but so far I can only do this by turning off the snapback feature entirely, which is not really of interest.

    I have a current list that includes

    Windows\System32\wbem\Logs, 
    
    Windows\System32\winevt\Logs, 
    
    HKLM\CurrentControlSet\Control\Session Manager\Memory Management, 
    
    HKLM\CurrentControlSet\Control\WMI\GlobalLogger,
    
    HKLM\CurrentControlSet\services\rdyboost\Parameters,
    
    HKLM\Software\Microsoft\WBEM\CIMOM,
    
    HKLM\Software\Microsoft\Windows\CurrentVersion\Run, HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce, 
    
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Prefetcher,
    
    and HKLM\SOFTWARE\Microsoft\Dfrg
    
    
    
    

    Am I missing anything obvious?

     The actual error message from xperf is:

    "Couldn't load state from registry.

    Couldn't find user-mode logger in active logger list."

    So there is a key in the registry I am missing. Any clue would be appreciated.

    Mark Roddy Windows Driver and OS consultant www.holl

    Thursday, March 31, 2011 9:40 PM

All replies