CPU temperature drop then big FPS drop

baardie12

Honorable
Dec 5, 2013
39
0
10,530
Hello, these last couple of days have been annoying as I have been experiencing an FPS drop when playing games. I use CAM to display loads/temps and I noticed that when I get these drops my CPU temperature drops roughly 10c from 65 to 50. I have also noticed that when shooting a gun in Garry's Mod my fps drops from 200fps to 1-3fps.

Is it the CPU over heating and removing load to try and reduce heat? I was going to buy NH-D14 at the end of the month.

Specs:
CPU: AMD FX 8320 with Shuriken Rev.B as the cooler
GPU: MSI Gaming 2GB R9 270x
RAM: Geil 2x4GB 1886Mhz
 
Solution


well thanks for the update!

thats the first time i've heard "lag" being caused by a poor hard drive... but i'll file that under the list of possible causes in the future. glad you have it sorted out!
looks like the cpu is overheating. at 65C on the cpu core temp or 72-75C on the motherboard socket temp, most piledrivers get throttled back by the motherboard.

Double check to make sure this is happening. Get something like MSI Afterburner, and HW Monitor, leave them open and running in the background, when it happens tab out of the game, and check out what the graphs say the "cpu" load and temps were for the previous couple of minutes.

Also look at what it says the gpu is doing...

I suspect your cpu is throttling back seriously.
 

baardie12

Honorable
Dec 5, 2013
39
0
10,530


The GPU is fine, 28-40c while playing games. Another thing, when I open MSI Afterburner and the UAC pops up, CAM says my CPU hits 255c but I think thats a bug.. Also noticed that a temp on mobo is 75-77 and thats when it drops in temp so I will buy the NH-D14 + Arctic Silver 5 paste ant it should stay cool, also buying a new case because this one barley fits my parts in..

Check the notification bar..
uIU80CJ.png
 

Nitesdeath

Honorable
Jan 13, 2014
316
0
10,790


To me it sounds like the CPU socket is overheating. The core temps should be fine at 65 C. My fx 6300 runs at 66 C core temp when playing CSGO although I am installing my Hyper 212 Evo pretty soon as this is a little hot.

The socket temp shouldn't be passing 72 C to be honest.

Download AMD overdrive from AMD's official website. http://sites.amd.com/us/game/downloads/amd-overdrive/Pages/overview.aspx

This program will confirm if your CPU is overheating or not. It tells you the Thermal Margin. Thermal Margin is how far you CPU's current temperature is from it's overheating point. At idle you should see high Thermal Margin, when gaming it shrinks. Do not use any other temp monitoring programs when using this because they might interfere just like you said earlier you had one of your programs tell you 255 C. If that were true your PC would light on fire.

Also are you overclocking?
 
yep. that's a socket temp overheat. your motherboard is throttling your cpu to keep the board from catching on fire or something blowing.

This is a common issue with piledrivers, especially the 8 core variety. There are a few solutions to them.
1) try placing a fan over the mosfet heatsinks and see if the temps drop
2) try placing a small fan behind the cpu socket, many cases have cutouts behind the cpu socket, to allow airflow, a little doublesided tape and a small 90mm fan will do wonders
 

baardie12

Honorable
Dec 5, 2013
39
0
10,530


Hi, when I get paid this month and I install a NH-D14, will my socket temp go down with the CPU temp? Also, is there any particular reason that the socket temp is 20-30c higher than the cores?
 
core temp reporting on most cpus is unreliable, more so on AMD cpus, as they haven't had an actual thermometer on their cpu cores since the k8 (athlon64 days). the socket temp is often far more reliable an indicator of the temp of a piledriver then the core temp is.

and yes, putting a nh-d14 on that cpu will help a lot.
 

baardie12

Honorable
Dec 5, 2013
39
0
10,530


My hard drive died, got a new one and it fixed nearly all of my lag problems..
 


well thanks for the update!

thats the first time i've heard "lag" being caused by a poor hard drive... but i'll file that under the list of possible causes in the future. glad you have it sorted out!
 
Solution