ERROR_INVALID_VERIFY_SWITCH (0x76) – Verify-on-write switch wrong

What causes ERROR_INVALID_VERIFY_SWITCH

This error code 0x76 (decimal 118) shows up when the Windows kernel can't make sense of the parameter that tells it to verify data before writing. You'll usually see it during a system crash dump or when a driver tries to use the verify routine with a bad switch value.

The most common trigger? A corrupted registry key under HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management that controls the verify switch. I've seen this on Windows 10 22H2 and Server 2019 after a failed driver update or a disk error that scrambled the hive.

Let's walk through the three most likely fixes. Start with the first one — it'll resolve about 7 out of 10 cases.

Fix 1: Registry key is missing or has a wrong DWORD value

The verify-on-write switch lives in a specific registry location. If the DWORD is missing, set to zero, or has a value Windows doesn't expect, you'll get error 0x76.

1. Press Windows + R, type regedit, and hit Enter. Click Yes on the UAC prompt.
2. Go to this path:
   

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

3. In the right pane, look for a DWORD named VerifyOnWriteSwitch. If it's not there, right-click an empty area, choose New → DWORD (32-bit) Value, and name it VerifyOnWriteSwitch.
4. Double-click that DWORD. Set the value to 1 (decimal). Click OK.
5. Close Registry Editor. After doing this, you should see the error stop appearing on next reboot.

If the DWORD already exists but is set to 0 or some other number like 3, change it to 1. I've seen 0 block the verify-on-write routine entirely. Stick with 1 — that's the standard enable value.

Fix 2: Corrupted or outdated verify driver file (verifier.sys)

The verifier.sys driver is what actually performs the verification. If that file is damaged or a mismatch for your Windows build, the verify switch can't parse correctly. This happens more often than you'd think after a Windows update that replaced the file with a wrong version.

1. Open Command Prompt as admin. Click Start, type cmd, right-click Command Prompt, choose Run as administrator.
2. Run this command to check the file integrity:
   

   sfc /scanfile=c:\windows\system32\drivers\verifier.sys

3. If SFC reports corruption, fix it with:
   

   sfc /restorefile=c:\windows\system32\drivers\verifier.sys

4. Still broken? Use DISM to pull a clean version from Windows Update:
   

   dism /online /cleanup-image /restorehealth

5. After DISM finishes, reboot. The verify driver should now be a known-good copy.

I've had cases where SFC couldn't fix it because the source was also corrupted. In that situation, run the DISM command first — it downloads fresh files from Microsoft's servers. Then run SFC again.

Fix 3: Corrupted memory dump files that hold verify state

Windows caches verify state in dump files under %SystemRoot%\Minidump and %SystemRoot%\MEMORY.DMP. If those files have bad data, the switch parameter can get scrambled. This is rare but real — I've seen it on machines that had a disk error during a crash dump.

1. Open File Explorer. Go to C:\Windows\Minidump. Delete everything in that folder. If you get a permission error, take ownership first — right-click the folder, Properties → Security → Advanced → Change owner to your admin account.
2. Also delete C:\Windows\MEMORY.DMP if it exists. That file can be huge, so it might take a moment.
3. Open System Properties (press Windows + Pause/Break → Advanced system settings). Under Startup and Recovery, click Settings.
4. Set Write debugging information to (none). Click OK, then OK again.
5. Reboot. After the restart, go back to the same settings and change it back to Automatic memory dump (or Small memory dump, depending on your preference).

Clearing the dump files and resetting the dump type forces Windows to rebuild the verify state from scratch. I'd only do this if the registry fix and driver repair didn't work — because you'll lose any crash data you might want to analyze later.

Quick-reference summary

Start with the registry fix. If that doesn't cut it, move to the driver repair. Only bother with the dump cleanup as a last resort. Most people will have this error gone after step one.