Fixing PFN SHARE COUNT (0X0000001B) Stop Code on Windows 10 & 11 – Step by Step

by

Fixing PFN SHARE COUNT (0X0000001B) Stop Code on Windows 10 & 11 Step by Step

The PFN SHARE COUNT (0x0000001B) stop code, also known as a Blue Screen of Death (BSOD), is an error that can occur in Windows 10 and 11. This issue typically appears when the system encounters a problem with memory management, often related to how Windows handles physical memory pages. If you’re experiencing this error, your screen may suddenly go blue with technical details before restarting automatically. Below, well explain what causes this error, how to identify it, and provide step-by-step solutions to resolve it.

What Causes the PFN SHARE COUNT (0x0000001B) Error?

The PFN SHARE COUNT error usually occurs due to:

  • Corrupted system files or drivers: Damaged or outdated drivers, particularly those related to memory or hardware, can trigger this error.
  • Faulty RAM (Random Access Memory)
  • Overclocking or BIOS/UEFI settings: If your system is overclocked or has incorrect BIOS settings, it may cause instability in memory management.
  • Malware or virus infections: Some malware can interfere with system processes, leading to BSOD errors.
  • Hardware issues
  • Incompatible software or drivers

The error may appear during normal operation, while gaming, or when running resource-intensive applications. If left unresolved, it can lead to data loss or system instability.

How to Identify the PFN SHARE COUNT (0x00001B) Error

When this error occurs, your screen will display a blue screen with the following details:

*** STOP: 0x0000001B (0x00000000, 0x00000000, 0x00000000, 0x00000000)
PFN_SHARE_COUNT

After the restart, Windows may log the error in the Event Viewer. To check this:

  • Press Win + X and select Event Viewer.
  • Navigate to Windows Logs > System.
  • Look for recent critical errors related to memory or kernel issues.

Step-by-Step Fixes for PFN SHARE COUNT (0x00001B)

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

The System File Checker (SFC) and Deployment Image Servicing and Management (DISM) tools can repair corrupted system files. Follow these steps:

  • Open Command Prompt as Administrator:
    • Press Win + X, then select Terminal (Admin) or Command Prompt (Admin).
  • Run SFC Scan: 
          sfc /scannow

    Wait for the scan to complete. If errors are found, they will be repaired automatically.

  • Run DISM Repair (if SFC doesnt work): 
          DISM /Online /Cleanup-Image /RestoreHealth

    This may take several minutes. Restart your PC afterward.

Method 2: Check and Update Drivers

Outdated or incompatible drivers can cause this error. Update them manually:

  • Open Device Manager:
    • Press Win + X, then select Device Manager.
  • Look for devices with a yellow exclamation mark (e.g., network adapters, storage controllers). Right-click and select Update driver.
  • Use Windows Update:
    • Go to Settings > Windows Update > Check for updates.
    • Install any pending driver or system updates.

Method 3: Run CHKDSK to Check for Disk Errors

If the error is related to disk corruption, run the CHKDSK (Check Disk) tool:

  • Open Command Prompt as Admin (as described above).
  • Run CHKDSK with the following command: 
          chkdsk C: /f /r

    Replace C: with your system drive letter if needed.

  • If prompted, schedule the scan for the next reboot. Restart your PC to complete it.

Method 4: Test and Replace Faulty RAM

If hardware issues are causing the error, test your RAM:

  • Use Windows Memory Diagnostic Tool:
    • Search for Memory diagnostic tool in the Start menu and run it.
    • Select Restart now and check for problems.
  • Check for physical RAM issues: If errors are found, consider replacing faulty RAM sticks or testing them one at a time.

Method 5: Disable Overclocking and Update BIOS

If youve overclocked your CPU or GPU, reset BIOS settings to default:

  • Enter BIOS/UEFI (usually by pressing Del, F2, or F12 during boot).
  • Reset all settings to default and save changes.
  • Update BIOS/UEFI from the manufacturers website if needed.

Method 6: Scan for Malware

Run a full system scan using Windows Defender or third-party antivirus software to rule out malware-related issues.

Preventing Future PFN SHARE COUNT Errors

To minimize the risk of this error recurring:

  • Keep your system and drivers up to date.
  • Avoid overclocking unless necessary, or ensure stability with proper settings.
  • Regularly scan for malware using trusted security software.
  • Monitor system performance and check Event Viewer for early warnings.

FAQ About PFN SHARE COUNT (0x00001B)

  • Is this error hardware or software-related?

    It can be either. RAM, overheating, or driver issues are common causes.

  • Will a clean install fix the issue?

    A clean install of Windows may resolve deep system corruption, but identify and replace faulty hardware if needed.

  • Can I ignore this error if it doesnt happen often?

    No. Even occasional BSODs can indicate underlying issues that may worsen over time.

  • Does this error delete my files?

    Usually not, but back up important data to prevent data loss in case of unexpected crashes.

By following these steps, you should be able to resolve the PFN SHARE COUNT (0x00001B) error and stabilize your system. If the problem persists after trying all methods, consider consulting a professional technician or Microsoft Support for further diagnosis.

Last Updated: December 13, 2025

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

Leave a Comment