Low gpu load, high gpu load, power consumption

[beerman2222]

Hello guys.

you're my last chance to find a way to solve my problem.
btw, i'm not a english native '^^, pardon me ^^'

i've this issue for quite a long time, and still never found out how to solve it.

My gear :
gtx 1060 asus dual 6GB
i7 4770 (cooled by hdro corsair h60)
motherboard is a asus x87m plus
16gb ram (just bought it)
psu : Corsair CX750M
some ssd and hdd
144hz screen

My problem is in a game (any game i have)

my gpu load is quite low, like 30/33%
i've around 60 fps, sometime less
Then, the fps goes up for like 1 second to 110 120.
Gpu load goes up to 59%

then it go down for 10 second. at 33%
then it re-up at 59/60%

here's a picture of gpu-z

you can clearly see the spike in the gpu load and power consumption, and they are really... stable spike :S
the temp of both cpu and gpu are quite low, 40/50 for cpu
60 for gpu


my GC isn't overclocked at all (i did try using evga precision the power target limit and temp limit, i gain some fps, but still got the load issue)

i know it's my first post, but seriously, i really need your help

 

[Kanan]

Hi welcome,

check if any strange programs are running in the background and if yes close them. Also maybe deinstall your driver with DDU and reinstall, or simply select "clean install" when you install new nvidia driver.

Which PSU is it exactly? Brand, etc.

 

[beerman2222]

Hi, thanks for your fast reply.

I already did a clean install (done with Driver cleaner pro) i only installed the driver, not all the feature like shadowplay.
my psu is a Corsair CX750M
Added in the first post
btw my windows 10 is quite fresh

 

[slozomby]

did you set the temp limit to 60C? if so that's whats causing your spikes as it throttles the card back to low power mode to cool it off. power will spike as the gpu utilization spikes.

the default settings for temp and power limits should be fine for a non OC card. if you need to cool it down more try adusting the airflow or fan curves before setting the temp limit.

edit: looking at the gpuz charts closer. you're much higher than 60C when its spiking. so check the airflow around the card.

 

[beerman2222]

i did some benchmark using OCCT
and for 10 minutes as recommended, the gpu will rise to 78°
gpu load at 99%

After some testing, it seems that it happens in some particular game (atm, in black desert)
It's like blocked for 10 second et 60, then goes up to 110, then reblock at 60

i'll test with full fan , to see if the temp is a problem

EDIT : nop, 51° with fan at constant 70%, still the same gpu load with the huge up every 10 second.

i mean it's not normal, it' always at the exact 10 second that ma fps goes up.
that feeling, i know my gpu can do much better, but it get restricted my something, i don't know what

 

[beerman2222]

I tested 5 game,
and my gpu is always around 30% usage

 

[Kanan]

Install Afterburner and set the Power Target to 100% and temp target to 80°C. Test again (no overclocks).

 

[beerman2222]

I found out where the problem come from
i forget to precise that i have dual monitor
one screen is 144hz and the other one is 60hz

i unplugged my second screen (the 60hz) and the games works perfectly fine.
black desert apprently lock your refresh rate at the lowest you can have.
and with a program called CRU i could lock my refresh rate at 144, so the game run smoothly. still i don't know why every 10 second i could go up to more than 60 fps

still i don't want get rid off my second monitor.

 

[slozomby]

10 seconds is probably a polling interval in the driver for monitor detection. its just too round a number to be arbitrary.

 

[Kanan]

Check: Nvidia Control Panel -> 3D settings -> Multi Display acceleration -> if its set on "Mutiple Display performance mode". Maybe that solves the problem with dual monitor.

 

[beerman2222]

I downgrade my refresh rate to 120hz , and it seems to work now o,o
black desert, same place, same setup
constant 110 fps 74° 65/70% usage

i'll keep in touch, in case someone have the same issue

 

[Kanan]

I think this is a known bug with 144Hz refresh rate, glad you "solved" it.