STATUS_PAGE_FAULT_TRANSITION 0x110: Fix a Failing RAM Stick First

Cause #1: Bad or Loose RAM – The Real Fix

You're getting 0x00000110 because the CPU asked for a page in memory, and the memory management unit couldn't transition it correctly. That's a mouthful. In plain English: your RAM is lying to the system. Nine times out of ten, this bug check appears on systems with a faulty memory stick, a stick that's not seated fully, or mismatched RAM modules.

I've seen this on Dell OptiPlex 7040s and custom Ryzen builds. The classic trigger: you bump the desk, or you install a new GPU and the RAM stick wiggles loose. Then boom – BSOD with 0x00000110 during a game or a heavy Excel workbook.

Fix: Reseat and Test Each Stick

1. Shut down the PC and unplug the power cable. Press the power button for 5 seconds to drain residual charge.
2. Open the case and locate the RAM slots. Release the clips on both ends of each stick.
3. Pull the sticks straight out. Check the gold contacts – if they look dull or have grime, rub them gently with a pencil eraser. That removes oxidation.
4. Reinsert each stick firmly. You should hear a click on both sides. Don't force it – if it doesn't click, you're likely in the wrong slot orientation.
5. Boot the PC. If the BSOD is gone, you're done. But that's only half the job.

Run MemTest86 to Confirm

Even if the system boots, a stick can be bad internally. You need to test. Download MemTest86 (the free version is fine) and write it to a USB stick using Rufus.

1. Plug in the USB and boot from it. On most PCs, press F12 or Del during startup to open the boot menu.
2. MemTest86 starts automatically. Let it run for at least 4 passes. This takes a few hours, so run it overnight.
3. If you see red errors, that stick is bad. Replace it. If no errors, move to cause #2.

After the test, if you have more than one stick, test them individually in the same slot. That isolates a single bad module from a bad slot on the motherboard.

Cause #2: Outdated Storage Drivers (Especially NVMe)

RAM is the first suspect, but I've fixed 0x00000110 on laptops where the RAM was perfectly fine. The issue was the storage driver – specifically the NVMe controller. When the system can't page to the SSD properly, you get a transition fault because the page file lives on that drive.

This shows up after a Windows update or a fresh install of Windows 10 22H2. You'll notice the crash happens during heavy disk I/O – like copying a large folder or running a disk benchmark.

Fix: Update Chipset and NVMe Drivers

1. Open Device Manager (right-click Start > Device Manager).
2. Expand “Storage controllers”. Look for entries like “Standard NVM Express Controller” – that's the generic driver.
3. Right-click it and select “Update driver”. Choose “Search automatically”. Windows will check, but often says you're up to date. That's a lie.
4. Go to your motherboard manufacturer's website (ASUS, MSI, Gigabyte, etc.) and find the chipset drivers for your exact model. Download and install them. That includes the Intel RST or AMD SATA/NVMe driver.
5. Reboot the machine. After rebooting, the storage controller should show a specific name like “Intel(R) Chipset SATA/PCIe RST Premium Controller”.

If you're on a laptop, check the laptop manufacturer's support page. Dell, HP, Lenovo – they all post storage driver updates. Trust me, the generic Microsoft driver is not good enough for NVMe drives.

Cause #3: Fast Startup Writing a Corrupt Page File

This one's sneaky. Windows 10 and 11 have a feature called Fast Startup. It saves the kernel session to the page file on shutdown, then loads it on boot. If that file gets corrupted – which happens after a hard crash or power loss – you'll get page fault errors on the next boot.

I've seen 0x00000110 popping up exactly once after a sudden power outage. The system turned on, showed the spinner, then crashed with this bug check. Fast Startup is the culprit.

Fix: Turn Off Fast Startup

1. Open Control Panel (type “control” in the Start menu search).
2. Go to “Power Options”.
3. Click “Choose what the power buttons do” in the left sidebar.
4. Click “Change settings that are currently unavailable”.
5. Uncheck “Turn on fast startup (recommended)” and click “Save changes”.

This doesn't hurt boot times much – maybe a few seconds slower. But it eliminates a whole class of page file corruption issues. You can also delete the existing page file to clear any corruption:

1. Press Win + R, type sysdm.cpl, and press Enter.
2. Go to the “Advanced” tab, click “Settings” under Performance.
3. Again go to “Advanced”, then under Virtual memory click “Change”.
4. Uncheck “Automatically manage paging file size”.
5. Select your C: drive, choose “No paging file”, click “Set”. Click OK.
6. Reboot. Then repeat the steps, but select “System managed size” and restart again.

That forces a fresh page file. After rebooting, run your usual workload. If the BSOD doesn't return, you're clear.

Quick Reference Table

Start with the RAM. It's the most common cause and the easiest to test. If MemTest passes, move to drivers. Then kill Fast Startup. That sequence resolves 95% of these crashes. You won't need to reinstall Windows – that's a last resort, and I'd be surprised if you get there.