GPU No Display on Cold Boot but Works After Restart? Cold-Start Power Timing, Memory Training, Fast Startup & Link Retraining Diagnosis Guide

2026-11-12 | GPU Repair | 27 minutes | HK GPU Fix Editorial Team

GPU No Display on Cold Boot but Works After Restart? Cold-Start Power Timing, Memory Training, Fast Startup & Link Retraining Diagnosis Guide

Key Takeaways

A PC that shows nothing on the first cold boot but works normally after a restart is not randomly failing. A cold boot rebuilds power, memory timing and the display link from a fully powered-off state, while a warm restart keeps power running and reuses much of that state. The contrast between the two is the diagnosis.

What Counts as "No Display on Cold Boot, Works After Restart"

Before any diagnosis begins, the symptom has to be pinned down precisely. All five of the following must be true before this guide applies:

  1. The machine has been fully powered off for a while — for example, shut down overnight, the power supply switch turned off, or the power cord unplugged. On the first press of the power button, the fans spin and the lights come on, and the keyboard lights may respond, but the monitor shows nothing at all from start to finish — not even the motherboard logo or the BIOS screen.
  2. Pressing the restart button — or shutting down and powering on again immediately — brings the picture back normally, and the machine then works fine for the rest of the day.
  3. The monitor was already switched on, fully awake, and sitting on the correct input source before the machine was powered on. This rules out a power-on order problem, where the display simply was not ready when the graphics card tried to talk to it.
  4. Waiting two or three minutes does not bring the picture back on its own. A picture that arrives late is a delay problem, not this one. Here, waiting changes nothing; only a restart brings the picture back.
  5. The pattern repeats reliably. It happens on cold boot after cold boot, and the restart works every time. A single one-off failure can have many causes and is not enough to draw a conclusion from.

The dividing line is the contrast itself: first cold boot fails, restart succeeds. A cold boot and a warm restart are not the same journey. A cold boot has to rebuild everything from a fully powered-off state — establish power, train the memory, train the display link, and enumerate the devices. A warm restart never cuts power at all, so much of the device state, the power rails and the training results carry over. A failure on the first attempt and a success on the second means something goes wrong in the act of building from cold — not that the graphics card is randomly dying.

Four Ways of Starting a PC Are Not the Same Thing

Much of the confusion around this symptom comes from treating every kind of "turning it on" as the same event. They are not. The four operations below differ in what is rebuilt and what is carried over, and the difference matters for diagnosis.

OperationWhat happens to powerWhat happens to the Windows kernelWhat happens to hardware state
Shut down and power on, with Fast Startup onPower is not fully cut; standby power remainsThe kernel session is saved to disk and restored, not rebuiltDevices keep much of their state
Shut down and power on, with Fast Startup offPower is not fully cut; standby power remainsThe kernel session ends and is rebuilt on the next bootDevices keep much of their state
RestartPower runs continuously, never interruptedThe kernel session ends completely and is rebuilt from scratch; Fast Startup does not apply to a restartDevices keep their power, though the kernel is rebuilt
Full cold start after cutting powerThe power supply switch is turned off or the cord is unplugged, and standby power drains awayThe kernel is rebuilt from scratchHardware state is reset by the loss of power — the only operation in which devices fully lose power

The inference follows directly: if a problem disappears after a restart but appears after a full cold start, it cannot be explained by "the kernel needed a fresh start" — because a restart already gives the kernel a fresh start. The only things that can explain the contrast are conditions that exist only at a cold start: power establishment, memory training, link training, and firmware enumeration. Those four are the branches this guide tests.

The Four Cold-Start Branches

Branch One: Power Timing — the Power-Good Signal

When a power supply unit is switched on, its outputs do not become stable instantly. Once the outputs have settled, the power supply sends a signal called Power-Good — a +5V signal, normally delayed by 0.1 to 0.5 seconds — telling the motherboard to release the processor from reset so it can start running the BIOS. Without Power-Good, the processor stays held in reset and the system will not run on unstable power.

A poorly designed or ageing power supply can get the timing of this signal wrong: it may send Power-Good too early, releasing the processor before the outputs are stable, so the processor starts executing on unstable voltage and the boot fails; or an output may drift out of its permitted range part-way through, causing Power-Good to be withdrawn and the system to be reset. Public technical writing on this mechanism states the connection plainly: if a system does not boot properly the first time the switch is turned on but boots when the reset or warm-boot command is pressed, the Power-Good signal is a likely suspect. That sentence describes this article's symptom almost word for word, and it is the strongest public evidence for the power-timing branch.

Discussion in public hardware forums points the same way: several contributors describe a power rail that is unstable on a cold start — a rail that only settles once a small load is present, or electrolytic capacitors that have aged so that their behaviour is poor when cold and temporarily improves as temperature changes, leaving the rails stable by the time of the restart. An ageing CMOS battery was also raised in those discussions, but other contributors did not consider it the main cause, because a battery problem does not explain why a restart after a failed cold boot succeeds.

Two cautions belong here. First, Power-Good can only be discussed qualitatively — as timing that is wrong — because different power supply designs differ, and no specific voltage figure can be written as a diagnostic threshold for a home reader. Second, comparing power supplies by swapping one in is inspection work, not a home test. This guide never asks a reader to open a power supply unit, measure power rails, or short any pins.

Branch Two: Memory Training — Finding Timings from Cold

When the motherboard starts up, it performs memory training: it searches for a set of signal timings that lets the memory run stably. If training fails, the DRAM debug LED stays lit and the boot stops there. On the AM5 platform, memory training on a first boot or after clearing the CMOS is expected behaviour and can take five minutes or more; public motherboard documentation notes that restarting part-way through makes the motherboard start training all over again. Enabling EXPO, an overclocking profile, can make training necessary on every boot, while enabling Memory Context Restore can shorten it.

For this symptom, memory training matters because it is a step that only a cold boot has to do from scratch. Training that fails at the edge — because of a contact, a slot, or a profile setting — can leave the machine with no display on a cold boot; on a restart, the training conditions are different (temperature, residual charge, settings already loaded) and the same training may pass. This is a candidate mechanism to be tested, not a conclusion. It cannot be written as "your machine has this cause".

No specific training-time threshold can be given, because platforms and memory combinations differ too widely. The only principle is to wait long enough and not interrupt training by restarting part-way through. The debug LED observation — noting which LED the board stops on — is used here as an observation only; the full LED code table is in the debug-LED diagnosis (#257).

Branch Three: Fast Startup — a Restored Kernel State

Fast Startup, present since Windows 8 and switched on by default, is not a true shutdown. When the machine is shut down with Fast Startup on, programs close and the user is logged out, but the kernel session (session 0), together with the drivers already loaded, is written to the hiberfil.sys file. On the next power-on, that session is restored rather than rebuilt from scratch.

A restart bypasses Fast Startup completely: the kernel session ends in full, no snapshot is saved, and Windows performs a complete boot. Microsoft's own documentation notes that a restart usually means the user wants a completely fresh Windows state, for example after installing a driver or changing hardware. Microsoft also warns driver developers that, with Fast Startup on, the time between genuine kernel restarts can be much longer than in older versions of Windows, because the kernel, drivers and services are saved and restored rather than restarted each time. If a driver is in a bad state — stuck, for example — a Fast Startup shutdown can carry that state into the next session.

The symptom is "cold boot fails, restart succeeds", and Fast Startup affects the "shut down and power on" path. So the test logic is this: if what the user calls a "cold boot" is actually a hybrid shutdown with Fast Startup on, then it was never a cold start at all. The first step is to perform a genuinely complete shutdown — using `shutdown /s /t 0`, the method Microsoft's documentation names for a one-off complete shutdown, without changing any setting — or to switch Fast Startup off and run a genuine cold-start comparison. Only then can anyone say whether the cold boot itself really fails. Conversely, if cold boots become normal after Fast Startup is switched off, the evidence points at the restored kernel or driver state. Fast Startup is a branch to test, not a villain to blame; the evidence is "the pattern changed when Fast Startup was switched off", not "Fast Startup itself is broken".

Branch Four: PCIe Link Training from a Cold State

A PCIe link is not a fixed wire; it is a negotiated result. The training state machine starts at the lowest speed, then tries progressively higher speeds, agreeing the lane width, the speed, and the equalisation settings. A cold start trains from power-on; a warm restart renegotiates from a restored state, with different starting conditions — equalisation starting points, power management state, and the firmware enumeration path. A physical path whose signal margin is tight can fail during the power-on negotiation and succeed on renegotiation, and the reverse is also possible.

The same caution applies as with the other branches: this can only be treated as a candidate mechanism to be tested. Any comparison of link readings has to be done under load, on both the cold and warm paths, using the same workload; an idle reading that looks low is not evidence. And there is a hard limit on what this branch can show at home: the failed cold boot shows no picture, so no reading can be taken from it. The only thing that can be recorded is that the link is normal on the successful restart — which proves the link works when it works, not what happened during the cold boot that failed.

Two Smaller Branches

The CMOS battery. A flat battery usually only causes BIOS settings and the clock to be lost; the machine generally still powers on. Writing the CMOS battery up as the main cause of a machine that will not boot is an exaggeration. Its only role in this guide is as an observation fork: if BIOS settings — the date and time, the XMP profile, the boot order — reset to factory values after every full power cut, then an ageing battery is worth checking as a side item. Nobody should expect replacing the battery to fix a cold-boot no-display fault.

The display link and monitor wake-up. The graphics card and the monitor have to complete a handshake early in the boot, and a DisplayPort link has to negotiate its lane count and speed; the firmware display path has limited retries, while the driver has more once it takes over. In this guide those mechanisms are only an exclusion branch: if the monitor was already on and awake, and swapping the monitor, the cable or the port changes nothing, the display link is not the main cause. Those mechanisms are covered in their own diagnoses, not here.

Diagnosis, Step by Step

The order below is fixed. Do not rearrange it. Three rules govern every step: change only one variable at a time; repeat each test and look at the pattern, not a single result; and write down four things every time — which start operation was used (full cold start, hybrid shutdown, or restart), what the screen showed at each stage (completely blank, motherboard logo, Windows loading, sign-in screen), which debug LED the board stopped on, and what changed most recently.

Step 0: Define the Symptom

Keep a log over several days: the result of every cold boot (overnight or after cutting power) and the result of every immediate restart. If the cold boot sometimes works and sometimes does not, and the restart does not always work either, the pattern has not been established and this guide's flow does not apply.

Also record what the machine does when it starts: whether the fans spin, whether the lights come on, whether the keyboard lights respond, which debug LED the board stops on, and whether the monitor shows "No Signal" or is simply black. Those two are different: "No Signal" means the monitor is receiving no signal; a black screen can mean a signal is arriving but the content is black.

Step 1: Rule Out the Monitor and the Display Chain First

Switch the monitor on first, wait until it is fully awake, and confirm it is sitting on the correct input source — then power on the machine. If doing this makes every cold boot work, the problem is the power-on order and the handshake window, and it belongs to the monitor power-on order diagnosis (#325), not this one.

Then swap, one at a time, recording each result: a different monitor (or a television), a different known-good short cable, and a different output port. If the fault follows a particular monitor, cable or port, it belongs to the corresponding branch — a slow-warming monitor (#406), the general no-signal diagnosis (#105), or the single-port diagnosis (#426). The monitor's own on-screen menu is a useful check: press the monitor's menu button. If the menu appears but the computer picture does not, the problem is upstream of the monitor; if the menu does not appear either, the problem is inside the monitor.

Step 2: The Fast Startup Comparison

Run a genuinely complete shutdown with `shutdown /s /t 0`, then power on. If this cold boot works normally, the earlier "cold boot failures" may never have been cold starts at all — they may have been hybrid shutdowns restoring a faulty kernel or driver state.

Then switch Fast Startup off and run cold-boot comparisons over several days. If cold boots are normal every time with Fast Startup off, the evidence points at the restored-state branch. If the first boot still shows nothing with Fast Startup off, Fast Startup is not the variable, and the investigation moves on. Note that this step is not asking the reader to switch Fast Startup off permanently; it is a diagnostic probe, and the conclusion is "the pattern changed" or "the pattern did not change", not "switching it off fixed it".

Step 3: The Memory Training Comparison

When the first cold boot shows nothing, do not restart immediately. Wait long enough — do not interrupt the process — and watch whether the DRAM debug LED stays lit and whether a picture eventually appears on its own. On the AM5 platform, training after a first boot or a CMOS clear can take a long time, and restarting part-way through only makes the motherboard start training from the beginning again.

Record whether BIOS settings reset after a full power cut: the date jumping back to a factory date, XMP switching back off, or the boot order changing. If any of those happen, the CMOS battery goes on the list as a side item to check, without exaggeration.

Deeper memory tests — swapping slots, reducing to one stick, switching EXPO or XMP off — involve taking hardware apart or changing firmware settings, and they carry risk. A reader who is not confident with firmware settings should stop at this point. Those steps are not given here as a do-it-yourself procedure.

Step 4: The Power Cold-Start Comparison

Reduce the variables present at a cold boot: unplug non-essential external devices — hubs, a second monitor, USB devices — and run the cold-boot comparison again. If the pattern changes when the load is reduced, the evidence points towards the power-establishment edge.

Comparing power supplies by swapping one in belongs to inspection. The most this guide can say is to bring the full cold-versus-warm record to a check-in, because power timing can only be confirmed with professional instruments. No reader should be told to open a power supply, measure power rails, or short the power-on pins.

No general wattage threshold is given here either. Whether the wattage is enough and whether the machine powers on are two different things, and different configurations have different requirements.

Step 5: The Link and Slot Comparison

After a successful restart gets into Windows, record the PCIe generation and width under load, and compare them with what the graphics card and the slot are designed to support. Remember the limitation: the failed cold boot shows no picture, so no reading can be taken from it. This step can only prove that the link is normal on the successful restart; it cannot directly prove what the link did during the cold boot that failed.

Slot, riser cable and retimer variables are recorded as configuration facts only. The reader is not asked to remove and reinstall the card as a test, because removing a card changes four variables at once — power cut, time passing, refreshed slot contact, and link retraining — and no conclusion can be drawn from the result.

TestResultMore likely explanationNext step
Monitor on early and on the correct input, cold boot still shows nothing on the first tryMonitor order and handshake window ruled outContinue to Step 2Fast Startup comparison
Monitor on early, cold boot works every timePower-on order and handshake windowBelongs to the monitor power-on order diagnosis (#325)Note the working power-on order as a habit
Fault follows the monitor, cable or port when swappedDisplay chain componentBelongs to the slow-warming monitor (#406), general no-signal (#105), or single-port (#426) diagnosisFollow whichever component the fault followed
`shutdown /s /t 0` genuine cold boot works normallyThe earlier "cold boot" was not a genuine cold startRestored kernel or driver state branchSwitch Fast Startup off and compare over several days
Cold boots normal every time with Fast Startup offRestored kernel or driver stateFast Startup branchRecord the pattern; do not write it up as a permanent fix
First boot still shows nothing with Fast Startup offFast Startup is not the variableContinue to Step 3Memory training comparison
First cold boot eventually shows a picture if left long enoughA training or wake-up timing problem, not a permanent no-display faultMemory training or monitor wake-upWatch the DRAM LED and compare monitors
DRAM LED stays lit, and BIOS settings reset after a full power cutMemory training, with the CMOS battery as a side checkMemory training branchStop and send it in if firmware settings are unfamiliar
Pattern changes when the load is reducedPower establishment at the edgePower cold-start branchBring the record to a check-in; do not open the power supply
Pattern unchanged after reducing load, switching Fast Startup off, and swapping the display chainNarrowed to retained state, link, or firmware enumerationProfessional inspection neededBring the record of all four start operations to a check-in

Boundary Cases

Not every machine that shows no picture belongs to this guide. These look-alikes belong elsewhere:

SituationHow to tell it apartWhere it belongs
Cold boots are fine; only a warm restart goes wrongThe direction is exactly reversedThe warm-restart diagnosis (#339), whose boundary note explicitly excludes this cold-boot side
No picture only when the PC is switched on before the monitor; reversing the order fixes itA power-on order problemThe monitor power-on order diagnosis (#325)
The picture is only late and eventually arrives on its ownA delay, not a failure that needs a restartThe DisplayPort delay diagnosis (#324) or the slow-warming monitor diagnosis (#406)
The monitor itself warms up slowlyThe monitor is the main actor; swapping monitors rules it outThe slow-warming monitor diagnosis (#406)
Several presses are needed to get the machine to power on at all, fans and lights not respondingThe power-on chain itself is failing, not "powered on but no picture"The power-on failure diagnosis (#373)
The firmware screen is invisible but the picture appears once Windows loadsFirmware path versus driver pathThe firmware-versus-driver display diagnosis (#297)
The machine is stuck on the motherboard logo and does not moveA picture is present but frozen, not a complete absence of pictureThe stuck-at-logo diagnosis (#152)
No picture at all, in any order, by any methodNot a cold-versus-warm contrast problemThe general no-signal diagnosis (#105)
The picture appears, then the screen goes black or flickers intermittently during useA signal stability problem during use, not a start-up problemThe intermittent black screen diagnosis (#158)
The fault only appears after waking from sleepA different trigger pointThe sleep-wake diagnosis family (#284, #322)
The VGA debug LED stays litOnly the "which stage the LED stops on" observation is used hereThe debug-LED diagnosis (#257)
A laptopBuilt-in display switching and multi-display routing add a layer that desktop PCIe reasoning does not cover; the matrix still applies, but a laptop conclusion should not be drawn directly from desktop logicProfessional inspection

Common Misconceptions

When to Stop and Send It In

Stop and bring the machine in for a check-in if any of the following apply: no picture at all, in any order and by any method; a picture accompanied by garbled output, corruption or freezing; a boot accompanied by a crash, a black screen that cannot be recovered from, or a burning smell; or the full comparison sequence has been run and the result still cannot be tied to one variable.

Stop as well if a power supply comparison, removing the card, or changing firmware settings is needed and the reader is not confident doing it. For a graphics card still under warranty, opening it up, removing the cooler, or replacing thermal pads or thermal paste carries risk and may affect warranty eligibility — get a professional inspection first.

Bring a complete record to the check-in: the results of all four start operations, each with how many times it was repeated; what the screen showed at each stage; where the debug LED stopped; the Fast Startup on-versus-off comparison; the memory training observations (how long was waited, whether the DRAM LED stayed lit); a timeline of recent changes; and the results of the monitor, cable and port combinations tried.

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

Does no display on the first cold boot mean my graphics card is intermittently failing or about to die?

No. A cold boot and a warm restart take two different paths, and a first failure can come from conditions that only exist at a cold start — power timing or memory training — not from the card randomly failing. A randomly failing card would not follow the cold-versus-warm pattern so reliably. The contrast between the first cold boot and the restart is the diagnostic signal, and it has to be tested branch by branch before any part is blamed.

The restart fixed it, so did the machine repair itself?

No. A restart simply took the other path: power was never cut, and the kernel was rebuilt from scratch. The conditions that made the first attempt fail never appeared again, but they have not gone away. The next cold boot can fail again. A restart working is useful evidence about which path works; it is not a repair.

Is shutting down and powering on again the same as a cold boot?

No. A shutdown with Fast Startup on only restores a saved kernel state; a genuine cold start requires a full power cut — the power supply switch turned off or the cord unplugged. Using the wrong comparison produces the opposite conclusion. Use `shutdown /s /t 0` for a one-off genuinely complete shutdown, or switch Fast Startup off, before drawing any conclusion about cold boots.

I took the card out and put it back, and it works now. Does that mean I solved it?

No. Removing a card changes four variables at once — power cut, time passing, refreshed slot contact, and link retraining — and there is no way to tell which one mattered. Working afterwards does not mean the cause was found. If the pattern returns on the next cold boot, the original fault is still there.

Should I just wait longer for the picture to appear?

Waiting fits delay problems, where the picture arrives late on its own. In this symptom, waiting changes nothing — the cold start has already failed, and waiting only gives more time to a boot that has already failed. The one exception is memory training: on a first boot or after clearing the CMOS, training can take a long time, and restarting part-way through only starts training again. Wait long enough once, watch the DRAM LED, and then judge by the pattern.

Will a bigger power supply definitely fix it?

No. Whether the wattage is enough and whether the machine powers on are two different things. A power timing problem is not a wattage problem, and swapping in a bigger power supply is a gamble, not a diagnosis. Power timing can only be confirmed with professional instruments, so a power supply comparison belongs to inspection.

Is a dead CMOS battery the main cause of a machine that will not boot?

No. A flat battery usually only causes BIOS settings and the clock to be lost, and the machine generally still powers on. At most it is a side item to check — for example, if BIOS settings reset to factory values after every full power cut. Nobody should expect replacing the battery to fix a cold-boot no-display fault.

The fans are spinning, so does that mean the card is fine?

No. Fans spinning only shows that power reaches the fans. A card with a link, driver or firmware problem can still spin its fans. Fan movement is not evidence about the link, the driver or the firmware.

Will the latest driver or the latest firmware definitely fix it?

No. A driver or firmware change is itself a new variable that can contaminate the comparison. The version has to be recorded, and only one thing should be changed at a time. If the problem started after an update, rolling back and comparing is more informative than installing the newest version.

Is needing several presses to power on the same thing as no display on the first boot?

No. Needing several presses to power on is the power-on chain itself failing — the fans and lights do not respond. No display on the first boot is a machine that powers on but shows no picture. The dividing line is whether the fans and lights respond, and the two belong to different diagnoses.

Related articles

Related services

If you need Power connector repair, see these service pages: