Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>You could try to see if you can find something with <a href="http://blogs.msdn.com/b/pigscanfly/archive/2008/02/09/xperf-a-new-tool-in-the-windows-sdk.aspx" rel="nofollow noreferrer">Xperf</a> that is close to your periodically problem, do not run your application but keep the programs open that would normally run besides your application. You could also try to do it again with the application running but it could give a cluttered view.</p> <ol> <li><p>Start the tracing, do this in an elevated prompt.</p> <blockquote> <p>xperf -on BASE+LATENCY -stackWalk Profile</p> </blockquote></li> <li><p>Wait for a fair amount of time to be sure that the problem is traced.</p></li> <li><p>Stop the tracing and open it like this.</p> <blockquote> <p>xperf -d trace.etl<br> xperfview trace.etl</p> </blockquote></li> <li><p>Analyze by looking at the graphs and consulting tables of specific intervals and see if you can find something that is related to the problem, the highest chance on finding it would be in the DPC and Interrupts section. But it might as well be something odd at the CPU or I/O section. Good luck!</p></li> </ol> <p>Also more information on <a href="http://blogs.msdn.com/b/pigscanfly/archive/2008/02/09/xperf-a-new-tool-in-the-windows-sdk.aspx" rel="nofollow noreferrer">Xperf and how to obtain it</a>, hopefully this delivers results.</p> <hr> <p>If not, you can alternatively try <a href="http://graphics.stanford.edu/~mdfisher/GPUView.html" rel="nofollow noreferrer">GPUView</a> which has been used for improvements in DWM,<br> this is also included next to Xperf with the Windows Performance Toolkit so you can easily try both!</p> <blockquote> <p>log v </p> <p>... wait for a fair amount of time to be sure that the problem is traced ...</p> <p>log </p> <p>gpuview merged.etl</p> </blockquote> <p>In the case that gpuview gets out of memory you can try to add "/limit 3" or remove the v.</p> <p>Read the documentation of the tools if you are stuck somewhere.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload