GPU Artifacts, Flicker or Black Screen Only on the Login or Lock Screen, Fine on the Desktop? Login-Screen Display Mode, Driver Load & Power-State Diagnosis Guide

Key Takeaway
The login screen and the desktop are different display stages, with different modes, power states, and settings. Artifacts that appear only before login therefore point first at mode switching, driver loading, power states, or the display chain — not automatically at a failed card. Record which screen, what symptom, and how it clears before changing anything.
Why the Login Screen and the Desktop Are Two Different Worlds
The first thing to understand is that the login screen and the user desktop are not the same display stage wearing two different wallpapers. The login screen, including the lock screen, is handled by the system logon desktop, which runs under system default display settings. Only after a password or PIN is accepted does the system load the individual user profile, with its own resolution, refresh rate, HDR setting, colour profile, and multi-monitor arrangement.
The display driver itself loads during boot, but that is only part of the story. The driver full feature set, the vendor control panel service, and the per-user settings are enabled in layers as login proceeds. During the login screen, the graphics card is often still in a low power state, running at low clocks and low voltage, which is a very different operating point from the desktop at full speed. A fault that only appears at a low power state can therefore be completely invisible once the desktop is running.
Then there is the mode switch itself. The login screen usually runs in the monitor default mode. When login completes and the user settings take effect, the system switches display mode again if the user settings differ in resolution or refresh rate. Every mode switch involves output timing, cable bandwidth, monitor handshaking, and, for DisplayPort, link training. If any part of that chain is marginal, the symptom can appear on one side of the switch and vanish on the other.
The lock screen also deserves a careful distinction, because cold-boot login, pressing Win+L to lock, and waking from sleep to a lock screen follow different paths. Waking from sleep involves the monitor waking and the link retraining. A cold-boot login does not go through the sleep path at all. Treating all three as the same symptom throws away the most useful diagnostic clue available.
Finally, the lock screen can carry extra load of its own. Windows Hello cameras for face or fingerprint sign-in, lock screen slideshows, and rotating spotlight images all add activity during exactly the window when the symptom appears. None of these is a graphics card fault by itself, but each changes the system load and the graphics card power state at the moment the symptom is observed, so each is a variable worth recording.
First, Characterise the Symptom: Which Screen, What, and How It Clears
Before changing anything, record three dimensions of the symptom. Without all three, any conclusion is guesswork.
First, which screen shows the problem: the login screen after a cold boot, the lock screen after Win+L, the lock screen after waking from sleep, or all three. Second, what the symptom actually is: scattered dots or colour blocks, flicker, a black screen lasting a few seconds, or the whole login screen missing. Third, how it clears: on its own, after pressing a key or moving the mouse, only after entering the password and reaching the desktop, or only after restarting.
The key branching question is whether the symptom exists only on the login screen and disappears completely on the desktop, or whether it starts on the login screen and leaves some trace after login. The first pattern points at factors unique to the login stage, such as display mode, power state, or login services. The second pattern should be treated as a general display fault, and the login screen framing should be set aside.
Evidence matters, and the login screen cannot be captured with ordinary screenshot tools. The evidence is a phone photo or short video of the faulty login screen, paired with a photo of the normal desktop for contrast. A photo also helps place the problem in time, showing whether the fault sits in the login stage or the desktop stage.
Also note whether the symptom appears every time or only sometimes. Intermittent symptoms need a log: does it happen on cold boot only, or on every lock; and does it relate to how the machine was last shut down, whether by normal shutdown, fast startup, or sleep. That log is what turns a vague complaint into a diagnosable pattern.
Cause Layer A: Display Mode Switching
This is the first layer to consider, because the mode switch is the single biggest difference between the login screen and the desktop.
The login screen and the desktop can run at different resolutions or refresh rates. If the desktop is set to a high resolution and high refresh rate combination that sits near the edge of what the cable or port bandwidth supports, the switch at login can expose that marginal state on one side only. The same reasoning applies in reverse: the login mode itself may be the marginal one.
Multiple monitors add another dimension. The login screen may appear on only one monitor, or on the wrong monitor, because the user arrangement of primary and secondary screens only takes effect after login. A single-monitor test, with only the main monitor connected, is the decisive check here. If the symptom disappears with one monitor, the multi-monitor or primary-screen arrangement is implicated.
HDR is a variable to record rather than a suspect to blame. The login screen generally runs in SDR, while the desktop switches to HDR if HDR is enabled. A symptom that appears only on the login screen cannot be directly blamed on HDR, but the HDR setting changes the display path before and after login, so it belongs in the record alongside resolution and refresh rate.
Cause Layer B: Driver Loading and Services
During the login screen stage, the display driver may not yet be fully initialised. The vendor control panel service and driver helper services start after login. If the login screen shows artifacts but the desktop is stable, one possibility is that the driver is briefly unstable during a loading stage and settles once initialisation completes after login.
A driver crash followed by recovery, known as TDR, can also happen at the login screen: the picture freezes or goes black for a few seconds and then recovers by itself. In that case the Event Viewer should show display driver events around the time of the symptom. A TDR event by itself does not mean the graphics card hardware has failed. Driver, power delivery, and hardware are all possible contributors, and the events plus the conditions under which the symptom repeats are what separate them.
Timing is also evidence. If a driver update or a Windows update happened recently, compare the date the symptom started against the date of the update. A symptom that began immediately after an update points the investigation at the update; a symptom that began with no change at all points elsewhere.
Cause Layer C: Power States
At the login screen, the graphics card is usually in a low power state, at low clocks and low voltage. Some faults only appear in that low-load, low-voltage condition, for example faults related to power-state switching. That direction is the opposite of a fault that only appears while gaming, so a gaming stress test cannot be used to prove that a login-screen problem does not exist. The two tests measure different states.
Fast startup adds a further wrinkle. It is a hybrid shutdown, so shutting down and switching on again is not the same as a full cold start with power fully removed. Turning fast startup off in the power options and then shutting down completely and starting again is a useful test: if the symptom changes, the residual state left by hybrid shutdown is part of the picture.
Cause Layer D: The Display Chain — Cable, Port, and Monitor
At the moment the login screen appears, the monitor has just woken from standby, and the DisplayPort or HDMI link must retrain and complete its handshake. If the picture appears before link training has finished, the result can be brief artifacts, flicker, or a black screen that then settles. This is more worth suspecting when the monitor wakes slowly, the cable is long, or an adapter sits in the chain.
The decisive tests for this layer are swapping the cable, swapping the port, and swapping the monitor, changing only one variable at a time. If changing one item makes the symptom disappear, the display chain is implicated. If the symptom survives every swap, the cable and monitor are unlikely to be the cause, and attention moves back to mode, driver, or power state.
Cause Layer E: The User Profile
Everything that loads only after login — colour profiles, display settings, startup programs, vendor control software settings — cannot affect the login screen. That logic cuts both ways. If the symptom appears only on the login screen, a damaged user profile is a less likely cause. But that can only be confirmed with a second local account test: create a new local user account and check whether its login screen shows the same symptom. If it does, the original account settings are not the cause. If it does not, the original account settings and startup items are worth investigating.
Windows Hello, lock screen slideshows, and rotating lock screen backgrounds can be switched off one at a time to see whether the symptom follows. If the symptom disappears when one of them is off, that only proves the trigger condition, not the root cause. The underlying question remains whether the mode, power state, or display chain layer is at fault.
Three Lock Situations Compared
| Situation | What runs | What it points at when only this one fails |
|---|---|---|
| Cold-boot login screen | System logon desktop, default mode, driver still initialising | Login-stage mode, driver loading, or low power state |
| Win+L lock screen | Lock screen over a running session, monitor stays warm | Lock screen load, such as Hello or slideshow, or mode switch on return |
| Wake-from-sleep lock screen | Monitor re-wake, link retraining, sleep resume path | Sleep wake path, monitor handshake, or link training |
Use this table as a recording aid. Writing down which rows fail and which pass is the single most useful piece of evidence for the steps that follow.
The Diagnostic Order, Step by Step
Work through these steps in order, starting with the ones that need no hardware changes.
- Photograph the evidence. Use a phone to capture the faulty login screen, and the normal desktop afterwards for contrast. Record which of the three situations, cold boot, Win+L, or wake from sleep, show the symptom and which do not.
- Separate the three lock situations. Test the cold-boot login screen, the Win+L lock screen, and the wake-from-sleep lock screen individually. Only the wake case failing points at the sleep wake path; all three failing points at the login stage itself.
- Try a second local account. Create a new local user account and check its login screen for the same symptom. Present in the new account means the original account settings are not the cause; absent means the original account settings and startup items deserve a look.
- Test with a single monitor. Connect only the main monitor and remove the others, then repeat the test. A symptom that only appears with multiple monitors points at the multi-monitor or primary-screen arrangement.
- Swap the cable, port, or monitor, one at a time. If a swap removes the symptom, the display chain is implicated. If every swap leaves the symptom unchanged, the cable and monitor are unlikely to be the cause.
- Switch off Windows Hello and the lock screen slideshow, one at a time, and see whether the symptom follows. Treat this as a trigger test only, not a repair.
- Switch off fast startup in the power options, shut down completely, and start again. Compare the result with the previous behaviour.
- Check the Event Viewer around the time the symptom occurred for display driver stopped responding and recovered events, or other driver warnings and errors. A TDR event points the investigation at the driver, power delivery, and hardware paths; no event points more towards the mode or display chain layers.
- Cleanly reinstall the driver. Clean it out in Safe Mode with DDU and reinstall, noting the original driver version first and testing with the same version before trying any other version. Do not change several things at once.
- Compare with Safe Mode. Safe Mode uses the basic display driver. If the login screen still shows the symptom in Safe Mode, the driver layer is less likely and the hardware, display chain, and firmware layers move up the list. If Safe Mode is completely normal, the driver and user layers are more likely.
- Before seeking inspection, gather the records together: the symptom, the conditions under which it repeats, the steps already tried, and the Event Viewer findings. An inspection decision needs these records. A single sentence such as the login screen flickers is not enough.
Boundary Cases: When This Is Not a Login-Screen Problem
Not every black or faulty screen near login belongs to this guide. A desktop that is also faulty after login is a different direction and should be handled as a general display fault. A screen that goes black only after login, with a normal boot picture beforehand, is a separate topic. A machine that shows nothing at all until Windows appears is a firmware output problem, not a login screen problem. Artifacts already visible on the BIOS screen belong to a different diagnostic starting point, because the fault is present before the operating system display stages begin.
Symptoms that appear only after waking from sleep, with a normal cold-boot login screen, belong to the sleep wake path. A resolution or refresh rate that drops after waking is a wake display settings issue, distinct from whether the login screen itself shows artifacts. A machine that crashes or goes black only at low load is a low power state topic. A driver crash and recovery event is a TDR topic. The fact that a shutdown is not a full power-off under fast startup is a fast startup topic. And a symptom that began right after a driver or Windows update belongs to the update comparison and rollback topic. Each of these is mentioned here only as a one-line diversion so the reader lands in the right guide.
Common Misconceptions
A login screen artifact does not mean the graphics card has failed. The login screen and the desktop run different modes, different power states, and different setting layers, so a symptom confined to the login screen points more towards mode, state, or setting layers than towards a failed card.
A normal desktop does not prove the monitor is faultless. The monitor has just woken and renegotiated its link at the login screen, and stability on the desktop says nothing about that waking moment.
A normal screenshot does not prove there is no problem. The login screen cannot generally be captured with ordinary screenshot tools, and even when it can, a screenshot only reflects the frame buffer, not the output chain. A phone photo is the evidence for a login screen symptom.
Reinstalling Windows is not the first step. The second account test, single-monitor comparison, Event Viewer check, and fast startup switch are all low-cost separations that should come first. Reinstalling Windows does not fix a hardware, cable, or monitor layer problem.
Switching off the lock screen slideshow is not a repair. Removing a trigger only hides the symptom. If the underlying problem is in the mode or power state layer, the symptom can return under a different trigger.
A passing gaming stress test does not prove the card is healthy. A stress test measures the high-load state. A login screen problem may exist only in the low power state, which the stress test never measures.
Changing the driver does not always fix the problem. The driver is only one layer. Mode switching, display chain, and power state problems are untouched by a driver change.
A black screen lasting a few seconds at login is not necessarily a TDR. It can also be the monitor renegotiating its link, a mode switch, or a graphics card power state change. Whether a TDR event exists must be checked in the Event Viewer, not guessed.
When to Stop and Seek Inspection
Stop and seek in-shop inspection when the steps above cannot separate the layers, when Safe Mode and the normal desktop disagree and the records do not explain why, or when any proposed next step would involve opening the machine without knowing what to check. Bring the phone photos, the list of which lock situations fail, the steps already tried with their results, and the Event Viewer findings.
Inspection is available at the Shatin shop: Room 1209, Dali Plaza, Shek Mun. Telephone 2186 8010. WhatsApp 6558 6806. Published inspection and repair pricing on the site runs across three tiers from HK$400 to HK$2,800. There is no on-site service, so the machine is brought to the shop for inspection.
Frequently Asked Questions
Why does the login screen flicker but the desktop is fine?
Because the login screen and the desktop are different display stages. They can run at different resolutions and refresh rates, the graphics card sits in a different power state, and the user settings only load after login. A fault in the mode switch, the driver loading stage, the low power state, or the monitor link retraining can therefore appear only before login and vanish on the desktop.
Can I take a screenshot of the login screen to show the problem?
Not with ordinary screenshot tools, because those tools run inside the user session, which has not started yet at the login screen. Use a phone photo or short video of the faulty screen, together with a photo of the normal desktop for contrast. The photo is also what separates a login-stage fault from a desktop fault.
My card passes a gaming stress test, so is the card definitely fine?
No. A stress test measures the high-load state. A login screen fault may exist only in the low power state, at low clocks and low voltage, which the stress test never exercises. The two tests answer different questions, so one cannot substitute for the other.
I switched off the lock screen slideshow and the flicker stopped. Is it fixed?
Not necessarily. Switching off the slideshow removes a trigger, but the underlying cause in the mode, power state, or display chain layer may still be present and may reappear under a different trigger. Keep the record of what was switched off, and continue the diagnostic steps if the symptom returns.
Should I reinstall Windows first?
No. Try the low-cost separations first: a second local account, a single-monitor test, the Event Viewer check, and switching fast startup off and on. Reinstalling Windows does not fix cable, monitor, slot, or hardware layer problems, and it destroys the before-and-after comparison that makes the diagnosis possible.
What should I bring when I come in for inspection?
Bring the phone photos of the faulty login screen and the normal desktop, a note of which situations fail, cold boot, Win+L, or wake from sleep, a list of the steps already tried and what each one changed, and any Event Viewer findings. The shop is at Room 1209, Dali Plaza, Shek Mun. Telephone 2186 8010. WhatsApp 6558 6806.