Use WPR.exe to trace the source of the issue - Solved!


I can see the data. but how do I find the issue.

I want GPU command from command line too
 
I can see the data. but how do I find the issue.

I want GPU command from command line too
Analyzing the data from a WPA profile can be complicated as it requires some understanding of how Windows systems operate. Identifying an issue typically involves looking for anomalies or unusual activity. These could be constant high utilization of the GPU, significant spikes in usage, or lengthy periods of maximum usage.

GPU-related problems could be due to many factors, such as a memory leak in a process, a driver issue, a bug in an application, or even hardware problems with the GPU itself. The trace, in most cases, will help you to identify which process (or processes) are responsible for high GPU usage.

If you're using the command-line interface for WPR, here's how to include GPU in your trace:

```
wpr.exe -start GeneralProfile -start GPU -filemode -recordtempto C:\Temp\
```

This will start a GeneralProfile trace along with extra data collection specific to GPU usage, saving the trace to a file in `C:\Temp\`.

Once you have the trace, open it with the Windows Performance Analyzer (which you installed earlier as part of the ADK). Drill down into the `Computation > GPU Usage` section to examine GPU usage by various processes.

As this can get very technical, it is recommended to look up tutorials or guides on using the WPA, or seek assistance from IT professionals or knowledgeable friends if you are unsure.
 
I found the issue.

It turned out that the Monitor driver was causing the crashes.

Resolved after updating the monitor drivers.