Skip to content
PCTestHub

PFN_LIST_CORRUPT (0x4E) blue screen: what it means and how to fix it

Damaged internal memory list. Below you will find the most common causes and the steps to fix it, in order. To look up another code, use the search box.

Blue screenPFN_LIST_CORRUPT · 0x0000004E

Damaged internal memory list

The list Windows uses to keep track of physical memory was damaged. Microsoft usually attributes it to a driver that mishandles memory; faulty RAM can also cause it.

Why it happens

  • A faulty driver.
  • Failing RAM.
  • Drive errors.

How to fix it

  1. Check whether the blue screen says «What failed:» followed by a file ending in .sys: that is the driver that caused the error. Search for that name to find out which device it belongs to (for example, nvlddmkm.sys is the NVIDIA graphics driver) and update or reinstall that driver.
  2. Update the graphics, chipset, network and storage drivers from the support page of your PC or laptop maker. If the problem started after updating one, roll it back: Device Manager › right-click the device › Properties › Driver › Roll Back Driver.
  3. Test the RAM: press Windows + R, type mdsched and choose «Restart now and check for problems». If you have two sticks, also try with one at a time.
  4. Check the drive: in Command Prompt as administrator run chkdsk C: /f and accept checking it on the next restart. If the drive is old, makes noises or shows errors, back up your files as soon as possible.
  5. Repair Windows files: open Command Prompt as administrator (search for «cmd», right-click › Run as administrator) and run DISM /Online /Cleanup-Image /RestoreHealth and then sfc /scannow. Restart when it finishes.

Meaning based on Microsoft's official documentation. The steps are general guidance: if you are not sure, ask a technician for help.

How to find the code of a blue screen

The error screen shows the code on the «Stop code» line (for example CRITICAL_PROCESS_DIED) and sometimes «What failed» with the file that caused it (for example nvlddmkm.sys). In recent Windows 11 versions that screen is black instead of blue, but the codes are the same.

If the computer restarts before you can read it, the code is saved: press Windows + R, type eventvwr and go to Windows Logs › System. Look for an event with source BugCheck: it shows the code in hexadecimal (for example 0x0000007e), which you can also type in the search box. To stop Windows from restarting by itself so you can read the screen, go to Advanced system settings › Startup and Recovery › Settings and uncheck «Automatically restart».

What to do with any blue screen

This works for any code, including the ones without their own explanation. These are Microsoft's general steps, in the order worth trying them:

  1. Write down the code and the file shown in «What failed», if any: they tell you what failed.
  2. Think about what changed before it started (a program, a driver, an update or a part) and undo it. System Restore (rstrui) goes back to an earlier point without touching your documents.
  3. Install Windows updates and the drivers from your PC maker's website; if the problem started with a new driver, roll back to the previous one.
  4. Update the BIOS from the maker's website, with the charger connected.
  5. Test the hardware: memory with mdsched and the drive with chkdsk C: /f. If you raised speeds (overclock or XMP), go back to default values.
  6. Scan for malware with Windows Security (Microsoft Defender Offline scan).
  7. Free up space: Microsoft recommends 10% to 15% of the drive.
  8. Repair Windows with DISM /Online /Cleanup-Image /RestoreHealth and sfc /scannow in Command Prompt as administrator.

If Windows does not start, the Recovery Environment appears after two or three failed starts: from Troubleshoot › Advanced options you can use Startup Repair, System Restore, Uninstall Updates or enter Safe Mode.

Most common blue screens

Windows Update errors

Activation errors

Windows startup errors

Errors when opening programs

Meanings come from Microsoft's official documentation (bug check code reference and the page of each error), checked on November 17, 2026. The texts and steps are our own. See all codes → En español