GPU Resolution or Refresh Rate Resets on Every Boot? Boot Detection, Fast Startup & Mode Persistence Diagnosis Guide

2026-11-11 | GPU Repair | 21 minutes | HK GPU Fix Editorial Team

GPU Resolution or Refresh Rate Resets on Every Boot? Boot Detection, Fast Startup & Mode Persistence Diagnosis Guide

Key Takeaways

Every boot drops the desktop back to a low resolution or a low refresh rate, even though the wanted mode can still be selected by hand and works until the next boot. The cause usually sits in boot detection timing, Fast Startup restoring a stale saved mode, the Base video boot option, or a startup program forcing its own mode.

What the Symptom Is — and What It Is Not

Every boot — cold boot or restart — drops the desktop resolution or refresh rate back to a lower mode. A native resolution falls back to something like 1024×768, or 144 Hz falls back to 60 Hz. Setting the wanted mode by hand restores it for that session, and it works normally until the next boot, when it drops back again. Three features define the symptom:

  1. It follows the boot. Cold boot and restart both drop the mode. It is not tied to waking from sleep.
  2. It repeats. Not a one-off — every boot does the same thing.
  3. The wanted mode can still be set by hand. After selecting it in settings, the desktop runs normally for that session. The problem is that the next boot does not keep it.

Two triage splits belong at the very start, because getting them wrong sends the whole diagnosis down the wrong path.

Split One: Is the Wanted Mode Even Listed?

SituationWhich layer it points to
The wanted mode is not in the settings list at allThe mode list itself has shrunk — EDID read failure, not enough bandwidth, or the monitor identified wrongly. That is a different diagnosis
The wanted mode is listed and selectable, but the boot does not keep itThe mode persistence layer — boot detection, Fast Startup saved state, driver loading, or a startup program. This is the subject here

A mode that cannot be selected at all is a different problem — the mode list has shrunk. The persistence problem is the second row: the mode is listed and selectable, but the boot does not keep it.

Split Two: Which One Drops?

Record which one drops — resolution only, refresh rate only, or both together — and do not lump them together as "the picture got worse". Both dropping together leans towards the whole mode not being saved. Only the refresh rate dropping leans towards a conservative mode being used at boot detection. Only the resolution dropping needs a further look at whether the system has fallen back to a basic display mode.

Four Things Windows Has to Do at Boot

For the wanted mode to appear after a boot, Windows has to complete four steps. If any one of them fails, the system uses a more conservative fallback mode so that a picture appears as quickly as possible, rather than waiting for complete information to arrive.

  1. Load the driver. The graphics driver has to load successfully. If driver loading fails, or the driver is damaged or has been replaced, Windows falls back to a basic display mode — low modes such as 640×480 or 1024×768 — and the mode list shrinks with it. Driver trouble is one of the most commonly reported causes of resolution dropping after a boot.
  2. Detect the monitor. The driver has to read the monitor's EDID — its identity and supported-mode data — over the DDC channel. If the monitor is not ready at the moment of detection — still in standby, or switched off at a power strip — the system may receive incomplete data and use a low mode.
  3. Read the saved mode. Windows has to read back the display settings saved from last time. If the saved settings are damaged or have been reset, or if the system re-detects the monitor at boot and treats it as a "new" monitor, the saved mode is abandoned.
  4. Apply the mode. The driver applies the mode to the monitor. If a startup program or a third-party display management tool forces a different mode at sign-in, the apply step is hijacked. There are documented cases of a startup program setting itself to a 640×480 compatibility mode, causing the resolution to drop on every boot.

Fast Startup: A Shutdown That Is Not a Fresh Start

Fast Startup is the key mechanism for understanding this symptom. When Fast Startup is on, shutting down does not rebuild the system from scratch. It writes the kernel session into the hibernation file and restores it on the next boot. Standby power remains present. Only a complete disconnection from power — unplugging the wall cord — is a true cold boot.

For display modes, this has two consequences. First, the display settings saved into the hibernation file at shutdown may be old or damaged, and the boot restores that old mode. Second, Restart is not affected by Fast Startup, because a restart rebuilds the kernel. So the comparison "shutdown then power on drops the mode, but Restart keeps it" is itself evidence pointing at Fast Startup.

Turning off Fast Startup is a commonly reported fix for display settings resetting on every boot. The path is Control Panel, Power Options, Choose what the power buttons do, Change settings that are currently unavailable, uncheck "Turn on fast startup", Save changes, then restart.

The shutdown-versus-restart comparison is the cheapest test in the whole diagnosis, and it belongs early: if only shutdown-then-power-on drops the mode while Restart keeps it, Fast Startup is the suspect. If all three boot methods — shutdown then power on, Restart, and a true cold boot with the cord unplugged — drop the mode, Fast Startup is not the cause.

Base Video: A Boot Option That Forces Compatibility Mode Every Time

Windows has a boot option called Base video, found in System Configuration (msconfig) on the Boot tab, corresponding to the `vga` option in boot settings. Its effect is to force the standard VGA display driver instead of the full graphics driver. If this option has been ticked — it can happen by accident, or a troubleshooting tool may have switched it on and never switched it back — every boot uses a low-resolution compatibility mode.

This step is only about checking whether the option is ticked. Unfamiliar users should stop at the check and not change other boot settings. If Base video is ticked, untick that one option only and test again. If it is not ticked, this branch is excluded.

Monitor Power State: The Monitor Was Not Ready When Detection Ran

The detection timing mechanism works the same way as the wake-from-sleep handshake problem, but the trigger point is different: here it is the boot, not the wake. If the monitor is not fully on when the computer boots — its power button not pressed, in deep standby, or on a power strip that switches on together with the PC but the monitor wakes more slowly than the PC — the driver may think the monitor is not there at the detection moment, or may receive only part of the EDID, and a conservative mode is used.

The comparison is simple: switch the monitor fully on first, wait a few seconds, then power on the PC. If the mode is kept with that order, the cause is detection timing, not the driver or the settings. If both orders drop the mode, timing is not the cause.

The Driver Being Replaced: Windows Update Overwriting the Driver

If Device Manager shows the graphics card as Microsoft Basic Display Adapter, the driver is missing and the system has fallen back to a basic mode — that is a device-layer problem, not a persistence problem, and the missing driver has to be dealt with first.

Windows Update can replace the graphics driver with a different version during a boot or an update. After the replacement, the saved mode may no longer apply, and every boot uses a low mode. The check here is the driver version plus the update timeline: note the driver version and date, and match them against when the problem started. If the problem started right after an update, the driver version and the update timeline are the evidence. Rolling back to the previously working version is the comparison to make, judged by the timeline rather than by "newest is best". A custom resolution utility is an advanced tool; do not use it to change EDID data yourself — EDID changes are a job for inspection.

Diagnosis, One Variable at a Time

There is one iron rule for the whole diagnosis: change one variable at a time, test with a boot after each change, and write down the result. The order below should not be rearranged.

StepWhat to doWhat it proves
Step 1: Record the baselineThe wanted mode before boot versus the mode after boot; which one drops — resolution, refresh rate, or both; whether the wanted mode is listed in settingsWhether the problem is in the persistence layer or the mode-list layer
Step 2: Identity checkIn Settings and Device Manager, is the monitor the correct model?"Generic PnP Monitor" points to a monitor-identity diagnosis, not this one; the correct model means continue here
Step 3: Boot method comparisonCompare three boot methods: shutdown then power on (Fast Startup on), Restart, and a true cold boot with the cord unpluggedOnly shutdown-then-power-on drops the mode while Restart keeps it — Fast Startup suspect; all three drop it — not Fast Startup
Step 4: Turn off Fast Startup and testFollow the Fast Startup path above, then restart and testNormal after switching it off — Fast Startup was the cause; still drops — Fast Startup excluded
Step 5: Monitor power state comparisonSwitch the monitor fully on first, wait a few seconds, then power on the PC; compare with booting while the monitor is in standbyMonitor-first keeps the mode — detection timing; both drop it — not timing
Step 6: Base video checkIn msconfig, Boot tab, check whether Base video is tickedTicked — untick that one option only and test again; not ticked — this branch excluded
Step 7: Driver layerIn Device Manager, is the graphics card model normal? Note the driver version, date, and recent update timeline; cleanly reinstall the driverDriver version plus timeline is the judging evidence; after reinstalling, run the baseline comparison again
Step 8: Startup program comparisonClean boot — disable startup programs one at a time — and see which program changes the mode at sign-inNormal after disabling one program — that program was the cause; still drops with all disabled — not a startup program
Step 9: Multi-monitor branchRemove the second monitor one at a time and test with only one connectedNormal after removing one — multi-monitor re-enumeration or primary monitor identity swapping; still drops — not this branch
Step 10: Cable and interface comparisonChange the cable, change the interfaceA change after swapping cable or interface — signal or EDID transmission layer; no change — cable excluded

The Identity Check in Detail

Before the steps above, confirm the monitor identity. In Settings and Device Manager, the monitor should show its correct model name. If it shows "Generic PnP Monitor", the monitor identity has been read wrongly and the mode list has shrunk — that is a different diagnosis. A correct model name does not by itself prove the EDID was read completely on every boot: identity can be correct while detection timing still fails, because a picture appearing and an identity being read are two different things.

The Startup Program Comparison in Detail

A clean boot disables startup programs so that each one can be compared in turn. The documented pattern is a program that sets itself to a 640×480 compatibility mode at sign-in, dragging the desktop resolution down on every boot. Disable one program, boot, and check. Repeat for each program. Disabling them all at once leaves no way to know which one was responsible.

The Multi-Monitor Branch in Detail

With more than one monitor connected, Windows re-enumerates the displays at boot. If the primary monitor identity swaps, or the enumeration order changes, the saved mode may be applied to the wrong display or abandoned. Removing the second monitor and testing with one display only is the comparison. If the mode is kept with one monitor, the multi-monitor enumeration is the direction to follow.

The Cable and Interface Comparison in Detail

A different cable or a different interface — HDMI to DisplayPort, or the other way — is the comparison for the signal and EDID transmission layer. A change in behaviour after swapping points to that layer. No change excludes the cable. A more expensive cable is not a fix by itself: the cable is only one link in EDID transmission, and Fast Startup, Base video, the driver, and startup programs all have nothing to do with the cable.

Clearing the Saved Display Settings

If the saved display settings themselves are damaged, Device Manager can be used to uninstall the monitor device and then restart, letting the system rebuild the display settings. That is the only settings-clearing step to try at home. Do not edit the registry.

Boundary Cases

These look-alikes belong to different diagnoses:

SituationHow to tell it apartWhere it belongs
Boot screen resolution is low with huge text, but normal once Windows loadsFirmware-stage output mode; normal once Windows loads. Usually normal behaviourA boot-screen resolution diagnosis
The mode drops only after waking from sleep; boots are fineThe trigger is sleep wake, not the bootA wake-from-sleep mode reset diagnosis
The mode drops at the moment a monitor is plugged or unpluggedThe trigger is hot-plug re-handshakingA hot-plug re-handshake diagnosis
The monitor is identified as "Generic PnP Monitor"Identity read wrongly, mode list shrunkA monitor-identity diagnosis
Resolution or refresh rate is permanently locked low, whether sleeping or booting or notThe mode is locked, not reset on every bootA bandwidth or cable mode diagnosis
Black bars or unfilled screen inside a gameGame output layer, not the desktop modeA game output diagnosis
Driver settings such as colour or power mode revert on restartSettings profile layer, not display mode persistenceA driver settings reset diagnosis
The drop happens only inside one game or one programProgram-triggered layerA program-triggered mode diagnosis
Window layout is scrambled after wakingWindow position memory, not the resolution modeA window layout diagnosis

Common Misconceptions

What to Note Down Before a Check-In

Bringing a clear record makes a check-in faster and more accurate. Note the wanted mode and the mode after boot — which one drops, resolution, refresh rate, or both — and whether the wanted mode is listed in settings. Note the monitor model as shown in Settings and Device Manager. Note the result of each of the three boot methods: shutdown then power on, Restart, and a true cold boot. Note whether turning off Fast Startup changed anything, whether switching the monitor on first changed anything, whether Base video was ticked, the driver version and date, and which startup programs were disabled one at a time and with what result. Note whether removing a second monitor or changing the cable or interface changed anything.

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

Every boot drops my resolution or refresh rate. What is actually happening?

The wanted mode can still be selected by hand and works until the next boot, so the mode itself is available — it is the saving of the mode that fails. At boot, Windows has to load the driver, detect the monitor, read the saved mode, and apply it. If any of those steps fails, a conservative fallback mode is used so that a picture appears quickly.

Does a low resolution mean my graphics card is broken?

No. A mode that does not persist can come from Fast Startup, detection timing, the Base video option, driver loading, or a startup program. Graphics card hardware damage is only one possibility among those, and not the most common one. The driver version and the update timeline, the three boot methods, and the startup program comparison separate the layers before any hardware conclusion.

How do I know whether this is a saving problem or a mode-list problem?

Check whether the wanted mode is listed in settings at all. If it is listed and selectable but the boot does not keep it, the persistence layer is the problem. If it is not listed at all, the mode list itself has shrunk — EDID read failure, not enough bandwidth, or the monitor identified wrongly — and that is a different diagnosis.

Does it matter whether only the resolution drops, or only the refresh rate?

Yes. Both dropping together leans towards the whole mode not being saved. Only the refresh rate dropping leans towards a conservative mode being used at boot detection. Only the resolution dropping needs a further look at whether the system has fallen back to a basic display mode. Record which one drops before changing anything.

Shutdown then power on drops the mode, but Restart keeps it. What does that mean?

It points at Fast Startup. When Fast Startup is on, shutting down writes the kernel session into the hibernation file and restores it on the next boot, rather than rebuilding from scratch. Restart rebuilds the kernel and is not affected — so only shutdown-then-power-on dropping the mode while Restart keeps it is itself evidence pointing at Fast Startup.

What is Fast Startup, and why does it affect my display mode?

When Fast Startup is on, shutting down writes the kernel session into the hibernation file and restores it on the next boot, rather than rebuilding from scratch. The display settings saved into that file may be old or damaged, and the boot restores that old mode. Restart is not affected, because a restart rebuilds the kernel — so "shutdown then power on drops the mode, but Restart keeps it" is itself evidence pointing at Fast Startup.

How do I turn off Fast Startup to test it?

Go to Control Panel, Power Options, Choose what the power buttons do, Change settings that are currently unavailable, uncheck "Turn on fast startup", Save changes, then restart and test. If the mode is kept after switching it off, Fast Startup was the cause. If it still drops, Fast Startup is excluded.

What is Base video, and how do I check it?

Base video is a boot option in System Configuration (msconfig), on the Boot tab, that forces the standard VGA display driver instead of the full graphics driver. If it has been ticked — by accident, or by a troubleshooting tool that never switched it back — every boot uses a low-resolution compatibility mode. Check whether it is ticked; if it is, untick that one option only and test again.

Why would the monitor's power state matter at boot?

If the monitor is not fully on when the computer boots — still in standby, or waking more slowly than the PC — the driver may think the monitor is not there at the detection moment, or may receive only part of the EDID, and a conservative mode is used. Switch the monitor fully on first, wait a few seconds, then power on the PC. If the mode is kept with that order, the cause is detection timing.

I set the mode back by hand and it works. Is it fixed?

No. Setting the mode back by hand only changes the mode for that session. It does nothing about the cause that drops it again on the next boot. The fix is finding which layer drops the mode — Fast Startup, detection timing, Base video, the driver, or a startup program — and removing that cause.

The problem started right after a driver update. What do I do?

Note the driver version and date, and match them against when the problem started. If the problem started right after an update, roll back to the previously working version — version choice is judged by the timeline, not by "newest is best". After a clean reinstall, run the baseline comparison again to see whether the reinstall changed anything.

Could a startup program be changing my mode?

Yes. There are documented cases of a startup program setting itself to a 640×480 compatibility mode at sign-in, dragging the desktop resolution down on every boot. Use a clean boot and disable startup programs one at a time, booting after each change, until the mode is kept. Disabling them all at once leaves no way to know which one was responsible.

Why does one monitor keep dropping the mode when two are connected?

With more than one monitor connected, Windows re-enumerates the displays at boot. If the primary monitor identity swaps, or the enumeration order changes, the saved mode may be applied to the wrong display or abandoned. Remove the second monitor and test with one display only: if the mode is kept with one monitor, the multi-monitor enumeration is the direction to follow.

Will a new cable fix it?

Not necessarily. The cable is only one link in EDID transmission. Fast Startup, Base video, the driver, and startup programs all have nothing to do with the cable. Run the comparisons in the diagnosis order first, and only change the cable as one comparison step — if swapping the cable or interface changes the behaviour, the signal layer is the direction; if nothing changes, the cable is excluded.

The boot screen is low resolution, but Windows is fine once it loads. Is that the same problem?

No. The boot screen runs on a firmware output mode, and Windows only runs the driver mode after loading. A low-resolution boot screen with huge text that returns to normal once Windows loads is usually normal behaviour. The problem here is different: the desktop mode itself drops after Windows has loaded, on every boot.

When should I stop and send it in for a check-in?

When the wanted mode is listed but no boot method keeps it, after Fast Startup has been switched off, the monitor-first order has been tried, Base video has been checked, the driver has been cleanly reinstalled, startup programs have been compared one at a time, and a second monitor has been removed and the cable changed without effect. Bring the wanted mode, the mode after boot, the monitor model, the driver version and date, and the result of each step 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.

Related articles

Related services

If you need Chip-level GPU repair, see these service pages: