Site icon EfmSoft

What does BSOD 27 (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 result bug check has a value of 0x0000001B.

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

Important

This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.

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. AllStat summarizes the condition as “this result”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.

Analysis order

Do not repeatedly reboot a machine affected by this result before collecting the dump and event logs. Recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.

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.


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

Exit mobile version