This is a two part question.
1) For whatever reason I am finding it impossible to stop the "NT Kernel Logger" and that means I am completely unable to use xperf. Something like:
xperf.exe -stop "NT Kernel Logger"
seems to do nothing (from an elevated command prompt.) If I run `xperf -loggers` before and after an attempt to stop it, I find NT Kernel Logger showing up in both outputs. What am I missing?
2) To get past #1, I started using Circular Kernel Context Logger. I was successfully able to start & stop this one and even managed to get some traces to analyze. When I bring up this .etl file on WPA UI, I find that I am unable to setup the proper symbol paths. Under the Trace menu both "Load Symbols" and "Configure Symbol Paths" are disabled. Anyone knows why? I do have my _NT_SYMBOL_PATH environment variable setup correctly but I don't know if that is good enough (as the stack traces don't show resolved symbols.)
1) For whatever reason I am finding it impossible to stop the "NT Kernel Logger" and that means I am completely unable to use xperf. Something like:
xperf.exe -stop "NT Kernel Logger"
seems to do nothing (from an elevated command prompt.) If I run `xperf -loggers` before and after an attempt to stop it, I find NT Kernel Logger showing up in both outputs. What am I missing?
2) To get past #1, I started using Circular Kernel Context Logger. I was successfully able to start & stop this one and even managed to get some traces to analyze. When I bring up this .etl file on WPA UI, I find that I am unable to setup the proper symbol paths. Under the Trace menu both "Load Symbols" and "Configure Symbol Paths" are disabled. Anyone knows why? I do have my _NT_SYMBOL_PATH environment variable setup correctly but I don't know if that is good enough (as the stack traces don't show resolved symbols.)