If I run Furmark with an up-to-date NVidia driver (398.11), CPU load might start at around 60%. Settings are:
1024x768, windowed, 8xAA
Dynamic Background, Burn-In, Extreme Burn-In, Post-FX
If I use CPU Burner then with 2 cores, CPU load due to Furmark might drop to ~30%, and after quitting CPU Burner, it might or might not stay there (or go back to ~60%).
If I use CPU Burner then with 4 cores, CPU load due to Furmark might drop to ~2.5%, and after quitting CPU Burner, it might or might not stay there (or go back to ~30%).
Wadu heck? Initially I though "Shoot, my Zotac barebone with a GTX1060 GPU has issues with drivers downloaded directly from NVidia." Because I saw an increase of CPU load during running Furmark from 30 to 60% after I updated from the latest manufacturers drivers (376.33). During more extensive testing I found out that CPU load created by Furmark does not mean anything performance-wise. FPS do not go down more than 1-2 frames (from 55 to 54 fps) due to high concurrent CPU load. Furmark might or might not stutter for a moment, but it will recover quickly and continue running with nearly the same performance unless concurrent CPU load actually reaches 100%.
I would really like to know what Furmark is doing in the background, that it can easily do without. I hope its not crypto-mining...
