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

    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      186
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!