How to Fix PFN REFERENCE COUNT (0X0000001C) BSOD on Windows 10 & 11

How to Fix PFN REFERENCE COUNT (0X0000001C) BSOD on Windows 10 & 11

The PFN REFERENCE COUNT (0x0000001C) Blue Screen of Death (BSOD) is a critical error that can suddenly crash your Windows system, often without warning. This error occurs when the Page Frame Number (PFN) reference count in the memory management system becomes corrupted or mismanaged, leading to system instability. If you’re experiencing this issue on Windows 10 or 11, dont worryweve compiled a comprehensive guide with step-by-step solutions to help you resolve it.

What Causes the PFN REFERENCE COUNT (0x0000001C) BSOD?

The PFN REFERENCE COUNT error typically arises due to:

  • Corrupt system files or drivers: Damaged Windows components, such as the kernel or memory-related drivers, can trigger this error.
  • Faulty or outdated device drivers, especially those related to storage (e.g., hard drives, SSDs) or network adapters.
  • Malware or virus infections that interfere with system memory management.
  • Incompatible software or recent Windows updates that introduce instability.
  • Hardware conflicts, such as faulty RAM modules or overclocked components (if applicable).

This error can appear during normal operations, gaming, or while using resource-intensive applications. If left unresolved, it may lead to data loss or further system corruption.

How to Fix PFN REFERENCE COUNT (0x0000001C) BSOD

Follow these methods in order, starting with the simplest and progressing to more advanced solutions:

Method 1: Restart Your PC and Check for Updates

The first step is often the easiest. A simple restart can resolve temporary glitches causing the BSOD.

  • Save any unsaved work and close all applications.
  • Hold down the power button to force a shutdown (if Windows doesnt respond).
  • Wait 30 seconds, then power your PC back on.
  • Check for Windows updates by going to Settings > Update & Security > Windows Update and install any pending updates.

Method 2: Run System File Checker (SFC) and DISM

The System File Checker (SFC) and Deployment Image Servicing and Management (DISM) tools repair corrupted system files that may be causing the error.

Step 1: Run SFC Scan

  • Open Command Prompt as Administrator. Press Win + X, then select Terminal (Admin) or Command Prompt (Admin).
  • Type the following command and press Enter:
    sfc /scannow
  • Wait for the scan to complete (this may take several minutes). Restart your PC afterward.

Step 2: Run DISM Repair

  • In the same elevated Command Prompt, run:
    DISM /Online /Cleanup-Image /RestoreHealth
  • Wait for the process to finish (this can take 1030 minutes). Restart your PC.

Method 3: Run CHKDSK to Check for Disk Errors

If file system corruption is suspected, use CHKDSK to scan and repair disk errors:

  • Open Command Prompt as Administrator.
  • Type the following command (replace C with your system drive if needed):
    chkdsk C: /f /r /x
  • Press Y to confirm, then restart your PC. The scan runs automatically at the next boot.

Method 4: Update or Reinstall Drivers

Outdated or faulty drivers (especially for storage controllers, chipset, or network) can trigger this error.

  • Press Win + X and select Device Manager.
  • Expand categories like Disk drives, Storage controllers, or Network adapters.
  • Right-click any device with a yellow exclamation mark, then choose Update driver. Select Search automatically for drivers.
  • If no updates are found, use the manufacturers website to download the latest drivers (e.g., Intel, NVIDIA, or your motherboard brand).
  • Alternatively, roll back drivers by right-clicking a device and selecting Properties > Driver > Roll Back Driver.

Method 5: Test for RAM Issues

Faulty RAM can cause PFN-related errors. Use Windows built-in tool to test memory:

  • Press Win + R, type mdsched.exe, and press Enter.
  • Select Restart now and check for problems (recommended).
  • The tool will test your RAM. If errors are found, replace the faulty module(s).

Method 6: Uninstall Recent Software or Updates

If the BSOD started after installing new software or a Windows update:

  • Go to Settings > Update & Security > Windows Update > View update history.
  • Uninstall recent updates by selecting them and clicking Uninstall.
  • For third-party software, go to Control Panel > Programs > Uninstall a program, select the recently installed app, and click Uninstall.

Method 7: Check for Malware

Malware can corrupt system files. Run a full scan with:

  • Open Windows Security (search in the Start menu).
  • Go to Virus & threat protection > Quick scan. If threats are found, follow the removal steps.
  • For thorough scanning, use Microsoft Defender Offline Scan under Scan options.

Method 8: Reset or Reinstall Windows (Last Resort)

If all else fails, reset your PC to factory settings:

  • Go to Settings > Update & Security > Recovery.
  • Under Reset this PC, choose Keep my files or Remove everything (back up important data first).
  • Follow the on-screen instructions to complete the reset.

FAQ About PFN REFERENCE COUNT (0x0000001C)

  • Is this error hardware-related?

    It can be, especially if RAM or storage devices are faulty. Test your hardware using tools like MemTest86 for deeper diagnostics.

  • Will a clean install fix it permanently?

    A clean Windows installation (not just reset) may resolve deep-seated issues, but ensure you back up data first.

  • Can I prevent this error in the future?

    Yes! Regularly update drivers, avoid overclocking hardware (if applicable), and scan for malware. Use reliable antivirus software.

  • Why does it happen during gaming or heavy tasks?

    Intensive processes strain memory management, exposing underlying corruption that may only surface under load.

If the issue persists after trying all steps, consult a professional technician to inspect hardware (e.g., RAM, SSD/HDD) or consider manufacturer warranty support if your PC is new.

By following these troubleshooting steps, you should be able to resolve the PFN REFERENCE COUNT BSOD and stabilize your system.

Last Updated: December 13, 2025

Tested on: Windows 10 (22H2) & Windows 11 (23H2)

Leave a Comment