GPU Object Flickering in Games? Z-Fighting, Depth-Buffer Precision & Coplanar Surfaces Diagnosis Guide

2026-11-14 | GPU Repair | 29 minutes | HK GPU Fix Editorial Team

GPU Object Flickering in Games? Z-Fighting, Depth-Buffer Precision & Coplanar Surfaces Diagnosis Guide

Key Takeaway

When a game surface flickers only while the camera moves, the cause is often not a dying graphics card: two surfaces are fighting over the same depth position, and the depth buffer cannot tell which one is in front. Record the game, scene, and surface, then use the screenshot test to separate a rendering problem from a hardware fault.

What This Problem Is — and What It Is Not

The same game, the same scene. A wall, a stretch of ground, a decal on a wall, or the edge of an overlapping object keeps flickering and jumping while the camera moves, as if two pictures were fighting over the same spot. Stop the camera, and the flickering eases or disappears altogether. Move the camera again, and it comes straight back. That shape — flicker while moving, calm while still — is the whole problem this guide covers, and it is the most important piece of evidence in the diagnosis.

The mechanism behind it is simple to state and easy to misread. The graphics card uses a depth buffer to decide, for every pixel, which surface is in front: each surface carries a depth value, the nearer surface wins, and the farther one is hidden. But the depth buffer has only a fixed, limited set of values to cover the whole visible range, so when two surfaces sit at the same depth, or so close together that the buffer cannot separate them, it cannot decide which one is nearer. Frame by frame, pixel by pixel, it takes turns drawing one and then the other — and the surface flickers. The reference entry on z-fighting describes exactly this: two or more shapes at very similar distances from the camera, a buffer that cannot distinguish precisely which one is farther, and a flickering, noisy result as the two shapes fight to colour the same pixels.

That is the counter-intuitive core of this guide: flicker does not mean the graphics card is broken. It means two surfaces are contesting one depth position. A dying card announces itself differently — with fixed patterns, freezes, and crashes — and this guide keeps those two stories apart from the first paragraph to the last.

Four conditions must all be true before the steps below apply:

  1. The flicker sits on specific surfaces — a wall, the ground, a decal, an overlapping object edge — rather than across the whole screen at once.
  2. The flicker appears or worsens while the camera moves, and eases or disappears when the camera is completely still.
  3. The game keeps running. There is no crash, no freeze, and no black screen while the flicker happens.
  4. The symptom repeats at the same scene and the same surface, rather than appearing once at random and never returning.

This guide is not about every kind of flicker. A whole screen that pulses in brightness is a different problem. A staircase edge along a slanted line is an anti-aliasing problem. Fine detail such as wire mesh or leaves that appears and vanishes as it is sampled is a shading problem. A picture that turns blurry or smeared after upscaling is switched on is an upscaling problem. Coloured blocks, checkerboards, and corrupted textures that stay put are a hardware pattern problem. Each of those belongs to its own guide, and the boundaries section at the end of this article says which one to follow. What follows here is only the flicker of surfaces fighting over depth.

The Five Suspicion Layers

Surface flicker can come from five layers, and they must be kept separate. Mixing them together is how a settings problem gets treated by replacing hardware, or a problem in the game's own geometry gets treated by changing the cable again and again, and how the real cause survives because the wrong layer was treated. The five layers below are ordered the way the diagnosis should work through them, and each one has its own deciding test.

Layer One: The Depth-Buffer Layer — Two Surfaces, One Depth Position

The first layer is the depth buffer itself, and it is the layer most often misunderstood. For every pixel on screen, the graphics card compares depth values and draws whichever surface is nearer, hiding the one behind it. That comparison only works when the two depth values are far enough apart for the buffer to tell them apart. The buffer holds a fixed, limited number of values for the entire visible range, so two surfaces whose depth values are identical, or differ by less than one step of that limited scale, look the same to it. It cannot tell which one is nearer, so it alternates — one frame it draws the first surface on top, the next frame the second — and the surface flickers.

The deciding evidence for this layer is the shape of the symptom itself: flicker confined to a surface, appearing while the camera moves, vanishing when the camera stops. A pattern is only a clue, not a diagnosis, and this shape is the clue that points at depth. It also explains why the flicker can look noisy and irregular rather than rhythmic: the decision flips pixel by pixel as the camera angle shifts by tiny amounts, so different parts of the same surface can flicker out of step with each other. Nothing here points at heat, load, or a failing part, and that absence is itself evidence — the flicker follows the camera, not the temperature or the workload.

Layer Two: The Distance Layer — Precision Is Not Shared Evenly

The second layer is distance, and it explains where the flicker shows up. Depth precision is not spread evenly across the visible range: it is much higher close to the camera and much lower far away, and the wider the span between the nearest and farthest distances the game has to draw, the more precision is wasted on empty range. So z-fighting is most common on distant surfaces — a far wall, a distant stretch of ground, a hillside — and rare up close, where the buffer still has room to separate two nearby depths.

That is why the same game can look perfect at close range and start flickering as soon as the view opens up and the camera looks far away. The mechanism is direction, not distance: farther means worse, nearer means better, and no universal distance figure exists for when it starts, because the point at which it appears depends on the scene, the game, and the depth range that particular game uses. Any source that states a single distance at which flicker begins should be set aside. The deciding test for this layer is the near-far comparison in Step 4: walk up to the same surface, then step back, and watch whether the flicker follows the distance.

Layer Three: The Coplanar Layer — Surfaces Designed to Overlap

The third layer is coplanar surfaces, and it is different from the first layer in a way that matters. In the first layer, the buffer lacks the precision to separate two surfaces that are merely close together. In this layer, the geometry itself overlaps: a decal pasted onto a wall, two wall panels built at the same position, repeated geometry stacked exactly on top of itself. These surfaces occupy the same plane, so their depth values are identical, and no amount of precision could separate them — the contest is built into the scene, not into the hardware.

The deciding evidence here is location. Coplanar flicker stays pinned to the specific overlapping spot — the edge of a decal, the join where two wall panels meet — while the rest of the view stays calm. Depth-precision flicker, by contrast, spreads across whole distant surfaces. So the question to ask is not only whether the surface flickers, but where: a flicker that follows one decal everywhere it appears points at the decal's placement, while a flicker that covers every distant wall points at precision. That distinction decides whether the problem belongs to one object in the scene or to the whole depth range, and it is the reason Step 4 tests distance before anything is changed.

Layer Four: The Settings Layer — Forced Driver Settings and Upscaling Change the Render Path

The fourth layer is settings, and it can make the flicker worse without being its cause. Driver-forced anti-aliasing and driver-forced anisotropic filtering change the game's original render path: the game was built to be drawn one way, and the driver overrides part of that drawing. That change can aggravate flicker on surfaces that were already close to the edge of what the depth buffer could separate. Upscaling does something similar from a different direction: it draws at a lower internal resolution and then reconstructs the picture back up, and fine detail can flicker during that reconstruction. Picture problems caused by upscaling are not, on their own, evidence that the graphics card is damaged.

The diagnostic value of this layer is the on-off comparison. Turn upscaling off and use the native resolution, restore the forced driver settings to their defaults, and test the same scene after each single change to see whether the flicker follows the setting. Settings can aggravate flicker, but they are not its cause — turning on anti-aliasing does not cause z-fighting, because the contest for depth exists in the scene whether the setting is on or off. What a setting changes is how visible that contest becomes, and that is exactly what the on-off comparison in Step 6 is built to reveal.

Layer Five: The Hardware Layer — Fault Patterns Look Completely Different

The fifth layer is hardware, and it is the layer that closes the fork rather than opening it. A memory fault tends to show as coloured blocks, straight lines, a checkerboard, or corrupted textures, and a damage pattern that changes with the picture content points toward the memory. A core fault tends to show as the whole picture freezing, the driver crashing, or the machine dying as soon as a three-dimensional load starts. Z-fighting is none of these: it is a specific surface flickering while the camera moves, it does not follow temperature or load, and it does not crash the game.

This layer is the closing fork, and it must be ruled out before the rendering explanation can stand with confidence: exclude the hardware patterns first, and what remains is a rendering problem with a known mechanism. If the picture shows a fixed pattern that stays put while the camera moves, or the game freezes or the screen goes black alongside the flicker, the problem has left this guide and the hardware route in Step 7 applies. If none of those signs is present, the flicker belongs to the four layers above, and no part needs to be blamed for it.

LayerWhat is happeningDeciding evidenceWhat it means
1. Depth bufferTwo surfaces share one depth position and the buffer cannot tell which is nearerFlicker confined to a surface, worst while the camera movesA rendering contest, not a hardware fault
2. DistancePrecision is high near the camera and low far awayDistant surfaces flicker, near surfaces stay calmThe depth range is the problem, not one object
3. CoplanarSurfaces designed to overlap occupy the same planeFlicker pinned to one decal edge or one wall joinThe geometry itself overlaps
4. SettingsForced driver settings or upscaling change the render pathFlicker follows a setting when it is toggledThe setting aggravates the flicker, it does not create it
5. HardwareMemory or core fault shows a fixed pattern, a freeze, or a crashFixed pattern, freeze, crash, or black screenThe problem has left this guide

The Seven Diagnostic Steps

The seven steps below are ordered so that each one tests one layer, and so that no step destroys the evidence a later step needs. Work through them in order, one variable at a time, and write down the result of each step before moving on. Changing two things at once and seeing the flicker change leaves the reader not knowing which change mattered — and not knowing what to do when the problem returns.

Step 1: Record It — Game, Scene, Surface

Write down which game it happens in, which scene, and which surface — a wall, the ground, a decal, an object edge — together with whether the flicker appears when the camera moves. Do not write only the words "the picture flickers": flicker has many kinds, and the location and the trigger are the clues. Note the game version as well, because a problem in the game's own geometry can change from one version to the next, and that note is what a report to the developer will need later.

This step proves that the problem has been narrowed to a named surface in a named scene, and it records the only direct evidence of where the flicker lives. It proves nothing about why the surface flickers — that is what the later steps are for. But without the game, the scene, and the surface, nothing else can be checked against them. A note that says "the north wall of the market hall flickers when the camera pans, calm when the camera stops" is a diagnosis in progress. A note that says "the picture flickers" is a starting point with no direction.

Step 2: The Camera-Movement Test — Still Means Calm, Moving Means Flicker

Stop the camera completely and watch the surface: does the flicker ease or disappear? Then move the camera slowly and watch again: does the flicker return? Still means calm and moving means flicker points at the rendering layer — z-fighting, shading flicker, and upscaling artefacts are the three candidates there, and the later steps separate them. A still screenshot can hide this difference, so still and moving judgements must be made separately, and a judgement made from a still picture alone is not enough.

If the flicker continues while the camera is completely still, this flow does not apply, and it must not be forced: a still flicker points at another layer — the panel, the signal, or a fixed hardware pattern — and the right guide is the one for that symptom. This step is the gate for the whole diagnosis. Everything after it assumes the flicker follows movement, and if that assumption fails, the honest move is to stop here and follow the other trail.

Step 3: The Screenshot Test — Flicker in the Screenshot, or a Clean Screenshot

Capture a screenshot, or record a short video, and view it on a second device. If the flicker shows in the screenshot as well, the fault sits before the frame buffer — it is in the rendering layer — and the panel and the cable can largely be ruled out. Damage that appears in the screenshot as well sits inside the frame buffer, and the same rule applies here: what the screenshot holds was drawn before the picture ever left the machine. If the screenshot is clean and only the eye sees the flicker, the fault sits after the frame buffer — the picture was drawn correctly, and something changed it on the way to the eye — and the direction turns toward the panel and the cable.

The screenshot test needs care: if the flaw shows in the screenshot, it was produced before the cable and the display, so changing the cable cannot remove it. This step is the most important fork in the whole guide, and it must not be skipped. A still picture alone cannot settle it — a flicker that only appears while moving may not survive in a single still frame — so capture a video as well when a still screenshot shows nothing, and judge the moving picture, not only the still one.

Step 4: The Near-Far Comparison — Distant Flicker or Close Flicker Too

Walk up close to the same surface and look at it, then step back and look at the same surface from farther away. Far flickers and near stays calm points at the depth-precision layer: the buffer can still separate the two surfaces up close, and loses the separation as the distance grows. Near flickers too points at the coplanar layer or the settings layer: surfaces that share one plane flicker at any distance, and a setting that changes the render path can make a near surface flicker as well.

This step narrows which mechanism is at work down to two roads, and it does so without changing a single setting. Keep the scene, the surface, and the settings identical for both looks, and change only the distance. A note that says "the far wall flickers, the same wall calm from two paces away" is a precise result. A note that says "it flickers sometimes" is not.

Step 5: One Game or Every Game

Ask whether the flicker happens in only one game or in every game. Only one game flickering, against every game flickering, points in opposite directions. One game points at that game's geometry or its upscaling integration: overlapping surfaces in one scene, or an upscaling mode interacting with one scene differently from another. Every game points at the driver settings layer or the hardware layer, because a cause that lives in the system shows up everywhere the system is used.

This step decides the direction of everything that follows it. A single-game problem that is treated as a system problem wastes effort on the system, and a system problem that is treated as a single-game problem wastes effort on one game's settings. The split must be made with observation, not with a guess: the same camera-movement test, run in at least two different games, in a comparable scene in each.

Step 6: The On-Off Comparison — One Change at a Time

Turn upscaling off and use the native resolution, and look at the same scene. Restore the forced driver anti-aliasing and forced anisotropic filtering to their defaults, and look at the same scene. Switch to a different quality preset, and look at the same scene. Each time, change only one thing, and write down whether anything changed. If the flicker follows the upscaling toggle, it points at an upscaling artefact: the flicker lives in the reconstruction, and the upscaling guide is the one to follow. If it follows the forced driver settings, it points at the settings layer. If it follows nothing at all, it points at the game's own geometry — coplanar surfaces that no setting can separate.

In older games, flickering textures have been linked to forced driver anti-aliasing, and removing that forced setting is one step in this check. That is the only sense in which a driver setting is a suspect here, and it is a suspect to be tested, not a verdict to be assumed. Never change two settings at once in this step: two changes and a better picture leave the reader not knowing which change mattered, and the same trap waiting at the next game.

Step 7: Decide — and Record What Happened

The decision follows from the steps, and there are three directions.

If the cause is the game's own geometry — coplanar surfaces, or distant precision that no player setting can change — there is no direct fix at the player's level: accept the current picture, wait for a game update, or report the problem to the game's developer with the record from Step 1, including the game version, the scene, and the settings used. The adjustments that would separate those surfaces live inside the game's own code, and they are not settings a player can reach from a menu — so this guide does not present them as steps, and it never asks the reader to edit game files, engine settings, or the registry to chase them.

If the cause is a driver setting, restore the defaults and then test one setting at a time, so the single setting that matters is known by name and can be left off while the rest stay as the reader likes them.

If the suspicion is hardware — a fixed pattern in the screenshot, flicker that does not follow the camera, or flicker that arrives with crashes or black screens — bring the machine in with the complete record: the game name, the scene, the screenshots, and the on-off comparison results. Inspection takes place at Room 1209, Dali Plaza, Shek Mun. You can call 2186 8010, or reach the shop on WhatsApp at 6558 6806. Inspection is charged at the site's published three-tier fees of HK$400–2,800, quoted after inspection. There is no home-visit service and no Mong Kok shop; inspection is carried out in the shop.

StepWhat to doWhat it provesWhat it does not prove
1. Record itGame, scene, surface, and whether the camera movesWhich surface in which scene flickersWhy it flickers
2. Camera-movement testStop the camera, then move it slowlyWhether the flicker follows movementWhich rendering mechanism it is, on its own
3. Screenshot testScreenshot or video, viewed on a second deviceWhether the fault sits before or after the frame bufferWhich surface or setting is at fault
4. Near-far comparisonSame surface, close up and from farther awayWhether distance decides the flickerAnything about the settings
5. One game or every gameSame test in a second gameWhether the cause is per-game or system-levelWhich setting, on its own
6. On-off comparisonUpscaling, forced driver settings, quality preset; one change at a timeWhether a setting moves the flickerAnything, if nothing moves it
7. DecideAccept, report, restore defaults, or bring the record inWhich direction follows from the evidenceAnything beyond the test that was actually run

Six Common Misconceptions

Misconception 1: Object flicker means the graphics card is broken

No. Z-fighting is a rendering-layer problem: two surfaces contest one depth position, and the depth buffer cannot tell which one is nearer. Flicker on its own is not evidence of a hardware fault. The signs that genuinely point at hardware are a fixed pattern, the whole picture freezing, a crash, or a black screen — and none of those is the flicker described in this guide.

Misconception 2: Higher quality settings, or forced anti-aliasing, will fix it

No. Driver-forced anti-aliasing and forced anisotropic filtering change the render path, and they can aggravate flicker rather than cure it. Settings must be tested one at a time in an on-off comparison, never switched on all at once in the hope that more quality means less flicker. More quality and less flicker are not the same thing.

Misconception 3: A still screenshot shows nothing, so there is no problem

No. Z-fighting appears while things move, and a still screenshot can hide the difference. Judgement must be made from the moving picture — a video, or the live game with the camera moving — and a still screenshot alone is never enough to rule the problem out. A clean still frame and a flickering moving picture are entirely consistent with each other.

Misconception 4: All flicker is the same problem

No. A staircase edge is a geometry sampling problem, a fine detail that appears and vanishes is a shading sampling problem, a flaw that follows the upscaling toggle is an upscaling problem, and two surfaces contesting one depth position is a depth problem — four different mechanisms, and the fix for one cannot be used on another. A method that fixes edge sampling cannot cure a flicker that lives in depth, and using the wrong fix is the most common route to disappointment.

Misconception 5: Changing the cable or the monitor will fix it

No. If the flicker shows in the screenshot, the fault sits before the frame buffer, and it never travels through the cable or the monitor — so changing either one cannot remove it. A cable change is an isolation test, a way of ruling the cable out, not a cure for a rendering-layer flicker. The screenshot test in Step 3 settles this before any cable is touched.

Misconception 6: One game flickering means that game damaged the card

No. Overlapping geometry in one game is that game's design or integration problem, and it does not damage hardware. A game-layer problem and a hardware fault are two separate roads, and a conclusion from one cannot be carried onto the other. A game that flickers in one scene and runs cleanly everywhere else has a scene problem, not a card problem.

Boundaries: Problems That Look Similar but Are Not This One

Not every flicker is z-fighting, and the similar problems each belong to their own guide. If the symptom is one of the following, follow that guide, not this one.

A staircase edge along a slanted line is an anti-aliasing problem, and it is judged by the edge, not by a surface. Fine detail such as wire mesh, leaves, or railings that appears and vanishes as it is sampled is a shading flicker, and its mechanism is detail smaller than a pixel, not two surfaces contesting one depth. A picture that turns blurry, smeared, or ghosted after upscaling is switched on is an upscaling quality problem, and an upscaling ghost is a faint trailing image behind a moving object after upscaling is turned on, which shows in the screenshot as well — a leftover of the previous picture, not two surfaces taking turns. Coloured blocks, checkerboards, and corrupted textures that stay put are a hardware pattern problem. A faint shadow left behind after the picture changes, or a mark that stays on the panel when the machine is off, is a panel problem. A missing texture shows up as a flat placeholder colour, visible even when the camera is still — which is different from a flicker that only appears while things move. A game that crashes, goes black, or shows corrupted pictures on an old title is an old-game compatibility problem, not a depth problem.

Finally, there are things this guide will never teach, and a source that teaches them should be closed. Never edit game files, engine settings, or the registry to chase this problem. Never download a single driver file from an unofficial source, and never install an unknown "repair tool". None of these is a diagnosis, and each one trades a working machine for a less safe one. The checks in this guide use only the game's own options, the driver's own settings, screenshots, and observation.

When to Stop and Bring the Machine In

Stop when all seven steps have been worked through, one variable at a time, and the same result appears every time — or when the question becomes which part to change, rather than which layer is at fault. Stop sooner if the screenshot holds a fixed pattern, if the flicker arrives with crashes or black screens, or if the flicker does not follow the camera at all, because those signs have left this guide and belong to the hardware route.

Bring the machine in with the notes from every step: the game name, the scene, the surface, the screenshots or video, and the on-off comparison results. In-store inspection takes place at Room 1209, Dali Plaza, Shek Mun. You can call 2186 8010, or reach the shop on WhatsApp at 6558 6806. Inspection is charged at the site's published three-tier fees of HK$400–2,800, quoted after inspection. There is no home-visit service and no Mong Kok shop; inspection is carried out in the shop.

A diagnosis that ends at the stop line is not a failed diagnosis. A note that says "the north wall flickers while the camera pans and stays calm when it stops, the screenshot shows the flicker, far flickers and near stays calm, one game only, no setting moves it" is a precise description of where the fault lives, and it is exactly what an in-store inspection needs to start from the right place instead of from the beginning.

Frequently Asked Questions

Is object flickering in games a sign my GPU is broken?

Not on its own. Flicker on a specific surface while the camera moves usually means two surfaces are contesting one depth position, and the depth buffer cannot tell which one is nearer. The signs that genuinely point at hardware are different: a fixed pattern that stays put, the whole picture freezing, a crash, or a black screen. If none of those is present, the flicker belongs to the rendering layer, and the steps in this guide separate it from a hardware fault before any part is blamed.

How do I tell z-fighting apart from aliasing / shading flicker?

Look at what flickers and when. Z-fighting is a surface — a wall, the ground, a decal — flickering as a whole while the camera moves, because two surfaces contest one depth position. Aliasing is a staircase edge along a slanted line, judged by the edge rather than by a surface. Shading flicker is fine detail such as wire mesh, leaves, or railings appearing and vanishing as it is sampled, because the detail is smaller than a pixel. Three different mechanisms, three different shapes, and the fix for one cannot be used on another.

Why does the flickering ease when the camera stops moving?

Because the depth decision stops changing. While the camera moves, the depth values of the two contesting surfaces shift by tiny amounts from frame to frame, so the buffer keeps changing its mind about which surface is in front, and the picture flickers. When the camera stops, the depth values stop shifting, the buffer settles on one answer, and the surface stays calm. That is why a still picture can look perfect while the same scene flickers the moment the camera moves.

How does the screenshot test work? What does flicker in the screenshot vs a clean screenshot mean?

Capture a screenshot or a short video and view it on a second device. If the flicker shows in the screenshot, the fault sits before the frame buffer — it is in the rendering layer — and the panel and the cable can largely be ruled out, because the flaw was drawn before the picture ever left the machine. If the screenshot is clean and only the eye sees the flicker, the fault sits after the frame buffer, and the direction turns toward the panel and the cable. Because the flicker may not survive in a single still frame, capture a video as well when a still screenshot shows nothing.

Why does flickering happen more in distant scenery than up close?

Because depth precision is not shared evenly: it is much higher near the camera and much lower far away, and the wider the span the game has to draw, the more precision is wasted. Up close, the buffer still has room to separate two nearby depths, so the surfaces stay calm. Far away, the same two surfaces fall inside one step of the buffer's limited scale, and it can no longer tell which one is nearer. The direction is always the same — farther means worse — but there is no single distance at which it begins, because it depends on the scene and the game.

How do I tell decal / overlapping-surface flicker apart?

Look at where the flicker is pinned. Decal and overlapping-surface flicker stays on the specific overlapping spot — the edge of a decal, the join where two wall panels meet — while the rest of the view stays calm, and it flickers at any distance, near or far. Depth-precision flicker, by contrast, spreads across whole distant surfaces and eases up close. A flicker that follows one decal everywhere it appears points at that object's placement; a flicker that covers every distant wall points at precision.

What should I toggle in the on/off comparison, and why change only one thing at a time?

Toggle three things, each on its own: upscaling off with the native resolution, the forced driver anti-aliasing and forced anisotropic filtering restored to their defaults, and a different quality preset. After each single change, look at the same scene and write down whether anything changed. Changing only one thing at a time is what makes the result mean something: if two things change at once and the picture improves, nobody knows which change mattered, and the same trap will be waiting at the next game.

Can forced driver anti-aliasing make flickering worse?

Yes, it can. Forced driver anti-aliasing changes the game's original render path, and on surfaces that were already close to the edge of what the depth buffer could separate, that change can make the flicker more visible. It does not create the contest for depth — the contest exists in the scene whether the setting is on or off — but it can aggravate it. That is why the on-off comparison restores the forced settings to their defaults and tests the same scene before and after, rather than assuming the setting is either the cure or the cause.

What can I do about a problem in the game's own geometry?

At the player's level, there is no direct fix: coplanar surfaces and distant precision limits live inside the game's own code, and they are not settings a player can reach from a menu. The useful actions are to accept the current picture, wait for a game update, or report the problem to the game's developer with the record from the steps in this guide — the game and its version, the scene, the surface, and the settings used. This guide never asks the reader to edit game files, engine settings, or the registry to chase such a problem.

When should I bring my records in for inspection?

Bring them in when the seven steps have been worked through one variable at a time and the answer is still unclear, or when the suspicion has turned to hardware: a fixed pattern in the screenshot, flicker that does not follow the camera, or flicker that arrives with crashes or black screens. Bring the game name, the scene, the surface, the screenshots or video, and the on-off comparison results. Inspection takes place at Room 1209, Dali Plaza, Shek Mun; call 2186 8010 or WhatsApp 6558 6806. Inspection is charged at the site's published three-tier fees of HK$400–2,800, quoted after inspection.

Related articles

Related services

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