-
Notifications
You must be signed in to change notification settings - Fork 705
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unable to start collect #2105
Comments
@bian6 The links above look like a malware. I would recommend not doing anything with the content. ❗ From the log you posted I see Also can you share how are you starting the collect? |
yes,there is no previous trace file(s) in |
Yeah, I was not expecting existing file to be the case. PerfView would overwrite @brianrob Anything rings the bell from the log ? |
I have not seen this before. Can you please try with an older version of PerfView just to rule out any recent changes? https://github.com/microsoft/perfview/releases/tag/v3.1.13. My suspicion is that this won't matter based on the stack, but want to be sure. Also, is it possible that there is a permissions issue with the target location? I've seen things like that before result in similar errors. Perhaps try to save the trace to the OS drive in your user profile directory? |
This happended a lot in Windows 7, because here only 1 #635 also shows this |
The NT Kernel Logger is still the issue, also you still use this name. @brianrob If you don't support Windows 7 any longer in Trace Event/Perfview you can define your own name like
@brian6 make sure you don't run any software that use ETW like ProcessExplorer, ResMon, ProcMon |
I have tried excute perfView---abort, and restart the computer, and used in different computer, the above error will occurs alse, the version is [PerfView and TraceEvent 3.1.15]. and the computer version is win10 ,
The text was updated successfully, but these errors were encountered: