Turning off a Windows display and putting Windows to sleep can look almost identical from the desk: the screen becomes black, the room gets quiet, and the machine appears to be doing nothing. Under the surface, however, these are different power-management situations. Display off can leave the computer fully running in S0, while traditional S3 sleep removes power from the processor and keeps system memory refreshed. Modern Standby adds another layer because Windows can move through a screen-off phase before reaching a deeper low-power state.
That difference answers several practical questions. Why can a laptop continue working after its display turns off? Why does the same laptop stop most activity after Sleep? Why does RAM keep an open session alive when the CPU is no longer executing normal application code? And why do newer Windows PCs sometimes behave differently from older machines even though both options look like "sleep"?
Display Off Does Not Mean the Windows Session Has Stopped
The simplest case is a display timeout. Windows can turn off the monitor while keeping the operating system in its normal working state, S0. Microsoft describes S0 as the fully operational state and explicitly notes that the computer remains in a full running state whether the screen is on or off. The display is only one component of the system, not the boundary between "on" and "off."
That means the CPU can continue executing instructions after the screen goes dark. Programs may keep processing files, compiling code, calculating data, communicating over a network, or waiting for timers and hardware events. CPU cores can still enter their own idle states when they have no work, but Windows has not suspended the whole machine merely because the panel is dark.
RAM is therefore ordinary working memory in this situation. Its contents do not need to be preserved as a special sleep snapshot because the operating system is still running normally. A browser tab, an open document, or an application's allocated memory remains part of the live system state.
This is why "turn off display after 10 minutes" and "put the computer to sleep after 10 minutes" are not equivalent settings. Microsoft documents separate display and sleep idle timers precisely because a system can remain fully running while its display is powered down.
Traditional S3 Sleep Turns the CPU Off but Keeps RAM Alive
Traditional sleep, commonly associated with ACPI S3, takes the power-saving idea much further. In S3, the processor is off and CPU cache and processor context are not retained, while system memory remains powered and refreshed. Microsoft describes S3 as a state where only system memory is retained, allowing Windows to resume without a normal operating-system reboot.
This produces a useful mental picture: the CPU stops working, but RAM keeps the stage set.
Suppose a system has an application open with a large amount of data in memory. Entering S3 does not mean Windows writes that entire live session to disk and then reconstructs it from scratch at every wake. The important system memory remains available because DRAM is kept in a refreshed state. The processor and other hardware context can be lost, then restored as the machine returns to the working state.
That is also why S3 sleep needs more power than hibernation. RAM must remain powered, while hibernation stores the operating-system context in a hibernation file and powers the hardware down much further. S4 is designed as a lower-power state with longer wake latency.
The CPU question is therefore surprisingly simple for classic S3: it is not sitting there executing Windows in the background at normal speed. The processor is powered off. RAM is the part that remains alive specifically to preserve the working session.
Modern Standby Makes the Screen Off Phase More Complicated
Newer Windows PCs may use Modern Standby instead of S3. Microsoft defines Modern Standby as an S0 low-power idle model, and a system using that model does not use S1-S3. From the user's perspective, however, the experience still looks like sleep: press the power button, the screen goes dark, and the computer wakes quickly.
Modern Standby is deliberately more dynamic than classic S3. Microsoft separates a Modern Standby session into a Screen Off phase and a Sleep phase. After the screen turns off, Windows first quiets applications, drivers, and hardware. Once the platform reaches its low-power phase, it spends most of the time in a deep idle condition called DRIPS.
This explains an apparently contradictory behavior: a sleeping Modern Standby computer can sometimes perform a small amount of background work. The processor is not running continuously like it does with a simple display-off state. Instead, the platform can briefly wake for permitted tasks and then return to its lowest-power idle condition.
Microsoft describes DRIPS as a state in which no CPU code is allowed to run. Memory contents are preserved in self-refresh, while selected hardware can wake the system for events such as networking or input.
The practical result is that "CPU off" is a useful description of the deepest low-power portion, but not a complete description of the whole Modern Standby session. There can be short active intervals between long periods of deep idle.
What Actually Happens to RAM When Windows Sleeps
RAM is often described as if it were simply "kept on," but the hardware mechanism is more interesting. DRAM stores information in cells that require periodic refresh. During low-power operation, supported platforms can place memory into self-refresh so the memory subsystem maintains its contents without normal CPU-driven activity.
Microsoft describes both S3 and Modern Standby around this principle, although the surrounding power architecture differs. In S3, system memory is retained while the processor and much of the rest of the system lose power. In Modern Standby's deepest idle state, memory is preserved in self-refresh while the SoC reaches a very low-power condition.
This is why a sleeping PC can preserve an open session without keeping the CPU busy. The data is still physically present in volatile memory, but the processor is not required to execute the application code that created it.
There is an important limit: volatile memory is not permanent storage. If the machine loses the power needed to maintain RAM, the contents disappear. That is fundamentally different from hibernation, where Windows writes an image of memory to storage before powering the hardware down.
A useful comparison is to think of RAM as a whiteboard and storage as a notebook. Sleep keeps the room dark while preserving the whiteboard. Hibernation copies the board into the notebook so the room can be completely powered down.
Why the CPU Can Be Idle Even When the Display Is On
The opposite misconception is just as common: a running Windows PC does not keep every CPU core busy merely because the operating system is awake. Modern processors constantly move between active and low-power idle states depending on workload.
That matters because "display off" is not a CPU power state in the same sense as S3 or Modern Standby. The screen can be off while Windows remains in S0, and the CPU can independently spend much of its time idle. A machine with no active workload may therefore consume far less power than a machine rendering a game, even though both are technically in S0. Microsoft notes that Windows manages CPU power states continuously, including when the screen is on, and uses the same general power-management mechanisms during Modern Standby.
The distinction is easiest to remember this way:
-
Display off only: the Windows session can keep running normally;
-
Traditional S3 sleep: the processor is off while RAM remains refreshed;
-
Modern Standby: the system moves into a low-power S0 idle model, with the CPU spending most of the time in deep idle and brief wake periods allowed for selected work;
-
Hibernate: Windows saves the memory image to storage and powers the machine down much further.
These states may produce the same black screen, but they are not interchangeable.
Why Windows Sometimes Wakes Briefly During Modern Standby
A modern laptop is expected to wake quickly and may still need to respond to selected events while appearing asleep. Microsoft describes networking, input, timers, maintenance, and other hardware events as possible wake sources for Modern Standby systems. The platform can leave its deepest idle state, perform a permitted operation, and return to low power.
The key word is "briefly." Modern Standby is not intended to behave like a desktop that simply continues running with the monitor switched off. Its design goal is to keep the average power level low by spending most of the session in the deepest idle condition.
That is why battery drain during Modern Standby can still occur even though the display is dark. The machine is not necessarily electrically equivalent to a powered-off PC. Network hardware, firmware, memory, and other platform components may remain in carefully controlled states, and the SoC can wake for approved events.
On a traditional S3 machine, the picture is different. The system enters a fixed sleep state in which the processor is off and RAM is retained. The amount of background activity is therefore much more limited.
Which Mode Is Better Depends on What "Idle" Means
The choice between display off and sleep is really a choice about whether the computer should remain a working machine or become a low-power machine that preserves its session.
Display off is appropriate when the computer still needs to work. A long calculation, a file operation, or another permitted task can continue because Windows remains in its normal running state. The exact behavior still depends on the application and on other power-management settings.
Sleep is appropriate when the active work should stop but the session should remain immediately available. With S3, the CPU and much of the platform power down while RAM preserves the system state. With Modern Standby, Windows and the hardware cooperate to reach very low power while retaining selected background capabilities.
The most useful diagnostic question is not "Is the screen black?" It is "Which system power state is Windows actually using?" A black display tells almost nothing by itself. It can represent an ordinary S0 session with the monitor powered down, a Modern Standby transition, or a deeper traditional sleep state.
Once that distinction is clear, the behavior stops looking mysterious. Turning off the display changes the visibility and power use of one component. Sleep changes the power state of the platform while preserving enough memory and system context to resume the user's session. The screen is merely the messenger; the CPU, RAM, firmware, drivers, and Windows power manager are doing the real work.