Game Stuck on the Loading Screen After You Press Start? Shader Compilation, Asset Loading & Server Handshake Diagnosis Guide

Key Takeaway
A game stuck on its loading screen is not necessarily frozen: the bar may be still while the processor compiles shaders or the drive reads game files. The text at the bottom says which stage is stuck, and Task Manager shows whether anything is working. This guide works through five layers and seven steps to find the stage that stopped.
What This Problem Is — and What It Is Not
You press Start, or Play. The game opens. It reaches a loading screen — or a screen that says it is compiling shaders or preparing — and then nothing changes. The progress bar sits at one percentage and does not move. The picture does not change. However long you watch, the main menu or the game world never arrives.
That scene is the whole problem this guide covers, and its shape is the most important piece of evidence in the diagnosis. The game opened, the loading screen appeared, and progress stopped. It is not a game that does nothing at all when you press Play — no window, no picture, no error message. That is a different problem, covered by the guide on a game that shows no response at all. It is not a game that stutters for a moment when you enter a new area and then runs smoothly afterwards. That is a different problem too, covered by the guide on shader compilation stutter. It is not a game that opens, plays for a while, and then closes itself. And it is not a progress bar that is moving, only slowly. A moving bar, however slow, is a game that is still working. This guide is about a bar that has stopped, and a game that cannot be entered.
Four conditions must all be true before the steps below apply:
- The game opens and reaches a loading screen, or a shader compilation or preparation screen, after Start or Play is pressed, and the progress bar then stops at one percentage, or the screen stays unchanged.
- The machine boots into Windows and shows a desktop normally. If there is no display at all, the problem is a display problem, not a loading problem, and a different guide applies.
- The game has not reached the main menu or the game world. If the game loads, plays, and then closes itself, that is a crash during play, and the steps below do not apply to it.
- The progress bar is stopped, not merely slow. If the percentage is still changing, or the screen is still changing, the game is still working through its loading chain, and the correct action is to let it finish, dealt with in Step 3.
The distinction this guide turns on is between a game that is working and a game that has stopped, and the screen in front of you cannot tell you which one it is. A loading screen is designed to look the same in both cases: a still picture, a still bar. The evidence that separates the two lives elsewhere — in the small line of text at the bottom of the screen, and in Task Manager. The five suspicion layers below are the five stages the loading chain can stall at, and the seven steps are the order in which to test them.
The Small Text at the Bottom of the Screen Is the Map
Before changing anything, read the loading screen itself. Most games print a small line of text at the bottom of the loading screen, and that line changes as the game moves through its loading chain: "compiling shaders", "preparing", "loading files", "contacting server", "synchronising save data". That line is a map of where the game is, and when the game stalls, the line that is showing is the stage it stalled at.
This is the single most useful habit in this diagnosis, and it costs nothing. Write down the exact words the line shows, and the percentage the progress bar shows, before doing anything else. Note also when the problem first appeared: the first time the game was ever started, after a game update, after a driver update, or after the game had been working normally for weeks and then suddenly changed. A stall that appears on the very first launch points at a different layer from a stall that appears only after an update, and a stall that appears only when loading one particular save file points at a different layer again.
Three wordings that sound alike must never be confused. "Compiling shaders" means the game is in the shader compilation stage, and the processor is doing the work. "Loading files" or "reading data" means the game is in the asset reading stage, and the drive is doing the work. "Contacting server", "logging in", or "synchronising" means the game is in the server handshake stage, and the network is doing the work. If the screen shows no text at all, that is also evidence, of a different kind: the game has not told you which stage it is in, and guessing which stage it is in is the worst possible next step. In that case the diagnosis must proceed by the Task Manager test in Step 2, which can still separate a working game from a stopped one without the text.
The reason the stage matters is that every fix in this guide belongs to one stage only, and a fix applied to the wrong stage is wasted time at best. Verifying game files belongs to the asset reading stage. Checking the server status belongs to the handshake stage. Waiting belongs to the shader compilation stage. A diagnosis that starts by guessing a fix, without first reading which stage is stuck, is a diagnosis that will try the wrong fix first and may never find the right one.
The Five Suspicion Layers
A loading stall can come from five layers, and they must be kept separate. Mixing them together is how a server handshake problem gets treated with a driver reinstall, or a shader compilation problem gets treated by verifying game files, 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 Progress Layer — Which Stage Is Stuck
The first layer is the loading chain itself. Loading is not one screen; it is a chain of stages: shader compilation, then asset reading, then, for an online game, the server handshake, then entry into the world. The game moves through these stages in order, and a stall at any one of them produces the same outward picture — a still progress bar — while meaning something different at each stage.
The deciding evidence for this layer is the small line of text at the bottom of the loading screen, recorded before anything is changed, together with the percentage the bar shows and whether that percentage has changed since you last looked. If the text says the game is compiling shaders, the stall is at the compilation stage. If it says the game is contacting the server, the stall is at the handshake stage. If the percentage has moved since you last looked, even by one point, the game is not stuck at all — it is still working through a slow stage, and the correct action is to let it finish. The most common error at this layer is also the simplest: treating every still bar as the same problem, and reaching for a fix before reading which stage the bar belongs to.
Layer Two: The Compilation Layer — Shader Compilation Is Processor Work
The second layer is shader compilation, and it is the layer most often mistaken for a frozen game. Modern games, especially those built on DirectX 12 or Vulkan, must compile their shaders into machine code the graphics card can run. That compilation happens when the game is first started, after a large game update, and after a driver change, because each of those events can invalidate the compiled shaders the game had stored. The compilation is processor work. While the processor compiles, the graphics card waits. The progress bar moves slowly, the picture does not change, and the machine can look idle from the front — but the processor is working hard, and the game is not frozen.
The deciding evidence for this layer is processor activity in Task Manager while the game is on the loading screen. High processor usage by the game process, sustained over time, means compilation is in progress, and the correct action is to let it finish. Compilation time varies with the game, the processor, and the driver version, and there is no universal figure for how long it should take. Any source that quotes a time for one game on one machine is quoting that game on that machine, and it cannot be used as a standard for any other game or any other machine. The only reliable test is whether the work is still happening: the percentage moving, or the processor and the drive showing activity.
Two facts about compiled shaders matter here. First, once a shader has been compiled, the game stores the result in a shader cache, so the next time the same shader is needed the game can load it from the cache instead of compiling it again. That is why the first launch after an update can be slow while later launches are quick. Second, the shader cache has three layers, and they should not be confused with each other — the game, the driver, and the operating system each keep their own cache, and clearing one does not clear the others. Clearing a cache is dealt with in Step 6, and it is never the first step, because clearing a cache forces the game to compile everything again from the beginning, and the next launch will be slower, not faster.
Layer Three: The Reading Layer — Asset Streaming and File Integrity
The third layer is asset reading. Loading requires the game to read a large volume of assets from the drive: textures, models, level data. Damaged or missing files, a drive that is nearly full, or a game installed on a slow drive can all bring that reading to a halt. The evidence for this layer is drive activity, not a feeling about how long the loading has taken.
The deciding evidence is sustained drive activity in Task Manager while the game is on the loading screen, together with the result of verifying the game files. If the drive is reading steadily and the percentage is creeping upward, the game is reading assets and should be left to finish. If the drive shows no activity at all while the bar is still, the reading has stopped, and the next question is why: a damaged file, a missing file, or a drive that cannot supply the data. Verifying the game files — Steam's "Verify integrity of game files", or the repair function in the game's own launcher — checks for damaged or missing files, and it is the right test for this layer. But it is only the right test for this layer. Run on a game that is stuck at the handshake stage, it wastes time and proves nothing. Run on a game that is stuck at the compilation stage, it will not make compilation any faster.
One more detail at this layer: the drive the game is installed on matters. A game installed on a nearly full drive can stall because the drive has no room to work with, and a game installed on a slow drive will read its assets more slowly than the same game on a faster one. Neither of those is a graphics card problem, and neither is fixed by changing a graphics setting.
Layer Four: The Handshake Layer — Online Games Must Talk to the Server First
The fourth layer applies only to online games, and it is the layer most often missed by a diagnosis that treats every loading stall as a local problem. An online game, during loading, must complete a handshake with the server: logging in, checking the account status, synchronising save data. If the server is under maintenance, if the network connection has dropped, or if the login has failed, the loading will stop at the handshake stage — and no amount of local work will move it.
The deciding evidence for this layer is the server status and the login result. Check the game's official status page or community announcements for maintenance or an outage, check whether the network connection itself is working, and look for a login error code. If the server is down or the login has failed, nothing on the local machine needs to be done, and nothing on the local machine can help. Wait for the server to return, and try again. Verifying local files, clearing caches, and reinstalling the driver are all wasted effort while the real problem is a dead handshake, and they should not be attempted until the server side has been ruled out.
This layer is also the reason the single-player versus online split in Step 4 comes before any file work. A single-player game has no handshake stage, so a stall in a single-player game cannot be a handshake problem, and the diagnosis can move straight to the file layer. An online game has a handshake stage, and it must be checked before any local fix is attempted, because a local fix cannot repair a server that is not answering.
Layer Five: The Driver and System Layer — Driver Version, Overlay Software, Damaged Saves
The fifth layer is the driver and the system around the game, and it is deliberately checked last, not first. A driver version that does not suit the game, overlay software that fails to inject itself into the game, or a damaged local save file can each bring loading to a halt. But each of these is a narrow cause, and treating them first — reinstalling the driver before knowing which stage is stuck, or deleting a save file before knowing whether the save is the problem — destroys evidence and wastes effort.
The deciding evidence for this layer depends on which part of it is suspected. A driver problem is suspected when the stall began immediately after a driver update, and the test is the driver version itself, compared against the version the manufacturer currently lists for the exact card model. An overlay problem is suspected when the stall began after overlay software was installed or updated, and the test is to disable the overlay and try again, changing one thing at a time. A damaged save is suspected when only one particular save file stalls on loading while a new game, or a different save, loads normally — and that is the only situation in which the save file itself is the suspect. A save file must never be deleted outright. Back it up first, and then follow the game's own official guidance for dealing with a damaged save.
| Layer | What can be wrong | Deciding evidence | What resolves it |
|---|---|---|---|
| 1. Progress | The stage that is stuck has not been identified | The small text at the bottom of the loading screen; whether the percentage has moved | Reading the stage before acting |
| 2. Compilation | Shader compilation is in progress; the processor is working and the graphics card is waiting | Sustained processor usage by the game in Task Manager; the percentage moving | Letting the compilation finish |
| 3. Reading | Damaged or missing files, a full drive, or a slow drive | Sustained drive activity; the result of verifying the game files | Verifying and repairing the game files; freeing drive space |
| 4. Handshake | The server is down, the network has dropped, or the login has failed | The official server status page; a login error code | Waiting for the server; fixing the login, not the local machine |
| 5. Driver and system | An unsuitable driver version, overlay software, or a damaged save file | The stall starting after a driver or overlay change; only one save file stalling | The current manufacturer driver; disabling the overlay; backing up the save before following official guidance |
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 game load leaves the reader not knowing which change mattered — and not knowing what to do when the stall returns.
Step 1: Write Down Which Screen It Is Stuck On
Write down the percentage the progress bar shows, the exact words of the small text at the bottom of the screen, and whether the screen shows any text at all. Note whether this is the first launch, the first launch after an update, or a game that used to work and has suddenly changed. Note how many times it has happened, and whether it always stops at the same percentage.
This step proves that the problem has been narrowed to a loading stall at a named stage, and it records the only direct evidence of which stage that is. It proves nothing about whether the game is still working — that is what Step 2 is for. But without the wording, nothing else can be checked against it: the text names the stage, and the rest of the diagnosis tests that stage. A note that says "Stuck on 'compiling shaders', first launch after the update, third time" is a diagnosis in progress. A note that says "it got stuck" is a starting point with no direction.
Step 2: Look at Task Manager — Is It Working or Has It Stopped?
Open Task Manager and look at the game process: its processor usage, its drive usage, and its graphics card usage. This is the most important step in the whole guide, and it must not be skipped, because it is the step that separates a game that is working from a game that has stopped, and everything after it depends on the answer.
If the processor is running high, or the drive is reading steadily, the game is working — compiling shaders or reading assets — and it is not frozen, however still the screen looks. If the processor, the drive, and the graphics card are all close to zero, and the process shows "Not responding", the game has genuinely stopped. That distinction is the fork the rest of the diagnosis follows. Do not judge by the clock. Judge by movement: the percentage changing, or the processor and the drive showing activity. A game that is still working should be left alone. A game that has stopped is the one that needs the steps below.
Step 3: Give a Working Game a Fair Window
If the percentage is moving, or the processor and the drive show activity, let the game finish. Do not close the game partway through, and do not switch away from it with Alt-Tab while it is compiling, because interrupting a compilation can leave the shader cache in an incomplete state and force the work to be done again. If nothing is moving — the percentage, the processor, and the drive have all been still for a sustained period — move on to the next step.
No fixed waiting time can be given here, because the time a compilation or a load takes varies so widely between games and machines that any single figure would be wrong for most readers. The judgement is movement, not minutes. A game whose percentage is still changing is a game that is still working, however long it has taken. A game whose percentage, processor, and drive have all been still is a game that has stopped, and waiting longer will not change that.
Step 4: Split Single-Player from Online
If the game is a single-player game, there is no handshake stage, so skip the handshake layer and go to Step 5. If the game is an online game, check the server side first: the game's official status page or community announcements for maintenance or an outage, the network connection, and whether the login has produced an error code. If the server is under maintenance or the login has failed, nothing on the local machine needs to be done. Wait for the server to return, and try again.
This split must come before any file work, because file work cannot fix a handshake problem. Verifying the game files while the server is down is wasted time, and it can also mislead: a verification that finds nothing wrong may be read as proof that the local machine is fine, when the real problem was never on the local machine at all.
Step 5: Verify the Game Files
Use Steam's "Verify integrity of game files", or the repair function in the game's own launcher, to check for damaged or missing files. Before verifying, write down the percentage and any error code the game showed. After verifying, try the game again and note whether it stops at the same percentage or gets past it. A stall that moves to a later percentage after verification is evidence that the file layer was part of the problem. A stall at exactly the same percentage, after a clean verification, is evidence that the file layer is not the problem, and the search moves on.
Verification only tests the file layer. It will not make shader compilation faster, and it will not repair a handshake. Its result is only meaningful when it is read against the stage the game was stuck at, which is why Step 1 came first.
Step 6: Compare the Shader Cache — Only When It Is Indicated
Consider clearing the shader cache only in two situations: the game's or the driver's official guidance recommends it, or the game still stalls at the compilation stage after the files have been verified. Do not clear the cache as a first step. Clearing it forces the game to compile everything again from the beginning, so the next launch will be slower, not faster, and a cache that was not damaged has been destroyed for nothing.
Steam's shader pre-caching applies to Vulkan and OpenGL games, not to DirectX 12 games, so it must not be presented as a general fix for a DirectX 12 compilation stall. After clearing a cache, expect the next launch to compile again — that is the cache being rebuilt, not a new problem — and judge the result by whether the game gets past the stage it stalled at, not by whether the next launch is fast.
Step 7: Decide — and Record What Happened
The decision follows from the steps, and there are only three directions.
If the game loads after one more try, write down which stage it had stalled at. The same stage may stall again after the next update, and knowing which one it was will make the next diagnosis faster.
If the same stage stalls every time, bring the machine in with the complete record: which screen it stalls on, the percentage, the processor and drive readings from Task Manager, whether the game is single-player or online, and the result of verifying the files. 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.
If only one particular save file stalls on loading, back up the save file first, and then follow the game's own official guidance for dealing with a damaged save. Do not delete the save file directly. A deleted save cannot be recovered, and a save that was not the problem has been destroyed for nothing.
| Step | What to do | What it proves | What it does not prove |
|---|---|---|---|
| 1. Write down the stuck screen | The percentage, the small text, first launch or after an update, how many times | Which stage the game stalled at | Whether the game is still working |
| 2. Check Task Manager | Processor, drive, and graphics card usage of the game process | Whether the game is working or has stopped | Which stage is at fault, on its own |
| 3. Give a working game a fair window | Let a moving game finish; do not interrupt a compilation | Whether the stall clears on its own | Anything, if nothing is moving |
| 4. Split single-player from online | Server status page, network, login error code for online games | Whether the problem is the handshake | Anything about the local files |
| 5. Verify the game files | Steam verification or the launcher's repair function; note the percentage before and after | Whether damaged or missing files were the cause | Anything about compilation or the handshake |
| 6. Compare the shader cache | Clear the cache only on official guidance or a verified stall at compilation | Whether a damaged cache was the cause | Anything, if the cache was not the problem |
| 7. Decide | Retry and record the stage, or bring the record in, or back up a suspect save | Which direction follows from the evidence | Anything beyond the test that was actually run |
Six Common Misconceptions
Misconception 1: A stopped progress bar means the game has crashed
No. A progress bar that is not moving is not the same as a game that has stopped. While the processor compiles shaders or the drive reads game files, the bar may sit still and the picture may not change. A crash is defined by the process not responding and all resources sitting still — processor, drive, and graphics card close to zero — not by the picture being still. The screen cannot tell you which one it is. Task Manager can.
Misconception 2: A long wait means the hardware is broken
No. A first compilation, or a cache rebuild after a driver update, can take a long time, and how long it takes varies with the game and the machine. There is no universal standard for how long is too long. The judgement must be made from resource activity, not from the clock. A game whose processor is still working is a game that is still working, however long it has taken. A game whose resources have all been still is a game that has stopped, and the length of the wait is not the evidence — the stillness is.
Misconception 3: Verifying the game files is the universal first step
No. Verification only tests the file layer. When the game is stuck at the server handshake, verifying files wastes time, because the files were never the problem. When the game is stuck at shader compilation, verifying files will not make the compilation any faster. Verification belongs after the stage has been identified and the handshake has been ruled out, not before. A fix applied to the wrong layer is not a diagnosis; it is a guess with a progress bar of its own.
Misconception 4: Clearing the shader cache will always make it faster
No. Clearing the cache forces the game to compile everything again from the beginning, so the next launch will be slower, not faster. A cache should only be cleared when the game's or the driver's official guidance recommends it, or when the game still stalls at the compilation stage after the files have been verified. Clearing it as a first step destroys a cache that may have been perfectly good, and the slowness that follows is the rebuild, not a new problem.
Misconception 5: A slow load means the graphics card is not powerful enough
No. The bottleneck during loading is usually the processor compiling shaders, the drive reading assets, or the network completing a handshake — not the graphics card's rendering power. During loading, the graphics card is mostly waiting: it has nothing to render until the shaders are compiled and the assets are read. Judging the graphics card by how fast a game loads is judging it by work it is not doing. The card's rendering power is tested during play, not during loading.
Misconception 6: Reinstalling the game or the driver will definitely fix it
No. Reinstalling will not fix a server handshake problem, because the server is not on the local machine. It will not fix a damaged save file, because the save is not part of the installation. And it will not make shader compilation faster, because compilation time depends on the game, the processor, and the driver version, not on how fresh the installation is. Before reinstalling anything, identify which stage is stuck. A reinstall is a step, not a cure, and it is the wrong step for most of the stages in this guide.
Boundaries: Problems That Look Similar but Are Not This One
Not every game that fails to start is a loading stall, and the similar problems each belong to their own guide. If the symptom is one of the following, follow that guide, not this one.
Pressing Play and getting no window, no picture, and no error message at all is a game that shows no response, and it belongs to the guide on the launch chain. A game that stutters for a moment when entering a new area and then runs smoothly is a shader compilation stutter during play, not a loading stall. A game that opens, plays, and then closes itself is a crash during play. A progress bar that stops while rendering or exporting video is an encoder stall in creative work, not a game loading stall. A loading screen that produces a device-removed error is a device-removal problem, with its own error codes. And a screen that goes black as soon as Windows starts is a system-level black screen, not a game loading screen at all.
Finally, there are things this guide will never teach, and a source that teaches them should be closed. Never delete files inside the game folder that you do not recognise. Never edit the registry. Never download a single DLL file from the internet. Never install an unofficial "repair tool". None of these is a diagnosis, and each one trades a working machine for a less safe one.
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 stage stalls every time — or when the question becomes which part to change, rather than which stage is at fault. Stop sooner if the game stalls only when loading one particular save file and the save cannot be recovered by the game's own official guidance, or if any step involves editing the registry or downloading files from an unknown source.
Bring the machine in with the notes from every step: which screen it stalls on, the percentage, the processor and drive readings from Task Manager, whether the game is single-player or online, and the result of verifying the files. 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 "Stuck on 'compiling shaders', processor at high usage, drive reading, single-player game, files verified clean, stalls at the same stage every time" 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
Q1: The progress bar has stopped moving. Does that mean the game has crashed?
Not necessarily. A progress bar that is not moving is not the same as a game that has stopped. While the processor compiles shaders or the drive reads game files, the bar may sit still and the picture may not change. A crash is defined by the process not responding and all resources sitting still — processor, drive, and graphics card close to zero. Open Task Manager and look at the game process: if the processor is running high or the drive is reading steadily, the game is still working and should be left to finish.
Q2: It has been stuck for a long time. Does that mean the hardware is broken?
No. A first compilation, or a cache rebuild after a driver update, can take a long time, and how long it takes varies with the game and the machine. There is no universal standard for how long is too long, so the length of the wait is not evidence on its own. Judge by movement instead: if the percentage is still changing, or the processor and the drive show activity, the game is still working. Only when everything has been still is the game genuinely stopped.
Q3: Should verifying the game files be the first thing I do?
No. Verification only tests the file layer. If the game is stuck at the server handshake, verifying files wastes time, because the files were never the problem. If the game is stuck at shader compilation, verifying files will not make the compilation any faster. First read the small text at the bottom of the loading screen to find which stage is stuck, then split single-player from online, and only then verify the files — and note the percentage before and after, so the result means something.
Q4: Will clearing the shader cache make loading faster?
No — clearing the cache usually makes the next launch slower, because it forces the game to compile everything again from the beginning. A cache should only be cleared when the game's or the driver's official guidance recommends it, or when the game still stalls at the compilation stage after the files have been verified. After clearing, expect the next launch to compile again; that is the cache being rebuilt, not a new problem. Steam's shader pre-caching applies to Vulkan and OpenGL games, not to DirectX 12 games.
Q5: Does a stuck loading screen mean my graphics card is not powerful enough?
No. The bottleneck during loading is usually the processor compiling shaders, the drive reading assets, or the network completing a handshake — not the graphics card's rendering power. During loading, the graphics card is mostly waiting: it has nothing to render until the shaders are compiled and the assets are read. The card's rendering power is tested during play, not during loading, so a slow load says nothing about whether the card is strong enough.
Q6: Will reinstalling the game or the driver definitely fix it?
No. Reinstalling will not fix a server handshake problem, because the server is not on the local machine. It will not fix a damaged save file, because the save is not part of the installation. And it will not make shader compilation faster, because compilation time depends on the game, the processor, and the driver version, not on how fresh the installation is. Identify which stage is stuck first; a reinstall is a step, not a cure, and it is the wrong step for most of the stages in this guide.
Q7: How do I tell whether the game is still working or has actually stopped?
Open Task Manager and look at the game process: its processor usage, its drive usage, and its graphics card usage. If the processor is running high or the drive is reading steadily, the game is working — compiling shaders or reading assets — and it is not frozen, however still the screen looks. If the processor, the drive, and the graphics card are all close to zero, and the process shows "Not responding", the game has genuinely stopped. That is the decisive test in this guide, and it must be done before any fix is attempted.
Q8: How can I tell which stage is stuck from the small text at the bottom of the screen?
Read the small line of text at the bottom of the loading screen — it is the map. "Compiling shaders" means the compilation layer, "loading files" means the reading layer, and "contacting server" or "synchronising save data" means the handshake layer. Write down exactly what it says, then check it against the stage map: the wording tells you which layer to check next. If there is no text at all, use the Task Manager test first, and look at whether the processor, the drive, or the graphics card is showing activity.
Q9: What is different about a stall in a single-player game versus an online game — and what if only one save file gets stuck?
A single-player game has no handshake stage, so skip the handshake layer and go straight to verifying the game files and comparing the shader cache. An online game may be stuck at the handshake: check the game's official status page or community announcements for maintenance or an outage, check the network connection, and look for a login error code first. If the server is down or the login has failed, nothing on the local machine needs to be done. Separately, if only one particular save file stalls on loading while a new game or a different save loads normally, that pattern points at the save file itself, not at the game or the hardware. Back up the save file first, before doing anything else, and then follow the game's own official guidance for dealing with a damaged save. Do not delete the save file directly: a deleted save cannot be recovered, and a save that was not the problem has been destroyed for nothing.
Q10: When should I stop trying things myself and bring the machine in for inspection?
Stop when all seven steps have been worked through and the same stage stalls every time, or when the question becomes which part to change rather than which stage is at fault. Stop sooner if the stall involves only one save file that cannot be recovered by the game's own official guidance. Bring your notes: which screen it stalls on, the percentage, the processor and drive readings from Task Manager, whether the game is single-player or online, and the result of verifying the files. In-store inspection is at Room 1209, Dali Plaza, Shek Mun, charged at the site's published three-tier fees of HK$400–2,800, quoted after inspection. You can call 2186 8010 or WhatsApp 6558 6806.