Fans going crazy, CPU 100% idle


Recommended Posts

I'm going insane over the behavior of my 27-inch, medio 2010 iMac. The CPU fan continues to spin up even though the iMac doesn't do a thing. I've reinstalled OS X Lion multiple times, I reinstalled OS X Mountain Lion several times. I did PRAM-resets more times I can count, same goes for SMC resets. Today I even disconnected the iMac, laid it down on my bed and cleared all the vents with the vacuum cleaner on the weakest setting. The other day a friend of mine walked in and immediately asked why my iMac was making so much noise.

The first picture shows the CPU Fan right after startup. The second less than two hours later. I haven't done a thing with the iMac except play music and browse the web a bit.

How on Earth is it possible the fans spin up, sometimes over 4000 rpm, when the CPU sits next to idle most of the time? The worst part is they won't power down once the iMac cooled off. There are no optical drives in the SuperDrive either.

The measurements are in Celsius. The room temperature averaging at 20,5 degrees throughout my apartment. It's only 14 degrees here in Amsterdam.

post-128385-0-15321200-1348764232_thumb.

post-128385-0-38335300-1348764664_thumb.

post-128385-0-02210400-1348765019.png

Link to comment
https://www.neowin.net/forum/topic/1108523-fans-going-crazy-cpu-100-idle/
Share on other sites

assuming your temps are in Celsius it is spinning up because the chip is hot. Is there anything to justify the chip being hot? Dust on the HSF, high ambient temp, etc?

I can't really say for sure how much dust has accumulated inside the iMac itself, but judging by how little there was directly underneath the grill I seriously doubt it's a lot. I tried looking inside with a flashlight but everything seemed clear.

If I leave my iMac on for long periods of time the fans will gradually get faster and faster until they are 100% on, and they will not go back to normal speeds unless I shut down and power back on. Rebooting just keeps them running at full tilt.

It's strange. It's like the driver/sensor controlling it has failed to do it's job properly. :/

Yeah if it's THAT hot at idle, you have a problem on your hands.... either your system has absolutely 0 airflow or the heatsink aint applied correctly, if so I'd take the computer and bring it to a store.

Did you recently install an SSD?

http://forums.macrum...d.php?t=1235234

That actually affects the hard drive fan, not the CPU fan (at least it did in my Late 2010 iMac). Also, it happens a lot sooner than 2 hours after boot. :p

Maybe your GPU is being taxed by something? The CPU fan cools both, so...

Yeah if it's THAT hot at idle, you have a problem on your hands.... either your system has absolutely 0 airflow or the heatsink aint applied correctly, if so I'd take the computer and bring it to a store.

It's an iMac. It's normal for things to run a little bit hotter.

Did you recently install an SSD?

Everything is stock. No modifications whatsoever have been made to the iMac after I unpacked it. Also, the SSD issue wouldn't affect the CPU fan, rather the HDD fan.

Maybe your GPU is being taxed by something? The CPU fan cools both, so...

Okay, this is something I can work with. Is there any way of checking what the GPU load is?

If I leave my iMac on for long periods of time the fans will gradually get faster and faster until they are 100% on, and they will not go back to normal speeds unless I shut down and power back on. Rebooting just keeps them running at full tilt.

It's strange. It's like the driver/sensor controlling it has failed to do it's job properly. :/

That's EXACTLY what ****es me off. The fans won't slow down once things are cooling off.

UPDATE:

Okay this is incredibly interesting. I'm now 100% sure this is indeed a software issue, rather than a hardware related one. For whatever reason OS X Mountain Lion is telling my iMac to increase CPU fan speed in order to cool off. But apparently this is a one-way street. As time progresses the fan speed just continues to go up until it hits a maximum of about 4150 rpm. Like jamesyfx noticed they it will continue running at its maximum until I do a full shutdown. So for whatever reason OS X Mountain Lion won't tell my iMac to reduce fan speeds once it cooled off.

After a lot of Googling I noticed other people having the same issue with OS X Mountain Lion. Not just iMacs but MacBook Pros too. One person came with the suggestion to temporarily download and install iStat Menus 2, set Fan speed control to "Medium" (it's on of the default "rules") and then return to "Default". In literally an instant my iMac's CPU fan would drop from its maximum of ?4150 to a quiet 1940 and then continued to drop.

Check out the below screen shot and note the uptime: Over 6 hours and a regular CPU fan speed of 1885 (it's still dropping as I type).

So what's going on here people?

post-128385-0-90926700-1348790216_thumb.

It does a similar thing on my system, CPU fan speed drops down to a steady 1190rpm when I set to default.

Seems like it kicks the default behaviour back in once you set it as such.

My iMac is a completely different model to yours, so the issue must be software related.. and I think using this utility has proven that.

Yeah that's exactly what seems to happen. iStat basically slaps OS X on the wrist telling it do proper fan control. After a while CPU fans would indeed drop to an average of 1190 rpm on my model as well. Here I was thinking my CPU/GPU fan was constantly triggered because it couldn't handle the new OS X Lion/Mountain Lion graphics effects. But that's not it either.

Anyway, it seems like you can uninstall iStats Menu from your system until you do a SMC reset.

I'm not familiar with Mac since i never owned one but why does OSX has to control the fan ?

I would never ever trust any OS to control the fan speed of my computer. Right now i have a fan controller but if i would not have one i would let my Motherboard control the fan speed or at worst install my MB software (or a 3rd party alternative like speedfan) to control them.

Here's an interesting blog post about the issue. You probably have already read it since it was in the first 10 results of a google search but i still post it just in case.

http://gigaom.com/ap...lion-heres-why/

Spotlight reindexing doesn't take days or weeks.

  • 2 weeks later...

Maybe this helps:

http://www.hddfancontrol.com/

OR:

Symptoms

After plugging in the iMac and turning it on, the fans (blowers) may be noisy and appear to run at full speed. In this event, shutting the iMac off and turning it on again wouldn't fix the issue.

Resolution

If you press the iMac power button while you are inserting the power cord, the iMac will enter a mode in which the fans (blowers) run at full speed. In order to correct the issue, reset the SMC and then start the computer by pressing the power button after the power cord has been fully inserted.

The iMac should now start up and operate as expected.

http://support.apple.com/kb/TS1433

AND:

First download and install smcFanControl 2.2.2. Set it up to provide (still quiet) minimum fan speeds of 2200 rpm for the HD and 2800 rpm for the CPU, leave the Optical Drive fan at 600 rpm to minimize dust accumulation (or just tweak it up if/when you will be using it much) ....

http://hints.macworl...110606033134359

UPDATE:

Okay this is incredibly interesting. I'm now 100% sure this is indeed a software issue, rather than a hardware related one. For whatever reason OS X Mountain Lion is telling my iMac to increase CPU fan speed in order to cool off. But apparently this is a one-way street. As time progresses the fan speed just continues to go up until it hits a maximum of about 4150 rpm. Like jamesyfx noticed they it will continue running at its maximum until I do a full shutdown. So for whatever reason OS X Mountain Lion won't tell my iMac to reduce fan speeds once it cooled off.

After a lot of Googling I noticed other people having the same issue with OS X Mountain Lion. Not just iMacs but MacBook Pros too. One person came with the suggestion to temporarily download and install iStat Menus 2, set Fan speed control to "Medium" (it's on of the default "rules") and then return to "Default". In literally an instant my iMac's CPU fan would drop from its maximum of ?4150 to a quiet 1940 and then continued to drop.

Check out the below screen shot and note the uptime: Over 6 hours and a regular CPU fan speed of 1885 (it's still dropping as I type).

So what's going on here people?

I'm confused. Did that software package end up solving the problem for you or is it still an issue?

Off hand I would say the temp gauges are wrong, without touching the cpu or the motherboard touch the bottom of the heat sink(while the computer is on) and see if its hot. That feels like the CPU is over heating(which would cause the 100% cpu usage).

I have no idea what you're talking about or why you think there is 100% CPU usage. :/

  • 2 weeks later...
  • 2 years later...

Hi there, old thread, but hopefully someone is still around.

I have an iMac 27 late-2009, 3.06 Ghz, 8gb RAM, running OS 10.8.5, and all the hardware is original (no HD swap...). So, it has a similar problem: it takes about an hour for the CPU fan to gradually speed up from the initial approx 1200 RPM to around 4000 RPM. Then, all I have to do is to put it to sleep for enough time to let the fans stop spinning (that's not even 5 seconds) and then wake it up to see the CPU fan at normal speeds. And here it goes for another hour of gradual increase... See the screenshot of the iStats Menu, the graph shows the increase in the last hour, and the three previous increase/sleep patterns... The other two fans are just fine. All of that time, the iMac is at idle, nothing running at all. My iMac isn't my main computer, so i kinda left the problem as it was, spending an hour or so every couple of months trying to solve the issue, but after these 5 years of fruitless efforts, I can't believe I haven't solve it yet! Even though I get answers a lot from forums, here's my first post in one of them (ever!), in hope it will help.

 

Here are the solutions I tried already: smcFanControl, HDD Fan Control, iStats Fan Rules... Nothing seems to be able to override the fan speeds, nothing at all! I vacuumed the air input and output... And of course, I did the SMC reset. I try to remember all the other things I tried to do, but it gets confusing after those years of diverse problem solving. I did many upgrades (and even downgrades) too but I doubt it has anything to do.

 

Even though I never opened the iMac's case (I DID open the bottom latch to replace RAM memory at some point, comes to my mind... but that's not the back case) I wonder if it has anything to do with some hardware that would just be misplaced at the factory of because of a shock while moving the computer around... 

 

Anyone has any idea? Anything I could try?

 

Screenshot:

https://www.dropbox.com/s/vfvkr1zordrbznb/Screen%20Shot%202015-01-14%20at%2011.59.57%20PM.png?dl=0

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Yup, that's a doozy right there 😄
    • It's a bundle of tools created by a variety of people, so things can go wrong sometimes. It's a great addition to Windows, and I use a lot of the tools on a daily basis. Also, it's still a 0.**** release so quick updates are to be expected 😉
    • Oh, I did. And it's even worse than I was hoping! Besides a lot of techno-babble jargon (yes I understand 100% of it but it's still all just techno-babble) there's 2 key points that make me super-weary about even considering testing this out. -- By default, after installation, a relay is automatically set up, so you do not need to care about that. * Non-chatmail apps use email servers as a long-term message archive while chatmail clients use email servers for ephemeral instant message relay. * Supporting the full variety of classic email setups would require considerable development and maintenance efforts, and complicate making chatmail-based messaging more resilient, reliable and fast. -- Basically, the end-user device is the 'server' (relay) so there is NO ARCHIVING whatsoever because every message is necessarily ephemeral. Great for techno-paranoia (and for illicit activities preferring no tracks to cover) but terrible for everybody else. It's also ironically contradictory to engineering principles of redundancies besides the transport layers due to the explicit absence of any persistent storage. Instead of 'classic email address' retaining multi-GB messaging archives on its server, now every device must retain 100% of those storage demands. (Email messages were originally meant to be short correspondences, not the multi-MB attachments boondoggle that now exists with unlimited spam engines flooding every potential recipient.) Any device swap or reset (or loss) makes the entire message history go bye-bye forever... lest there's an off-device auto-archival "relay" mechanism that's really a separate server that holds onto all transported messages (an email server) that utilizes 'chatmail email address' identities (like an email server) and its own persistent storage archive (like an email server). But... this solution is hoping to exist alongside real-world email address identities (based on the email server relay pathway) but simply render messages in chat thread format in an ephemeral manner (with contents being encrypted, and messages auto-expiring) ... In the end, it's a chat app/experience for the Web3/P2P-at-all-costs zealots. (I have accts on all sorts of federated web3 services so I understand the technical and non-technical alike.) For any practical users, however, it's just another service to download/install, register, cross-share id cards/qr codes, but know that there's no history/archive whatsoever (by design) so no account/message recovery whatsoever... update the device, install a bummed update patch, or dare upgrade your device... all history, poof, gone. Ya gotta start everything over again like they're a brand new person.
    • You've tried DuckDuckGo and Brave Search, now get serious with SearXNG by Paul Hill Over the last decade, it has become quite trendy to dump Google Search in favor of privacy-preserving alternatives such as DuckDuckGo, Startpage, and Brave Search. These search engines have done a very good job at highlighting dodgy practices by Google, such as adjusting search results based on what it thinks you’ll like (filter bubble) and stalking you around the web to advertise to you. While these search engines are good starting points when compared to non-private services like Google, there are still quite a few issues with them. For example, both DuckDuckGo and Brave Search require running non-free JavaScript in your web browser, which is comparable to running proprietary software on your computer, meaning you can be sure about what it’s actually doing in the background. Another issue is that these search engines are hosted on the respective companies’ servers, and you are using a service that you don’t control. Finally, DuckDuckGo, while offering privacy features, relies heavily on Microsoft’s infrastructure for its results and, in the past, has permitted Microsoft tracking scripts. If you are looking for a more private search solution than DuckDuckGo, Brave Search, and Startpage, then I recommend taking a look at SearXNG. It is a privacy-respecting metasearch engine that can be used via different public instances, which is useful for mobile users, or you can install it on your computer or server and run it locally with maximum control. Unlike Google, Bing, or Brave Search, which crawl the web and have their own search indexes, SearXNG is a metasearch engine, meaning it taps other search engines, stripping your identifying data, such as IP address, user agent, and cookies, in the process. Your search query is sent to the other search engines you enable before aggregating the results. SearXNG has deployment flexibility. If you are a casual user or a mobile user and don’t want to run SearXNG locally, you can use a public instance that is hosted by someone else. The main problem with this is that you are putting trust in the maintainer of the instance regarding stuff like logs that they may keep; good hosts should have a privacy policy explaining their policies. If you are trying to use SearXNG, you can also install the software on your device and then head to 127.0.0.1:8080 in your browser and search from there. While you don’t have to worry about a third-party admin like the public instances, search engines could ultimately block your IP address if they frown on you pulling in their search results locally. If you want to run it locally, it’s a good idea to use proxies or VPNs to hide your actual IP. You don’t have to worry about this with a public instance, as search engines never see your IP address. The main privacy benefit of using SearXNG is that it isolates your identity from the underlying engines that it’s capable of searching, such as Google and Bing. These search engines will only see requests coming from a generic server, so they can’t profile you and create a bubble filter that influences what results you see. This also ensures that your search engine doesn’t turn into an echo chamber that prevents you from reading alternative points of view. As a free software project, you are allowed to inspect SearXNG to make sure there are no negative features bundled inside. This sets it apart from the privacy search engines mentioned earlier because you can’t check their source code. As a meta search engine, you are not restricted to getting results from one source. Due to the fact that it scrapes content from other websites, your SearXNG instance will periodically get blocked from different providers, so it’s good to select a range of sources as a backup. While enabling all of the services will give you great results, this can make searching slower. I am personally happy with slower searches for the best results, but you can always check which providers are slowing down your search from the search results page and disable them to speed things up. If you want decent results quickly, enable the main search providers such as Google, Brave, DuckDuckGo, Qwant, Bing, and Yahoo. This way, you get wide coverage without the latency. On the Engines tab in Preferences, do note that there are different tabs, such as General, Images, and Videos, with their own providers that can be toggled and are not covered by "Enable all" while on the General tab, so be sure to dig into each. Just a note, if you want to enable everything, press "Enable all" in one tab, then hit save at the bottom of the page, then do the next tab, and so on. If you press "Enable all", then do that in each tab, and then save, nothing will stick. When I had just some of the search engines enabled, I searched “define nefarious” and results came back with the definition of “define” - obviously that was a sucky result. However, when I had everything enabled, it found dictionary pages for the word “nefarious” and even had an inline definition on the sidebar, which is quite nice too - that was delivered by WolframAlpha for anyone wondering! Probably the worst thing about this meta search engine is that the engines you select are saved with a cookie, so you must enable them on every new device you use SearXNG on, including if you decide to go into incognito mode with your web browser. Honestly, I would say this is the most annoying aspect, and perhaps if your browser lets you choose a separate private browsing search engine, then it would be best to use DuckDuckGo for this portion of your browsing. Another weakness of SearXNG is the random blocking of it by search providers. When you are on the results page, expand the “Response time” box, and it will show things like “Suspended: too many requests” or “access denied”. This is why it is good to enable several providers so that there is always a fallback to get results from. I won’t pretend SearXNG will be for everyone, however, if you enable all of the providers and put up with the slower response time, the results can be really amazing. Even if you don’t want to use it as your daily driver, keeping a bookmark handy that links to it is a good idea if you ever feel like doing a deep dive into a niche topic where other search engines are just failing to bring up any good result, due to the amount of sources it looks on. If you’re interested in radical user control over the software you use, installing SearXNG locally can also be a good idea, but be prepared to be temporarily blocked from sites if you trigger bot sensors without a VPN. Personally, I’ve opted to use a public instance, rather than install it myself. If you want to use it via a public instance, head over to searx.space to find a provider. Let us know in the comments if you have used SearXNG or its predecessor, Searx. What do you think about the quality of the results?
    • Dear Neowin, If it is not too much trouble, can you start using the new-ish designations for Insider Preview? "Experimental" is different than "former Dev" as it can apply to different models, eg 26H1 or 26H2 etc, right? No need to seed confusion IMHO. And, please "finally" update your graphics. OK?
  • Recent Achievements

    • Week One Done
      flexorcist earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      503
    2. 2
      +Edouard
      226
    3. 3
      PsYcHoKiLLa
      158
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!