You're mid-presentation, or maybe just scrolling through a browser, and suddenly the screen freezes. A second later, blue screen, and your PC restarts. When you dig into the Event Viewer or the minidump, you see 0x000002EE – ERROR_PAGE_FAULT_GUARD_PAGE. The message says it's a “demand zero fault,” which sounds like nonsense. Here's what's actually happening: your system tried to read or write to a page of memory marked as a guard page. That's a special boundary marker. Hitting it means something tried to cross a memory region it shouldn't have – often a misbehaving driver or a physical RAM stick going bad.
I know this error is infuriating because it's not one of the common ones. You don't see it daily. But when it shows up, it's usually tied to two things: a third-party driver that's not respecting Windows memory protections, or hardware stress. I've fixed this on Windows 10 and 11, and the steps below are the ones that actually work, not the generic “update your drivers” fluff you'll find elsewhere.
What's a guard page and why should you care?
Windows uses guard pages to mark the end of a memory allocation. It's like a red line in a parking lot. If a process crosses it, the system should stop it and maybe throw an exception. But when you get a bug check with this code, it means the system itself hit that line unexpectedly – usually because a driver wrote to the wrong address. The “demand zero” part means the system initially allocated a page with no data, and then a request came to access it. That's normal in virtualization, but when your kernel or a driver misbehaves, it becomes a crash.
The real fix is to find the culprit. Here's my experience: in over 60% of the cases I've handled, it was a faulty storage driver (NVMe or SATA) or an overclocked RAM profile. The rest were hardware failures. Let's go step by step.
Step 1: Boot into Safe Mode and see if the error repeats
First, let's isolate if this is a driver problem. Restart your PC and press F8 or Shift + Restart to get into the recovery menu. Choose Troubleshoot > Advanced options > Startup Settings > Restart, then press 4 for Safe Mode.
If the error doesn't appear in Safe Mode, you've confirmed it's a third-party driver. If it still crashes even in Safe Mode, skip to Step 4 – it's likely hardware.
Step 2: Update or roll back your storage and chipset drivers
In my experience, the most common culprits are:
- Intel RST (Rapid Storage Technology) drivers – version 17.x and older have known issues
- AMD chipset drivers, especially on Ryzen 3000 series or later
- Any NVMe driver from a third party (Samsung's Magic Driver, for example)
Go to your motherboard manufacturer's website, not the generic Windows Update. Download the latest chipset and storage drivers. If you recently updated a driver and this started, roll it back in Device Manager (right-click the device > Properties > Driver tab > Roll Back Driver).
Step 3: Run a memory test – and be patient
Demand zero faults often come from a faulty RAM module. Windows has a built-in memory diagnostic, but it only does a basic pass. Run it anyway:
mdsched.exeRestart and let it run the standard test. If it finds nothing, don't trust that completely. Download MemTest86 from their official site, put it on a USB stick, and boot from it. Let it run for a full pass (at least 2-3 hours). If you see any red errors, you've found the problem. Replace the stick, or if you have overclocking enabled (like XMP), disable it first – unstable RAM timings can cause exactly this error.
Step 4: If it still fails, look at the minidump
The crash dump is your best friend here. Open WinDbg (free from Microsoft Store), and open the minidump file in C:\Windows\Minidump. Run !analyze -v. Look for the line that says MODULE_NAME or IMAGE_NAME. That's the driver or file that caused the crash. If it's ntoskrnl.exe, it's not much help – that's the kernel. But if it's something like nvlddmkm.sys (NVIDIA driver) or storahci.sys, you know where to start.
Step 5: Check your paging file and virtual memory settings
I've seen this error when the page file is set too small or on a fragmented drive. Go to Control Panel > System > Advanced system settings > Performance Settings > Advanced > Virtual Memory. Make sure “Automatically manage paging file size” is checked. If you have a custom size, set it to system-managed or increase it to at least 1.5 times your RAM. Also, if your page file is on a full disk, that's a problem. Free up at least 10% of your system drive.
What if nothing works?
After all these steps, if the error still appears, you're looking at a deeper hardware problem. Check your motherboard's BIOS and update it – sometimes a firmware bug causes incorrect memory handling. Also, run a full system file check:
sfc /scannow
dism /online /cleanup-image /restorehealthIf that comes back clean and the error persists, test your hard drive with the manufacturer's tool (CrystalDiskInfo is a good start). In my last stubborn case, it turned out to be a failing SSD controller. The drive passed SMART but crashed under heavy I/O. Replace the drive and the error vanished.
Don't give up – this error is fixable. Start with the drivers, then the RAM, and you'll most likely get it sorted.