What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Error 0x0000001B is Windows’ PFN_SHARE_COUNT stop code, a kernel-level blue screen. The number identifies the type of failure, not the part that failed: a third-party driver, firmware, RAM, storage, or recently changed hardware can all be involved. Start with reversible checks, then use a memory dump or hardware diagnostic before replacing components.
What 0x0000001B means
Microsoft maps hexadecimal bug check 0x0000001B to PFN_SHARE_COUNT. PFN refers to Windows’ page-frame-number database, which tracks physical memory pages and their references. A stop error occurs when the kernel detects an invalid page-frame reference and halts to protect the system. It is not the same as bug check 0x0000002B (PANIC_STACK_SWITCH); the codes describe different conditions. See Microsoft’s bug-check code reference.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Microsoft Windows 11 (USB) | $128.99 | Buy on Amazon |
| 2 |
|
Microsoft System Builder | Windоws 11 Home | Intended use for new systems | Install on a new PC |... | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
The code alone does not prove that a RAM module is defective. Windows can reach the same stop condition after a faulty driver, BIOS/UEFI or device firmware, storage corruption, unstable overclocking, or a newly installed device damages kernel memory bookkeeping. Treat 0x1B as a direction to investigate, not as a diagnosis.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsWhy PFN_SHARE_COUNT happens
Third-party drivers are the leading general stop-error category
Microsoft says the root cause of stop errors is “rarely a user-mode process.” Its overall stop-error analysis, cited on the Windows Client stop-error troubleshooting page, attributes approximately 70% to third-party driver code, 10% to hardware, 5% to Microsoft code, and 15% to unknown causes. Those percentages cover stop errors generally, not PFN_SHARE_COUNT specifically, and should not be used to calculate the odds for your PC. They do, however, justify checking recently installed drivers and utilities before buying replacement hardware. Read the Microsoft stop-code troubleshooting guidance.
#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
Hardware, firmware, and storage
- Defective, poorly seated, incompatible, or overclocked RAM can corrupt page data.
- A graphics, storage, network, audio, Bluetooth, USB, or chipset driver can make an invalid kernel memory request.
- Out-of-date BIOS/UEFI or device firmware can expose compatibility bugs, especially after a Windows feature update.
- File-system or drive errors can damage paging, dump, or system files.
- A device or utility added immediately before the crashes may be the trigger, even if the blue screen names no module.
A dump or diagnostic result is stronger evidence than the stop-code number. Avoid replacing RAM, the motherboard, or the SSD solely because 0x1B appeared.
Choose the next action from the symptoms
| What you observe | Start here | Why |
|---|---|---|
| Windows still starts and the crash happened once | Record details, install updates, and undo the most recent change | A one-off driver or update conflict may not recur after the change is reversed. |
| Windows starts but blue-screens repeatedly | Safe Mode, Device Manager review, driver rollback, memory and storage diagnostics | Safe Mode limits third-party startup components and makes comparison possible. |
| Crashes occur during gaming, large file copies, or other heavy loads | Check graphics/chipset/storage drivers, temperatures, free space, RAM, and drive health | Load-sensitive failures often expose a marginal device, driver, or memory path. |
A specific .sys module appears in the screen or dump |
Identify the owning device or software, then update, roll back, or uninstall it | The module gives you a testable lead; do not delete a system file at random. |
| Windows cannot boot normally | Enter Windows Recovery Environment (WinRE) and run Startup Repair | Recovery tools work without a full Windows session. |
Step 1: Record the stop details before changing anything
- Photograph the blue screen. Record
0x0000001B, any text after the code, and any “What failed” module name. - Note what happened immediately beforehand: a Windows update, driver installation, BIOS change, new USB device, RAM upgrade, software installation, or unusual workload.
- After rebooting, open Event Viewer by pressing
Win+Xand choosing Event Viewer. Go to Windows Logs > System, choose Filter Current Log…, and look around the crash time for a BugCheck or unexpected-shutdown entry. - Check
C:WindowsMinidumpfor.dmpfiles. If the folder is empty, configure dumps for the next crash: pressWin+R, runsysdm.cpl, open the Advanced tab, select Startup and Recovery > Settings, and set Write debugging information to Small memory dump (256 KB) with the default path%SystemRoot%Minidump. Clear Automatically restart temporarily if you need time to read the screen.
Copy the dump files somewhere safe before using cleanup software. A dump can reveal whether a driver or memory-management operation was involved; it is more useful than repeatedly guessing at components.
Step 2: Undo recent hardware, drivers, and utilities
Shut down fully, disconnect newly added USB, PCIe, storage, or memory hardware, and return any BIOS/UEFI overclock, undervolt, XMP/EXPO, or timing change to the manufacturer’s default. If the crashes stop, reconnect or re-enable one change at a time to isolate the trigger.
For software changes, open Settings > Apps > Installed apps in Windows 11 or Settings > Apps > Apps & features in Windows 10, sort by install date, and remove a recently added device utility, tuning tool, or low-level security component. For a driver that was updated just before the first crash, use Device Manager’s rollback option rather than downloading a random package.
Step 3: Start Windows in Safe Mode
Safe Mode loads a minimal driver set. If the blue screen disappears there, a normal-startup driver or service becomes a stronger suspect.
- Open Settings > System > Recovery (Windows 11) or Settings > Update & Security > Recovery (Windows 10).
- Under Advanced startup, select Restart now. You can also hold
Shiftwhile choosing Power > Restart from the sign-in screen. - Choose Troubleshoot > Advanced options > Startup Settings > Restart.
- Press
4orF4for Safe Mode, or5/F5for Safe Mode with Networking only when you need network access.
In Safe Mode, open Device Manager (right-click Start), expand recently changed categories, and look for a yellow warning icon. Right-click the suspected device and choose Properties > Driver. Try Roll Back Driver when available; otherwise choose Update driver using a package from the computer or device manufacturer, or choose Uninstall device and restart so Windows can redetect it. Do not uninstall an unknown device repeatedly without recording its name and hardware ID.
Step 4: Install Windows, driver, and firmware updates
Windows Update
- Windows 11: open Settings > Windows Update. Windows 10: open Settings > Update & Security > Windows Update.
- Select Check for updates, install quality and optional driver updates that match your hardware, and restart.
- Check again after the restart; updates can arrive in stages.
Manufacturer drivers and BIOS/UEFI
Use the support page for your exact computer model or motherboard. Compare the installed and offered versions, read the release notes, and keep the AC adapter connected during a firmware update. Do not interrupt a BIOS/UEFI flash. If a crash began immediately after a firmware or driver update, use the manufacturer’s documented rollback path instead of forcing an older file.
Step 5: Check system files, the drive, and free space
Keep the Windows system volume comfortably below capacity. Microsoft’s general guidance is about 10–15% free space, depending on configuration; the exact amount is not a PFN_SHARE_COUNT threshold. In File Explorer > This PC, check the free-space bar and remove or move large personal files after making a backup.
Open Windows Terminal (Admin) or Command Prompt (Admin) and run these commands in order:
DISM.exe /Online /Cleanup-Image /RestoreHealthsfc /scannow- Restart Windows after both commands finish.
DISM repairs the component store that SFC uses; SFC then verifies protected Windows files. If storage corruption is suspected, back up important data first and run chkdsk C: /scan. To schedule repairs that require a restart, use chkdsk C: /f, confirm the prompt, and reboot. Replace C: only after confirming the correct volume letter in your running Windows installation.
Rank #2
- STREAMLINED & INTUITIVE UI, DVD FORMAT | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
- PRODUCT SHIPS IN PLAIN ENVELOPE | Activation key is located under scratch-off area on label.
- GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.
Step 6: Test memory and other hardware
Windows Memory Diagnostic
- Press
Win+R, typemdsched.exe, and press Enter. - Choose Restart now and check for problems when you can allow an immediate reboot.
- After Windows returns, open Event Viewer and go to Windows Logs > System. Filter for the MemoryDiagnostics-Results source to see the result.
A reported error is evidence to test modules individually, reseat them with the PC powered off, and consult the motherboard or computer manual for supported slots and speeds. A clean Windows test does not prove RAM is perfect; intermittent faults can require the manufacturer’s longer diagnostic or a bootable memory test. If errors follow one module or slot, stop using the affected configuration and obtain professional service or a replacement that matches the system’s specifications.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Storage and device diagnostics
Run the SSD or hard-drive diagnostic supplied by its manufacturer and the computer maker’s built-in hardware test when available. Repeated read errors, disappearing drives, or SMART warnings justify an immediate backup and drive replacement; do not continue stressing a failing disk while troubleshooting Windows.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Step 7: Use System Restore and other recovery options
If the crashes began after a driver, application, or system change, open Control Panel > Recovery > Open System Restore, select a restore point dated before the change, and review the affected programs before confirming. System Restore does not remove personal documents, but it can remove drivers and applications installed after the selected point.
Windows 11 and 10 also provide Settings > System > Recovery (Windows 11) or Settings > Update & Security > Recovery (Windows 10) options such as Reset this PC. Choose Keep my files only after backing up; applications and many settings will still be removed. A reset is a last resort when diagnostics point to damaged Windows installation files and other recovery methods have failed.
Step 8: Repair a PC that will not boot
You need another working computer and a blank or erasable USB flash drive for Windows installation media with enough capacity for the current Windows installer. Create installation media using Microsoft’s official Windows media process; an unofficial preloaded drive is not Microsoft software.
- Insert the installation USB, power on the affected PC, and use its documented boot-menu key (often shown briefly on screen) to boot from USB.
- At Windows Setup, choose your language and keyboard, then select Repair your computer, not Install now.
- Choose Troubleshoot > Advanced options > Startup Repair. Let it complete and restart without the USB.
- If Startup Repair cannot fix the problem, return to Advanced options and try System Restore or Uninstall Updates when those options are available.
Microsoft’s Windows boot-issues guide also documents boot-code and BCD repair. From Advanced options > Command Prompt, first use diskpart and list vol to identify the Windows and system partitions; WinRE may assign them different letters. Then run only the commands appropriate to your boot mode and the guide’s instructions, such as bootrec /scanos and bootrec /rebuildbcd. Do not blindly run commands that write boot sectors or recreate the BCD on a disk you have not identified, because a wrong volume can make recovery harder.
Step 9: Analyze a recurring dump instead of guessing
When 0x1B returns, preserve the newest dump and compare it with earlier files. A debugger can show the bug-check parameters, the active thread, and a probable driver stack. A module name is a lead, not automatic proof: security software, storage filters, virtual-machine drivers, and graphics stacks can appear in a crash even when another component corrupted memory earlier.
- Update, roll back, or uninstall the device or software that owns the named module.
- Search the exact file name in the manufacturer’s documentation and verify its digital signature and file path.
- If different modules appear on each crash, prioritize RAM, firmware, storage, and power or thermal stability over deleting individual files.
- Keep copies of dumps, Event Viewer exports, and the dates of every change so a technician can reproduce the timeline.
Driver Verifier is an advanced, evidence-gathering option for a machine that still boots. It deliberately stresses selected drivers and can cause additional crashes, so create a restore point, select only a suspected third-party driver, and know how to enter Safe Mode. To turn it off from an elevated command prompt after testing, run verifier /reset and restart. Do not enable every verifier test indefinitely on a production PC.
When to stop troubleshooting yourself
- Memory diagnostics report errors, the drive shows SMART warnings, or the machine powers off during tests.
- The PC remains in a boot loop after recovery changes, or BitLocker asks for a recovery key you do not have.
- The crashes began after liquid damage, a failed firmware flash, or visible motherboard or connector damage.
- You have isolated a component but cannot safely reseat or replace it.
Back up data before further testing and give a technician the stop-code photograph, dump files, hardware model, recent-change timeline, and diagnostic results. Those details reduce the chance of replacing a healthy part on the basis of 0x1B alone.
If you prefer an automated starting point after trying the manual checks, Outbyte PC Repair can look for more than 100 common Windows issues, clean temporary and cache files, review settings and missing updates, and provide an app-crash log on Windows 11, 10, 8, and 7. It is optional, results vary, and it complements an antivirus rather than replacing one; a free trial is available by category for at least two days before a subscription.
Sources and scope
The code definition and recovery sequence above follow Microsoft documentation. The cited stop-error percentages are Microsoft’s general analysis, not a PFN_SHARE_COUNT-specific failure rate. No published source establishes a guaranteed repair time, success rate, or component-failure rate for 0x0000001B, so any diagnosis should be based on your dump and test evidence.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
