GPU Artifacts Only After Windows Loads, But the BIOS Screen Is Clean? Pre-Driver vs Driver Rendering Path Diagnosis Guide

Key Takeaways
The BIOS screen is drawn by the card's firmware through a simple frame buffer, before Windows loads its graphics driver. So a clean boot screen only shows that this low-load path works. Artifacts that appear only after Windows loads point to a different rendering path, and this guide works through the stages, in order, to find which one it is.
What the Boot Screen Actually Uses
When a computer starts, the motherboard firmware (BIOS or UEFI) and the graphics card firmware draw the motherboard logo, the BIOS setup screen and the boot logo through the Graphics Output Protocol, or GOP. This is a simple frame-buffer output: the firmware writes pixels into a buffer and the card displays them. No Windows graphics driver is involved at this stage. Game shaders, overlay software, driver settings and driver versions have not entered the picture yet.
GOP lives in the graphics card firmware, not in Windows. Reinstalling, updating or rolling back the Windows driver does not change what the boot screen looks like, and a clean boot screen does not prove the graphics card hardware is fully healthy. It only proves that the firmware frame-buffer path and the output chain work under a very light load. A VRAM fault or a GPU core fault can stay hidden at this stage and only show up once the driver loads and the card is asked to do high-speed rendering. That is the single most important point in this guide: a clean BIOS screen narrows the problem down, but it does not clear the hardware.
The Handover: How the Display Path Changes Inside Windows
After the firmware hands over to Windows, the display path changes in stages, and each stage uses different parts of the card:
- Windows boot loader screen — still simple output, close to the firmware path.
- The vendor driver loads — the manufacturer's driver replaces the Microsoft Basic Display Driver and takes over the card. This is the first moment the 3D engine, shaders, video memory management, hardware decoding and overlay planes are switched on.
- The login screen — drawn with the vendor driver active, in a different session from the desktop.
- The desktop — composed by the Desktop Window Manager (DWM), which uses the driver for compositing.
- Applications and games — full 3D rendering, the heaviest load the card sees.
Because each stage uses a different path, the stage where artifacts first appear is itself diagnostic evidence. Artifacts that begin at the login screen, at the desktop, or only inside one application point in different directions, and the decision tree below follows that order.
Safe Mode and the Basic Display Driver: The Decisive Comparison
Safe Mode loads only the basic display driver. The vendor driver is not used, so the 3D engine, hardware acceleration and driver settings are all out of the picture. Microsoft's own support documentation and multiple repair sources agree on what this comparison means: if the screen is clean in Safe Mode and artifacts appear only in normal mode, suspicion narrows to the vendor driver, its settings, or software that loads with the driver. If artifacts appear in Safe Mode too, suspicion moves towards the hardware, the firmware or the output chain — but that is not an immediate verdict on the hardware, because the basic driver still sends its frame buffer through the same output chain and the same video memory.
Device Manager may show the card as "Microsoft Basic Display Adapter". That name means Windows can see the card but has not loaded the vendor driver — because it is not installed, it is damaged, or it has been replaced. It provides basic output with no hardware acceleration, and the resolution may be limited. Seeing that name does not mean the card is faulty; it only means the driver layer has not taken over yet.
The Diagnosis, Step by Step
Work in this order. Each step narrows the field, and skipping ahead — for example, reinstalling the driver before the Safe Mode comparison — turns diagnosis into blind trial and error.
Step 1: Pin down the first stage where the problem appears
Look at the boot screen first: the motherboard logo and the BIOS setup screen. If artifacts are already there, this is not the situation this guide covers — the fault is present before Windows loads, and the companion guide on artifacts already visible on the BIOS screen (#295) is the right path. That companion guide states plainly that it does not cover artifacts that appear only after Windows has loaded; this guide covers exactly that other half, and the two together form the complete before-and-after picture.
If the boot screen is clean, move on and note the first Windows stage where artifacts appear: the login screen, the desktop as soon as it appears, or only when a particular program opens.
Step 2: Separate the login screen from the desktop
The login screen and the desktop are different sessions, with different display modes and different driver loading stages. Artifacts that appear only on the login screen and vanish once the desktop appears belong to that stage, and the login-screen guide (#349) covers them. Artifacts that start at the desktop and stay belong to this guide's path. Artifacts that appear only inside one particular program point towards that program's rendering path, and the application-specific guides (#341, #290) are the right follow-up.
Step 3: Screenshot versus phone photograph
As soon as the artifacts appear, take a screenshot (Win + Shift + S, or Print Screen) and photograph the physical screen with a phone, then compare the two. If the screenshot shows the same artifacts, the fault travels with the frame buffer — it sits in the rendering or driver or video memory layer. If the screenshot is clean but the eye can see artifacts on the screen, the fault sits after the output chain — the cable, the connector or the monitor — or it is a fleeting, timing-related symptom that a slow-motion recording may catch. This test belongs at this point in the order, not first, because the stage where the symptom appears has to be established before the layer can be judged.
Step 4: The Safe Mode comparison
Boot into Safe Mode and see whether the artifacts are still there. Safe Mode clean, normal mode faulty: the vendor driver, its settings, or software that loads with the driver is the strongest suspect. Safe Mode faulty too: suspicion rises for hardware, firmware or the output chain — but do not stop here, because the cable, connector and monitor still have to be ruled out before any hardware conclusion is drawn.
Step 5: The driver restart shortcut
Press Win + Ctrl + Shift + B. This restarts the display driver: the screen goes black for a moment and then returns, without restarting the whole computer. It is a legitimate quick comparison test, not a repair. If the artifacts clear immediately after the shortcut, that points towards a driver or compositing state problem. If nothing changes, continue down the tree. Do not write this off as a fix — restarting the driver only clears state for a comparison.
Step 6: The driver branch (only if Step 4 points to the driver)
Check Device Manager for the card's name — whether it reads "Microsoft Basic Display Adapter" — and check the driver version and date, and whether a driver update or a Windows update happened recently. If the artifacts began right after a driver or Windows update, driver-layer suspicion rises sharply, but the Safe Mode comparison still has to confirm it before any conclusion is drawn. A clean reinstall with DDU is a last resort, not a first step; the DDU process itself is covered in the driver-cleanup guides (#102, #256) and is only pointed to here, not repeated.
Step 7: The hardware branch (only if Step 4 points to hardware)
Apply the second dividing line: the 2D desktop versus 3D load. Artifacts on the desktop with games running normally point more towards the 2D, compositing, driver-settings or overlay-plane side. A normal desktop with artifacts only under 3D load points more towards the 3D engine, shaders, video memory bandwidth or power delivery. Artifacts in both point more towards a shared path — the driver core, the video memory, or the output. The video-memory-versus-core split, including the pattern comparison, belongs to the dedicated guide (#107) and is only pointed to here; the pattern comparison there has to be combined with testing, and a pattern on its own does not convict either part. Rule out the output chain by swapping the cable, the connector and the monitor. Do not conclude that the card needs repair before the driver has been ruled out.
Step 8: The closing judgement
There are four possible endings, and each one names its next step rather than ending in a single "send it for repair":
- Driver layer — the Safe Mode comparison and the driver restart shortcut both point here. Follow the driver-cleanup guides (#102, #256) for the reinstall process.
- Settings layer — the driver loads, but a setting, an overlay or a compositing option is the trigger. The next step is to reset driver settings and disable overlays one at a time.
- Output chain — the screenshot is clean while the eye sees artifacts, or swapping the cable, connector or monitor clears the problem. The next step is to replace the faulty link in the chain.
- Hardware layer — Safe Mode is faulty too, the output chain has been ruled out, and the 2D-versus-3D split points to the card. The next step is an inspection, and the published three-tier repair service fee range on this site is HK$400–2,800, with the actual quote given after inspection.
Reading the Stages at a Glance
| First stage where artifacts appear | What that stage uses | Direction the evidence points |
|---|---|---|
| BIOS setup screen or boot logo | Card firmware, GOP frame buffer, basic output chain | Before Windows loads — see the BIOS-screen guide (#295) |
| Login screen only, gone on the desktop | Vendor driver in the login session | Login-screen stage — see the login-screen guide (#349) |
| Desktop as soon as it appears | Vendor driver plus desktop compositing (DWM) | Driver, settings, overlay planes, or shared rendering path |
| Only inside one application or game | That application's 3D or video-decoding path | Application-specific path — see #341 / #290 |
| Only when watching video or in a browser | Hardware video decoding path | Decoding path — see #173 |
| Safe Mode clean, normal mode faulty | Vendor driver and everything that loads with it | Driver layer is the strongest suspect |
| Safe Mode faulty too | Basic driver through the same output chain and video memory | Hardware, firmware or output chain — still needs the output chain ruled out |
Boundary Cases
- Artifacts only on the login screen, gone on the desktop. The login screen and the desktop are different sessions. Follow the login-screen guide (#349) rather than treating this as a desktop problem.
- Artifacts only on one monitor or one connector. That is an output-chain problem, not a driver problem. Swapping the connector is the decisive test.
- Artifacts began after a driver update or a Windows update. Driver-layer suspicion rises sharply, but the Safe Mode comparison still has to confirm it. Do not settle on the driver from timing alone.
- Artifacts come and go, and a restart sometimes clears them and sometimes does not. That pattern fits a state problem — driver state or compositing state — and the driver restart shortcut is the most valuable comparison here. Do not write it off as an intermittent hardware fault first.
- The monitor's own on-screen menu (OSD) shows artifacts too. The monitor itself is the problem, and the graphics card is not involved. This is the same principle used in the BIOS-screen guide (#295).
- Artifacts only when watching video or in a browser. That is the hardware video decoding path, covered in the decoding guide (#173), and it is not expanded here.
- Artifacts only in games. That is the 3D path, covered in the game-specific guides (#341, #290).
Common Mistakes
- "A clean BIOS screen means the hardware is definitely fine." Wrong. A VRAM or core fault can stay hidden until the driver loads and the high-speed rendering path is used. The GOP frame buffer runs at a very low load and cannot prove the high-speed path is healthy.
- "Artifacts only after Windows loads means the driver is definitely broken." Wrong. The driver is only one suspect. A video memory fault, an output-chain problem or a monitor problem can all first appear in the Windows stage — for example, a high resolution or high refresh-rate mode that is only enabled once Windows loads.
- "Reinstalling the driver will fix it." Wrong. Reinstalling the driver only helps if the fault is in the driver layer. Reinstalling before the Safe Mode comparison is a blind attempt, not a diagnosis.
- "A clean screenshot means the graphics card is fine." Wrong. A clean screenshot only proves the frame buffer is clean. An output-chain problem — cable, connector or monitor — can still make artifacts visible to the eye.
- "Artifacts in Safe Mode mean the card has to be replaced." Wrong. Artifacts in Safe Mode only push suspicion towards hardware or the output chain. The cable, connector and monitor still have to be ruled out before any hardware conclusion is drawn.
- "The artifact pattern alone can convict VRAM or the core." Wrong. A pattern is only a clue, not a verdict. The pattern comparison in the dedicated guide (#107) has to be combined with testing; no conclusion should rest on the pattern alone.
- "The driver restart shortcut fixed it." Wrong. Restarting the driver only clears state for a comparison. It is a diagnostic test, not a repair, and the underlying cause still has to be found.
Frequently Asked Questions
My BIOS screen is clean but Windows shows artifacts. Is my card dying?
Not necessarily, and that conclusion cannot be drawn from the timing alone. A clean BIOS screen only shows that the firmware frame-buffer path works at a low load. The fault could sit in the driver layer, the settings layer, the output chain, or the hardware — and the Safe Mode comparison is the step that separates the driver from the rest.
Why does Safe Mode matter so much?
Because Safe Mode loads only the basic display driver and leaves the vendor driver unused. If the artifacts vanish in Safe Mode, the vendor driver or something that loads with it is the strongest suspect. If they stay, the fault is deeper — but the output chain still has to be ruled out before the hardware is blamed.
The screenshot is clean but I can see artifacts on the screen. What does that mean?
It means the frame buffer itself is clean, so the fault sits after the output chain — the cable, the connector or the monitor — or it is a fleeting timing symptom. Swap the cable, the connector and the monitor one at a time to find which link is responsible.
Artifacts started right after I updated the driver. Should I just roll back?
The timing makes the driver the strongest suspect, but confirm it first with the Safe Mode comparison. If Safe Mode is clean and normal mode is faulty, a driver reinstall is the right next step; the DDU cleanup process is covered in the driver guides (#102, #256). Rolling back without the comparison is a guess, not a diagnosis.
What does Win + Ctrl + Shift + B actually do?
It restarts the display driver. The screen goes black for a moment and then returns, without restarting the whole computer. If the artifacts clear immediately, that points towards a driver or compositing state problem. It is a diagnostic test, not a repair.
Artifacts appear only when I play games, never on the desktop. Is that the same problem?
No — that is a different dividing line. A normal desktop with artifacts only under 3D load points more towards the 3D engine, shaders, video memory bandwidth or power delivery. The game-specific guides (#341, #290) cover that path.
The monitor's own menu shows artifacts too. Is the card at fault?
No. If the monitor's own on-screen menu shows artifacts, the monitor itself is the problem and the graphics card is not involved. That check alone can save a needless driver reinstall or a needless inspection.
Getting Help
A clean boot screen with artifacts only after Windows loads is a stage problem, and the stages have to be worked through in order: first the stage where the problem appears, then the screenshot comparison, then Safe Mode, then the driver restart shortcut, and only then the driver or hardware branch. Each step narrows the field, and no step on its own is a verdict. When the fault points to the hardware layer and the output chain has been ruled out, the card should be brought in for inspection. HK GPU Fix is at Room 1209, Dali Plaza, Shek Mun. For enquiries, call 2186 8010 or WhatsApp 6558 6806. There is no on-site service, so the card should be brought to the shop for inspection.