GPU Fan or Lights Stay On After Shutdown? Standby Power (+5VSB), ErP Settings & Wake Settings Explained

2026-10-25 ｜ GPU Repair ｜ About 24 minutes ｜ HK GPU Fix Editorial Team

重點摘要

A graphics card fan or light staying on after shutdown is usually standby power, not a system still running. This guide separates normal standby behaviour from a system that never reaches soft-off, using the power-supply switch test and the BIOS, Windows, and lighting layers in order.

The Short Answer First

After shutdown, a graphics card fan still spinning or a light still glowing does not, on its own, mean the computer is still on. Modern computers have a standby power path that remains live while the power supply is connected to mains electricity and its rear switch is on, even after the operating system has stopped. Lights, USB charging, and wake circuits can all draw from that standby path. The question to answer is therefore narrower than "why is there power": it is "which things are powered, to what degree, and does that match the settings the user has chosen".

That distinction separates two very different situations. In the first, only a standby light glows, a USB device charges, or a fan spins briefly and then stops, and the system itself has stopped. That situation is consistent with standby design, and it can be left alone or changed through settings, according to preference. In the second, a fan spins continuously at high speed, the whole system looks as though it never stopped, or the behaviour persists long after mains power is removed. That situation is beyond a standby-light question and needs a different diagnostic direction.

This article deals only with the state after a normal shutdown. It does not cover a system that fails to shut down, a system that crashes while idle, a system that fails its power-on self-test, a system that wakes from sleep with no picture, or instability that appears after a power cut. Those symptoms belong to other diagnoses, and the settings here should not be forced onto them. If the reader is unsure whether the machine was shut down, put to sleep, or hibernated, the first diagnostic step below resolves that uncertainty before any setting is changed.

Shutdown Is Not Mechanical Off: The Power States

The vocabulary of power states makes the whole article intelligible. In simplified form, the states are:

Only G3 is complete removal of mains input. S5 is a stopped system, not a disconnected one. That single fact explains most post-shutdown lights: the system has stopped, but the power supply has not been disconnected, so its standby rail can still supply the circuits that are designed to stay alert.

Windows Fast Startup adds a further complication to the word "shutdown". With Fast Startup enabled, the default Shut down command is a hybrid shutdown: the user session is logged out, but kernel state is written to the hibernation file and reloaded at the next boot. Only Restart necessarily performs a full cold boot. Testing standby behaviour with Shut down and testing it with Restart are therefore two different paths, and results from one cannot be substituted for the other. A behaviour that appears only after Shut down, and not through a restart cycle, points toward the shutdown path, Fast Startup, or standby settings rather than toward boot hardware.

Plus Five Volt Standby: What It Powers, and What It Cannot Prove

An ATX power supply provides a standby rail, +5VSB, in addition to its main outputs. While the power supply has mains input, this rail supplies power continuously, regardless of whether the main outputs are on. Its purposes include the power-button standby circuit, motherboard standby logic, network wake, keyboard and mouse wake, USB standby charging, and the standby lighting of some RGB controllers.

The important limit is one of scale. +5VSB is a low-power standby rail, not main power. It can keep a light glowing, a USB device charging, and a wake circuit alert, but it should not be equated with a graphics card running at full speed. A light glowing after shutdown is therefore weak evidence about the state of the system: it proves that a standby circuit has power, which is expected by design, and it proves nothing about whether the system is running.

A second, independent power path must be kept separate from motherboard standby power. Some case fan and lighting hubs and controllers are powered directly from the power supply through a SATA or Molex connector, and they carry their own standby logic. Even when motherboard RGB has been switched off, a strip or fan light powered through such a hub can stay lit, because its power does not pass through the motherboard setting that was changed. Any diagnosis that treats "motherboard RGB" and "hub-powered lighting" as one path will conclude, wrongly, that a BIOS change had no effect. The power source of each lit item is a diagnostic fact in its own right.

ErP: The Master Switch for Standby Power, and Its Price

ErP, short for Energy-related Products, is a BIOS setting concerned with standby power consumption. Enabling ErP — commonly written as ErP Ready set to Enabled, or as Enable for S4 and S5, or Enable for S5, depending on the motherboard — tightens standby power in the off and sleep states. Its design goal is to push shutdown standby consumption down to a low level. The setting should be described in those terms, as a design goal, rather than as a measured consumption figure that holds for every motherboard.

Enabling ErP has a price that must be stated alongside its effect, or the article would mislead. The same standby path that ErP tightens also carries Wake-on-LAN, keyboard and mouse wake, USB standby charging, and some standby lighting effects. Enabling ErP can disable or limit those functions. A user who needs Wake-on-LAN, or who charges a device from a USB port while the machine is off, should not enable ErP as a blanket step. The finer-grained settings described later — individual USB standby options and individual wake-event options — are the appropriate alternative when one function must be kept and another must go.

ErP is also not a universal off switch, and it should not be presented as one. On some motherboards, even with ErP enabled, individual USB ports or RGB lighting can remain powered, because of an independently powered hub, a lighting software shutdown setting, or a motherboard design that retains certain standby circuits. A light that remains on after ErP is enabled does not automatically mean the setting failed; it means the remaining light has a power path that ErP does not control, and that path must be identified.

Wake Settings: Four Sources, Two Layers

A lit standby light and a system that wakes by itself are different phenomena, and confusing them leads to the wrong settings. A light is standby power. A wake is the system returning from off or sleep to operation. The wake sources fall into four groups, and each group must be checked separately.

Both layers must be checked, because a setting changed in one layer alone can leave the behaviour unchanged. The BIOS layer holds the wake-event options: real-time clock alarm, USB wake, PCIe and onboard LAN wake, and keyboard and mouse wake, each of which can be enabled or disabled individually. The Windows layer holds the complementary controls: in Device Manager, each device has a power-management page with an option to allow that device to wake the computer; in Power Options, there is a setting for wake timers; and in Task Scheduler, individual tasks can carry the option to wake the computer to run the task. If the BIOS disables a wake source but Windows still arms a device, or the reverse, the resulting behaviour will be inconsistent, and the inconsistency itself is a clue that only one layer was changed.

For readers investigating a system that actually wakes by itself, rather than a light that merely stays on, Windows provides three diagnostic commands, which must be run with administrator rights: powercfg -lastwake, which reports the source of the most recent wake; powercfg -devicequery wake_armed, which lists the devices currently armed to wake the system; and powercfg -waketimers, which lists active wake timers. These commands are only meaningful for a genuine wake. When the system has not woken and only a light is on, there may be no corresponding wake record, and forcing an interpretation onto an empty result would be a diagnostic error.

RGB Shutdown Lighting: A Separate Layer From ErP

RGB software from the various motherboard and graphics card makers commonly includes an independent shutdown lighting setting, often called a shutdown effect. That setting chooses whether lights go fully dark at shutdown or keep a chosen effect after shutdown. It is a software layer, separate from the BIOS ErP and wake layers, and the two layers must both be checked.

Changing only the software leaves the BIOS layer untouched, and changing only the BIOS leaves the software layer untouched. Either omission can produce the frustrating result of a setting that appears to have been changed while the light remains on. The correct procedure is to check the software shutdown effect and the BIOS standby lighting options as two entries on the same checklist, not as alternatives.

A related detail concerns graphics card lighting specifically. Some graphics cards remember their last lighting setting in their own controller, and that remembered setting continues to apply when the control software is not running. If a graphics card light holds one fixed colour after shutdown while the software controls it normally during operation, the stronger explanation is a shutdown lighting effect or standby power path, not a failed light. The distinction matters because it points toward settings rather than toward replacement.

Graphics Card Fans: Three Kinds of Spinning

Not every post-shutdown fan movement means the same thing, and the differences in duration and speed are the diagnostic content.

One confusion must be cleared up explicitly. A fan that stops during operation under light load is a different phenomenon: the zero-RPM or fan-stop design, in which a fan halts at low load to save power and reduce noise. That is normal operating behaviour. This article concerns fans after shutdown, and the two situations must not be merged.

Diagnosis in Order: Separate, Then Change One Thing at a Time

The sequence below is ordered by cost and risk: observation first, then the power-supply test, then Windows settings, then BIOS settings, then software and wiring, and only then hardware suspicion. Each step produces a fact that narrows the next step. Changing several settings at once destroys that narrowing, because the result can no longer be attributed to any one change.

Step 0: Confirm what was pressed. Was the command Shut down, Sleep, or Hibernate, chosen from the Start menu? After the command, is the screen fully dark and the case power light off? Does the system return to the desktop by itself later? If the machine was actually put to sleep, a fan stopped and a standby light glowing are expected sleep behaviour, not a shutdown problem. Comparing one Restart cycle with one Shut down cycle is a useful control, because the two paths differ as described above.

Step 1: The power-supply rear-switch test, the most important separation in this article. After shutdown, observe and record the fan and light state. Then switch off the power supply rear switch, or unplug the power cord, wait, and observe again. Three outcomes are possible. If the fan and lights go out when the rear switch is off, the phenomenon comes from mains power through the power supply standby path, and the next steps are BIOS, software, and hub settings. If they stay on for a short time and then go out, residual capacitor discharge is the stronger explanation, and the question becomes whether that short pattern repeats every time. If they stay on for a long time after the switch is off and the cord is unplugged, the phenomenon is not normal standby power, and an independent battery, an external power source, or another supply path must be investigated by checking the wiring rather than by opening any unit. After the test, switch the rear switch back on; otherwise the next press of the case power button will produce no response, which is easily mistaken for a failure to boot. This test involves only the external rear switch and the power cord. It does not involve opening the case while mains power is connected, removing graphics card power cables, or shorting any pins.

Step 2: Identify exactly which items stay on. Record each one separately: the graphics card's own light or fan, the motherboard light, case fan lights, light strips, keyboard and mouse lights. A pattern confined to keyboard, mouse, or USB devices points toward USB standby power settings. A pattern confined to hub-connected strips or fans points toward independent hub power. A pattern confined to the graphics card light while its fan has stopped points toward the graphics card shutdown lighting setting or its standby light path. A pattern in which the graphics card fan, its light, and case fans all keep running together points toward the system not having truly entered soft-off, or toward motherboard power-control behaviour. Recording the items separately is not paperwork for its own sake; it is what prevents a single blanket setting change from being applied to several unrelated paths.

Step 3: Check the Windows layer before changing BIOS settings, because it is the lowest-cost layer. In Power Options, under the function for choosing what the power buttons do, turn off Fast Startup and run one full shutdown comparison. Note the expected cost: boot may be slightly slower without Fast Startup, and the setting can be restored after testing if the user prefers it on; the change is a diagnostic step, not a permanent prescription for every user. In Device Manager, check the power-management page of the keyboard, mouse, network adapter, and USB controllers, and note which devices are allowed to wake the computer; unnecessary wake devices can be disabled for the test. For a genuine wake case, run the three powercfg commands described above. In Task Scheduler, check whether any task, particularly maintenance, update, or backup tasks, is set to wake the computer to run.

Step 4: Check the BIOS and UEFI layer, changing one item at a time and running one shutdown comparison after each change. The ErP Ready setting is commonly found in a power-management or advanced power-management page; enable it and compare. USB standby power options, where a motherboard provides separate S4 and S5 USB power choices, are the finer control for a user who wants USB lights off while keeping Wake-on-LAN. Wake-event options — real-time clock alarm, USB wake, PCIe and onboard LAN wake, keyboard and mouse wake — should be checked individually, with unneeded sources disabled. BIOS RGB or standby-light options, where present, are a further layer alongside the software shutdown effect. After each BIOS change, save, restart once, and run a shutdown comparison before changing anything else. Option names and locations differ between motherboard makers, so the motherboard manufacturer's documentation and the actual BIOS screens for the installed board are the final authority, and no single maker's path should be treated as universal.

Step 5: Check the RGB software and hub wiring layer. In the RGB software, check the shutdown effect setting and set it to off for the comparison, where a keep-lit option is present. In the wiring, determine whether each fan and light strip connects directly to a motherboard fan or addressable RGB header, or through an independent hub or controller. Where a hub is present, note its power cable source, whether SATA or Molex, and its control cable source, whether USB or addressable RGB. A comparison with the hub power disconnected, carried out in the shutdown state and following the manufacturer's instructions, can establish whether the hub's independent power is the source. Where a graphics card light is controlled by both motherboard software and graphics card software, both must be checked, because one can overwrite the other.

Step 6: Before any hardware suspicion, exclude the remaining low-cost explanations. Check the power cord, extension lead, and power strip for independent switches or smart-socket schedules, and for USB charging sockets that could supply an external path and mislead the diagnosis. Consider motherboard BIOS version as a factor: an outdated BIOS can produce abnormal power-management behaviour, and a BIOS update is a possible step, but it carries risk, must follow the manufacturer's procedure without interruption, and should not be presented as a guaranteed fix. Graphics card firmware is a theoretical factor in a very small number of cases; it should be described as such, and unofficial firmware should not be used. Only after the settings layers, the hub layer, and these exclusions have been worked through does hardware suspicion become the reasonable next step.

Boundary Cases: Normal Behaviour, and Signals That Warrant Inspection

Several post-shutdown behaviours are normal and need no repair, and naming them first prevents unnecessary work. A power-button or motherboard standby light glowing faintly, USB charging while off, or a keyboard light glowing faintly, where the user has enabled standby charging or wake functions, is consistent with those functions being on. A brief fan spin after shutdown that then stops is consistent with residual discharge. A light that stays on because the user set a shutdown lighting effect in RGB software is consistent with that setting. In any of these cases, if the user accepts the behaviour, the power supply rear switch or a switched power strip is a sufficient everyday control, and no BIOS change is required.

This article does not apply to a system that cannot shut down at all, that returns to the desktop or restarts by itself after a shutdown command, that fails its power-on self-test, that crashes while idle, that wakes from sleep with no picture, or that became unstable after a power cut. Those symptoms each belong to a different diagnosis, and ErP or wake settings cannot be applied to them as a blanket fix.

Consider professional inspection when several of the following signals are present, or when every settings layer, the software layer, and the hub layer have been excluded and the behaviour continues. The signals are: fans or lights staying on for a long time after the power supply rear switch is off and the cord is unplugged, which is not a normal standby path; a fan spinning continuously at high speed after shutdown, or the whole system looking as though it never stopped; any added smell, unusual noise, intermittent restarting, or boot instability alongside the behaviour; a graphics card fan that keeps spinning at near-operating speed after ErP, wake, lighting, and hub causes have all been excluded; and any accompanying power-on self-test failure, display abnormality, or power instability, which moves the case beyond this article's scope.

Readers should not open a power supply, modify its internals, short power pins, use unofficial firmware on a graphics card or motherboard, or remove and insert graphics card power cables while mains power is connected. Before seeking inspection, it helps to gather the motherboard model and BIOS version, the graphics card model, the result of the power-supply rear-switch test, the list of exactly which lights and fans stay on, the current ErP and wake settings, the RGB software shutdown lighting setting, and when the behaviour began, for example after a hardware change, a driver update, or a BIOS change. That record allows an inspection to start from the layer already isolated.

Misconceptions, Corrected in One Place

A light on after shutdown does not mean the computer is still running or the graphics card is still working at full speed. In soft-off, the power supply can still provide standby power, and a light proves only that a standby circuit has power.

Shutdown does not mean complete disconnection from mains electricity. While the power supply is connected and its rear switch is on, standby power can exist. Only mechanical off, with the rear switch off or the cord unplugged, removes mains input entirely.

Enabling ErP does not guarantee that every light goes out. ErP tightens standby power, but independently powered hubs, RGB shutdown effects, and individual motherboard designs can still leave some lights on.

Disabling ErP does not simultaneously preserve Wake-on-LAN and switch off every USB light. The two functions often share the same standby path, and not every motherboard can separate them fully. The correct approach is a trade-off chosen per motherboard design, not a setting that delivers both unconditionally.

A spinning fan does not, on its own, prove a graphics card fault. Fan power can come through a hub, a motherboard fan header, or a standby circuit, and the source must be separated before any component is blamed.

Changing RGB software is not the same as changing BIOS settings. The software shutdown effect and the BIOS ErP and wake settings are two control layers, and both must be checked.

A Fast Startup shutdown is not a full shutdown. It is a hybrid shutdown that saves kernel state, while Restart is the path that always performs a full cold boot.

A system waking by itself at night is not the same problem as a light staying on after shutdown. The first is a wake event, from a clock alarm, a scheduled task, a network packet, or a USB signal. The second is standby power. The diagnostic tools and the settings layers differ accordingly.

Unplugging the power cord is not the end of the diagnosis. It proves that the standby path comes from mains power, but the BIOS, software, and hub settings must still be worked through, or the behaviour will return the next time mains power is reconnected.

Updating BIOS or firmware is not the first step. Settings-layer diagnosis is lower in cost and lower in risk, and it should come first. Firmware work carries risk and belongs only to a small number of cases, after the settings layers have been excluded.

When Inspection Is Warranted, and What to Prepare

If the ordered checks above have been completed, the settings layers have been excluded, and a fan still spins continuously or a light pattern remains that does not belong to any normal standby path, inspection is the reasonable next step rather than further adjustment by trial and error. Inspection in this context means a check of the power and graphics output path against the information already gathered, not a promise of a particular outcome.

For readers in Hong Kong who reach that point, the workshop is at Shek Mun, Dali Plaza, Room 1209. The telephone number is 2186 8010 and the WhatsApp number is 6558 6806. Bringing the motherboard model and BIOS version, the graphics card model, the power-supply rear-switch test result, the list of lights and fans that stay on, the current ErP and wake settings, the RGB software shutdown lighting setting, and the date the behaviour began allows the check to start from the layer already isolated. Where a repair is relevant, fees fall within the published range of HK$400 to HK$2,800, subject to inspection quote. That range is not a fixed quote for any particular fault, and the applicable figure depends on what inspection finds.

Frequently Asked Questions

Is it normal for a graphics card light to stay on after I shut down my computer?

It can be normal. While the power supply is connected to mains electricity and its rear switch is on, standby power can keep a standby light, a wake circuit, or USB charging alive even though the system has stopped. The power-supply rear-switch test distinguishes this normal standby path from any other power source: if the light goes out when the rear switch is off, mains standby power is the source.

Why does my graphics card fan spin briefly after shutdown and then stop?

A brief spin that then stops is consistent with residual capacitor discharge or a delayed fan-controller stop. The observation that matters is duration and repetition: a short spin that stops, happening consistently, is a different pattern from a fan that keeps spinning continuously, and only the continuous pattern points toward a standby power path or a system that never truly entered soft-off.

I enabled ErP, but one light still stays on. Did the setting fail?

Not necessarily. ErP tightens motherboard standby power, but it does not control every power path. A light powered through an independent hub, a light held on by an RGB software shutdown effect, or a standby circuit that a particular motherboard design retains can all remain lit with ErP enabled. Identifying which item stays lit, and where its power comes from, is the next step.

Will turning off ErP let me keep Wake-on-LAN and still switch off all USB lights?

Not reliably, because the two functions often share the same standby power path, and not every motherboard can separate them fully. The practical approach is to choose per motherboard: use the finer-grained USB standby and wake-event options where they exist, keep only the wake sources that are actually needed, and accept that some combinations cannot both be satisfied on every board.

My computer wakes by itself at night. Is that the same as a light staying on after shutdown?

No. A system waking by itself is a wake event, caused by a clock alarm, a scheduled task or wake timer, a network wake packet, or a USB signal. A light staying on with no wake is standby power. The wake case is investigated with the powercfg commands and the BIOS and Windows wake settings; the standby-light case is investigated with the power-supply switch test and the ErP, lighting, and hub settings.

Should I just update the BIOS to fix a fan or light that stays on after shutdown?

No, not as a first step. Settings-layer checks — the power-supply switch test, the Windows Fast Startup and wake-device settings, the BIOS ErP and wake-event options, the RGB shutdown effect, and the hub wiring — are lower in cost and lower in risk, and they resolve the standby-power cases in this article's scope. A BIOS update is a later consideration, it must follow the manufacturer's procedure without interruption, and it should not be presented as a certain fix.