You're stuck in a loop of blue screens with 0x00000111. Let's cut through the noise.
This error means Windows tried to grab a page of memory that should have been zeroed out (empty) but couldn't get it. Most of the time it's a driver that's messing with memory management or actual faulty RAM. I've seen it on Windows 10 and 11 machines, especially after a driver update or a new hardware install.
The Quick Fix – Roll Back or Replace the Suspect Driver
- Boot into Safe Mode with Networking. Mash F8 or Shift+Restart from the login screen, then choose Troubleshoot > Advanced Options > Startup Settings > Restart > press 5 for Safe Mode with Networking.
- Open Device Manager (right-click Start). Look for any device with a yellow exclamation mark. That's your first suspect.
- Right-click the device, choose Properties > Driver tab > Roll Back Driver. If that's grayed out, uninstall the driver, then check the box "Delete the driver software for this device", restart, and let Windows reinstall.
- If you recently updated a driver (graphics, network, or storage are the usual culprits), roll back that specific driver. Had a client last month whose NVIDIA driver update triggered 0x00000111 every time he opened Chrome. Rolling back fixed it instantly.
If rollback isn't possible, go to the manufacturer's site and download the previous stable version. Install that instead.
If the Driver Rollback Didn't Work – Run Driver Verifier
Driver Verifier stresses drivers to find the bad one. Be careful: it can cause a boot loop if you enable it on too many drivers. Here's how to do it safely.
- Open Command Prompt as Administrator. Type
verifierand hit Enter. - Select Create custom settings (for code developers) > Next.
- Check Enable special pool and Force IRQL checking (these catch memory corruption fast). Next.
- Select Select driver names from a list. Click Provider to sort by manufacturer. Uncheck all Microsoft and Intel drivers. Check any third-party driver that isn't signed by Microsoft (e.g., from NVIDIA, Realtek, Broadcom, etc.). Limit to 4-5 drivers.
- Click Finish, restart. If it blue-screens again, the bugcheck will name the faulty driver. Google that driver name + 0x00000111 for a targeted fix.
Pro tip: Boot back into Safe Mode and run verifier /reset to turn off Verifier after you've identified the driver. Otherwise it'll keep stressing drivers every boot.
When It's Really the RAM (Yes, It Happens)
If Verifier found nothing and you're still crashing, check your memory. Use the built-in Windows Memory Diagnostic. Type mdsched.exe in Start, choose Restart now and check for problems. Let it run for a full pass (can take an hour). If it reports errors, replace the faulty stick.
I've also seen a single bad DIMM cause this exact error on a Dell Optiplex 7080. Swapped the RAM, never saw the bug again.
Less Common Variations & Their Fixes
| Variant | Likely Cause | Fix |
|---|---|---|
| 0x00000111 + 0x00000004 parameter | Corrupted system file or pagefile | Run sfc /scannow then dism /online /cleanup-image /restorehealth. Reset pagefile: System Properties > Advanced > Performance > Advanced > Virtual Memory > uncheck auto, set initial and max to same size (e.g., 4096 MB), restart, re-enable auto. |
| 0x00000111 + 0x00000001 parameter | Kernel memory corruption from overclocking | Reset BIOS to defaults. Disable XMP/DOCP. Run Prime95 for 10 minutes – if it errors, your CPU or RAM can't handle the overclock. |
| 0x00000111 + 0x00000008 parameter | Antivirus or security software conflict | Boot into Safe Mode, uninstall the security suite (e.g., McAfee, Norton, Webroot). Reinstall after reboot. |
Keep It From Coming Back
- Never install beta drivers on a production machine. I've learned this the hard way. Stick to WHQL-certified releases.
- Update your BIOS if you're on an older version. Manufacturers patch memory compatibility issues all the time.
- Don't use system cleaner tools that mess with the registry or pagefile. They cause more bluescreens than they fix.
- If you're overclocking, stress-test properly. Run MemTest86 for 8+ hours before calling it stable. A 2-minute test doesn't prove anything.
Bottom line: 0x00000111 is almost always a driver or RAM issue. Start with the driver rollback, run Verifier if needed, then test your memory. You'll have it fixed in under an hour.