Sign in with
Sign up | Sign in
Your question

Is something wrong with my PC?

Tags:
  • CPUs
  • wrong
  • troubleshooting
  • something
  • problem
  • Systems
Last response: in Systems
Share
May 26, 2014 3:11:58 PM

Recently I installed a Hyper 212 EVO on my CPU, it has worked great for a couple weeks now, no problems at all, and it's been keeping things very cool.

However, very recently something strange has been going on. Whenever I run a game, with the graphics settings turned up, I get this very strange ticking noise coming from my PC.

After investigation I have determined it HAS to be the fan on the Hyper 212 that is making this noise.

The noise only occurs when my CPU starts getting hot (it only gets to around 55°C when this happens) and the fan starts spinning faster to compensate.

But that's not the weirdest part. I tested it today by playing CS:GO. I played for a few with the graphics set up to high, and after a few minutes of playing, the ticking started, and moments after the noise the game shut down entirely.

No warning, no error message, it literally just acts like I hit Alt+F4, it just vanishes off my screen in the middle of playing.

It ALWAYS seems to happen when the ticking starts. Every time the ticking starts, my game shuts down within minutes.

However, when I play on LOW graphics settings, this doesn't seem to do any of this, to prove it I tested it. I played the same game, on LOW this time, for about 30 minutes or so, and nothing happened. No noise, no shut downs, nothing.

My temps are all within range, on both my MoBo & CPU, my voltages all seem fine & in range, My GPU is fine, and I'm not even overclocking, just running on stock speeds. Everything seems to be fine, why does this keep happening?

More about : wrong

a c 207 à CPUs
May 26, 2014 3:19:18 PM

look for three parts that could be the issue. one check that your power supply fan is moving and not clogged. look and use msi afterburner to turn the gpu fan to max. max sure it spins up to max speed and there no wires being sucked in. on the cpu check that the cpu wires not cut or falling into the cpu fan.
m
1
l
May 26, 2014 3:49:16 PM

smorizio said:
look for three parts that could be the issue. one check that your power supply fan is moving and not clogged. look and use msi afterburner to turn the gpu fan to max. max sure it spins up to max speed and there no wires being sucked in. on the cpu check that the cpu wires not cut or falling into the cpu fan.


Thanks for the input.

-I just checked the PSU, and the fan is spinning, and does not seem clogged at all.
-I checked the CPU fan, and there are no cables or wires touching it. There are wires near it, but they do not actually touch the fan itself.
-I also just installed afterburner after reading your post (I swear I had it before, mustve gotten delted by accident) and turned the fans up to 100% speed, they did in fact speed up to around 4000 RPM (I'm not actually sure what the RPM is supposed to be on these fans)

The GPU fans did not make any ticking noises at all.

Also, I took the CPU fan off the heatsink completely (while the PC was turned off of course) and spun it gently by hand, and when I did this, the fan actually did make a VERY similar ticking noise very slightly when I would spin it by hand.

Thus leading me to believe it is my CPU fan (The stock Cooler Master fan that comes with the Hyper 212 EVO)

But this does not really explain why my games would just quit out on me. Back when I had my stock heatsink, I would play games that would push my CPU temps to around 65°C, and the games would still run fine.

With this heatsink, my temps have never even gotten above 55°C even while gaming.

And it's only been doing this very recently as I said, it started the day before yesterday (Saturday, May 24th)
m
0
l
June 5, 2014 9:38:49 AM

There is a chance the game-shutdown is a separate problem from the noise--even if it seems like a very, very small chance.

What I would do is synchronize a clock with your system time; and, when and if the game-shutdown occurs again, note the time. Then, check the Windows Application Log, from the eventviewer to see if any entries AT, or just BEFORE the time the game-stopped, and see if any clues are left from the log-entries (like an application-name, or error-code). You will be looking for critical-errors (red-flagged). Similarly, there may be some useful information in the Windows System Log.
m
0
l
!