What does BSOD 0x1B (PFN_SHARE_COUNT) mean?

 
Could be also:
ConstantTypeOS
ERROR_SECTOR_NOT_FOUNDWin32 errorWindows
KERN_POLICY_LIMITKern returnMac
ippStsOverlongStringIntel Ipp StatusAny
EFBIGerrnoAny
Previous Next
MEMORY_MANAGEMENT PFN_REFERENCE_COUNT

PFN_SHARE_COUNT

The PFN_SHARE_COUNT bug check has a value of 0x0000001B.

This bug check code is no longer used by the Windows operating system.

Dump evidence for PFN_SHARE_COUNT

Preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop.

Analysis order

  • Run WinDbg !analyze -v, then inspect the documented meaning of each parameter instead of relying only on the probably-caused-by line.
  • Find the earliest abnormal event preceding the stop: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang.
  • Keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.

Distinctive failure boundary

This result identifies page-frame share-count inconsistency. Examine the PFN database entry, share and reference counts, PTEs that map the page, locked-page activity, DMA buffers, and drivers that map or unmap physical pages.

Separating the result from neighboring bug checks

Memory diagnostics can rule out hardware, but a repeatable stack around page locking or MDL handling strongly suggests a driver accounting error. Preserve the original dump and use the documented parameters and stack to verify this distinction before changing drivers or platform configuration.

References


Looking for a different code? Search another status or error code.