Game Screen Frozen on the Last Frame While Audio Keeps Playing? Present-Queue Stall, Logic Still Running and Full-Freeze Diagnosis Guide

2026-11-19 | GPU Repair | 16 minutes | HK GPU Fix Editorial Team

Game Screen Frozen on the Last Frame While Audio Keeps Playing? Present-Queue Stall, Logic Still Running and Full-Freeze Diagnosis Guide

Key takeaway

The screen stops on one correct, complete frame while the game music, dialogue and effects keep moving forward. That shape points at a stall in the presentation step, not the game logic, which runs on a separate path. Two comparisons decide the case: Alt+Tab to the desktop, and asking teammates whether your character still moves.

The shape of this fault — and why the shape is the diagnosis

This article is about one narrowly defined symptom. During a game, the picture suddenly stops on the last frame and does not move at all, while the picture itself remains complete: the game scene, the character and the interface are all still there, clear and intact. It is not a single solid colour, not a black screen and not a corrupted, garbled picture. At the same time the sound keeps going forward: the music, the dialogue and the sound effects continue to play, and the content keeps bringing new material. It is not the same one-second fragment looping over and over, and it is not silence.

Both halves of that definition must be present. If either half is missing, the fault is a different one, and the tests below will not apply.

Three shapes that look similar at first glance are in fact three different faults, and each one is diagnosed differently:

ShapeWhat the picture showsWhat the sound doesDirection to follow
Last-frame freeze (this article)The last frame, complete and correct, simply not updatingSound keeps moving forward with new contentPresent-queue stall — this guide
Solid-colour freezeThe whole screen becomes one single colourSound may continue, repeat or stopA different fault: the frame buffer contents have been replaced by a single colour
Full system freezeThe picture does not moveThe sound stops as well, and the keyboard stops respondingA different fault: the whole machine has locked up

Confusing the first shape with the second or third is a common reason this fault gets misdiagnosed. A frozen picture does not by itself say where the fault sits. Only the combination — correct last frame plus sound moving forward — narrows the fault to the presentation step, and even then the narrowing has to be confirmed by the tests below, not assumed from the symptom alone.

How a frame is produced, and why sound can outlive the picture

Every frame a game shows is the result of a relay between two different jobs. The CPU runs the game logic: the rules of the game, the physics, the behaviour of computer-controlled characters, and the player's inputs. It then hands drawing instructions to the graphics driver. The graphics card executes those instructions, draws the picture, and sends it through the present queue — also called the swap chain — to the display. When the picture stops on the last frame, it means the presentation step has stopped. It does not mean the logic step has stopped, because the two steps run on separate paths.

Sound runs on yet another path again. The Windows audio system runs on its own core thread, separate from the graphics card's presentation pipeline. External guidance on this fault makes the same point from two angles: one source describes graphics and sound as running separately, so a stuck picture does not necessarily mean the sound stops; another describes the audio driver as running on a different core thread and continuing while the display pipeline fails. That is why sound continuing proves nothing about the picture path. It only proves that the sound path is still running.

The exact state of the sound is itself evidence, but it has to be read carefully. Sound that keeps bringing new content — new music, new dialogue, new effects — is evidence that the game logic is still advancing. A one-second fragment looping over and over, like a broken record, is the opposite evidence: it suggests that the program, or the audio buffer, has also become stuck. Silence is a third state again, pointing in the direction of a full freeze. All three states must be recorded at the moment the fault happens, not reconstructed from memory afterwards, because memory of exactly what the sound was doing a minute earlier is unreliable.

There is one more piece of mechanism that matters before any testing begins. Windows has a driver timeout reset mechanism, known as TDR, with a default time limit of two seconds: if the graphics engine does not finish its work within that limit, Windows resets the display driver, and when the reset succeeds the picture flickers briefly and then recovers. A freeze is therefore not the moment to force the machine off. The first step is to wait 30 to 60 seconds and give TDR the chance to complete its reset. If the picture returns by itself after a flicker, the fault belongs to the driver-reset direction, not to this guide.

The two decisive forks

Most checks in this area can only narrow the fault slightly. Two comparisons decide it. Everything else in this guide is supporting evidence around them.

Fork one: the Alt+Tab desktop comparison

While the picture is frozen, press Alt+Tab and switch to the desktop. If the desktop comes back and works normally, the compositor is still running and the stall is confined to the game's rendering or presentation layer. If the desktop does not come back either, the stall covers a wider area, and the fault should be treated as a full-freeze direction instead.

This test must not be overstated. A desktop that returns does not prove the graphics card is healthy, and it does not prove the driver is healthy. It proves only that the machine has not completely locked up and that the compositor is still running. External guidance on this fault makes the same caution: check whether Windows is still responding first, and compare with other games — a desktop that returns is evidence against a complete lock-up, not evidence for a healthy driver.

Fork two: the online-game world comparison

If the game being played is an online game, ask your teammates whether your character is still moving, and whether voice chat is still working. If they say your character is still moving and voice chat is normal, the game logic is still running and only your picture presentation has stopped. If they say your character is standing still, the logic may have stopped as well.

Offline games need a different form of the same question, and its limit has to be stated honestly: the in-game clock or animation would show whether the game world is still advancing, but the picture has stopped, so the clock cannot be seen. For an offline game, this comparison can only rely on whether the sound content is still advancing, and that limitation should be kept in mind when weighing the result. The two forks together — desktop returns plus teammates see you moving — are what point at a present-queue stall. Either one alone is weaker than both together.

The six suspect layers

Once the two forks have been run, the result maps onto one of six layers. The layers are listed from the most specific to this fault to the widest.

LayerWhat points at itWhat argues against it
1. Present-queue stallLast frame plus sound moving forward plus desktop returning on Alt+Tab, all three togetherAny one of the three missing
2. Driver timeout / resetThe picture returns by itself after waiting, or Event Viewer shows Event 4101 or LiveKernelEvent 141No reset, no such event, and the freeze repeats identically
3. The game itself deadlockingOnly one game is affected, especially after an update or a mod changeEvery game freezes the same way
4. Load, temperature or powerLowering the texture or resolution setting by one level stops the fault from returningThe fault returns at the lowest settings as well
5. Display mode / compositionSwitching between exclusive fullscreen and borderless window changes the behaviourThe fault is identical in both modes
6. Full system freezeSound stops too, keyboard lights stop responding, Ctrl+Alt+Del does not returnSound continues and the desktop returns — then this is not the layer

A note on layer two: Event 4101 records that the driver once timed out and was reset. It is not a conviction that the hardware is faulty. Its causes can include the driver, the power supply, overheating, overclocking, or a program's instructions, and it only gains meaning when combined with how often it appears and with the comparison tests. The same caution applies to the temperature figures published by one external source — GPU core temperatures of 85–90°C, memory at 95°C and CPU at 95°C — which are that source's figures, unverified by this shop, and must not be used here as a threshold for deciding anything.

Seven-step diagnosis

  1. Define the shape. Confirm that the picture is a last frame with complete content and that the sound is moving forward with new content. It is not a solid colour, not a black screen and not repeating audio.
  2. Wait 30 to 60 seconds. Give TDR the chance to complete a driver reset. Do not press anything in the meantime. If the picture flickers back by itself, follow the driver-reset direction; only continue if it does not return.
  3. Run the Alt+Tab desktop comparison. Note whether the desktop returns and whether it works normally, and record the result.
  4. Record the sound and cursor state in one line. Note whether the sound is moving forward, repeating or silent, and whether the mouse cursor still moves — the hardware cursor is drawn by an independent cursor plane that does not pass through the main frame buffer, so a cursor that still moves means the main frame buffer has stalled while the cursor layer is still running — along with which game and which scene were on screen.
  5. Run the Ctrl+Alt+Del system-survival test. If the security screen appears, Windows is still responding and the stall is confined to the game or rendering layer; if it does not appear, the affected area is wider.
  6. Press Win+Ctrl+Shift+B to reset the display driver. If the picture returns, that points at a driver or composition state problem; if nothing happens, continue. This is a diagnostic test only, not a repair method, and needing it repeatedly means the underlying cause has not been dealt with.
  7. Compare games and settings, then gather evidence after the event. After restarting, try a different game and lower the settings by one level; in Event Viewer look for Event 4101 or LiveKernelEvent 141. If the layers still cannot be separated, stop and bring the full record — the game, the scene, the sound state, the Alt+Tab result, the cursor result and the event entries — to the shop at Room 1209, Dali Plaza, Shek Mun, telephone 2186 8010, WhatsApp 6558 6806.

Boundary cases — when this is not the fault

One further caution belongs here. A screenshot taken while the picture is frozen shows only the last frame itself. It is not independent evidence of anything, and it should not be treated as layered proof of the fault.

Six common mistakes

  1. Sound continuing means the machine is fine. Wrong. Sound runs on its own thread, and the picture can stop while the sound carries on.
  2. A frozen picture means the graphics card has burned out. Wrong. A driver timeout, a game deadlock and a present-queue stall can all freeze the picture; no such conclusion can be drawn without the comparisons.
  3. Sound continuing means the game is fine. Wrong. Logic still running is not the same as presentation being fine; the two are separate paths.
  4. The desktop returning on Alt+Tab means the graphics card is fine. Wrong. It only means the machine has not completely locked up and the compositor is still running; it says nothing about driver health.
  5. Win+Ctrl+Shift+B is a repair. Wrong. It only resets the display driver state. If it has to be used again and again, the root cause has not been dealt with.
  6. Event 4101 appearing means the graphics hardware is faulty. Wrong. Event 4101 only records that the driver once timed out and was reset; its causes can be the driver, power, heat, overclocking or program instructions, and it needs frequency plus comparison tests before it can indicate a direction.

What is not known

Three things should be stated plainly rather than guessed. First, the exact stall position behind each last-frame freeze — present queue, driver or game logic — has no settled conclusion in the public material available, so no single one of them can be written here as a proven mechanism; what is known is the symptom shape and the testing logic. Second, which cause is most common has no settled answer either: the external sources disagree, some pointing at the driver, others at temperature or power, and this shop cannot present any one of them as its own conclusion. Third, no temperature threshold can be used as a standard for deciding this fault; temperature figures appear only as a named external source's figures, unverified by this shop.

Sources

Frequently asked questions

If the sound keeps playing, is my graphics card definitely fine?

No. Sound and picture run on separate paths. Sound continuing proves only that the sound path is still running; it says nothing about the graphics card, the driver or the present queue.

The desktop came back when I pressed Alt+Tab. Does that mean the graphics card is fine?

No. It means the machine has not completely locked up and the compositor is still running. It does not prove the driver is healthy, and it is not a reason to stop diagnosing.

My teammates say my character is still moving, but my screen is frozen. What does that mean?

It means the game logic is still running and only your picture presentation has stopped. That combination is the strongest evidence for a present-queue stall, and it is worth recording exactly what your teammates saw.

The picture came back by itself after a few seconds. Is the fault gone?

Not necessarily. A brief return can be a driver reset completing. Note whether it happens again, how often, and whether Event Viewer shows Event 4101 or LiveKernelEvent 141.

Event Viewer shows Event 4101. Does that mean the graphics card hardware is faulty?

No. Event 4101 records that the driver once timed out and was reset. Its causes can include the driver, power, heat, overclocking or program instructions. Frequency and comparison tests are needed before it can indicate a direction.

Can I use a screenshot as proof of the fault?

No. A screenshot taken while the picture is frozen shows only the last frame itself, which is the symptom, not independent evidence.

When should I stop testing and bring the machine in?

When the two decisive comparisons and the seven steps still do not separate the layers, or when the freeze repeats. Bring the full record — game, scene, sound state, Alt+Tab result, cursor result and event entries — to Room 1209, Dali Plaza, Shek Mun. The shop's published three-tier service charges are HK$400–2,800; telephone 2186 8010, WhatsApp 6558 6806.

Glossary

Related articles

Related services

If you need Chip-level GPU repair, see these service pages: