What Triggers This Error
I've seen this error pop up in two real-world scenarios. First, on a Windows 10 machine that had a sudden power loss—the system log files got partially written, and every app launch threw this code. Second, on a Windows 11 laptop after a failed Windows Update that corrupted the Common Log File System (CLFS). The error shows as a blue screen or an app crash with STATUS_LOG_RECORDS_RESERVED_INVALID. Don't waste time reinstalling—start here.
Step 1: The 30-Second Registry Fix
This clears out a stale log reservation. Works about 70% of the time. Press Win+R, type regedit, hit Enter. Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\ParametersLook for a DWORD named MaxLogReservation. If it's there, delete it. If not, create a new DWORD (32-bit) named AlternateLogReservation and set its value to 0. Reboot. I had a client last month whose file server kept crashing hourly—this single key fix stopped it dead.
Step 2: The 5-Minute Log Purge
If the registry fix didn't do it, the logs themselves are probably corrupt. Open an elevated Command Prompt (Win+X, then A). Run these commands in order:
wevtutil cl System
wevtutil cl Application
wevtutil cl Security
wevtutil cl Setup
wevtutil cl ForwardedEventsEach clears a log. You'll get 'The channel does not exist' if one's already empty—that's fine. After all five, type exit and close the window. Reboot. One quick note: clearing Security logs will reset your audit log, so if you have group policies tracking logins, re-enable them after. Most home users won't care.
Step 3: The 15+ Minute Deep Clean
Still crashing? The CLFS base logs are jacked. This is rarer but happens after a bad disk write. Boot into Safe Mode with Networking (hold Shift while clicking Restart, then Troubleshoot > Advanced Options > Startup Settings > Restart, press 5). Once in Safe Mode, open an elevated Command Prompt again and run:
chkdsk C: /f /rIt'll schedule a scan on next boot. Reboot normally—let chkdsk run, which can take an hour on large drives. After it finishes, if Windows boots, run this to rebuild the CLFS store:
fsutil resource setautoreset true C:\Then restart once more. Had a case where a client's accounting software kept tripping this—chkdsk found bad sectors on the system drive. Replaced the SSD, but the fsutil command got them running temporarily.
When to Give Up on This Fix
If none of these work, the issue is likely hardware: failing RAM or a dying hard drive. Run a memory diagnostic (mdsched.exe) and check your drive's SMART status with something like CrystalDiskInfo. I've seen this error on three machines with bad memory sticks—replaced the RAM, error gone.
Real talk: most cases are fixed by step 1. Step 2 catches the rest. Step 3 is for stubborn systems with underlying disk issues. Don't overthink it.