One core always at 100%

apexnewg

Prominent
Oct 8, 2017
3
0
510
Hello! During gaming I noticed a worse performance than I would expect. After checking a bunch of things I realized that no matter how many times I restarted / time went by (it's been about a week since I built my PC) the first thread on my CPU (0) would always be at 100%

Here's an example while running Cinebench (single core):
https://i.imgur.com/Y5TZXTr.png

It's the same for gaming and I'm worried about the same thread constantly being pegged at 100% during all my games, rather than switching around etc

If I change the CPU affinity of the process and disable CPU 0, then re-enable it it will look like this:
https://i.imgur.com/ZKXBE01.png

I've been trying a bunch of different things (disabling hyper-threading, tried the response in this thread: http://www.tomshardware.co.uk/forum/341375-28-only-core-time, tried refreshing Task Scheduler service, ..) but haven't had any success

I'm out of ideas and could really use some help fixing this lol
 

kanewolf

Titan
Moderator
If you are running Cinebench single core and it is maxing out a single core, then it sounds normal to me. It is not required that the scheduler move a CPU bound task between cores. It is usually better to leave it on a single core since that maximized the L2 and L3 cache usage.
 

apexnewg

Prominent
Oct 8, 2017
3
0
510


Thanks for your response! Does the same go for gaming? I was a little worried that it would run 100% on that thread for long durations, especially since it didn't seem to do that for my friends

I should mention the main game I have been testing this on is Rust and have been seeing worse performance with my setup (7900x 4.6GHz, 1080 Ti) than some of my friends' builds (5930k 4.4GHz 980 & 6700k 1080) - I knew I would be sacrificing some performance by going for this chip but decided it was worth it to be able to handle my workload so easily. However I wasn't sure if those results were correct
 

apexnewg

Prominent
Oct 8, 2017
3
0
510


I just tried another weird test: Running Minecraft (capped at 170 fps) would max out the same (CPU 0) thread and send my temperatures up, yet if I uncap my fps it goes up to 2000+ and the temperatures don't change, disabling and reapplying affinity and setting my fps cap to 170 again only uses about 20% of the thread it gets switched to

I'm so lost as to what could be causing this and really have no clue how to go about fixing it