GPU Code 48 in Device Manager: Driver Blocked from Starting? Windows Driver Protection, Memory Integrity & Compatible Driver Diagnosis Guide

Key Takeaway
Code 48 means Windows has blocked the graphics driver from starting because the driver version is on the Windows Driver Protection blocklist, not because its signature failed. This guide explains the blocklist, Memory Integrity, and driver compatibility, and walks through seven diagnostic steps to find a compatible driver — without disabling security protections.
What This Problem Is — and What It Is Not
Open Device Manager, expand Display adapters, and instead of a working graphics card you see a yellow exclamation mark. Open the card's Properties, look at the General tab, and the Device status box reads, in full: "The software for this device has been blocked from starting because it is known to have problems with Windows. Contact the hardware vendor for a new driver. (Code 48)". The display may still work — Windows falls back to its generic driver and the desktop appears — but games stutter or refuse to start, hardware acceleration is gone, and the manufacturer's control panel will not open.
That message is the whole problem this guide covers, and every word of it matters. Read it slowly. It does not say the card is broken. It does not say the driver is unsigned, or corrupt, or missing. It says the software for this device "has been blocked from starting" because it "is known to have problems with Windows". Windows knows this driver version. Windows has decided, in advance, that this version should not be allowed to run. And Windows is refusing to load it — not failing to load it, refusing.
That distinction is the key to the entire diagnosis. Most Device Manager error codes describe something that went wrong during an attempt: the driver tried to start and failed, the device tried to start and stopped, the signature check ran and the signature did not verify. Code 48 describes something different. No attempt to start the driver gets as far as running it. Windows consults a list before loading begins, finds this driver version on it, and declines. The driver may be perfectly signed. Its signature chain may be complete and valid. The file may be intact, unmodified, and exactly as the manufacturer shipped it. None of that matters, because the block is not about the signature. The block is about the version being on a list.
Four conditions must all be true before the steps below apply:
- Device Manager shows the graphics card with a yellow exclamation mark, and the Device status text is the Code 48 message quoted above, or a close paraphrase of it ending in "(Code 48)".
- The card is a discrete or integrated graphics processor whose manufacturer still publishes, or once published, a driver for it — NVIDIA, AMD, or Intel graphics.
- The machine boots into Windows and shows a desktop. If there is no display at all, the problem is a display problem, not a Code 48 problem, and a different guide applies.
- The reader is looking at a driver problem, not a hardware problem that happens to share a symptom. Code 48 itself is never, on its own, evidence that the card is faulty. That is the first misconception, and it is dealt with in full below.
The Exact Words Matter: Copy the Device Status Before Doing Anything Else
The single most useful habit in Device Manager diagnosis is also the simplest: copy down the full Device status text, word for word, together with the code number, before changing anything. The code number is the diagnosis. Two machines can show the same yellow exclamation mark and need completely different fixes, because the code underneath is different. The yellow icon is only a flag that says "something is wrong here". The code says what kind of wrong it is.
That habit matters more than usual with Code 48, because Code 48 belongs to a family of codes that all look alike at a glance and mean different things. Code 52 means Windows could not verify the digital signature of the driver. Code 31 means the driver failed to load. Code 10 means the device could not start. Code 43 means the driver loaded, the device started, and then stopped. Code 38 means the previous driver instance is still in memory. Code 22 means the device has been disabled. Code 19 and Code 39 mean registry damage or a damaged driver. Each code is a different layer, each has its own guide on this site, and the steps for one cannot be transplanted onto another. Code 48 is the blocked-driver code, and this guide is written for it alone.
There is a second reason to write the status down before touching anything: the code can change as the diagnosis proceeds, and a change is itself diagnostic information. If Code 48 becomes Code 31 after a driver change, the blocklist layer has been passed and a different layer has now surfaced. If Code 48 becomes Code 10, the driver is now loading but the device cannot start. If Code 48 disappears entirely and the card works, the step just taken was the one that mattered. None of that can be read afterwards unless the starting code was recorded first. Write it down, with the date, and keep the note. It costs thirty seconds and it is the foundation every later step stands on.
How Windows Decides to Block a Driver: The Protection Database and the Blocklist
To understand Code 48, it helps to understand what happens, in sequence, when Windows loads a graphics driver — and where, in that sequence, Code 48 intervenes.
When Windows starts a device, it goes through a chain. First it identifies the hardware and finds a matching driver package. Then it checks that the driver is signed, that the signature chain is intact, and that the signing certificate is trusted. Then it loads the driver into the kernel, the driver initialises the hardware, and the device reports itself ready. Most driver failures happen somewhere inside that chain: a signature that does not verify, a file that is damaged, a device that will not initialise. Code 48 happens before the chain is even allowed to run.
Windows maintains a database called Windows Driver Protection, distributed through Windows Update. When Microsoft identifies a driver version that is known to have problems with Windows — a version that crashes systems, conflicts with a Windows release, carries a known security vulnerability, or behaves in a way that undermines Windows security — that version is added to the database. The next time Windows Update delivers the protection database to a machine, the machine learns that this driver version is blocked. When the system then tries to start a device using that driver version, it checks the database first. A match means the driver is not loaded at all. The device is given Code 48.
There is a second, related list on Windows 11: the vulnerable-driver blocklist. This list targets drivers with known security vulnerabilities, drivers associated with malware, and drivers that attempt to bypass the Windows security model. It overlaps in purpose with the Windows Driver Protection database — both are lists of driver versions Windows refuses to run — but the vulnerable-driver blocklist is specifically about security: a driver on it is not merely incompatible, it is considered unsafe to load. A graphics driver can land on either list, and from the reader's side the visible result is the same: Code 48, and a driver that Windows will not start.
Three consequences follow from this mechanism, and each one shapes the diagnosis.
First, the block is version-specific, not model-specific. Windows does not block "the NVIDIA driver" or "the AMD driver". It blocks a particular version of a driver for a particular device. A newer version of the same driver, for the same card, may be perfectly acceptable. An older version may also be acceptable, if it was never added to the list. That is why the fix for Code 48 is almost always a different driver version, not a different card — and why the exact driver version currently installed, recorded in Step 1, is the single most important fact in the whole diagnosis.
Second, the block can arrive without the reader doing anything. The protection database is delivered through Windows Update, in the background, like any other update. A machine that worked yesterday can show Code 48 today because the database was updated overnight and the installed driver version was added to it. Nothing was installed, nothing was changed, no setting was touched — and yet the driver that loaded fine yesterday is blocked today. This is the most confusing way Code 48 appears, and it is also the most informative: a Code 48 that appears with no change at all points strongly at the blocklist layer, because nothing else changed. Step 2, the timeline comparison, exists to catch exactly this pattern.
Third, the block is enforced at load time, every time. Reinstalling the same blocked version changes nothing. Rebooting changes nothing. Reinstalling Windows changes nothing in the long run, because Windows Update will deliver the same protection database again and the same driver version will be blocked again. This is why two of the most common instincts — "reinstall the driver" and "reinstall Windows" — both fail against Code 48 when they are done without changing the driver version. Reinstalling the same version reinstalls the same blocked version. The version has to change, to one that is not on the list, or the block stays. That single fact rules out a large amount of wasted effort, and it is worth holding onto through every step that follows.
Code 48 vs Code 52: The Two Codes Readers Confuse Most
Code 48 and Code 52 are the two codes readers most often confuse, and the confusion is understandable: both involve a driver that will not load, both show a yellow exclamation mark, and both are about Windows refusing to trust a driver. But they refuse for opposite reasons, and the fixes are different. Treating a Code 48 as a Code 52 — or the reverse — sends the reader down the wrong path entirely.
Code 52 means Windows could not verify the digital signature of the driver. The signature chain is broken somewhere — the driver is unsigned, the signature is damaged, the certificate has expired or been revoked, or the catalogue file is missing — and Windows reports Code 52. The problem is the signature; the full five-layer chain is explained in the Code 52 guide on this site. The driver might be perfectly good code, but Windows cannot prove it came from who it claims to come from, so it will not load it.
Code 48 means the driver is on a blocklist. The signature may be complete and valid. The certificate chain may be intact. The file hash may match exactly what the manufacturer shipped. Windows is not saying "I cannot verify this driver". Windows is saying "I know this driver, and I will not run it". The problem is the version, not the signature.
The practical difference is sharp. For Code 52, the question is whether the signature chain can be repaired — a properly signed driver from the manufacturer, a correct catalogue file, a certificate that has not expired. For Code 48, the signature is irrelevant, and no amount of signature repair will help, because the signature was never the problem. The question for Code 48 is whether a different driver version exists that is not on the blocklist and is compatible with the card and the Windows version. If such a version exists, installing it resolves the code. If no such version exists — because the manufacturer no longer supports the card on this Windows version — then the honest answer is that the card may no longer be supported, and no setting change can conjure a compatible driver into existence.
There is one more boundary worth stating plainly, because it is where the two codes' worlds touch without overlapping. An older, properly signed driver can still load on a newer Windows version if its signature chain is complete — that is the Code 52 boundary, and it is about signatures. But that same older driver, signature intact, can still be blocked with Code 48 if its version has been added to the protection database. A complete signature is necessary for a driver to load, but it is not sufficient: the driver must also not be on the blocklist. Code 52 tests the first condition. Code 48 tests the second. A driver has to pass both.
| Feature | Code 48 | Code 52 |
|---|---|---|
| Full message theme | Driver blocked from starting; known to have problems with Windows | Windows cannot verify the digital signature of the driver |
| What Windows objects to | The driver version is on a blocklist | The signature verification failed |
| Can the signature be valid? | Yes — often perfectly valid | No — the signature chain is broken somewhere |
| Where the decision comes from | Windows Driver Protection database / vulnerable-driver blocklist, delivered via Windows Update | Signature and certificate verification at load time |
| Typical trigger | Protection database update; Windows feature update; driver version added to a list | Unsigned, damaged, or expired-signature driver; test-signing mode |
| Correct direction of fix | Find a compatible driver version not on the blocklist | Obtain a properly signed driver from the manufacturer |
| What does not help | Reinstalling the same blocked version; reinstalling Windows alone | Any fix aimed at the blocklist |
| Related guide on this site | This guide | The Code 52 guide: signature verification and the five-layer chain |
Memory Integrity, HVCI, and Code 48: What the Security Feature Actually Does
Memory Integrity is the feature most often blamed for Code 48, and the blame is partly deserved — but the relationship is widely misunderstood, and the misunderstanding leads readers to turn off a security feature they should keep on. This section explains what Memory Integrity actually does, how it can produce Code 48, and why turning it off is a diagnostic comparison at most, never a fix.
Memory Integrity is part of Windows Security, under Device security and Core isolation. Its technical name is Hypervisor-protected Code Integrity, or HVCI. Its job is to check that kernel-mode drivers — the drivers that run at the deepest level of the system, with the most privilege — meet modern security requirements before they are allowed to load. A driver that does not meet those requirements is not loaded, and the device it belongs to can report Code 48. Windows lists incompatible drivers in the Core isolation details page, under "Windows Security, Device security, Core isolation details", where Memory Integrity lives. If the graphics driver is listed there as incompatible, that is direct evidence that this layer is involved.
The mechanism is worth understanding because it explains why the problem appears when it does. Memory Integrity is often switched on by a Windows feature update, by a change in the machine's security settings, or on a new machine where it is enabled by default. A driver that loaded happily for years with Memory Integrity off can be blocked the day Memory Integrity is switched on — not because the driver changed, but because the check that now runs against it is stricter than the check that ran before. The driver did not get worse. The bar got higher. This is also why reports exist of Code 48 appearing on older graphics cards, such as Intel HD 4000 graphics, after Memory Integrity was enabled: the old driver predates the security requirements Memory Integrity enforces, and it cannot meet them.
There is a related trigger worth knowing about. Reports exist of Code 48 appearing after Hyper-V is enabled. Hyper-V is the virtualisation platform that underpins Memory Integrity — HVCI runs on top of the hypervisor — so enabling Hyper-V can bring the same stricter checks into play. If Code 48 appeared shortly after Hyper-V was enabled, that timing is a clue, not a coincidence. It is a clue, however — not a repair instruction. The correct response to the clue is to note it in Step 2 and to check the Core isolation details page in Step 3, not to start switching virtualisation features off.
And here is the point that must be stated without any softening: turning off Memory Integrity is not a fix for Code 48. Turning it off removes the check that is blocking the driver, which lets the blocked driver load — but it does not make the driver compatible, supported, or safe. The driver is still the same version Windows considers problematic. The machine is now simply running without the protection that was keeping that driver out. The right direction is the opposite one: find a driver version that is not on the blocklist and that meets the current security requirements, so that Memory Integrity can stay on and the driver can load. A driver that only works with the security feature disabled is a driver that should be replaced, not a driver that has been fixed.
That said, there is one legitimate, narrow use for switching Memory Integrity off: as a diagnostic comparison. If the reader wants to confirm whether Memory Integrity is the layer doing the blocking, they may switch it off once, restart, check whether Code 48 disappears, and then switch it back on immediately. The result is information, not a repair. If Code 48 disappears while Memory Integrity is off and returns when it is switched back on, the diagnosis is confirmed: this layer is involved, and the answer is a compatible driver, not a permanently disabled security feature. If Code 48 stays while Memory Integrity is off, this layer is ruled out, and the search moves on. Either way, Memory Integrity goes back on at the end of the comparison. It is never left off as the solution. This guide repeats that rule wherever it matters, because it is the single most common way readers turn a diagnosable Code 48 into a permanently less secure machine.
Two things this guide will never teach, and the reader should treat any source that teaches them with suspicion. The first is disabling driver signature enforcement as a way around Code 48. Driver signature enforcement is a protection against malicious and unknown drivers being loaded into the kernel. Disabling it removes the barrier that stops any unsigned, unknown-origin driver from loading. It does not fix a blocklist problem — a blocked driver is blocked regardless of signature enforcement — and it leaves the machine exposed. The second is any method that promises to remove a driver from the blocklist, edit the protection database, or bypass the block. There is no supported way to do that, and attempts to do it are exactly the kind of change that should never be made to a machine that is otherwise working. If a source offers either of these as a fix, close it.
There is one more setting in the same neighbourhood that deserves a single sentence, because it appears in some guides as a Code 48 fix and it is not one. Enhanced Sign-in Security is a feature on some business and school machines that imposes additional requirements on drivers; if a driver does not meet those requirements, the system will prevent the device from starting. On a company or school machine, that is a matter for the IT department, not something to change alone. This guide does not expand on it further, because it is an enterprise setting, and changing enterprise security policy from a home diagnosis is never the right move.
Why the Display Still Works When the Driver Is Blocked
Readers often ask a reasonable question: if the graphics driver is blocked, why is there a picture at all? The answer is that Windows has a fallback. When the manufacturer's driver cannot load, Windows runs the display on its generic driver, and Device Manager shows the card as "Microsoft Basic Display Adapter". The generic driver is enough to draw the desktop, open windows, and show a picture. It is not enough to run games properly, to provide hardware acceleration, or to expose the card's real capabilities. It is a stand-in, not a substitute.
That distinction matters for diagnosis. A picture on the screen does not mean the graphics driver loaded. It means some driver loaded — and the one that loaded may be the generic one. The test is the error code, not the picture. If Device Manager shows Code 48 and the card's name has become "Microsoft Basic Display Adapter", the machine is running on the generic driver while the manufacturer's driver sits blocked. The display works, and the graphics card does not. Both facts can be true at once, and both must be read together.
The same logic applies in reverse. If the display works and the card shows its full model name with no error, the driver loaded, and the problem — whatever it is — is not Code 48. The name in Device Manager is the fastest single check in the whole guide: full model name means the manufacturer's driver is in play; "Microsoft Basic Display Adapter" means Windows is running on the generic driver and the manufacturer's driver is not loaded.
The Five Suspicion Layers
A Code 48 can come from five layers, and they must be kept separate. Mixing them together is how a blocklist problem gets treated with a system file repair, or a version mismatch gets treated by switching off a security feature, and how the real cause survives because the wrong layer was treated. The five layers below are ordered from the most Code 48-specific to the most general, and each one has its own deciding test.
Layer One: The Driver Blocklist Layer — the Version Is on a List
The first layer is the blocklist itself. The installed driver version is listed in the Windows Driver Protection database, delivered through Windows Update, or in the Windows 11 vulnerable-driver blocklist. Windows recognises this version as one known to have problems, and actively refuses to load it. The signature can be complete and valid; the problem is not the signature. The problem is the version.
The clearest sign of this layer is timing. Code 48 appears after a Windows Update, or after a Windows feature update, with no driver change by the reader. The driver version that loaded yesterday is the same version that is blocked today — and the only thing that changed in between was the protection database. A second sign is specificity: the same driver version is blocked on more than one machine, or the manufacturer's own support pages note that this version has been superseded. A third sign is the absence of any other explanation: the Core isolation details page does not list the driver as incompatible, the driver is the correct one for the exact model, and yet Code 48 persists. When every other layer has been checked and cleared, and the version is the only thing left, the version is the answer.
The fix for this layer is a different driver version — one that is not on the blocklist, published by the manufacturer for this exact card model and this Windows version. Not a newer version from an unofficial source. Not a version for a different model. A version from the manufacturer's own website, matched to the exact model and the exact Windows version and build. If the manufacturer has published no such version, that is itself an answer, and it is dealt with in Step 7.
Layer Two: The Windows Version and Driver Pairing Layer — the Wrong Pair
The second layer is pairing: the driver and the current Windows version do not match. The most common form is a feature update. A driver that was written for an older Windows version may not be compatible with the new one, and a feature update can turn a working pairing into a broken one overnight. The reader did nothing wrong. The pairing simply expired.
The other common form is the end of support. A manufacturer may stop publishing new drivers for an older card. The last driver it published may have been written for an older Windows version. On the current Windows version, that driver may be blocked, or it may be incompatible in a way that shows up as Code 48. The card still works as hardware. The pairing is what has ended. This is the boundary case that matters most for older cards, and it is the one where the honest answer may be that no compatible driver exists for this Windows version. That answer is not a failure of diagnosis. It is the diagnosis, and it is far better than a string of setting changes that cannot create a driver that does not exist.
The deciding evidence for this layer is the manufacturer's own support list. Before guessing from the card's age, check the official list: does the manufacturer still list this card as supported on this Windows version, and does it publish a driver for it? A card's age is not evidence. The support list is. If the list says the card is supported and a driver exists, the pairing layer is not the problem, and the search moves on. If the list says support has ended, the pairing layer is the answer, and the remaining question is what to do about a card whose driver support has ended — which is a decision about the machine, not a setting to change.
Layer Three: The Memory Integrity and Code Integrity Layer — the Security Check
The third layer is the security check described in full above: Memory Integrity, or HVCI, checks whether kernel-mode drivers meet modern security requirements, and a driver that does not meet them is not loaded. The driver is listed as incompatible in the Core isolation details page. Hyper-V being enabled can bring the same checks into play.
The deciding evidence for this layer is the Core isolation details page itself. It is a read-only check: open Windows Security, go to Device security, open Core isolation details, and look at whether Memory Integrity lists this driver as incompatible. If it does, this layer is involved. If it does not, this layer's suspicion falls. Note what this step is not: it is not an instruction to switch Memory Integrity off. It is an instruction to look. Looking is free, reversible, and informative. Switching the feature off is a diagnostic comparison only, done once, with the feature switched back on immediately afterwards, as described above.
A subtlety worth noting: this layer and the blocklist layer can overlap. A driver can be both on the blocklist and incompatible with Memory Integrity. In that case, fixing one does not fix the other. A new driver version has to clear both: not on the blocklist, and meeting the security requirements. That is another reason the fix is a different, current driver version from the manufacturer, rather than a setting change. A current driver is the only single change that can clear both layers at once.
Layer Four: The Driver Source and Installation Layer — the Wrong Package or a Leftover
The fourth layer is the source and the installation: where the driver came from, and whether it was installed cleanly. Three distinct faults live here.
First, Windows Update can deliver a driver version that is blocked or incompatible. Windows Update's job is to keep drivers current, but the version it delivers is not always the version the manufacturer currently recommends for this exact card and Windows build. After a Windows Update, the driver version can change without the reader choosing it, and the new version can be the one that is blocked. This is the scenario behind the guidance to check the driver version before and after an update, and to pause automatic driver installation before installing a driver by hand — so that Windows Update does not replace the hand-installed driver with the blocked version again. That guidance is worth following here: install the right driver, then stop Windows from immediately replacing it with the wrong one.
Second, the wrong driver package can be installed. There is no single "Code 48 driver". Graphics cards, network cards, and printers can all report Code 48, because the code describes the block, not the device. Within graphics cards, a driver package for the wrong model, or for the wrong Windows version, can produce Code 48 just as surely as a blocked version can. The driver must match the exact model and the exact Windows version and build. A package that is close is not close enough.
Third, leftover files from an old driver can prevent a new driver from installing cleanly. A previous driver that was not fully removed can leave files and registry entries behind, and the new installation can fail or install incompletely. The clean-install tool for this is Display Driver Uninstaller, run in Safe Mode, and the full procedure belongs to its own guide. This guide says only this: a clean removal followed by a clean installation is the correct form of "reinstall the driver", and a reinstall over the top of an old installation is not the same thing. If the reader has reinstalled the driver several times over the top and Code 48 persists, the installation layer — not the driver version — may be the part that has never actually been tested.
Layer Five: The System Files and Hardware Layer — the Last Resort
The fifth layer is the most general: damaged system files, and, last of all, hardware itself. System file damage is checked with the System File Checker, `sfc /scannow`, which is a general Windows step, not a graphics-specific one. It scans protected system files and repairs those that are damaged. If it finds and repairs damage, restart and check whether Code 48 is still there. If it finds nothing, that proves nothing about the system layer in general — it proves only that the files it checks are intact — and the diagnosis continues. A clean result from this check does not clear the layer. It only narrows it.
Hardware is the last thing to consider, and it must be said plainly: Code 48 is not a hardware verdict. A faulty card does not produce Code 48 by itself, because Code 48 is a decision Windows makes about a driver version before the driver ever runs. A card can be completely healthy and still show Code 48, because the block is about the driver, not the card. Hardware only enters the picture when every driver layer has been tested — a compatible, current driver from the manufacturer, cleanly installed, with Memory Integrity on, on a Windows version the manufacturer supports — and Code 48 still persists, or when a cross-test with a known-good card points at the hardware. Until that point, no conclusion about the hardware can be drawn, and none should be.
| Layer | What is wrong | Deciding evidence | What resolves it |
|---|---|---|---|
| 1. Driver blocklist | Driver version is on the Windows Driver Protection database or vulnerable-driver blocklist | Code 48 appears after a Windows Update with no driver change; version is the only suspect left | A different manufacturer driver version not on the list |
| 2. Windows version / driver pairing | Driver and current Windows version do not match; support may have ended | Manufacturer support list shows no driver for this card on this Windows version | A supported pairing, or an honest assessment that support has ended |
| 3. Memory Integrity / code integrity | Driver does not meet HVCI security requirements | Driver listed as incompatible in Core isolation details | A current driver that meets the requirements; Memory Integrity stays on |
| 4. Driver source / installation | Wrong package, Windows Update replacement, or leftover files | Version changed after an update; wrong model package; repeated over-the-top reinstalls | Correct package, clean install, pause automatic driver replacement |
| 5. System files / hardware | Damaged system files; hardware fault only as a last resort | `sfc /scannow` findings; cross-test results | System file repair; hardware assessment only after all driver layers are cleared |
The Seven Diagnostic Steps
The seven steps below are ordered so that each one tests one layer, and so that no step destroys the evidence a later step needs. Work through them in order, one variable at a time, and write down the result of each step before moving on. Changing two things at once and seeing Code 48 disappear leaves the reader not knowing which change mattered — and not knowing what to do when the problem returns.
Step 1: Copy Down the Full Device Status, Driver Provider, Version, and Date
Open Device Manager, expand Display adapters, right-click the graphics card, and open Properties. On the General tab, copy the full Device status text, word for word, including the code number. Then open the Driver tab and note the driver provider, the driver version, and the driver date. Write all of it down, with today's date.
This step proves that the problem has been narrowed to the blocklist layer: the code is 48, and the message says the driver has been blocked. It proves nothing about which list, or which reason — that is what the steps below are for. But without the version, nothing else can be checked: the block is version-specific, so the version is the fact every later step refers back to. A note that says "Code 48, driver version 31.0.15.1234, dated March 2026, provider NVIDIA" is a diagnosis in progress. A note that says "Code 48" is a starting point with no direction.
While in Device Manager, note one more thing: the name shown for the card. If it reads "Microsoft Basic Display Adapter", Windows is running on its generic driver, not the manufacturer's driver, and the manufacturer's driver is the one that is blocked. That single observation separates a blocked-driver problem from a problem where the manufacturer's driver is loading but misbehaving — a distinction the Code 43 guide covers, and one that does not apply here.
Step 2: Match the Timeline — What Changed Just Before Code 48 Appeared?
Ask when Code 48 first appeared, and what changed immediately before it. The five changes that matter are: a Windows feature update, a driver update, Memory Integrity being switched on, Hyper-V being enabled, or the card being changed. Each one points at a different layer.
If Code 48 appeared right after a Windows feature update, the pairing layer and the blocklist layer are the leading suspects: the new Windows version may not match the old driver, or the update may have delivered a new protection database that lists the installed version. If it appeared right after a driver update, the new version itself may be the blocked one, or the wrong package may have been installed — and the previous version, which worked, is the most useful fact in the whole diagnosis, because it is a version known to load. If it appeared after Memory Integrity was switched on, or after Hyper-V was enabled, the security-check layer is the leading suspect, and Step 3 will confirm or rule it out. If it appeared after the card was changed, the driver package may be for the wrong model, and Step 5 will catch it.
If Code 48 appeared with no change at all — no update, no new driver, no setting touched, no hardware swapped — that is itself an answer. The most likely cause is a protection database update delivered silently through Windows Update: the database changed, the driver did not, and the version that loaded yesterday is blocked today. That pattern points directly at the blocklist layer, and it is the reason the timeline question is asked before any driver is touched. A driver that has not changed cannot be the thing that changed; something else changed around it.
Write the timeline down next to the Step 1 note. "Code 48 appeared the morning after the Windows feature update" is evidence. "It just stopped working" is not, and it will be forgotten by the time Step 5 is reached.
Step 3: Read-Only Check of the Core Isolation Details Page
Open Windows Security, go to Device security, and open Core isolation details. Look at the Memory Integrity section and at whether any driver is listed there as incompatible. This step is read-only: it teaches the reader how to look, not how to switch anything off.
If the graphics driver is listed as incompatible, the third layer is involved: Memory Integrity is refusing a driver that does not meet its requirements. That is useful information, and it narrows the search. It does not change the direction of the fix. The fix is still a compatible driver version — one that meets the requirements — not a disabled security feature.
If the graphics driver is not listed, the third layer's suspicion falls. Memory Integrity may still be involved in a way the list does not show, but the direct evidence is absent, and the search moves on to the driver version itself.
One optional comparison belongs here, and only here, and it must be done exactly as described. If the reader wants to confirm whether Memory Integrity is the layer doing the blocking, they may switch Memory Integrity off once, restart, check whether Code 48 disappears, and then switch Memory Integrity back on immediately. The result is information: if Code 48 disappears while Memory Integrity is off and returns when it is switched back on, this layer is confirmed. If Code 48 stays while Memory Integrity is off, this layer is ruled out. Either way, Memory Integrity goes back on at the end of the comparison. It is never left off as the solution, and it is never presented as one. A driver that only loads with a security feature disabled is a driver that should be replaced.
Step 4: Check Windows Update — and Compare the Driver Version Before and After
Open Settings, go to Windows Update, and check for updates. Microsoft's own guidance for Code 48 starts here: check for updates, because an update may deliver a newer driver, or a newer protection database, that changes the situation. Note the driver version before the update and after it. Two questions must be answered separately: did the update change the driver version, and did the update change the Code 48 status?
That separation matters, because an update can change either one without the other. An update may deliver a new driver version that is not blocked, and Code 48 disappears — in which case the update was the fix, and the version change is the reason. An update may deliver a new protection database that adds the installed version to the blocklist, and Code 48 appears — in which case the update is the trigger, not the fix, and the answer is a different driver version. And an update may change nothing at all, in which case the blocklist layer is neither confirmed nor ruled out by this step, and the search continues.
What this step does not prove is also worth stating. An update delivers signed drivers. A Code 48 on a driver delivered by Windows Update does not mean the update delivered the wrong driver, or a broken driver. It means the version delivered is one the protection database lists. The signature is valid. The version is blocked. Those are two different statements, and confusing them is how readers end up blaming the update for a decision the protection database made.
If an update does deliver a new driver version, write it down next to the Step 1 version before doing anything else. The version history — what was installed, when it changed, and what the code did after each change — is the evidence the later steps are built on.
Step 5: Match the Exact Model and Windows Version on the Manufacturer's Website, Then Cleanly Install
Go to the graphics card manufacturer's own website — NVIDIA, AMD, or Intel — and find the driver for the exact card model and the exact Windows version and build. Not a similar model. Not the same series. The exact model, and the exact Windows version. There is no single "Code 48 driver": graphics cards, network cards, and printers can all report Code 48, and within graphics cards, a package for the wrong model can produce Code 48 just as surely as a blocked version. The driver must match the model and the Windows version, or the step has not been performed.
Before installing, stop Windows from immediately replacing the hand-installed driver with the version Windows Update prefers. Windows Update can deliver a driver version that is blocked or incompatible, and if it replaces the correct driver straight after installation, the reader will conclude — wrongly — that the correct driver did not work. Pause automatic driver installation first, install the manufacturer's driver second, and check the result third. That order exists because the failure mode it prevents is a real one.
Install cleanly. A clean installation means removing the old driver fully first, in Safe Mode, with Display Driver Uninstaller, and then installing the manufacturer's driver. The full DDU procedure belongs to its own guide; this guide says only that a clean removal followed by a clean installation is the correct form of "reinstall the driver", and that installing a new driver over the top of an old one is not the same thing. If the reader has already reinstalled the driver several times over the top and Code 48 persists, the installation itself has never actually been tested. A note about the installation method belongs next to the version note: "clean install, Safe Mode, DDU, then manufacturer driver version X" is a test. "Reinstalled the driver" is not specific enough to be one.
If Code 48 disappears after the clean install, the first or fourth layer is confirmed: the version was the problem, or the installation was. If Code 48 persists with the correct, current, cleanly installed driver, move to Step 6. The driver version is now known-good, the installation is known-clean, and the remaining suspects are narrower than they were.
Step 6: Run the System File Checker
Run `sfc /scannow` from an elevated command prompt. This is a general Windows step, not a graphics-specific one: it scans protected system files and repairs those that are damaged. Let it finish, restart the machine, and check whether Code 48 is still there.
This step's result must be read carefully, because it is easy to over-read in both directions. If the checker finds and repairs damaged files and Code 48 disappears, the system-files layer was involved, and the repair was the fix. If the checker finds nothing, that proves only that the files it checks are intact. It does not prove the system layer is clear in general, and it does not prove the hardware is healthy. A clean result narrows the field; it does not close the case. And if the checker finds damage but Code 48 persists after repair, the damage was real but it was not the cause of Code 48 — the blocklist layer is still the answer, and the search returns to the driver version.
The System File Checker belongs at this point in the order, not earlier, for a reason. It is a general step, and general steps are worth doing only after the specific steps have been tried. Running it first, before the version has been checked, wastes the one thing the reader cannot get back: the evidence of which layer actually mattered. Run it sixth, read it narrowly, and move on.
Step 7: Cross-Test, and Know the Stop Line
The last step is a cross-test, and it is the step that separates a driver problem from a machine problem and from a hardware problem. Either test the same card in a different Windows computer, installing the same official driver there, or test a different, known-good card in this computer. One variable changes. Everything else stays the same.
If the same official driver installs on the other computer with the same card and there is no Code 48, the problem follows this machine, not the driver or the card: the block is specific to this machine's Windows version, its protection database state, or its security settings. If the other computer also shows Code 48 with the same driver, the problem follows the driver package or the model's support: the version is blocked wherever it is installed, or the model is no longer supported on this Windows version. If a different, known-good card works in this computer with no Code 48, the machine's driver layers are healthy and the problem follows the original card's driver pairing. Each outcome points somewhere different, and each one is worth writing down, because it is the answer the next person to look at the machine will need.
The stop line is this: if the manufacturer confirms there is no compatible driver for this card on this Windows version, stop. Do not teach yourself around the block. Do not disable driver signature enforcement. Do not leave Memory Integrity off. Do not look for a way to edit the protection database or remove the driver from the blocklist. There is no supported way to do any of those things, and each one trades a working display for a less secure machine. The honest outcome is that the card's driver support has ended on this Windows version, and the decision that follows is about the machine — whether to keep the card on an older Windows version it is supported on, or to replace the card — not about a setting that can conjure a driver that does not exist.
Bring the machine in at that point, with the notes from Steps 1 to 7: the full Code 48 message, the driver provider, version, and date, the timeline, the Core isolation details result, the Windows Update before-and-after versions, the clean-install version and method, the System File Checker result, and the cross-test outcome. Inspection takes place at Room 1209, Dali Plaza, Shek Mun. You can call 2186 8010, or reach the shop on WhatsApp at 6558 6806. Inspection is charged at the site's published three-tier fees of HK$400–2,800, quoted after inspection. There is no home-visit service and no Mong Kok shop; inspection is carried out in the shop.
| Step | What to do | What it proves | What it does not prove |
|---|---|---|---|
| 1. Copy the status and driver details | Device Manager: full status text, provider, version, date | The problem is narrowed to the blocklist layer; the version is recorded | Which list, or which reason — that comes later |
| 2. Match the timeline | What changed just before Code 48 appeared? | Whether an update, a driver change, or a security setting is the trigger | The cause, on its own — timing is a clue, not a verdict |
| 3. Read the Core isolation details | Windows Security, Device security, Core isolation details — look only | Whether Memory Integrity lists this driver as incompatible | Nothing about the blocklist; looking is not switching off |
| 4. Check Windows Update | Check for updates; note the driver version before and after | Whether an update changed the version or the code | That an update delivered the wrong driver — a blocked version is still signed |
| 5. Cleanly install the manufacturer's driver | Exact model and Windows version; pause automatic driver replacement; clean install in Safe Mode | Whether a different, correct version clears the code | Anything, if the wrong package was installed |
| 6. Run the System File Checker | `sfc /scannow`, restart, re-check Code 48 | Whether damaged system files were involved | That the system layer is clear if nothing is found |
| 7. Cross-test and stop | Same card in another machine, or a known-good card in this one | Whether the problem follows the machine, the driver, or the card | Nothing beyond the test that was actually run |
Six Common Misconceptions
Misconception 1: Code 48 means the graphics card is broken
No. Code 48 is a driver trust and blocklist problem, not a hardware verdict. A driver version on the blocklist, or a driver that does not match the Windows version, will produce Code 48 on a card that is completely healthy. The card itself may be entirely normal. Hardware is the last layer to consider, and only after a compatible, current, cleanly installed driver has been tested with Memory Integrity on, on a Windows version the manufacturer supports. A Code 48 on its own is never evidence that the card is faulty, and it should never be read as a reason to replace the card.
Misconception 2: Turning off Memory Integrity fixes Code 48
No. Turning off Memory Integrity removes the check that blocks the driver, which lets the blocked driver load — but it does not make the driver compatible, supported, or safe. The driver is still the same version Windows considers problematic. The machine is now simply running without the protection that was keeping that driver out. The correct direction is to find a driver version that is not on the blocklist and that meets the current security requirements, so that Memory Integrity can stay on and the driver can load. Turning Memory Integrity off is, at most, a diagnostic comparison: switch it off once, confirm whether the code disappears, and switch it back on immediately. It is never the fix, and it is never left off as the solution.
Misconception 3: Disabling driver signature enforcement will solve it
No, and this must never be taught as a fix. Disabling driver signature enforcement removes the barrier that stops unsigned, unknown-origin drivers from loading into the kernel. After that, any unsigned driver can load. It does not fix a blocklist problem — a blocked driver is blocked regardless of signature enforcement — and it leaves the machine exposed to malicious drivers. A source that offers this as a Code 48 fix is offering a security downgrade, not a repair.
Misconception 4: Any graphics driver will do; the exact model does not matter
No. There is no single "Code 48 driver". Graphics cards, network cards, and printers can all report Code 48, because the code describes the block, not the device. Within graphics cards, the driver must match the exact model and the exact Windows version and build. A package for a different model, or for a different Windows version, can produce Code 48 just as surely as a blocked version. A driver that is close is not close enough. Check the manufacturer's own support list for the exact model before installing anything.
Misconception 5: Reinstalling Windows will definitely fix Code 48
No. Reinstalling Windows resets the driver and the system-files layers, but it does not change the driver version, and it does not change the protection database. After a reinstall, Windows Update will deliver the same protection database again, and the same driver version will be blocked again. The problem returns, because the thing that caused it — the version being on the list — was never addressed. Reinstalling Windows is a large, destructive step that fixes a Code 48 only when the cause was damaged system files, and Step 6 tests that far more cheaply. If the cause is the blocklist, a reinstall is wasted effort.
Misconception 6: Code 48 and Code 52 are the same thing
No. Code 52 is a signature verification failure at load time: the signature chain is broken somewhere, and Windows cannot prove the driver came from who it claims to come from. Code 48 is a blocklist refusal: the driver is listed as known to have problems with Windows, Windows actively refuses to load it, and the signature can be perfectly valid. The starting points are different, the checks are different, and the fixes are different. The two codes' procedures cannot be swapped. Code 52 is covered by its own guide on this site, which explains the five-layer signature chain in full.
Boundaries: Problems That Look Similar but Are Not Code 48
Not every yellow exclamation mark in Device Manager is Code 48, and not every driver that will not load is blocked. The codes below are the ones most often confused with it, and each one belongs to its own guide. If the Device status shows one of these codes instead, follow that code's guide, not this one.
Code 52 is a signature verification failure. Code 31 is a driver load failure, with broad causes. Code 10 means the device could not start. Code 43 means the driver loaded, the device started, and then stopped during operation — the starting point is different from Code 48, where loading is refused from the outset. Code 38 means the previous driver instance is still in memory, and its only official remedy is a restart; it is a timing problem, not a blocklist problem. Code 22 means the device has been disabled, and it shows a downward arrow rather than a yellow exclamation mark. Code 19 and Code 39 mean registry damage or a damaged driver.
Two more boundaries deserve a sentence each. The first is the old card on a new Windows version: the manufacturer may no longer sign new drivers for an old card, and an older, properly signed driver whose chain is complete can still load — that is the Code 52 boundary, about signatures. Code 48 is a different matter: a driver on the blocklist is refused even when its signature is complete. Check the manufacturer's official support list rather than guessing from the card's age. The second is test-signing mode: test-signing mode is a Code 52 matter, not a Code 48 matter, and the two should not be mixed together.
Finally, a Code 48 with a picture on the screen is still a Code 48. The system is running on the Microsoft Basic Display Adapter, the generic driver, which is enough to draw the desktop and nothing more. A picture does not mean the graphics driver loaded. The error code is the test, not the picture.
When to Stop and Bring the Machine In
Stop when all seven steps have been worked through, one variable at a time, and Code 48 still persists. Stop sooner if the card disappears from Device Manager, if the display goes black, if the machine crashes, or if any step involves deleting system files or registry entries. Stop, above all, at the point where the manufacturer confirms there is no compatible driver for this card on this Windows version — at that point the diagnosis is complete, and the remaining decision is about the machine, not about a setting.
Bring the machine in with the notes from every step: the full Code 48 message, the driver provider, version, and date, the timeline of what changed, the Core isolation details result, the Windows Update before-and-after versions, the clean-install version and method, the System File Checker result, and the cross-test outcome. In-store inspection takes place at Room 1209, Dali Plaza, Shek Mun. You can call 2186 8010, or reach the shop on WhatsApp at 6558 6806. Inspection is charged at the site's published three-tier fees of HK$400–2,800, quoted after inspection. There is no home-visit service and no Mong Kok shop; inspection is carried out in the shop.
A diagnosis that ends at the stop line is not a failed diagnosis. A note that says "Code 48, driver version X, appeared the morning after the Windows feature update; Core isolation details does not list the driver; clean install of manufacturer driver version Y in Safe Mode, Code 48 persists; same driver on a second machine, Code 48 persists; manufacturer support list shows no driver for this card on this Windows version" is a precise description of where the fault lives, and it is exactly what an in-store inspection needs to start from the right place instead of from the beginning.
FAQ
Q1: Does Code 48 mean my graphics card is broken?
No. Code 48 is a driver trust and blocklist problem, not a hardware verdict. A driver version on the blocklist, or a driver that does not match the Windows version, will produce Code 48 on a card that is completely healthy. Hardware is the last layer to consider, and only after a compatible, current, cleanly installed driver has been tested with Memory Integrity on, on a Windows version the manufacturer supports. A Code 48 on its own is never evidence that the card is faulty.
Q2: What is the difference between Code 48 and Code 52?
Code 52 means Windows could not verify the digital signature of the driver — the signature chain is broken somewhere. Code 48 means the driver is on a blocklist: Windows actively refuses to load it because the version is known to have problems with Windows, and the signature can be perfectly valid. The starting points are different, the checks are different, and the fixes are different. Code 52 is covered by its own guide on this site, which explains the five-layer signature chain.
Q3: Will turning off Memory Integrity fix Code 48?
No. Turning it off removes the check that blocks the driver, which lets the blocked driver load — but it does not make the driver compatible, supported, or safe. The correct direction is to find a driver version that is not on the blocklist and that meets the current security requirements, so Memory Integrity can stay on. Turning Memory Integrity off is, at most, a diagnostic comparison: switch it off once, confirm whether the code disappears, and switch it back on immediately.
Q4: Can I disable driver signature enforcement to get around Code 48?
No, and this should never be done as a fix. Disabling driver signature enforcement removes the barrier that stops unsigned, unknown-origin drivers from loading into the kernel. It does not fix a blocklist problem — a blocked driver is blocked regardless of signature enforcement — and it leaves the machine exposed to malicious drivers. If a source offers this as a Code 48 fix, close it.
Q5: Will installing the latest driver always fix Code 48 — and what if Code 48 appeared right after Windows Update?
No. The latest driver only helps if it is a version that is not on the blocklist, matched to the exact card model and the exact Windows version, and installed cleanly. A driver for the wrong model, a version that is itself blocked, an install over the top of leftover files, or a Windows Update replacement straight after installation can all leave Code 48 in place. The version, the match, and the installation method all have to be right, and Step 5 tests all three.
The same applies after Windows Update: the driver delivered by the update is itself signed, and Code 48 appearing after an update points at a protection-database update, with the installed version added to the blocklist — not at the update delivering the wrong driver. Compare the driver version in use before the update with the version after it; the two answers together show whether it was a list update or a version change.
Q6: How can I tell whether my driver is on the blocklist?
There is no public interface that lists, version by version, which drivers are blocked. The answer has to come from a set of indirect evidence: the timeline (Code 48 appearing with no change points at a list update), the manufacturer's support list (whether a newer version exists for this model), the read-only Core isolation details check (whether Memory Integrity lists this driver as incompatible), and the cross-test (the same driver showing Code 48 on a second machine means the problem follows the driver package). Only when several pieces of evidence point at the same layer can the conclusion be drawn.
Q7: Does the exact graphics card model matter, or will any driver for the same brand work?
The exact model matters. There is no single "Code 48 driver": graphics cards, network cards, and printers can all report Code 48, and within graphics cards a package for the wrong model can produce Code 48 just as surely as a blocked version. The driver must match the exact model and the exact Windows version and build. Check the manufacturer's own support list for the exact model before installing anything.
Q8: Will reinstalling Windows fix Code 48?
No, not on its own. Reinstalling Windows resets the driver and system-files layers, but it does not change the driver version, and Windows Update will deliver the same protection database again after the reinstall. The same driver version will be blocked again. A reinstall only helps when the cause was damaged system files, and Step 6 tests that far more cheaply with the System File Checker.
Q9: Device Manager shows "Microsoft Basic Display Adapter", or Code 48 changed to Code 31, Code 10, or Code 43. What does that mean?
It means Windows is running on its generic driver, not the manufacturer's driver. The generic driver is enough to draw the desktop, but it provides no hardware acceleration and none of the card's real capabilities. A picture on the screen does not mean the graphics driver loaded. Check the error code: if it is Code 48, the manufacturer's driver is the one that is blocked, and the steps in this guide apply.
It means the blocklist layer has been passed and a different layer has surfaced. Code 31 is a driver load failure, Code 10 means the device could not start, and Code 43 means the driver loaded, the device started, and then stopped during operation. A code change is diagnostic information in its own right: write down the new code, with the step that produced it, and follow the guide for the new code. Do not keep applying the Code 48 steps to a problem that is no longer a Code 48.
Q10: When should I stop trying things myself and bring the machine in for inspection?
Stop when all seven steps have been worked through, one variable at a time, and Code 48 still persists; or when the manufacturer confirms there is no compatible driver for this card on this Windows version; or before any step that involves deleting system files or registry entries, disabling driver signature enforcement, or leaving Memory Integrity off. Bring your notes: the full Code 48 message, the driver provider, version, and date, the timeline, the Core isolation details result, the Windows Update before-and-after versions, the clean-install version and method, the System File Checker result, and the cross-test outcome. In-store inspection is at Room 1209, Dali Plaza, Shek Mun, charged at the site's published three-tier fees of HK$400–2,800, quoted after inspection. You can call 2186 8010 or WhatsApp 6558 6806.