I looked at the trace, and the two culprits that show up above all others are in DirectX calling DpiFdoDpcForIsr, and afd.sys (network stack) calling AfdTimeoutPoll. I noticed an interesting usage pattern of consistent behavior of chrome.exe and OneDrive.exe processes on the system that correlated almost exactly with the DPC timeline, and there were almost zero changes when OneDrive spiked up in activity. That would indicate the usage is being driven by chrome.exe (it's not Chrome's fault, but that's the process running and driving the behavior) - given that Chrome is a browser (thus generating network traffic from time to time, and in the background) and is also GPU-accelerated by default (thus driving DirectX calls), I'd say that this will come down to either (or both) graphics or network card drivers. It's less likely to be the Intel NIC drivers than the AMD video drivers for a Radeon HD 5700, but I would strongly recommend getting the latest Windows 10 certified drivers for both from Gigabyte, and barring that, from Intel or AMD directly.
Has Sysnative Forums helped you? Please consider donating to help us support the site!
