The BAD_SYSTEM_CONFIG_INFO error is a Windows Blue Screen of Death (BSOD) stop error that generally indicates Windows has detected a serious problem with system configuration information required to start or operate correctly.

The error may appear as:

Your device ran into a problem and needs to restart.

Stop code: BAD_SYSTEM_CONFIG_INFO

The computer may restart normally after the error, repeatedly display the blue screen, enter an Automatic Repair loop, or become completely unable to start Windows.

BAD_SYSTEM_CONFIG_INFO can be caused by damaged system files, incorrect boot configuration, registry problems, faulty RAM, storage errors, problematic drivers, unsuccessful Windows updates, or incorrect configuration changes.

This guide covers troubleshooting from simple recovery methods through advanced boot and system repair procedures.

What Does BAD_SYSTEM_CONFIG_INFO Mean?

BAD_SYSTEM_CONFIG_INFO is a Windows bug check associated with inconsistent or damaged system configuration data.

In technical terms, the stop error is commonly associated with Bug Check 0x74 (BAD_SYSTEM_CONFIG_INFO).

Windows depends on several configuration components during startup, including:

• Boot Configuration Data (BCD)
• Windows Registry
• Device drivers
• System files
• Memory configuration
• Storage configuration
• Boot Manager
• Hardware configuration information

If critical configuration information becomes invalid or inaccessible, Windows may stop rather than continue operating in an unreliable state.

Common Symptoms

A computer affected by BAD_SYSTEM_CONFIG_INFO may show one or more of the following symptoms:

• Blue screen immediately after switching on the computer
• Windows starts and then crashes
• Continuous restart loop
• Automatic Repair loop
• Windows fails after an update
• Windows fails after installing a driver
• Error after adding or replacing RAM
• Error after cloning or replacing an SSD/HDD
• Windows Safe Mode works but normal mode fails
• Computer becomes unstable before displaying the BSOD
• System Restore becomes necessary to boot Windows

The exact cause therefore needs to be identified rather than assuming that every BAD_SYSTEM_CONFIG_INFO error has the same solution.

Common Causes of BAD_SYSTEM_CONFIG_INFO

1. Damaged Windows System Files

Unexpected shutdowns, disk errors, interrupted Windows updates, malware, or storage problems can corrupt critical Windows files.

Windows may then fail while loading those components.

2. Incorrect Boot Configuration Data (BCD)

BCD tells Windows Boot Manager how the operating system should be loaded.

Problems may occur after:

• Disk cloning
• Partition changes
• Dual-boot configuration
• Failed Windows updates
• Boot repair attempts
• Changing disks
• Incorrect use of BCDEdit or similar utilities

A damaged boot configuration can prevent Windows from starting normally.

3. Incorrect MSConfig Boot Settings

This is an especially important cause to check if the problem began after modifying:

System Configuration → Boot → Advanced options

Users sometimes enable:

• Number of processors
• Maximum memory

believing that doing so will increase computer performance.

Normally, Windows automatically manages available processors and memory. Incorrectly forcing these values can create startup problems.

Solution 1: Undo Incorrect Processor or Memory Boot Configuration

If you recently changed MSConfig settings, try reversing those changes first.

If Windows still starts:

Press:

Windows + R

Type:

msconfig

Press Enter.

Go to:

Boot → Advanced options

Normally, leave these options unchecked unless they are required for a specific troubleshooting purpose:

• Number of processors
• Maximum memory

Click OK → Apply → Restart.

Important

Setting the processor count or maximum memory manually does not normally make Windows faster. These options are primarily diagnostic/configuration controls.

Solution 2: Perform a Complete Power Cycle

Before advanced troubleshooting, perform a full shutdown.

1. Turn off the computer.
2. Disconnect external USB devices.
3. Disconnect unnecessary accessories.
4. If practical for the device, disconnect external power.
5. Wait approximately 30 seconds.
6. Reconnect essential devices.
7. Start the computer.

If the BSOD appeared after connecting new hardware, leave that device disconnected while testing.

Solution 3: Enter Windows Recovery Environment (WinRE)

If Windows cannot start normally, access Windows Recovery Environment.

Depending on the PC and Windows installation, WinRE may appear automatically after repeated failed startup attempts.

You can also boot from compatible Windows installation/recovery media and choose:

Repair your computer

Then navigate to:

Troubleshoot → Advanced options

From here you can access tools such as:

• Startup Repair
• Startup Settings
• Command Prompt
• System Restore
• Uninstall Updates
• UEFI Firmware Settings

Solution 4: Run Startup Repair

From Windows Recovery Environment select:

Troubleshoot → Advanced options → Startup Repair

Select the Windows installation/account when requested.

Windows will attempt to identify and repair startup-related problems automatically.

Restart the computer after Startup Repair completes.

If BAD_SYSTEM_CONFIG_INFO remains, continue with the following solutions.

Solution 5: Start Windows in Safe Mode

Safe Mode starts Windows with a reduced set of drivers and services.

Navigate to:

Troubleshoot → Advanced options → Startup Settings → Restart

After restarting, select:

Enable Safe Mode

or:

Enable Safe Mode with Networking

If Windows works correctly in Safe Mode, investigate recently installed:

• Drivers
• Applications
• Antivirus/security software
• Hardware utilities
• Windows updates
• Startup programs

This strongly suggests that a software or driver loaded during normal startup may be involved.

Solution 6: Run System File Checker (SFC)

If Windows starts normally or in Safe Mode, open Command Prompt or Windows Terminal as Administrator.

Run:

SFC /scannow

System File Checker scans protected Windows system files and attempts to replace damaged versions.

Possible results include:

Windows Resource Protection did not find any integrity violations

No protected system-file corruption was detected.

Windows Resource Protection found corrupt files and successfully repaired them

Restart Windows and test again.

If SFC cannot repair everything, run DISM.

Solution 7: Repair Windows Component Store with DISM

Open an elevated Command Prompt or Terminal.

Run:

DISM /Online /Cleanup-Image /ScanHealth

Then:

DISM /Online /Cleanup-Image /RestoreHealth

After DISM completes successfully, run:

SFC /scannow

again.

Restart Windows.

DISM and SFC address different parts of Windows servicing and file integrity, so running SFC again after a successful DISM repair can be useful.

Solution 8: Check the System Drive for File-System Errors

Disk or file-system corruption can also contribute to startup and BSOD problems.

Open Command Prompt as Administrator and run:

chkdsk C: /scan

For a more extensive repair, Windows may require an offline check. For example:

chkdsk C: /f

If Windows reports that the drive is in use and asks whether the check should be scheduled at the next restart, follow the prompt and restart.

Important

Repeated disk corruption can indicate an underlying SSD/HDD, storage-controller, power, or hardware problem. Do not rely only on CHKDSK if errors repeatedly return.

Maintain a current backup of important data.

Solution 9: Check RAM

Defective or unstable RAM can cause BSODs and corrupted configuration data.

Press:

Windows + R

Type:

mdsched.exe

Choose:

Restart now and check for problems

Windows Memory Diagnostic will test memory during restart.

For systems with multiple RAM modules, technicians may also test modules individually if hardware diagnostics indicate a memory problem.

Also check:

• RAM is properly seated
• Correct memory type is installed
• Modules are compatible
• BIOS memory settings are appropriate
• XMP/EXPO or overclocking is not causing instability

If the problem began after upgrading RAM, test the original memory configuration.

Solution 10: Roll Back a Recently Updated Driver

If the error started immediately after a driver update:

Open:

Device Manager

Locate the affected device.

Open:

Properties → Driver → Roll Back Driver

Restart the computer.

Pay particular attention to:

• Storage controller drivers
• Chipset drivers
• Graphics drivers
• Network drivers
• Security-related drivers
• Recently installed hardware drivers

If rollback is unavailable, consider uninstalling the problematic driver and installing an appropriate driver from the computer or hardware manufacturer's support source.

Solution 11: Remove Recently Installed Software

If Windows works in Safe Mode but crashes normally, uninstall software installed shortly before the problem began.

Common candidates include:

• Antivirus/security software
• System optimization tools
• Registry cleaners
• Driver updater utilities
• Disk/partition utilities
• Hardware monitoring software
• Virtualization software
• Low-level system utilities

Restart after removal and test again.

Solution 12: Uninstall a Recent Windows Update

If BAD_SYSTEM_CONFIG_INFO appeared immediately after a Windows update, WinRE provides update-removal options.

Go to:

Troubleshoot → Advanced options → Uninstall Updates

Depending on the recovery environment, you may be offered options such as:

• Uninstall latest quality update
• Uninstall latest feature update

Start with the update most closely associated with when the problem began.

Do not repeatedly remove security updates without establishing whether the update is actually responsible.

Solution 13: Use System Restore

System Restore can return Windows system configuration to an earlier restore point without functioning as a personal-file backup/restore mechanism.

Open:

Troubleshoot → Advanced options → System Restore

Select a restore point created before BAD_SYSTEM_CONFIG_INFO started.

Review affected programs if Windows provides that option.

Proceed with restoration and restart the computer.

This can be particularly useful after problematic:

• Driver installation
• Registry modification
• Windows configuration change
• Software installation

Solution 14: Check BIOS/UEFI Configuration

Incorrect firmware settings can contribute to Windows startup problems, particularly after firmware changes or hardware replacement.

Enter BIOS/UEFI and review settings.

Potential areas include:

• Boot mode
• UEFI configuration
• Storage controller configuration
• RAM settings
• Overclocking
• Secure Boot
• Boot order

If the problem started immediately after changing BIOS settings, consider restoring the previous known-good configuration.

Warning

Do not randomly change storage-controller mode, UEFI/Legacy mode, Secure Boot, TPM, or related boot settings. A Windows installation configured for one storage/boot mode may fail after the mode is changed.

Document existing settings before making changes.

Solution 15: Repair Boot Configuration – Advanced Users

If diagnostics indicate that the boot configuration itself is damaged, Windows Recovery Environment provides Command Prompt access.

Go to:

Troubleshoot → Advanced options → Command Prompt

Traditional recovery commands that may be useful in appropriate configurations include:

bootrec /scanos

and:

bootrec /rebuildbcd

Other Bootrec options exist, but they should not be executed blindly.

Important for Modern UEFI Systems

Many Windows 10 and Windows 11 computers use UEFI/GPT booting with an EFI System Partition. In these installations, blindly following old BIOS/MBR repair tutorials may not repair the actual problem and can complicate troubleshooting.

For UEFI systems, BCDBoot is often used when boot files genuinely need to be recreated.

The correct procedure depends on:

• Whether Windows is UEFI/GPT or Legacy/MBR
• Windows partition letter inside WinRE
• EFI System Partition location
• Disk and partition structure

For this reason, inspect the disk layout before performing manual BCD/EFI repairs.

Important: Drive Letters Can Change in Recovery Environment

Do not assume Windows is always installed on C: when using WinRE Command Prompt.

Check first.

You can use:

diskpart

then:

list volume

and exit DiskPart with:

exit

Identify the actual Windows volume before running offline repair commands.

You can also inspect likely volumes for the Windows folder.

This is especially important before running commands that modify boot configuration.

Solution 16: Run Offline SFC When Windows Does Not Boot

If Windows cannot start, SFC can be used from the recovery environment, but the correct Windows and boot partition letters must first be identified.

A typical offline syntax is:

SFC /scannow /offbootdir=<boot-drive>\ /offwindir=<windows-drive>\Windows

The exact drive letters vary by computer and may differ from those shown during normal Windows operation.

Do not simply copy C: from an online repair guide without verifying the recovery-environment disk layout.

Solution 17: Check SSD/HDD Health

A failing storage device can corrupt:

• Registry files
• Windows system files
• BCD
• User data
• Application files

Warning signs include:

• Frequent BSODs
• Extremely slow boot
• File corruption
• CHKDSK errors repeatedly returning
• Disk disappearing intermittently
• SMART warnings
• Read/write errors
• Freezing during file operations

Use the SSD/HDD manufacturer's diagnostic utility or another reputable hardware diagnostic method.

If drive failure is suspected, prioritize data backup before intensive repair attempts.

Solution 18: Analyze Windows Reliability Monitor

If Windows still starts, Reliability Monitor can help identify when the crashes began.

Search Windows for:

View reliability history

Look for:

• Windows failures
• Application failures
• Driver installations
• Updates
• Hardware errors

Check events immediately before the first BAD_SYSTEM_CONFIG_INFO crash.

The timing can reveal whether the issue followed a driver, update, application, or hardware change.

Solution 19: Check Event Viewer

Open:

Event Viewer

Review:

Windows Logs → System

Look around the time of the crash for events involving:

• Disk
• NTFS
• Storage
• WHEA
• Kernel-Power
• Service failures
• Driver failures

Remember that some events recorded around a BSOD are consequences of the crash rather than its root cause.

For example, an unexpected shutdown event confirms that Windows did not shut down cleanly, but does not by itself identify why the BSOD occurred.

Solution 20: Analyze Minidump Files

For repeated BSODs, dump-file analysis can provide significantly better evidence than guessing.

Windows commonly stores small crash dumps under:

C:\Windows\Minidump

Depending on system settings, a larger memory dump may also exist.

Microsoft's debugging tools, including WinDbg, can analyze dump files.

Useful information may include:

• Bug check code
• Bug check parameters
• Faulting module
• Loaded drivers
• Call stack
• Failure bucket information

A driver name shown in a dump should be treated as evidence to investigate, not automatically as proof that the named file itself is defective.

Solution 21: Remove Recent Hardware Changes

If BAD_SYSTEM_CONFIG_INFO began after hardware modification, temporarily return the computer to its previous configuration where practical.

Check recent changes involving:

• RAM
• SSD/HDD
• PCIe devices
• USB devices
• Graphics card
• Storage controller
• Docking station
• External hardware

If Windows starts normally after removing a recently added component, investigate compatibility, drivers, firmware, and hardware condition.

Solution 22: Check for Overclocking or Unstable Memory Profiles

CPU, GPU, and RAM instability can produce unpredictable BSODs.

If the PC is overclocked:

• Restore CPU settings to default
• Restore RAM settings to default
• Temporarily disable aggressive memory profiles if instability is suspected
• Remove manual voltage/frequency adjustments
• Test Windows again

This is especially relevant when crashes occur under heavy load or after a BIOS configuration change.

Solution 23: Reset Windows While Keeping Personal Files

If Windows remains unusable after reasonable repair attempts, Windows Recovery Environment may provide:

Troubleshoot → Reset this PC

One option may allow you to:

Keep my files

This reinstalls Windows while attempting to preserve personal files, but installed desktop applications and system configuration may be removed or reset.

Before Resetting

Whenever possible, back up:

• Documents
• Desktop
• Downloads
• Browser data
• Email data
• Accounting/business data
• Application databases
• Software license information
• Encryption recovery information
• Other critical files

Do not treat Keep my files as a substitute for a verified backup.

Solution 24: Reinstall Windows

If the operating system remains severely corrupted and hardware diagnostics are satisfactory, a clean Windows installation may be the final solution.

Before reinstalling:

1. Back up all important data.
2. Verify application/database backups.
3. Record software licenses where necessary.
4. Confirm the correct Windows edition.
5. Confirm BitLocker/device-encryption recovery information where applicable.
6. Download essential drivers if required.
7. Verify that important business data can actually be restored.

A clean installation should normally be considered after appropriate troubleshooting rather than as the first response to a single BSOD.

Recommended Troubleshooting Order

For most computers, use this order:

Step 1: Disconnect recently added external hardware.

Step 2: Undo recent MSConfig, BIOS, driver, or hardware changes.

Step 3: Try Startup Repair.

Step 4: Start Windows in Safe Mode.

Step 5: Run SFC.

Step 6: Run DISM and then SFC again.

Step 7: Check the file system/storage.

Step 8: Test RAM.

Step 9: Roll back problematic drivers or updates.

Step 10: Use System Restore.

Step 11: Analyze Reliability Monitor, Event Viewer, and crash dumps.

Step 12: Investigate BCD/EFI only if evidence points to boot-configuration damage.

Step 13: Reset or reinstall Windows only after backups and hardware checks.

This order avoids unnecessary destructive changes while moving from common and reversible fixes toward advanced recovery procedures.

Special Case: BAD_SYSTEM_CONFIG_INFO After Changing MSConfig

If the BSOD started immediately after changing:

msconfig → Boot → Advanced options

the boot configuration should be one of the first areas investigated.

Avoid using Number of processors or Maximum memory as performance tweaks.

Windows normally detects and uses the appropriate available CPU and memory resources automatically.

Special Case: BAD_SYSTEM_CONFIG_INFO After RAM Upgrade

If the error appeared immediately after adding memory:

1. Shut down the computer.
2. Disconnect power as appropriate.
3. Reseat the RAM.
4. Verify compatibility.
5. Test using the previous RAM configuration.
6. Test individual modules if necessary.
7. Run a memory diagnostic.
8. Review BIOS memory settings.

Do not assume Windows corruption until the new hardware has been ruled out.

Special Case: BAD_SYSTEM_CONFIG_INFO After SSD Cloning

If the problem started after cloning Windows to another SSD, investigate:

• EFI System Partition
• BCD entries
• Disk partition layout
• UEFI boot entry
• Boot order
• Source and destination disk configuration
• Whether the PC is booting from the old disk instead of the cloned disk

A cloning problem should be diagnosed as a boot-layout issue before performing random registry modifications.

Special Case: BAD_SYSTEM_CONFIG_INFO After Windows Update

Try:

WinRE → Troubleshoot → Advanced options → Uninstall Updates

If necessary, use:

System Restore

If Windows can enter Safe Mode, also inspect Device Manager and update history to determine what changed immediately before the first crash.

What You Should NOT Do

Avoid these common troubleshooting mistakes:

• Do not download random DLL or SYS files from third-party websites.
• Do not use untrusted registry-cleaning applications.
• Do not randomly delete registry entries.
• Do not change multiple BIOS settings simultaneously.
• Do not assume every BSOD is caused by Windows corruption.
• Do not format the computer before checking hardware and backups.
• Do not blindly execute old MBR repair instructions on a modern UEFI/GPT installation.
• Do not assume the Windows partition is C: inside WinRE.
• Do not repeatedly run repair operations on a potentially failing SSD without protecting important data first.

When Should You Suspect Hardware?

Hardware should receive increased attention when:

• Windows repeatedly corrupts after repair
• BSODs occur during Windows installation
• Multiple unrelated stop codes occur
• Memory diagnostics report errors
• SSD/HDD diagnostics report errors
• The computer freezes even outside normal Windows operation
• Crashes began immediately after RAM or storage replacement
• The machine becomes unstable under load
• WHEA hardware errors appear repeatedly

In these situations, reinstalling Windows may not solve the underlying problem.

Frequently Asked Questions (FAQ)

1. What is BAD_SYSTEM_CONFIG_INFO?

BAD_SYSTEM_CONFIG_INFO is a Windows blue-screen stop error indicating that Windows encountered invalid, inconsistent, or inaccessible system configuration information.

2. What is the BAD_SYSTEM_CONFIG_INFO bug check code?

The error is commonly associated with:

Bug Check 0x74 – BAD_SYSTEM_CONFIG_INFO

3. Can BAD_SYSTEM_CONFIG_INFO be repaired without reinstalling Windows?

Yes. Many cases can be repaired using Startup Repair, Safe Mode, SFC, DISM, System Restore, driver rollback, update removal, or correction of boot/configuration problems.

4. Can faulty RAM cause BAD_SYSTEM_CONFIG_INFO?

Yes. Defective or unstable memory can cause BSODs and can also contribute to data or system-file corruption.

5. Can an SSD cause this blue screen?

Yes. Storage failure or file-system corruption can damage system files, registry data, and boot information.

6. Why did BAD_SYSTEM_CONFIG_INFO appear after changing MSConfig?

Incorrect boot parameters, particularly forced processor or memory limits, can interfere with startup. If the error began immediately after such a change, undoing it should be a priority.

7. Should I set Number of Processors to the highest value in MSConfig?

Normally, no.

Windows automatically manages available processors. The MSConfig setting should not generally be used as a performance optimization.

8. Should Maximum Memory be enabled in MSConfig?

Normally, no. Windows automatically manages available physical memory. This setting is generally unnecessary for ordinary use and troubleshooting changes should be made carefully.

9. Can Windows Update cause BAD_SYSTEM_CONFIG_INFO?

A problem may sometimes begin after an update because of a driver, system component, boot, or compatibility issue. If timing strongly points to an update, WinRE provides update-removal and System Restore options.

10. Can a driver cause this error?

Yes. Faulty, incompatible, or corrupted drivers can contribute to Windows startup and BSOD problems.

11. Can I fix BAD_SYSTEM_CONFIG_INFO from Safe Mode?

Possibly. Safe Mode can allow you to uninstall problematic drivers/software, run SFC/DISM, inspect logs, and undo recent changes.

12. What if Windows cannot enter Safe Mode?

Use Windows Recovery Environment and try Startup Repair, System Restore, Uninstall Updates, Command Prompt, or other recovery options.

13. Does Startup Repair delete personal files?

Startup Repair is intended to repair startup-related problems rather than erase personal data. Nevertheless, maintaining a current backup is always recommended before major troubleshooting.

14. Does SFC delete personal data?

SFC is designed to verify and repair protected Windows system files. It does not normally delete personal documents.

15. What is the difference between SFC and DISM?

SFC checks and repairs protected Windows system files.

DISM can repair the Windows component store/image used by Windows servicing and by SFC.

They are often used together.

16. Should I run DISM or SFC first?

For many routine Windows repairs, you can run SFC first. If corruption cannot be repaired, run DISM RestoreHealth and then run SFC again.

17. Can CHKDSK fix BAD_SYSTEM_CONFIG_INFO?

CHKDSK can repair certain file-system problems, but it will not fix every cause of BAD_SYSTEM_CONFIG_INFO. Repeated disk errors may indicate a storage problem requiring further diagnostics.

18. Can BIOS settings cause this BSOD?

Potentially, especially after changing boot mode, storage settings, RAM configuration, or overclocking. Do not randomly change firmware settings while troubleshooting.

19. Can overclocking cause BAD_SYSTEM_CONFIG_INFO?

Unstable CPU or RAM settings can cause system crashes and corruption. Return the system to standard settings while troubleshooting.

20. Why does the PC keep restarting with BAD_SYSTEM_CONFIG_INFO?

Windows may be crashing during startup and automatically restarting after each failure. Use WinRE to access repair tools and investigate the underlying problem.

21. Can I repair BCD manually?

Yes, but manual BCD repair is an advanced procedure. The correct commands depend on whether the computer uses UEFI/GPT or Legacy BIOS/MBR and on the actual partition layout.

22. Why might C: not be my Windows drive in Command Prompt recovery?

Windows Recovery Environment can assign different drive letters from normal Windows. Always identify the Windows partition before running offline repair or boot commands.

23. Where are Windows BSOD dump files stored?

Small crash dumps are commonly located at:

C:\Windows\Minidump

Dump creation depends on Windows crash-dump settings.

24. How can I determine what actually caused the BSOD?

Check:

• Reliability Monitor
• Event Viewer
• Minidump files
• Recent Windows updates
• Recent driver changes
• Recent hardware changes
• RAM diagnostics
• SSD/HDD diagnostics

For recurring crashes, dump analysis can be particularly valuable.

25. Should I reset Windows immediately?

Usually not after a single occurrence. First investigate recent changes, system-file corruption, drivers, memory, storage, and available recovery options.

26. Will Reset this PC fix BAD_SYSTEM_CONFIG_INFO?

It may fix software-related corruption, but it will not repair defective RAM, a failing SSD, or other hardware faults.

27. Will reinstalling Windows permanently solve the error?

Only if the root cause is software-related. If RAM, storage, firmware configuration, or other hardware is defective, the error or other crashes can return.

28. What should I do if the BSOD appeared after installing new RAM?

Restore the previous memory configuration, reseat the modules, verify compatibility, disable unstable memory settings, and run memory diagnostics.

29. What should I do if the error appeared after cloning my SSD?

Check the EFI/BCD configuration, disk layout, UEFI boot entry, and boot order. Also verify that the PC is actually booting from the intended SSD.

30. When should I contact a technician?

Professional diagnosis is recommended when Windows cannot start after recovery attempts, important data is at risk, storage diagnostics indicate failure, memory tests report errors, BitLocker/encryption complicates recovery, or you are uncertain about EFI/BCD or partition modifications.

Conclusion

BAD_SYSTEM_CONFIG_INFO can look like a severe Windows failure, but it does not automatically mean Windows must be reinstalled.

The most important step is to identify what changed immediately before the first crash.

Start with reversible troubleshooting such as:

Startup Repair → Safe Mode → SFC/DISM → disk and RAM checks → driver/update rollback → System Restore

If the computer still fails, investigate crash dumps, storage health, hardware stability, and the boot configuration.

Manual BCD/EFI repairs should be performed only after confirming the actual boot mode and partition layout.

Finally, if Windows remains corrupted despite repair attempts and hardware tests are satisfactory, back up important information and consider Reset this PC or a clean Windows installation.

#Tags

#BAD_SYSTEM_CONFIG_INFO #BadSystemConfigInfo #Windows11 #Windows10 #WindowsBSOD #BSOD #BlueScreen #BlueScreenError #WindowsError #WindowsRepair #WindowsTroubleshooting #WindowsSupport #WindowsRecovery #WinRE #StartupRepair #SafeMode #SystemFileChecker #SFC #DISM #CHKDSK #WindowsBoot #BootError #BootRepair #BCD #BCDRepair #BootConfiguration #WindowsRegistry #RegistryError #SystemRestore #WindowsUpdate #WindowsUpdateError #DriverError #DriverTroubleshooting #RAM #RAMError #MemoryDiagnostic #SSD #SSDHealth #HardDiskError #WindowsCrash #CrashDump #Minidump #WinDbg #EventViewer #ReliabilityMonitor #UEFI #WindowsStartup #WindowsRecoveryEnvironment #WindowsTechnicalSupport #WindowsTips