Skip to main content

troubleshooting - How to tell if CPU is actually overheating or is a false positive?


How does the CPU know it's temperature? I've been having trouble turning on my computer as I keep getting "CPU fan error". I reapplied thermal paste and got a new heatsink/fan and still the same problem. Could it be a false positive? How can I tell? Any other causes of the error that don't actually have to do with the CPU heat, for example could the CPU not be correctly seated? The heatsink I'm using is stock Intel and I heard all 4 pins click in. Plus when I took it off the thermal paste had been smudged around so I knew it made contact, and I watched the fan spin.


UPDATE: it's working now. I didn't know it made a difference where you plugged in the power cable to the motherboard. I had tried plugging the fan into two connectors, and though the fan turned on, I guess the same channel is used to convey information about CPU temperature? Here is a picture with red arrows pointing to the power connectors (or what's the correct name?) where I plugged in the fan and had it turned on but got the CPU fan error. Interestingly there is a fan on the side of the case, which I unplugged and tried to plug the heatsink fan into, and it still didn't work. I guess there's something very special about the connector it's plugged into now. Thanks for the help everyone!


enter image description here



Answer



Basically there's multiple headers for fans on a motherboard, and while electrically and functionally identical, the CPU header is monitored seperately, since a non functioning CPU fan would be very bad. If you plugged it into the "aux" or "opt" header - meant for things like "push pull" cooler configurations or water pumps or a "cha" header, meant for chassis fans, the motherboard might decide "hey, the CPU fan isn't taking any power or reporting speeds, it must be dead" and warn you that the CPU.


As such when building a system where you plug in a fan matters, especially for automatically controlled fan speeds, and to prevent error messages like this.


Comments

Popular Posts

How do I transmit a single hexadecimal value serial data in PuTTY using an Alt code?

I am trying to sent a specific hexadecimal value across a serial COM port using PuTTY. Specifically, I want to send the hex codes 9C, B6, FC, and 8B. I have looked up the Alt codes for these and they are 156, 182, 252, and 139 respectively. However, whenever I input the Alt codes, a preceding hex value of C2 is sent before 9C, B6, and 8B so the values that are sent are C2 9C, C2 B6, and C2 8B. The value for FC is changed to C3 FC. Why are these values being placed before the hex value and why is FC being changed altogether? To me, it seems like there is a problem internally converting the Alt code to hex. Is there a way to directly input hex values without using Alt codes in PuTTY? Answer What you're seeing is just ordinary text character set conversion. As far as PuTTY is concerned, you are typing (and reading) text , not raw binary data, therefore it has to convert the text to bytes in whatever configured character set before sending it over the wire. In other words, when y...

linux - Extract/save a mail attachment using bash

Using normal bash tools (ie, built-ins or commonly-available command-line tools), is it possible, and how to extract/save attachments on emails? For example, say I have a nightly report which arrives via email but is a zip archive of several log files. I want to save all those zips into a backup directory. How would I accomplish that? Answer If you're aiming for portability, beware that there are several different versions of mail(1) and mailx(1) . There's a POSIX mailx command, but with very few requirements. And none of the implementations I have seem to parse attachments anyway. You might have the mpack package . Its munpack command saves all parts of a MIME message into separate files, then all you have to do is save the interesting parts and clean up the rest. There's also metamail . An equivalent of munpack is metamail -wy .

ubuntu - Why does my USB hdd returns SG_IO: bad/missing sense data?

I am able to boot and run commands from external USB hdd; the message in question appears for about 45 seconds then booting continues. GRUB2 is installed on internal HDD. When choosing to boot directly to /dev/sdb the message doesn't appear, however boot time is about the same as booting to internal HDD. /dev/sdb: Timing cached reads: 1018 MB in 2.00 seconds = 508.97 MB/sec Timing buffered disk reads: 80 MB in 3.03 seconds = 26.37 MB/sec pfeiffep@de:~$ sudo hdparm -i /dev/sdb /dev/sdb: SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 10 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 HDIO_GET_IDENTITY failed: Invalid argument Gparted correctly identifies the drive as SAMSUNG MP0402H. Any ideas how to remedy the HDIO & SG_IO messages?

Desktop reboots itself on sleep or hibernate

I have been using an ASUS M2NPV-VM motherboard for main home desktop workstation, operating Windows Vista x64. This computer has right from day one not been able to enter hibernate or standby; after Windows performs its final actions and brings the machine down, it would automatically revive itself for a reboot. Updating to the second latest BIOS (1201)has not helped (the latest BIOS revision would induce video refresh problems rendering it unusable). I have been reading related discussions on incidents similar to mine to no avail of a true workable solution. They appear to be more speculative guesses rather than actual knowledge on the inner workings of motherboard hardware. Does anybody have any electronic engineering experience on PC energy-saving standards to provide a more informed opinion how to go about getting this to work? More stories: this motherboard could not even reboot properly the first thing i used it. It was due to refresh rate of the onboard GPU, which had no influe...