Check all available temperatures first, then reset fan software and investigate driver faults. One stopped fan beside spinning fans points to a hardware or reporting fault; it does not prove a particular failsafe algorithm. If a fan stays stopped when it should run, stop load testing and contact the card vendor before opening the cooler.
Fans pinned at 100% are loud. Start with temperatures and software resets, then move to hardware checks. I would use this order because the early steps are reversible and cost nothing. Noise alone cannot identify the fault.
The diagram shows a shape, not a safe temperature limit. Use your model’s documented fan policy. ASUS’s start/stop table makes fan behavior depend on temperature, board power and the 0dB setting, and warns that conditions vary by configuration.
First: check startup behavior and temperature
During startup. A brief high-speed burst that settles at the desktop can be normal for a particular board. Firmware can control fans before Windows loads. Check the model’s behavior rather than treating pre-driver full speed as a universal design rule.
When temperatures are high. A high hotspot or memory-junction reading makes cooling checks the next step. Reduce the load. Check airflow and dust before opening the cooler, and follow the service boundary below if a fan has stopped.
The fix order
1. Reboot once, properly
Try a full shutdown and cold boot. It can clear a transient software or controller fault. If normal fan behavior returns and the problem never recurs, stop here. A recurring problem needs the remaining checks.
2. Find the fight between fan-control programs
List the programs that can control this GPU’s fans, such as Afterburner or the card vendor’s tuning utility. Check model support; a motherboard fan utility may control only motherboard headers. Leave one GPU controller enabled and reset its profile. Check for a fixed-speed override too. A stored 100% setting can return after every reboot.
3. Reset the curve itself
If the single remaining controller still pins the fans, its stored curve or the card’s fan table may be corrupt. Reset the utility to defaults (or uninstall it and let the driver’s automatic control take over). On cards with a dual-BIOS switch, confirm it did not get bumped to the performance position, which runs a deliberately aggressive curve on some models.
4. Investigate a driver fault
Full-speed fans appearing alongside a black screen, driver reset or stutter make the driver a useful branch to investigate. Fallback behavior depends on the board and firmware; full speed alone does not prove a driver crash. ASUS’s troubleshooting page includes driver updates among its fan checks. If the problem began with a driver update, use the GPU driver crash guide for reinstall or rollback steps, then check whether the same symptom returns.
5. Check what the sensors report
Read every available GPU temperature. If a value is impossible or disagrees sharply with the other readings, check it in another compatible tool. A persistent reporting fault is a reason to contact support, especially when resetting the fan profile and driver does not resolve the symptom.
If the readings are plausible and come from one sustained-load session, the GPU hotspot delta census records the core, hotspot, sensor tool and version without turning one card into a universal limit.
6. Suspect the fan that reads zero
If one fan reports 0 RPM while its neighbors run flat out, compare that reading with what the fan is doing. Check whether the model exposes each fan’s RPM independently; one reported value may represent only one fan or a shared channel. A visibly spinning fan with a zero reading points toward reporting or tachometer trouble. A fan that remains still when the model’s policy calls for it to run points toward a fan, obstruction or connection fault.
The idea that the controller is compensating by maxing its other fans is a diagnostic inference. It is not a confirmed algorithm for every board. That pattern alone cannot tell you which component failed.
Stop load testing if a fan should spin and does not. ASUS’s fan troubleshooting guidance directs a stuck-fan case to support, advises stopping use with a malfunctioning fan, and warns against improper disassembly. For a card under warranty, contact its manufacturer about repair or RMA before removing the cooler. For an out-of-warranty repair, obtain a confirmed part for the exact card and cooler revision: fan diameter alone does not establish mounting fit, connector pinout, voltage or control compatibility. Power off and unplug the PC before inspecting an obstruction; keep hands and tools clear of powered fans.
After it is fixed
Restore the vendor’s automatic curve before tuning for noise. Use the undervolt guide for reducing heat, or GPU fans not spinning if a fan remains stopped.
Frequently asked questions
Why do my GPU fans run at full speed before Windows loads?
Can two fan-control programs conflict with each other?
Why are my GPU fans at 100% but the card is cool?
Is running GPU fans at 100% all the time harmful?
Do I need to replace a fan that reads 0 RPM while the others max out?
Sources and corrections
- Last updated
- Methodology
- See our methodology for research and review standards. It draws on 2 cited sources, listed below, each checked against the original page on the date above.
- Sources
- ASUS fan troubleshooting and service boundary accessed 2026-10-12
- ASUS model-dependent fan start and stop conditions accessed 2026-10-12
- Update log
- 2026-10-12 — Sourced fan-stop and service advice to ASUS support; labeled tachometer-compensation behavior as inference; added warranty, replacement-part and connector boundaries. Startup and diagram thresholds now carry model scope. No hardware test was added.
- 2026-08-13 — Published. The fix ladder is ordered by frequency-of-cause and cost; the zero-RPM and pre-driver behaviors are stated as the design defaults they are.
- Corrections
- Spotted an error? Email a correction with the affected line and what you found. The draft includes this page’s address. Verified changes are recorded here. Contact details.