Fix STATUS_LOG_CONTAINER_LIMIT_EXCEEDED (0xC01A0012) Fast

What You're Dealing With

This error — STATUS_LOG_CONTAINER_LIMIT_EXCEEDED (0xC01A0012) — means the Windows log service has run out of room to store new log containers. Think of it like your log file's filing cabinet is full, and every new entry gets kicked back. I see this often with apps that log like crazy—had a client last month whose print spooler service filled up the System log in about 15 minutes after a bad driver update. The fix is usually fast, sometimes permanent.

The 30-Second Fix: Clear the Log

Start here. It's the quickest way to get your system running again, but it's a band-aid unless you fix the root cause.

1. Open Event Viewer (eventvwr.msc).
2. Right-click the log showing the error—likely System, Application, or a custom log.
3. Select Clear Log... and choose Save and Clear if you want a copy, or just Clear to wipe it now.

That's it. The error vanishes instantly. But don't walk away yet — if the log fills up again quickly, the next section is for you.

The Moderate Fix (5 Minutes): Increase the Log Size

If clearing the log didn't stick, the log is too small for the amount of data being written. Here's how to give it more room.

1. In Event Viewer, right-click the same log and go to Properties.
2. Set Maximum log size to something bigger — I usually set this to 20 MB or 50 MB for busy servers. The default is 20 MB on many systems.
3. Under When the maximum event log size is reached, pick Overwrite events as needed — this keeps the log from stopping when full.
4. Click OK.

This works if the logging volume is normal but the log was just too small. If you're still seeing the error after a day, move to the advanced fix.

The Advanced Fix (15+ Minutes): Tame the App That's Flooding the Log

The real fix is finding and stopping the source. A runaway app or driver can generate thousands of events per minute. Here's how to hunt it down.

Step 1: Find the Culprit

Open Event Viewer and filter the log by the past hour. Look for repeating events with the same Event ID or source. Common offenders:

• Print drivers — bad driver versions, especially from HP or Brother.
• Backup software — VSS errors from Symantec or Veeam.
• Custom apps — .NET applications logging every exception.

Had a client whose QuickBooks database manager filled the Application log every 30 minutes with connection timeout errors. We bumped the timeout, and the error stopped.

Step 2: Fix or Disable the Source

Once you know the source, fix it:

• Driver issue: Update or roll back the driver in Device Manager.
• App issue: Check the app's logging level in its config file. Many apps have a loggingLevel or trace setting—set it to error or off to reduce output.
• Service issue: Stop the service temporarily to see if the error stops. If it does, you've found your culprit.

Step 3: Registry Tweaks (Last Resort)

If the app can't be controlled, you can increase the log's container limit via registry. This is rare — I've only needed it twice in 10 years. The key is here:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\System

Find the log name you need (like System or Application), and check the MaxSize DWORD. Default is 0x1400000 (20 MB). You can increase it to, say, 0x3200000 (50 MB). Reboot after changing it.

When to Call a Pro

If you've done all this and the error keeps coming back, the log itself might be corrupted. I'd nuke the log file (%SystemRoot%\System32\winevt\Logs\) after backing up needed events, then restart the Windows Event Log service. That's an advanced move — only try it if you're comfortable with the command line.

Otherwise, check with the app vendor. That QuickBooks issue I mentioned? Intuit had a hotfix that solved it. Sometimes it's not your fault.