Game Won't Launch When You Click It? Launcher, Anti-Cheat Driver, Runtime Libraries & GPU Selection Diagnosis Guide

Key Takeaways
You click Play and nothing happens — no window, no error, no game. This guide separates the three ways a launch can fail, walks the chain from launcher to anti-cheat driver, runtime libraries and graphics driver, and shows which check belongs to which layer, so you stop reinstalling a game that was never the problem.
What "Won't Launch" Actually Means
Clicking Play and getting nothing back is not one symptom. It is at least three different symptoms that happen to look the same from the desktop, and each one points at a different layer of the launch chain. The first thing to do is not to reinstall the game. The first thing to do is to open Task Manager, switch to the Details tab, and watch what the game process does in the seconds after you click Play. That observation is the whole diagnosis in miniature, and it costs nothing.
There are three patterns to look for:
- The game process appears for a few seconds, then disappears. The game did start, and then it stopped almost immediately. This points towards an overlay, an anti-cheat layer, an antivirus action, a missing runtime library, or a driver problem. The launch got far enough to begin, and something cut it short.
- The process appears and stays there, but no window ever opens. The game is running in the background, but nothing is drawn on screen. This points towards the window opening off-screen, or towards the renderer getting stuck at the graphics driver stage.
- No process appears at all. The launcher never handed over to the game. This points towards a damaged installation, a permissions problem, or the launcher's own download state being stuck.
On Steam, the typical presentation of the first pattern is that the button changes from Play to Stop for a few seconds, then flips back to Play, with no window and no error message. That is not a random glitch. It is the launcher reporting that the process started and then ended. Recording which of the three patterns you see, before changing anything, is what makes every later step meaningful — because each later step is a comparison against that starting observation.
A further distinction matters before any diagnosis begins. This article is about a game that will not start at all. A game that starts, runs, and then crashes back to the desktop in the middle of play is a different subject, covered in separate articles on this site. A game that opens and then shows a specific error window, such as a Direct3D initialisation error, is also a different subject. The checks below are written for the silent case: you click, and nothing happens.
The Launch Chain: Five Links, and Any One Can Break
A normal launch passes through five links in order: the launcher (Steam, Epic Games, Riot Client, or another), the anti-cheat service or driver (where the game has one), the game program itself, the runtime libraries (Visual C++, DirectX, .NET), and the graphics driver initialisation. When the launch fails, one of those links has broken — and which link broke is what the symptom pattern tells you.
| Link in the chain | Where it breaks | What you see |
|---|---|---|
| Launcher | The launcher itself is stuck | No game process appears at all, or the launcher sits on "Preparing to launch" |
| Anti-cheat driver or service | The anti-cheat driver fails to load, so the game refuses to start | The process flashes up and vanishes, or an anti-cheat error code appears, before any rendering begins |
| Runtime libraries | A required library is missing or damaged | A missing DLL message appears, or an error such as 0xc000007b or 0xc0000142 |
| Graphics driver / GPU selection | The driver fails to initialise, or the game is sent to the wrong GPU | The process stays in the background with no window, or it crashes immediately |
| Game files | The installation is damaged or half-updated | The process appears briefly and vanishes, or the launcher reports a problem |
The table is a map, not a verdict. A single symptom can have more than one cause, and the point of the diagnosis is to narrow the map down one link at a time, changing one thing at a time, so that when the game finally launches you know which change did it. Changing five things at once and then launching successfully tells you nothing, and the next time the problem returns you will be back at the beginning.
The Anti-Cheat Driver Layer
This is the layer most people skip, and it is the layer this article spends the most time on — because a game that refuses to start is often not broken at all. It is refusing to start on purpose, because the anti-cheat driver that is supposed to load before it could not load, and the game will not run without it.
It is important to be precise about what this layer is and is not. There is a separate article on this site about a game that is already running while a recording program shows a black capture. That article is about an anti-cheat system blocking a hook injection at the capture layer, after the game has started. This article is about something different: the anti-cheat driver itself failing to load, so the game refuses to start in the first place. The mechanism is different, the symptom is different, and the two must not be mixed up. Nothing in this article is about capture, recording, or hooks into a running game.
Five Systems, Five Different Load Times
The five widely used anti-cheat systems do not load at the same moment, and that timing is itself a diagnostic clue.
| System | Examples listed by the source | Level | When it loads |
|---|---|---|---|
| Riot Vanguard | Valorant, League of Legends | Kernel level | At Windows start-up, not when the game starts; the game will not run unless it loaded at boot |
| Easy Anti-Cheat (EAC) | Fortnite, Rust, and others | Kernel level | When the game starts; unloaded when the game closes |
| BattlEye | Rainbow Six Siege, Escape from Tarkov, PUBG, Destiny 2, ARK, and others | Kernel level | When the game starts; unloaded when the game closes |
| Ricochet | Call of Duty (Black Ops 6, Warzone) | Kernel level | When the game starts |
| VAC | Valve games | Mainly not kernel level | Loaded with the game |
The list of games is taken from the source comparison as it stood on the research date, and it is not a fixed register. Which anti-cheat system a game uses can change with a game version, so no game should be treated as permanently tied to one system. The timing column is the part that matters for diagnosis: Vanguard is the odd one out, because it loads at boot. If Vanguard did not load when Windows started, the game cannot start later, and no amount of clicking Play will change that.
Vanguard: Secure Boot and TPM 2.0 on Windows 11
On Windows 11, Vanguard requires Secure Boot and TPM 2.0 to be enabled at the same time, or the game will not start. Multiple sources agree on this, and the check is straightforward:
- Open `msinfo32` (System Information). The BIOS mode must be UEFI, and the Secure Boot state must be On.
- Open `tpm.msc`. It must show that the TPM is ready for use, with specification version 2.0. TPM 1.2 does not meet the requirement.
- Secure Boot is only available in UEFI mode. If the machine is running in Legacy mode with an MBR disk, forcing Secure Boot on can leave Windows unable to boot. Before converting to UEFI, confirm that the disk is GPT.
- If the hardware itself has no TPM 2.0, no BIOS setting can create one.
There is a restart detail that catches new installations. Vanguard is usually installed together with the game, and its kernel driver loads when Windows starts — so after the first installation, a restart is normally needed before the game can launch. Skipping that restart is a common reason a newly installed game will not open at all.
The error codes need care, because sources disagree about one of them. The codes below follow Riot's own support pages, and where sources disagree, the disagreement is stated rather than hidden:
- VAN 9001: Vanguard cannot detect that TPM 2.0 is enabled.
- VAN 9003: Secure Boot is not enabled.
- VAN 1067: sources disagree. One source groups it with TPM and Secure Boot. Another source points out that Riot's own VAN 1067 page does not describe it that way — Riot describes it as a Vanguard start-up or connection failure, not a TPM or Secure Boot problem, and the handling direction is the Vanguard service, Windows updates, and clearing the game cache. Do not treat VAN 1067 as a TPM problem. Check Riot's current page for what it says at the time you see the code.
There is also a report that a newer on-demand mode of Vanguard carries further requirements — Windows 11 25H2 or newer, plus Secure Boot, TPM 2.0, IOMMU, and Memory Integrity. That is a single-source report, and it is stated here as a report, not as a settled fact.
Easy Anti-Cheat: Driver Load Errors
Easy Anti-Cheat failures usually show up as a driver load error, with some sources mentioning error 1275, which means a driver failed to load. Two points from the sources are worth knowing:
- EAC cannot run while kernel debugging is enabled. Kernel debugging has to be disabled before the game can start.
- There are reports that EAC conflicts with Windows kernel-mode hardware-enforced stack protection, HVCI, or Memory Integrity. That is a report, not a settled conclusion, and it must not be taken to mean "turn off Memory Integrity and it will work". It belongs on a list of things to compare one at a time, not as a guaranteed fix.
- EAC ships with a repair tool bundled with each game, and that tool can repair most launch errors. When the EAC layer is the suspect, the official repair tool is the step to try before reinstalling the game.
BattlEye: "Blocked Loading of File" Is Not a Ban
BattlEye sometimes shows a message saying it blocked the loading of a file. The message means BattlEye stopped a kernel driver with a known security vulnerability from loading, because cheating software can exploit that kind of driver. The message lists the file path, which usually belongs to monitoring, RGB lighting, overclocking, or overlay software that ships an old version of such a driver.
Three things about this message need to be said plainly. First, it is not a ban, and it will not cause a ban. Second, if the blocked file is one the game needs, or the blocking keeps happening, it can still stop the game from loading. Third, the handling direction is to read the file path in the message, work out which software it belongs to, and update that software to a version with a signed, patched driver. If there is no update, close or remove that software while playing, and report the issue to that software's maker.
Ricochet
Ricochet requires Secure Boot and TPM 2.0. There are also reports that it conflicts with Memory Integrity or core isolation and can cause blue screens. As with the EAC reports above, that is a report, not a settled conclusion, and it belongs on a comparison list rather than being stated as a fact.
Common Failure Modes Across All Anti-Cheat Systems
The source comparison groups the common failures into five:
- Secure Boot or TPM 2.0 is not enabled — the most common cause for Vanguard and Ricochet.
- The anti-cheat Windows service is not running — stopped in services.msc, disabled by a cleaning tool, or blocked by third-party security software.
- The anti-cheat installation itself is damaged — interrupted during an update, or incomplete. Most vendors, or the game itself, ship a standalone repair or reinstall tool for this.
- The graphics or chipset driver is too old or mismatched, particularly after a Windows feature update changed driver signing or loading behaviour.
- Windows updates are missing — anti-cheat vendors often require a newer Windows build to keep driver signing and compatibility current.
Three Bottom Lines
These three principles are carried over from the companion article on capture, and they are restated here because they apply just as strongly at the launch layer:
- Never disable, bypass, or deceive an anti-cheat system. Searching online for a way to bypass anti-cheat is the most dangerous reaction to a game that will not launch, and it can lead to an account ban.
- Do not trust any blacklist claiming a particular game always blocks something. Anti-cheat behaviour changes with game versions, and each game's situation can only be judged one game at a time.
- Do not treat any game as definitely launching or definitely not launching. Conclusions stay at the layer level. Individual games are not named as accusations.
The Other Branches
The anti-cheat layer is the main branch of this article, but it is not the only one. Each branch below carries its own evidence, and each is checked in the same way: change one thing, watch the process pattern, and record the result.
Verify the Game Files First — Cheapest Step, Do It First
Multiple sources agree that verifying game file integrity is the first step. On Steam: Library, right-click the game, Properties, Installed Files, Verify integrity of game files. It only re-downloads files that differ, so there is no need to reinstall the whole game. This step repairs the most common cause in its class — damaged or half-updated files — and until it has been done, there is no basis for talking about other layers. Verify the game files first, and only consider reinstalling if that does not work — do not reverse this order. Reinstalling the game does not repair an anti-cheat service, a runtime library, or a driver layer, so it is not a substitute for this step.
The Launcher Itself Is Stuck
Sometimes the launcher is the broken link, not the game:
- Clear the Steam download cache (Steam, Settings, Downloads, Clear Cache). A stuck download state inside Steam itself can block a game from launching.
- Run Steam once as administrator. Permission failures usually come from an update that could not write a file.
- Exit Steam completely and reopen it (Steam, Exit), rather than just closing the window, because the background process may still be running.
Overlays Injecting at Launch
Overlays — Discord, Steam, GeForce Experience, Xbox Game Bar, MSI Afterburner, and others — inject code into the game process as it starts. An out-of-date overlay hook is one of the two most commonly cited causes of silent launch failure in the source guide. The comparison method is to turn them off one at a time, not all at once, because turning them all off together leaves no way to know which one was responsible. This is the same overlay layer discussed in the companion capture article, but the context here is different: there, the game is running and the capture is black; here, the game itself will not start.
Antivirus and Security Software
Antivirus software sometimes quarantines a component of a legitimate game after an update changes the executable. The check is to open Windows Security, Virus and threat protection, Protection history, and look for any game file that has been quarantined. Permanently turning off antivirus, or adding the game to an exclusion list, must not be treated as a universal fix. It is a check and a trade-off for the reader to decide, not a repair without cost.
Missing Runtime Libraries — the Error Message Is the Answer
When a runtime library is missing, the error message usually names the missing file, and the file name names the library. The table below is the mapping from the sources:
| Missing file | What it means | Fix |
|---|---|---|
| VCRUNTIME140.dll, MSVCP140.dll, VCRUNTIME140_1.dll | Visual C++ 2015–2022 Redistributable missing | Install the Microsoft Visual C++ 2015–2022 Redistributable, both x64 and x86 as the game architecture requires |
| MSVCR110.dll, MSVCP110.dll | Visual C++ 2012 missing | Install the Microsoft Visual C++ 2012 Redistributable |
| d3dx9_*.dll, d3dx10_*.dll, d3dx11_*.dll, xinput1_3.dll, xaudio2_7.dll | Older DirectX components missing | Install the DirectX End-User Runtime |
| 0xc000007b (application was unable to start correctly) | Usually a 32-bit / 64-bit mismatch or a damaged runtime | Repair the runtime libraries; check that the game and its libraries match in architecture |
| 0xc0000142 | Application start failure, usually a runtime or Windows file problem | Repair the runtime libraries and check Windows system files |
Two rules apply to this whole branch. First, never tell a reader to download individual DLL files from unofficial websites. Runtime libraries are repaired only with Microsoft's official installers. Second, running the game's executable directly from its installation folder can make a missing-DLL error visible that the launcher was hiding — the launcher sometimes swallows the message, and the direct run lets it appear.
Graphics Driver and Laptop GPU Selection
An old or damaged graphics driver is a common cause of launch crashes, particularly after a large game update. On a laptop, there is an extra branch: the game may be assigned to the integrated GPU instead of the discrete GPU, or the discrete GPU driver may not have loaded correctly. The comparison is to open Task Manager and check which GPU the game process is actually using, and to note the driver version before updating or cleanly reinstalling the driver, so that the change can be compared against the version that was there before.
Event Viewer: Clues When There Is No Error Message
When a game crashes silently with no error message at all, open Event Viewer (eventvwr.msc), go to Windows Logs, Application, and look for errors near the time of the launch attempt, noting the "Faulting application" and "Faulting module" names. There are documented cases where the faulting module points at EasyAntiCheat. Event Viewer must be described honestly: it does not always give the exact cause. It gives clues, and a clue that points at a driver or a system file is a different kind of result from a clue that points at the game itself.
One Game, or Every Game
- Only one game will not launch, and the others are fine. That leans towards that game's files, its anti-cheat layer, its settings, or its runtime requirements.
- Every game will not launch. That leans towards the launcher, the driver, the runtime libraries, or the system layer.
This split has to be stated clearly, but without naming any specific game as an accusation. It is a direction for the diagnosis, not a verdict on a title.
Diagnosis, Step by Step
The steps are ordered from cheapest to most disruptive, and each step is a comparison: change one thing, click Play, watch the process pattern, record the result.
Step 0: Record the Process Pattern
Open Task Manager, Details tab, click Play, and record which of the three patterns appears — process flashes and vanishes, process stays with no window, or no process at all. Also record whether the Steam button flips to Stop and back to Play, and whether any error message appears.
Step 1: Verify the Game Files
Verify integrity of the game files through the launcher. This is the cheapest repair and the most common fix in its class. Click Play again and record the pattern.
Step 2: Try a Second Game
Click Play on a second game. If only one game will not launch and the others are fine, the problem leans towards that game's files, its anti-cheat layer, its settings, or its runtime requirements. If no game launches, it leans towards the launcher, the driver, the runtime libraries, or the system layer. Record the first game's process pattern before trying the second — the two answers together are the evidence.
Step 3: Clear the Launcher Cache and Restart the Launcher
Clear the Steam download cache, exit Steam completely, and reopen it. If the launcher was the stuck link, the game should now hand over normally.
Step 4: Turn Off Overlays One at a Time
Disable one overlay, click Play, record the result. Repeat for each overlay. Do not disable them all at once, or the responsible one stays unknown.
Step 5: Check Antivirus Protection History
Look for a quarantined game file. If one is there, the game was stopped by security software, not by a fault in the game.
Step 6: Repair the Runtime Libraries
If a DLL name or an error code such as 0xc000007b or 0xc0000142 appears, repair the matching runtime library with the official Microsoft installer. Running the game executable directly from its installation folder can surface a hidden DLL error first.
Step 7: Check the Anti-Cheat Service
Open services.msc and check whether the game's anti-cheat service is running. For Vanguard, also check the Secure Boot and TPM 2.0 state in msinfo32 and tpm.msc, and confirm the machine was restarted after the first Vanguard installation. If an anti-cheat error code appears, read what the vendor's current support page says about that code — particularly for VAN 1067, where sources disagree.
Step 8: Check the GPU the Game Is Using
On a laptop, check in Task Manager which GPU the game process is using. If it is on the integrated GPU, or the discrete GPU driver has not loaded, that is the branch to follow. Note the driver version before updating or cleanly reinstalling it.
Step 9: Read Event Viewer
If there is still no error message, look in Event Viewer near the launch time for the faulting application and faulting module names. A module pointing at an anti-cheat component, a driver, or a system file narrows the layer further.
Step 10: The Check-In Boundary
If every step above has been done — files verified, cache cleared, overlays compared one at a time, antivirus checked, anti-cheat service checked, runtime libraries repaired, driver updated — and the game still will not launch, stop and bring the record to a check-in. The same applies sooner if Event Viewer points at a driver or system file, or if the launch failure comes together with a black screen, screen artefacts, a driver crash, or a blue screen, because those have already gone beyond the launch layer.
Boundary Cases
The game starts and then crashes back to the desktop during play. That is a crash-during-play subject, covered in separate articles on this site. The timing is different: the game got past the launch chain and failed later.
Only one game crashes or shows a black screen, and the others are fine. That is a single-game crash subject, covered separately. This article is about a game that produces no response at all when clicked.
The game shows a "Failed to initialise Direct3D" error. That is a specific error-window subject, covered separately. A visible error window is a different branch from silence.
The game says the driver is too old, even though the newest driver is installed. That is a driver-message subject, covered separately. This article covers the case where there is no message at all.
The screen goes black when Windows loads, or black after a driver install. Those are boot and display subjects, covered separately. They belong to the display chain, not the launch chain.
The game crashes only in the middle of play, with heat, memory, or settings involved. That is a during-play subject, not a launch subject.
Recording or capture: the game runs fine, but the recording shows a black screen. That is the companion capture article. This article does not cover hooks or capture.
Old games, DirectX versions, ray tracing, DLSS, or frame generation. Old-game compatibility, a game that crashes only on DirectX 12 while DirectX 11 works, and crashes that only happen with ray tracing, DLSS, or frame generation enabled are each separate subjects, covered in their own articles.
Common Misconceptions
- "If it will not open, the game is broken or the graphics card is broken." Wrong. The launch chain has five links, and the game itself may be completely fine.
- "Reinstall the game as soon as anything goes wrong." Wrong. Verify the game files first — it costs far less. Reinstalling will not repair an anti-cheat service, a runtime library, or a driver layer.
- "Search online for a way to bypass anti-cheat." Wrong, and dangerous. It can lead to an account ban. The correct direction is to check the anti-cheat service and driver layer.
- "VAN 1067 means TPM is not enabled." Wrong. Sources disagree about VAN 1067, and Riot's own page describes it as a Vanguard start-up or connection failure, not a TPM or Secure Boot problem. Check Riot's current page.
- "BattlEye saying 'Blocked loading of file' means I have been banned." Wrong. It is an informational block of a vulnerable driver, not a ban.
- "Turning off antivirus, or running the game as administrator, is a permanent fix." Wrong. Those are diagnostic isolation steps and trade-offs, not repairs without cost.
- "Download each missing DLL from the internet and it will be fixed." Wrong. Runtime libraries are repaired only with Microsoft's official installers. Unofficial DLL download sites must not be used.
- "Wait a few seconds and you will know whether it will open." Wrong. There is no universal number of seconds. Different games, different drives, and different anti-cheat load times vary widely. The judgement is based on how the process state changes in Task Manager, not on how many seconds have passed.
What to Note Down Before a Check-In
Bringing a clear record makes a check-in faster and more accurate. Note which of the three process patterns you saw, and whether the Steam button flipped to Stop and back to Play. Note whether only one game is affected or every game is. Note the exact error code or DLL name, if any appeared. Note the result of verifying the game files, which overlays were turned off one at a time, what the antivirus protection history showed, whether the anti-cheat service was running, and the Secure Boot and TPM 2.0 state. Note the driver version that was installed before any update, and the faulting module name from Event Viewer if one appeared.
Inspection is charged under the site's published three-tier fee of HK$400–2,800, with the actual figure confirmed after inspection. The shop is at Room 1209, Dali Plaza, Shek Mun. The phone number is 2186 8010 and WhatsApp is 6558 6806. There is no shop in Mong Kok and no on-site service.
Frequently Asked Questions
I clicked Play and nothing happened at all. Is the game broken?
Not necessarily. A launch passes through the launcher, the anti-cheat driver, the game itself, the runtime libraries, and the graphics driver. The game itself may be completely fine while another link in that chain is broken. The first step is to watch the game process in Task Manager and record which of the three patterns appears, because that pattern says which link to check first.
How do I use Task Manager to tell the three kinds of 'won't launch' apart?
Open Task Manager, switch to the Details tab, and watch what the game process does when you click Play. If it appears for a few seconds and then disappears, the problem leans towards the anti-cheat layer, overlays, or the runtime libraries. If it appears and stays there with no window, it leans towards the window position or the graphics driver initialisation. If no process appears at all, it leans towards the launcher, permissions, or the download cache.
Steam shows Stop for a few seconds, then goes back to Play. What does that mean?
It means the game process started and then ended almost immediately, with no window and no error. That is the first of the three patterns: the launch began and something cut it short. The usual layers to check are overlays, the anti-cheat layer, antivirus action, a missing runtime library, or a driver problem.
How long should I wait before deciding a game will not launch?
There is no universal number of seconds. Different games, different drives, and different anti-cheat load times vary widely, so no waiting time can be set as a standard. The judgement is based on the process state in Task Manager — whether the process appears and vanishes, stays in the background, or never appears — not on how many seconds have passed.
What is the difference between this and a game that crashes after it starts?
The timing is different. This article is about a game that never starts at all: you click, and there is no window, no error, and no game. A game that starts, runs, and then crashes back to the desktop during play has got past the launch chain and failed later, and it is covered in separate articles on this site.
What do VAN 9001 and VAN 9003 mean?
VAN 9001 means Vanguard cannot detect that TPM 2.0 is enabled, and VAN 9003 means Secure Boot is not enabled. Both meanings follow Riot's own support pages. The check is msinfo32 for the Secure Boot state and tpm.msc for whether the TPM specification version is 2.0.
Does VAN 1067 mean TPM is not enabled?
Do not treat VAN 1067 as a TPM problem. Sources disagree about it, and Riot's own page describes it as a Vanguard start-up or connection failure rather than a TPM or Secure Boot problem. The handling direction is the Vanguard service, Windows updates, and clearing the game cache. Check Riot's current support page for what it says at the time you see the code.
BattlEye says "Blocked loading of file". Have I been banned?
No. The message means BattlEye stopped a kernel driver with a known security vulnerability from loading, because cheating software can exploit that kind of driver. It is not a ban and it will not cause a ban. Read the file path in the message, work out which software it belongs to, and update that software to a version with a signed, patched driver.
Will reinstalling the game fix it?
Usually not as a first step, and often not at all. Verifying the game files through the launcher is cheaper and repairs the most common cause in its class, because it only re-downloads the files that differ. Reinstalling the whole game will not repair an anti-cheat service, a runtime library, or a driver layer, so it should not be the first thing tried.
How should I handle a missing DLL message?
Read the DLL name first: it tells you which runtime library is missing — for example, VCRUNTIME140.dll points to the Visual C++ 2015–2022 Redistributable, and d3dx9_*.dll points to the DirectX End-User Runtime. Repair the library with Microsoft's official installer, and never download individual DLL files from unofficial websites. Running the game executable directly from its installation folder can also make a hidden DLL error visible.
Why should I not search online for a way to bypass anti-cheat?
Disabling, bypassing, or deceiving an anti-cheat system can lead to an account ban. The correct direction is to check whether the anti-cheat service is running, whether the driver layer has a problem, and whether Secure Boot and TPM 2.0 are enabled.
Only one game will not launch, and the others are fine. What does that point to?
It leans towards that game's own files, its anti-cheat layer, its settings, or its runtime requirements. If every game will not launch, the problem leans towards the launcher, the driver, the runtime libraries, or the system layer instead. The split is a direction for diagnosis, not a verdict on any particular title.
When should I stop and send it in for a check-in?
When every step in this guide has been done — files verified, launcher cache cleared, overlays compared one at a time, antivirus checked, anti-cheat service checked, runtime libraries repaired, driver updated — and the game still will not launch. Stop sooner if Event Viewer points at a driver or system file, or if the launch failure comes together with a black screen, screen artefacts, a driver crash, or a blue screen, because those have already gone beyond the launch layer. Bring the record of the process pattern, the error code or DLL name, and the result of each step.