BAD_SYSTEM_CONFIG_INFO (stop code 0x00000074) means Windows tried to read its own configuration — the registry — and found it damaged. Without a working registry, Windows can’t start, so you get a blue screen instead of a desktop. On Acer laptops this often follows a Windows update gone wrong, a sudden power loss, or disk corruption.

The fix is to repair or restore the registry and verify the disk underneath it. You’ll work from the Windows Recovery Environment for most of this. If your crash names a different stop code, our general blue screen guide covers the rest.

Why this happens

  • Corrupted registry hives. The SYSTEM or SOFTWARE hive got damaged.
  • Failed Windows update. An update that crashed mid-install leaves configuration half-written.
  • Sudden power loss. Force shutdowns during writes corrupt registry files.
  • Disk errors. Bad sectors landing on registry files produce this error.
  • Faulty RAM. Memory errors corrupt registry data in transit.
  • Registry cleaner damage. Aggressive “cleaner” tools delete keys Windows needs.
  • Driver installation gone wrong. A bad driver install can corrupt the hardware-related hives.

How to fix it

Work through these in order — you’ll need WinRE (force it with 2-3 interrupted boots).

Fix 1: Run Startup Repair

Let Windows attempt the automatic fix first.

  1. Boot into WinRE via the forced-shutdown method.
  2. Choose Troubleshoot > Advanced options > Startup Repair.
  3. Select your Windows installation and let it run — it checks registry hives among other things.
  4. If it succeeds, you’ll boot to the desktop. Run sfc /scannow afterward to finish the job.
  5. If it fails, note the log path and continue to Fix 2.
  6. Don’t run it more than once — repeated failures mean you need manual repair.

Fix 2: Restore the registry from backup

Windows keeps automatic registry backups you can restore manually.

  1. In WinRE, go to Troubleshoot > Advanced options > Command Prompt.
  2. Find your Windows drive letter (often D: in WinRE): diskpart list volume exit
  3. Navigate to the config folder (replace D: with your letter): cd /d D:\Windows\System32\config
  4. Check for the automatic backup in the RegBack folder: dir D:\Windows\System32\config\RegBack
  5. If the backup files exist and are non-zero in size, back up the current hives first: md backup copy * backup
  6. Then restore: copy D:\Windows\System32\config\RegBack\* D:\Windows\System32\config\ Type exit and choose Continue to boot.

Fix 3: Repair with SFC and DISM from WinRE

Fix the system files around the registry.

  1. In WinRE’s Command Prompt, run an offline SFC scan: sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows
  2. Wait for it to complete — offline scans take longer.
  3. If SFC reports fixed corruption, type exit and boot normally.
  4. If SFC can’t fix everything, run DISM against the offline image: DISM /Image:D:\ /Cleanup-Image /RestoreHealth
  5. Then run SFC once more.
  6. Microsoft documents offline servicing on support.microsoft.com if you need the full syntax reference.

Fix 4: Check the disk for errors

Registry corruption is often a symptom of disk problems.

  1. In WinRE’s Command Prompt, run: chkdsk D: /f /r
  2. Let it complete fully — bad sectors on registry files are exactly what you’re hunting.
  3. Review the summary when it finishes.
  4. Type exit and try booting.
  5. If chkdsk found and repaired errors and the system boots, schedule monthly chkdsk C: /f scans going forward.
  6. If chkdsk reports many bad sectors, the drive is failing — back up immediately and replace it. See our NTFS.SYS guide for storage-focused diagnosis.

Fix 5: Test the RAM

Rule out memory as the corruption source.

  1. Boot into WinRE, then Troubleshoot > Advanced options > Startup Settings > Restart — or if you can boot Windows, press Win + R and type mdsched.exe.
  2. Run the memory diagnostic and let it complete.
  3. Check results in Event Viewer afterward (or note the on-screen result).
  4. If errors are found, reseat or replace the RAM before doing more registry repairs — fixing the registry while RAM corrupts it is futile.
  5. For a definitive test, run MemTest86 from a bootable USB overnight.
  6. Clean RAM + repaired registry = a stable system. If both are clean and crashes persist, continue.

Fix 6: Update drivers and the BIOS from Acer

Eliminate driver and firmware contributors.

  1. If you can boot (even in Safe Mode), go to Acer’s official support site for your exact model.
  2. Install the latest chipset and storage drivers.
  3. Install any available BIOS update with the charger connected — read the release notes for stability fixes.
  4. In Device Manager, resolve any yellow warning icons.
  5. If a specific driver install preceded the crashes, roll it back or reinstall it cleanly.
  6. Restart and monitor. Driver-caused registry corruption is uncommon but real, especially with storage filter drivers.

Fix 7: Reset Windows while keeping files

When the registry is beyond manual repair.

  1. In WinRE, choose Troubleshoot > Reset this PC.
  2. Select Keep my files.
  3. Choose Cloud download if you have good internet (fresher files) or Local reinstall otherwise.
  4. Let the reset complete — it rebuilds the entire registry and system from scratch.
  5. Afterward, reinstall your applications and the Acer drivers from the support site.
  6. Set up regular system image backups (Control Panel > Backup and Restore) so the next registry problem is a 20-minute restore instead of a day of repairs. As a final fallback, a clean install from Microsoft’s download page achieves the same result.

Closing

BAD_SYSTEM_CONFIG_INFO is Windows telling you its instruction manual got torn — and the repair is refreshingly mechanical: restore the registry backup, verify the disk, test the RAM. The RegBack restore in Fix 2 resolves most cases outright. Going forward, treat registry cleaners as the enemy, shut down cleanly, and keep an image backup — the registry is the one part of Windows where an ounce of prevention genuinely beats the cure.

Frequently asked questions

What does BAD_SYSTEM_CONFIG_INFO mean?
Stop code 0x00000074: the Windows registry or system configuration is damaged, so Windows can’t initialize properly. It usually follows a bad update, a corrupted registry hive, or disk errors damaging the config files.
Will I lose my files fixing this?
No. Registry repairs, Startup Repair, and SFC scans preserve your files. The registry hives being repaired contain settings, not your documents — your personal files live elsewhere on the drive.
Can a bad RAM stick cause this error?
Yes, indirectly — faulty RAM can corrupt registry data as it’s written, producing this exact error. If the error keeps returning after registry repairs, test your memory with Windows Memory Diagnostic.
How do I prevent registry corruption in the future?
Avoid registry cleaners and manual registry edits, shut down properly instead of force-powering off, keep your drive healthy with occasional chkdsk scans, and maintain regular system image backups.