Level 1

4 points

MacBook Pro M1 fans running loudly and constantly

> Hello everyone,

> I am experiencing a critical issue with my MacBook Pro M1 (Apple Silicon). The fans are running loudly and constantly, even when the system is idle or when I have no applications open. This started abruptly after my battery health indicator dropped unexpectedly to 1%.

> I have run extensive diagnostics, and the problem seems to be deep-rooted and independent of user-level software. I am looking for advice on whether this is a known hardware/sensor failure or a low-level system bug.

1. Key Diagnostic Findings (From Activity Monitor)

> The primary culprit is the graphics load, and the system is showing instability with core processes:

> * High GPU Load: The process WindowServer shows a persistent and high load on the GPU (over 30% GPU usage), which generates significant heat and forces the fans to spin rapidly.

> * System Process Instability: Core system processes like trustd, siriinteractionsd, and kernel_task show fluctuating, high CPU usage or high thread count, indicating the system is struggling to manage resources or temperature.

> * Battery Status: The battery indicator suddenly reads 1%, which may be a contributing factor or a separate symptom of a faulty SMC/power controller.

2. Steps Already Taken (Advanced Troubleshooting)

> I have performed all recommended software fixes, which have not solved the issue:

> * Safe Mode: Performed a successful Safe Mode boot and rebooted normally. Problem persisted.

> * SMC Reset: Performed the correct SMC reset procedure for M1 Macs (full power cycle). Problem persisted.

> * Disk Repair: Ran First Aid in Disk Utility on the main drive, and the file system reported no errors.

> * User Account Test: Created a new, clean Administrator account and logged in. The fans continued to run loudly and the GPU load on WindowServer remained high.

> Conclusion: Since the problem occurs on a clean user profile and after SMC/Safe Mode resets, I suspect a hardware failure (sensor, battery, or power controller).

> Has anyone encountered this specific combination of high GPU load on WindowServer + sudden 1% battery status on an M1 Mac? Should I proceed directly to an Apple Authorized Service Provider?

> Thank you for any help!

[Re-Titled by Moderator]

Original Title: MacBook Pro M1

MacBook Pro 13″, macOS 26.1

Posted on Nov 21, 2025 1:02 PM

Top-ranking reply

Michal_837 Author

Level 1

4 points

Posted on Nov 21, 2025 2:47 PM

EtreCheckPro version: 6.8.12 (68084)

Report generated: 2025-11-21 23:38:13

Major Issues:

Battery failure - Your battery is reporting that it needs to be serviced.

Minor Issues:

Apps crashing - There have been numerous app crashes.

Hardware Information:

MacBook Pro (13-inch, M1, 2020)

16 GB RAM - Not upgradeable

Battery: Health = Service Battery - Cycle count = 0

System Software:

macOS Tahoe 26.1 (25B78)

Launch Daemons (Power/Fan Control):

[Loaded] com.apphousekitchen.aldente-pro.helper.plist

[Running] com.crystalidea.macsfancontrol.smcwrite.plist

Performance:

Performance: Good

System Load: 3.07 (1 min ago)

Write speed: 3024 MB/s

Read speed: 2122 MB/s

CPU Usage Snapshot:

Type Overall

System: 5 %

User: 15 %

Idle: 80 %

Top Processes Snapshot by CPU:

Process (count) CPU (Source - Location)

WindowServer 21.44 % (Apple)

com.apple.WebKit.GPU (2) 21.16 % (Apple)

kernel_task 8.56 % (Apple)

Top Processes Snapshot by Energy Use:

Process (count) Energy (0-100) (Source - Location)

WindowServer 17 (Apple)

Virtual Memory Information:

Physical RAM: 16 GB

Used RAM: 9.43 GB

Swap Used: 0 B

Diagnostics Information (past 60 days):

2025-11-21 21:38:42 Spotify.app - Hang

2025-11-20 16:19:04 ANECompilerService - High CPU Use (2 times)

2025-11-19 19:34:50 ControlCenter.app - High CPU Use

2025-11-19 17:13:22 PerfPowerServices - Crash (16 times)

Executable: /usr/libexec/PerfPowerServices

Details: libsystem_c.dylib: abort() called

EtreCheckPro Report (Key Findings):

Major Issues:

Battery failure - Your battery is reporting that it needs to be serviced.

Hardware Information:

MacBook Pro (13-inch, M1, 2020)

Battery: Health = Service Battery - Cycle count = 0

Top Processes Snapshot by CPU:

WindowServer 24.72 % (Apple)

Diagnostics Information (past 60 days):

2025-11-19 17:13:22 PerfPowerServices - Crash (16 times)

Details: libsystem_c.dylib: abort() called

View in context

26 replies

Michal_837 Author

Level 1

4 points

Nov 22, 2025 2:43 AM in response to etresoft

I apologize for the confusion; I am very new to macOS and the Terminal environment. I am doing my best to follow all the commands precisely, but it is clear I missed a step or the system is being extremely stubborn.

I followed your instructions immediately and performed the following steps this morning: I ran the command to delete the executable file for Macs Fan Control:

sudo rm /Library/PrivilegedHelperTools/com.crystalidea.macsfancontrol.smcwrite

The Terminal reported back "No such file or directory", which I assume means the file was already deleted or never existed in that location on my system (perhaps I removed it manually before).
I performed the final, definitive restart.

The result is still the same: The critical "Service Recommended" error persists, and the battery is locked and will not charge. The issue is not resolved.

Given that I am a new macOS user and that I have followed all the cleanup steps for AlDente and Macs Fan Control, and the problem remains, I am now convinced that the damage is physical (PMIC/BMS failure).

Before I schedule a costly repair:

Could you please provide one final Terminal command—the most powerful command you know—that can force the macOS to completely flush and rebuild its system configuration files, just to make absolutely sure no remnants of AlDente or Macs Fan Control are forcing this hardware lock?

I want to exhaust every last software possibility before committing to a minimum 1000 PLN (250$) repair cost.

etre check

Michal_837 Author

Level 1

4 points

Nov 22, 2025 2:52 AM in response to Michal_837

I have an update regarding the software conflict and the Mac's status.

I have completed the last steps you suggested: I ran the sudo rm command again for Macs Fan Control, which reported the file was not found, and I performed the final necessary restart. The issue is still unresolved.

Crucially, I contacted the developer of AlDente (AppHouseKitchen GmbH) to inform them about the critical hardware failure.

They responded that:

They are not liable for hardware damage, citing their Terms of Service.
They claim the risk of AlDente causing this specific failure (PMIC lock) is "almost 0" because they use the same SMC keys as Apple.
They stated that this type of M1 failure also happens to Mac users who have never installed their app.

What I should do ?

Michal_837 Author

Level 1

4 points

Nov 21, 2025 2:34 PM in response to Gandolf243

Maybe it's the fault of the Aldente program ?

Michal_837 Author

Level 1

4 points

Nov 21, 2025 3:05 PM in response to Mac Jim ID

etre check pro

Michal_837 Author

Level 1

4 points

Nov 21, 2025 3:47 PM in response to Michal_837

Michal_837 Author

Level 1

4 points

Nov 21, 2025 4:00 PM in response to Mac Jim ID

What should I do now ?

Go to service ? It will cost a lot.

Michal_837 Author

Level 1

4 points

Nov 21, 2025 5:32 PM in response to etresoft

etre check latest

etre check

Mac Jim ID

Level 9

59,288 points

Nov 21, 2025 3:13 PM in response to Mac Jim ID

The battery indications will need to be checked by scheduling service with Apple. Heat is detrimental to the condition of the battery and when manually controlling the fans meant to keep it cool with third party fan control software, that may have been a contributor to the early failure.

etresoft

Level 9

56,212 points

Nov 21, 2025 5:04 PM in response to Michal_837

Michal_837 wrote:

I have uninstalled both **AlDente** and **Macs Fan Control** and performed a full system reboot (equivalent to an SMC reset).

How did you do that? These apps have components in hidden directories. If you just deleted a couple of apps, then all you've done is delete the user interface portion. The actual hardware modification logic may still be running.

You can generate a new EtreCheck report to confirm that they are no longer listed.