volsnap.sys should not be deleted or replaced; first run the Extended Windows Memory Diagnostic, because the crashes become more likely under heavier memory use, and then check drivers and storage if memory passes.
PAGE_FAULT_IN_NONPAGED_AREA (0x50) means invalid system memory was referenced. Possible causes include defective RAM, faulty driver code, storage corruption, or other failing hardware.^1^
volsnap.sys is a built-in component of Windows Volume Shadow Copy Service (VSS). Its name on the blue screen identifies code involved when the crash occurred, but does not by itself prove that Volsnap is damaged.^2^
1. Test the RAM
- Save your work and close all programs.
- Press Windows key + R.
- Enter
mdsched, and select OK. - Select Restart now and check for problems.
- When the diagnostic screen appears, press F1.
- Change Test Mix from Standard to Extended.
- Press F10 to begin.
The Extended test takes longer but is more appropriate for crashes that occur when games or downloads increase system load.^3^
After Windows restarts, check the result:
- Right-click Start and select Event Viewer.
- Open Applications and Services Logs → Microsoft → Windows → MemoryDiagnostics-Results → Debug.
- Open the latest result. Event ID 2001 means that this test did not detect a memory error.
If errors are reported, stop troubleshooting Windows software: the RAM or its configuration needs hardware service. If this is a desktop with multiple memory modules, a repair technician can test each module separately. Do not change memory voltages or timings unless you know the motherboard requirements.
2. Install Windows and manufacturer driver updates
If the memory test passes:
- Open Settings → Windows Update → Advanced options → Optional updates.
- Install the available driver updates.
- Return to Windows Update, select Check for updates, and install everything offered.
- Restart the computer.
- If crashes continue, obtain the latest chipset, storage, graphics, and network drivers from the computer or motherboard manufacturer—not from third-party driver-download utilities.
Microsoft also recommends checking Device Manager for devices marked with an exclamation point and updating, disabling, or uninstalling the affected device.^4^
3. Check the system drive
Because Volsnap participates in volume and storage operations, check the Windows volume if RAM and drivers pass:
- Back up important files first.
- Right-click Start → Terminal (Admin).
- Run:
chkdsk C: /f /r
- If prompted to schedule the scan, enter
Y. - Restart and allow the scan to finish without interrupting it.
This can take a long time. Microsoft identifies a corrupted NTFS volume as one possible cause of stop code 0x50 and documents chkdsk /f /r as the corresponding check.^1^
Also ensure the Windows drive has approximately 10–15% free space, because Windows and applications need space for swap files and related operations.^4^
If it still crashes
Check Event Viewer → Windows Logs → System for errors at the exact crash time. A technician should then analyze several crash dumps and compare MODULE_NAME, FAULTING_MODULE, and the stack; Microsoft recommends comparing multiple dumps because the module displayed on one blue screen may only be where earlier corruption became visible.^1^
Do not use Driver Verifier without recovery assistance—it intentionally stresses drivers and can make an unstable computer crash during startup.
References
- Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA
- Volume Shadow Copy Service (VSS)
- [Windows 11](https://support.microsoft.com/windows/experience/performance-optimization/how-to-fix-error-0xa-irql-not-less-or-equal#check-the-windows-device's-memory)
- [Windows 11](https://support.microsoft.com/windows/experience/performance-optimization/troubleshooting-windows-unexpected-restarts-and-stop-code-errors)