A "Huh!" moment

[bytheway_r]

Just a while ago I was working on some photos and heard the distinct buzzer indicating that something's wrong ( it stayed only for a second ). Decided to check my temps, nothing out of the ordinary. Continued working on my photos with HW Monitor in the background. Didn't hear the buzzer again so I thought it was a fluke or something.

Imagine my surprise when I checked the temps afterwards. My max temp reached 57 degrees ( buzzer set at 60 ). Funny thing is, Intel Burn Test never went over 50 degrees and I won't even start about 3dMark. Erm, any ideas? Maybe I should check stability with Canon DPP program?

I have no idea why I got such high temps, especially considering that I didn't process anything for more than about 2-5 seconds at a time... I don't want to think about temps after minutes of batch processing.

[Dark Mantis]

May have just been a glitch but make sure that you haven't got any dust build up as it can happen quite quickly depending on the surroundings. You didn't have anything else running at the same time ....maybe on auto?

[bytheway_r]

Hmm, maybe it was a glitch but I'll check later if it happens again. Nope, nothing else running. Dust is out of the question, it's pretty clean as I tend to open the case every now and again to change something and it's cleaning time whenever I see any real build-up of dust .

Or maybe this is why the program's free ( Canon's DPP )?

[Dark Mantis]

The only other thing to take into account is the level of the mains electricty supply. I don't know how stable it is in Poland but I remember when I was in Bulgaria there were times when it used to fluctuate and that was one reason for me always using a large UPS for stability of supply.

[bytheway_r]

Just tried again and... I don't get it. Did a noise reduction twice and both times I got a buzzer sound but no significant rise in temperatures. First time, it jumped to 42 degrees and later on, 38 degrees. One strange thing ( except the buzzer ) was that max CPU fan speed recored by HW Monitor was 1341 RPM which would be about 100%. Why is it strange? This was the first time my motherboard decided to run the fan much faster than 1000 RPM.

I guess I'll have some "fun" tomorrow trying to figure this out. I doubt I'll find out much, though. I think my only buzzer warning enabled is CPU temp. I'll have to check to make sure if there was anything more than CPU temp and CPU fan warning ( disabled as it went off with fan in "idle mode" ).

Ok, something more. It goes like this:

1. buzzer sound
2. slight temp jump and extreme fan speed jump to 90-100%
3. here's the strange one - fan speed drop to 0 RPM for a fraction of a second
4. fan speed back to normal

Looks like some kind of problem with the fan, it can't really drop to 0 RPM in such a short time but it could lose power for a moment for some reason. Why the buzzer, though?

[Dark Mantis]

As you say it would be worth checking that the heatsink is still securely fastened and working ok. You haven't done a BIOS update recently have you because of course that can affect the settings and not always in a good way!

EDIT

If your fan voltage drops even for a split second it could be enough to trigger the alarm. Even though the fan itself will hardly slow. The same would happen if the fan's feedback loop was faulty.

[bytheway_r]

It's not the heatsink that's the problem. No bios updates, either.

If your fan voltage drops even for a split second it could be enough to trigger the alarm.

The thing is, I have this warning disabled. I'll check it again as I haven't really looked at my bios for a while now. Maybe it somehow reset itself when that "keyboard not working during boot" issue disappeared on it's own.

I'm starting to think the buzzer and 57C previously could be caused by the fan not working right, though. Maybe earlier it stopped working for longer and that's why the CPU went as high as 57 degrees. Guess it's time to look for some fan controller and ditch the MB fan headers .

edit:

Fan warning is still disabled. The only thing that could conflict as far as I can tell is enabled hardware thermal control. That'd be due to my CPU overclock being managed by Windows based application and I'm not sure what'd happen if bios wanted to lower voltages and multi.

Btw. This is me at the moment -> ¯\(ºдಠ)/¯

[Dark Mantis]

¯\(ºдಠ)/¯

Cool!

As you say it could be a faulty fan or a conflict between the Windows utility and the  BIOS. Either is quite possible.