BAD_SYSTEM_CONFIG_INFO is a Windows Blue Screen of Death (BSOD) stop error associated with bug check:

0x00000074

Microsoft defines bug check 0x74 BAD_SYSTEM_CONFIG_INFO as an error indicating a problem with the Windows Registry. In particular, the error can occur when the SYSTEM registry hive is corrupted or when critical registry keys or values required by Windows are missing or damaged.

The computer may display a message similar to:

Your device ran into a problem and needs to restart.
Stop code: BAD_SYSTEM_CONFIG_INFO

In severe cases, Windows may fail before reaching the login screen and repeatedly enter a blue-screen or Automatic Repair loop.

Although registry corruption is an important cause of this error, practical troubleshooting should also investigate boot configuration, Windows system-file corruption, storage problems, problematic drivers, recent system changes, RAM instability and incorrect BIOS/UEFI or boot-related configuration.

Technical Information

Bug Check Name: BAD_SYSTEM_CONFIG_INFO
Bug Check Code: 0x00000074
Type: Windows Stop Error / BSOD
Primary Area: Windows Registry / System Configuration
Affected Systems: Windows 11, Windows 10 and applicable Windows/Windows Server environments

Microsoft documentation states that the bug check can occur if the SYSTEM hive is corrupt or critical registry keys and values are missing.

An NTSTATUS value may also be available in parameter 4 of the bug check and can provide additional diagnostic information.

For example:

0xC000014C – Registry Corrupt

This can indicate that a file containing Windows Registry data is corrupt or could not be recovered correctly.

Common Symptoms of BAD_SYSTEM_CONFIG_INFO

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

• Blue screen immediately after switching on the computer
• BAD_SYSTEM_CONFIG_INFO stop code
• Windows repeatedly restarts
• Windows cannot reach the desktop
• Automatic Repair appears after several failed boots
• Automatic Repair cannot repair the PC
• Windows fails after a driver or Windows update
• BSOD starts after changing RAM or other hardware
• System Restore becomes necessary
• Safe Mode works but normal Windows does not
• Startup Repair reports a boot or registry-related problem
• Windows freezes or crashes during startup
• The system enters a continuous recovery loop

What Causes BAD_SYSTEM_CONFIG_INFO?

1. Corrupted Windows Registry

This is one of the most important causes.

Windows stores essential operating-system configuration information in Registry hives. If the SYSTEM hive or critical keys inside it become corrupted, Windows may be unable to initialize correctly.

Registry corruption can occur because of:

• Unexpected shutdown
• Storage corruption
• Failed software installation
• Improper registry modification
• Malware or unwanted software
• Failed Windows servicing
• Disk errors
• Software that incorrectly changes critical system configuration

Microsoft specifically identifies SYSTEM-hive corruption and missing critical Registry keys or values as possible causes of bug check 0x74.

2. Corrupted Windows System Files

Damaged or missing operating-system files can contribute to startup instability.

Common causes include:

• Power failure during an update
• Improper shutdown
• Disk corruption
• Failed Windows update
• Damaged Windows component store
• Storage hardware problems

Windows includes DISM and System File Checker for detecting and repairing many such problems.

3. Boot Configuration Data Problems

The Boot Configuration Data, or BCD, contains information Windows Boot Manager needs to locate and start Windows.

A damaged boot configuration can result in:

• Startup failure
• Recovery loops
• Boot errors
• Incorrect Windows installation being selected
• Failure after disk cloning or partition changes

Microsoft's Startup Repair is capable of addressing some corrupted BCD and startup problems.

4. Incorrect System Configuration Changes

The error can sometimes appear after configuration changes involving:

• Boot options
• Processor settings
• Memory configuration
• Startup parameters
• Registry modifications
• Boot configuration commands

Changes made through System Configuration (msconfig) or BCDEdit should therefore be treated carefully.

5. RAM Problems

Defective, unstable or incorrectly configured memory can corrupt data being processed by Windows and may contribute to apparently random BSODs.

Possible situations include:

• Faulty RAM
• Loose RAM module
• Mixed incompatible memory
• Incorrect XMP/EXPO settings
• Memory overclocking
• Defective motherboard memory slot

RAM should be investigated particularly when several different BSOD codes occur rather than only BAD_SYSTEM_CONFIG_INFO.

6. SSD or Hard-Disk Problems

Registry and Windows system files are stored on the system drive.

Storage problems can therefore cause corruption.

Possible causes include:

• SSD degradation
• HDD bad sectors
• File-system errors
• Storage controller problems
• Sudden power loss
• Loose SATA connection
• NVMe instability

A recurring BAD_SYSTEM_CONFIG_INFO error after repairing Windows should therefore trigger a storage-health investigation.

7. Problematic Device Drivers

A recently installed or incompatible driver can destabilize Windows or interfere with startup.

Pay particular attention to:

• Storage drivers
• Chipset drivers
• Graphics drivers
• Motherboard utilities
• Antivirus/security drivers
• Disk encryption software
• Backup utilities
• Low-level system-management software

8. Recent Windows Update or Software Change

If the computer was working normally and BAD_SYSTEM_CONFIG_INFO started immediately after an update or installation, the recent change becomes an important troubleshooting clue.

Windows Recovery Environment provides options to remove certain recently installed updates.

9. Incorrect BIOS/UEFI Configuration

Incorrect firmware settings can contribute to startup problems.

Examples include:

• Incorrect storage-controller mode
• Aggressive memory profile
• CPU/RAM overclocking
• Incorrect boot mode
• Changed Secure Boot configuration
• Improper boot priority

Do not randomly change BIOS settings. If the problem began immediately after BIOS changes, reverting those specific changes or loading known-good/default settings may be appropriate.

How to Fix BAD_SYSTEM_CONFIG_INFO

The safest strategy is to begin with recovery methods that make the fewest changes and proceed toward more invasive repairs.

Method 1: Restart the Computer

If BAD_SYSTEM_CONFIG_INFO occurred only once, allow Windows to restart.

A temporary hardware, driver or configuration problem does not necessarily mean the Windows installation is permanently damaged.

If the error returns, continue troubleshooting.

Method 2: Disconnect Recently Added Hardware

Shut down the PC and disconnect unnecessary external devices such as:

• USB drives
• External hard drives
• USB adapters
• Printers
• Docking stations
• Recently installed peripherals

If RAM, an SSD, graphics card or another internal component was recently installed, verify that it is correctly seated and compatible.

Restart the system.

If Windows boots normally, reconnect devices individually to identify the problematic component.

Method 3: Enter Windows Recovery Environment

If Windows cannot start normally, use Windows Recovery Environment (WinRE).

Windows normally enters recovery automatically after repeated failed startup attempts.

You can also access it using Windows installation media and selecting:

Repair your computer → Troubleshoot → Advanced options

Windows RE provides tools including:

• Startup Repair
• Startup Settings
• Command Prompt
• System Restore
• Uninstall Updates
• UEFI Firmware Settings
• System Image Recovery
• Reset this PC

Important: BitLocker-protected computers may require the BitLocker recovery key before some recovery operations can be performed.

Method 4: Run Startup Repair

From Windows Recovery Environment select:

Troubleshoot → Advanced options → Startup Repair

Choose the appropriate Windows installation/account if requested.

Startup Repair automatically checks several problems that may prevent Windows from loading.

According to Microsoft, Startup Repair can help with issues including:

• Missing or damaged system files
• Corrupted Boot Configuration Data
• Damaged startup information
• Incompatible drivers
• Registry errors

After Startup Repair completes, restart the PC.

Method 5: Try Safe Mode

From WinRE:

Troubleshoot → Advanced options → Startup Settings → Restart

Select:

Safe Mode

or:

Safe Mode with Networking

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

If Windows works correctly in Safe Mode but crashes during normal startup, investigate:

• Recently installed drivers
• Startup applications
• Antivirus/security software
• Recently installed utilities
• Background services

Uninstall or roll back the suspicious recent change and restart normally.

Method 6: Use System Restore

If System Restore was enabled before the problem occurred:

WinRE → Troubleshoot → Advanced options → System Restore

Select a restore point created before the BAD_SYSTEM_CONFIG_INFO error started.

System Restore can reverse certain system-level changes without being intended to delete normal personal documents.

It is particularly useful when the error started after:

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

Method 7: Uninstall a Recent Windows Update

If the BSOD appeared immediately after Windows Update:

Open:

WinRE → Troubleshoot → Advanced options → Uninstall Updates

Depending on the available options, Windows may allow removal of a recent quality update or other applicable update.

Restart the computer afterward.

Do not automatically assume an update is responsible simply because Windows recently updated. Use timing and other evidence to determine whether the update is a likely cause.

Method 8: Repair Windows with DISM

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

Run:

DISM.exe /Online /Cleanup-Image /RestoreHealth

Allow the operation to complete.

DISM repairs problems in the Windows component store used for servicing and system-file recovery.

Microsoft recommends running DISM before SFC when repairing a running Windows installation.

After DISM reports successful completion, continue with SFC.

Method 9: Run System File Checker

Open an elevated Command Prompt and execute:

sfc /scannow

Wait until verification reaches 100%.

SFC checks protected Windows system files and attempts to replace corrupted versions with correct copies.

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 the computer and check whether the BSOD returns.

Windows Resource Protection found corrupt files but was unable to fix some of them

Further DISM, offline repair or Windows recovery may be required.

Method 10: Run SFC When Windows Cannot Boot

SFC also supports offline Windows installations.

First determine the actual Windows drive letter from WinRE because it may not necessarily be C:.

For example, if the Windows installation is located at D:\Windows, an offline command can use parameters similar to:

sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows

Replace the drive letters with the actual configuration of the affected computer.

Do not blindly assume that Windows is C: while working from the Recovery Environment.

Method 11: Check the Windows Drive for File-System Errors

Disk/file-system corruption should be investigated, especially if the BSOD repeatedly returns.

From an elevated Command Prompt you can use CHKDSK.

For example:

chkdsk C: /f

Windows may request that the scan be scheduled for the next restart if the volume is currently in use.

For deeper physical-sector testing on traditional hard disks, technicians may use additional CHKDSK options when appropriate, but such scans can take considerable time.

If disk errors repeatedly return, check the health of the SSD/HDD rather than repeatedly repairing the file system.

Method 12: Check RAM

Press:

Windows + R

Enter:

mdsched.exe

Select:

Restart now and check for problems

Windows Memory Diagnostic will restart the PC and test memory.

For systems experiencing frequent unexplained BSODs, technicians may also:

1. Shut down the computer.
2. Disconnect power.
3. Reseat RAM modules.
4. Test one RAM module at a time.
5. Test different motherboard slots.
6. Disable memory overclocking/XMP/EXPO temporarily.
7. Use a dedicated memory-testing utility for extended testing.

If errors occur only with a particular RAM module, investigate or replace that module.

Method 13: Undo Overclocking

Return CPU, RAM and GPU settings to their normal specifications.

Temporarily disable:

• CPU overclocking
• RAM overclocking
• XMP/EXPO profiles
• GPU overclocking
• Undervolting
• Custom memory timings

Then test Windows again.

A system that appears stable during ordinary use can still generate data corruption when memory or CPU settings are marginally unstable.

Method 14: Review Recent Drivers

If Windows starts in Safe Mode:

Open:

Device Manager

Check recently changed devices.

Possible options include:

• Roll Back Driver
• Uninstall Device
• Install the correct manufacturer driver

Focus especially on changes made immediately before the BSOD began.

Avoid downloading drivers from unknown third-party driver websites.

Prefer Windows Update or the computer/component manufacturer's official support source.

Method 15: Check Event Viewer

If Windows can boot, open:

Event Viewer → Windows Logs → System

Look around the time of the crash for:

• Registry errors
• Disk errors
• NTFS errors
• Storage controller errors
• Driver failures
• Unexpected shutdown events

Microsoft specifically recommends checking the Windows System event log for registry-related events when investigating BAD_SYSTEM_CONFIG_INFO.

If a registry event identifies a specific hive or key, it can significantly narrow the diagnosis.

Method 16: Analyze the Crash Dump

For advanced troubleshooting, inspect Windows memory dump files using WinDbg.

Common dump locations include:

C:\Windows\Minidump\

and:

C:\Windows\MEMORY.DMP

A debugger can analyze the stop code and its parameters.

Microsoft specifically notes that the WinDbg:

!analyze

extension can help investigate bug check 0x74.

Parameter 4 may contain an NTSTATUS value that provides additional information.

For example, an NTSTATUS result of:

0xC000014C

indicates Registry corruption.

Dump analysis is particularly useful when BAD_SYSTEM_CONFIG_INFO keeps returning after apparently successful repairs.

Method 17: Be Careful with BCD Repair Commands

Some troubleshooting guides immediately recommend commands such as:

bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd

These commands can be useful for particular boot problems, but they should not be treated as a universal BAD_SYSTEM_CONFIG_INFO fix.

Modern UEFI/GPT systems boot differently from older BIOS/MBR systems, and blindly changing boot configuration can create additional startup problems.

Start with Startup Repair whenever practical.

Use manual BCD/boot repair only when diagnostics indicate that the boot configuration is actually damaged and preferably after identifying whether the system uses UEFI/GPT or legacy BIOS/MBR.

Method 18: Check msconfig Boot Settings

Incorrect manual configuration in System Configuration can cause startup problems.

Press:

Windows + R

Type:

msconfig

Check the Boot tab and advanced boot settings.

If you previously manually configured:

• Number of processors
• Maximum memory
• Debug options
• Alternative boot parameters

return them to their previous/default state unless there is a specific technical reason for those settings.

A common misconception is that selecting the maximum processor count or maximum memory in msconfig improves Windows performance. These settings are primarily diagnostic/boot controls and normally do not need to be manually configured for everyday operation.

Method 19: Check BIOS/UEFI Settings

Enter the BIOS/UEFI firmware configuration and check for recent changes.

Pay attention to:

• Storage controller mode
• Boot mode
• Boot priority
• RAM profile
• CPU overclocking
• Secure Boot
• UEFI/Legacy configuration

If the problem started immediately after changing firmware settings, restore the previous known-working settings.

Warning: Changing storage-controller modes such as AHCI/RAID without understanding the existing Windows configuration can make Windows unbootable.

Method 20: Check SSD/HDD Health

If Registry corruption repeatedly returns, investigate the physical storage device.

Warning signs include:

• Repeated file corruption
• Frequent CHKDSK errors
• Very slow startup
• Disk disappearing from BIOS
• Windows freezing during file access
• SMART warnings
• Event Viewer disk/controller errors
• Multiple unrelated corrupted files

Back up important data immediately if drive failure is suspected.

Replacing a failing SSD/HDD is more important than repeatedly repairing Windows on an unreliable drive.

Method 21: Reset Windows

If repair methods fail, Windows Recovery Environment provides Reset this PC.

Depending on the available Windows version/options, you may be able to reinstall Windows while retaining personal files.

However, applications and configuration may need to be reinstalled.

Always create a backup before reset whenever the data is accessible.

Method 22: Reinstall Windows

A clean installation may be appropriate when:

• Registry corruption is extensive
• Windows cannot be repaired
• System Restore is unavailable
• Startup Repair repeatedly fails
• DISM/SFC cannot repair Windows
• Boot configuration is severely damaged
• Malware damage is suspected
• Multiple Windows components are corrupted

Before reinstalling Windows, back up important files and confirm that the SSD/HDD and RAM are healthy. Otherwise, a hardware fault may corrupt the fresh installation again.

Recommended Troubleshooting Sequence

For most BAD_SYSTEM_CONFIG_INFO cases, use this order:

Step 1: Restart once and confirm whether the error repeats.

Step 2: Disconnect recently added unnecessary hardware.

Step 3: Enter Windows Recovery Environment.

Step 4: Run Startup Repair.

Step 5: Try Safe Mode.

Step 6: Undo recent driver/software changes.

Step 7: Use System Restore if an appropriate restore point exists.

Step 8: Uninstall a recent update if the timing strongly indicates it caused the problem.

Step 9: Run DISM.

DISM /Online /Cleanup-Image /RestoreHealth

Step 10: Run SFC.

sfc /scannow

Step 11: Check the Windows file system and storage health.

Step 12: Test RAM.

Step 13: Reset overclocking/XMP/EXPO and review BIOS/UEFI changes.

Step 14: Examine Event Viewer and crash dumps.

Step 15: Investigate BCD manually only if evidence points to boot-configuration corruption.

Step 16: Use Reset this PC or reinstall Windows if repair is unsuccessful.

Important Warning About Registry Repair

BAD_SYSTEM_CONFIG_INFO is closely associated with Registry problems, but that does not mean users should start manually deleting or replacing Registry files.

Incorrect Registry modifications can make Windows completely unbootable.

Avoid blindly following instructions that tell you to copy, delete or overwrite files under locations such as:

C:\Windows\System32\Config

unless you have:

• A verified backup
• A clear understanding of the affected hive
• Confirmed recovery media
• Appropriate technical knowledge

Modern Windows recovery behavior can also differ from instructions written for older Windows versions.

Use supported recovery methods such as Startup Repair, System Restore, DISM, SFC and Windows Recovery Environment first.

How to Prevent BAD_SYSTEM_CONFIG_INFO

Although every BSOD cannot be prevented, the risk can be reduced.

Keep Windows Updated

Install security and reliability updates from trusted sources.

Avoid Registry Cleaner Utilities

Aggressive registry-cleaning applications can remove or modify configuration unnecessarily.

Do Not Modify Registry Keys Without a Backup

Before major Registry changes, create an appropriate backup or restore point.

Maintain Free Disk Space

Windows requires sufficient storage for:

• Updates
• Temporary files
• Paging
• Servicing
• Recovery operations

Monitor SSD/HDD Health

Replace drives showing persistent errors or health warnings.

Use Stable RAM Settings

Avoid unstable overclocking and memory timings on production computers.

Use Correct Drivers

Prefer drivers from Windows Update or the hardware manufacturer's official support channel.

Maintain Backups

Keep important business data backed up independently of the Windows system disk.

Frequently Asked Questions (FAQ)

1. What does BAD_SYSTEM_CONFIG_INFO mean?

BAD_SYSTEM_CONFIG_INFO is Windows bug check 0x00000074. Microsoft associates it primarily with errors involving the Windows Registry, including corruption of the SYSTEM hive or missing critical Registry information.

2. Is BAD_SYSTEM_CONFIG_INFO a hardware error?

Not necessarily.

It can be caused by Windows Registry or configuration corruption, but hardware problems such as unstable RAM or failing storage can contribute to corruption and recurring BSODs.

3. Can faulty RAM cause BAD_SYSTEM_CONFIG_INFO?

It can contribute to system instability or corruption. RAM becomes particularly suspicious when the PC displays several different BSOD codes, crashes randomly or fails memory testing.

4. Can an SSD cause BAD_SYSTEM_CONFIG_INFO?

A failing or unstable SSD can corrupt Windows files or Registry data. Repeated corruption after successful repairs is a strong reason to investigate storage health.

5. Can I fix BAD_SYSTEM_CONFIG_INFO without reinstalling Windows?

Often, yes.

Possible recovery methods include:

• Startup Repair
• Safe Mode
• System Restore
• Removing a problematic update
• DISM
• SFC
• Driver rollback
• Correcting boot configuration
• Resolving RAM or disk problems

Reinstallation should normally be considered after less destructive repair methods fail.

6. What is the first thing I should try?

If the error repeatedly prevents Windows from starting, enter Windows Recovery Environment and try Startup Repair.

7. What is error code 0x00000074?

It is the numerical bug-check value for:

BAD_SYSTEM_CONFIG_INFO

8. What does NTSTATUS 0xC000014C mean?

In this context it indicates that Registry data is corrupt or could not be correctly recovered.

9. Should I run SFC or DISM first?

For a running Windows installation, Microsoft recommends running:

DISM.exe /Online /Cleanup-Image /RestoreHealth

followed by:

sfc /scannow

DISM repairs the Windows image/component store that SFC may rely on when replacing damaged system files.

10. Can Startup Repair fix BAD_SYSTEM_CONFIG_INFO?

It may. Startup Repair is designed to diagnose several startup-related problems including damaged system files, boot configuration problems and certain Registry errors.

11. Will System Restore delete my personal files?

System Restore is designed to revert system changes such as drivers, Registry configuration and installed software state rather than ordinary personal documents. Nevertheless, important data should always be backed up before major recovery work when possible.

12. Can a Windows Update cause this error?

A failed or problematic update can sometimes precede startup or system corruption. If the error began immediately after an update, WinRE's Uninstall Updates option may be useful.

13. Can a driver cause BAD_SYSTEM_CONFIG_INFO?

A problematic driver or low-level system utility can contribute to Windows instability. Safe Mode is useful for determining whether the problem disappears when Windows starts with a reduced driver/service set.

14. Why does my computer keep restarting with BAD_SYSTEM_CONFIG_INFO?

Windows is encountering a critical condition during startup, generating the bug check and restarting. Because the underlying problem remains, the same process repeats.

Enter WinRE instead of continuously allowing the machine to reboot.

15. What if Automatic Repair cannot repair my PC?

Try other WinRE options including:

• System Restore
• Startup Settings/Safe Mode
• Uninstall Updates
• Command Prompt
• Reset this PC

Advanced technicians can then investigate offline Windows files, storage, Registry events and boot configuration.

16. Should I use bootrec commands immediately?

No.

BOOTREC is useful for specific boot-record or BCD problems, but BAD_SYSTEM_CONFIG_INFO is not automatically a BCD error. Diagnose the startup problem first and use Startup Repair before making unnecessary boot changes.

17. Does sfc /scannow repair the Registry?

SFC primarily verifies and repairs protected Windows system files. It is not a general-purpose Registry repair utility. However, system-file corruption may exist alongside Registry problems, so SFC remains an important troubleshooting step.

18. Can CHKDSK fix BAD_SYSTEM_CONFIG_INFO?

CHKDSK can repair certain file-system problems, which may help if disk corruption contributed to damaged Windows data. It does not directly solve every BAD_SYSTEM_CONFIG_INFO condition.

19. Should I use a Registry cleaner?

Generally, no.

Registry-cleaning utilities are not a recommended solution for this BSOD and unnecessary Registry modification may make the problem worse.

20. When should I replace the SSD?

Investigate replacement when you find evidence such as:

• SMART/health warnings
• Recurring file corruption
• Repeated disk errors
• Read/write failures
• SSD disappearing intermittently
• Windows repeatedly becoming corrupted after repair

Back up data immediately if drive failure is suspected.

21. When should I reinstall Windows?

Consider reinstalling Windows when supported recovery methods fail, Registry/system corruption is extensive, and hardware tests indicate that RAM and storage are reliable.

22. Can BAD_SYSTEM_CONFIG_INFO return after reinstalling Windows?

Yes.

If the underlying cause is failing RAM, a defective SSD, unstable overclocking, firmware configuration or another hardware problem, a fresh Windows installation can eventually fail again.

Repeated corruption after a clean installation strongly suggests that hardware and firmware configuration deserve closer investigation.

Conclusion

BAD_SYSTEM_CONFIG_INFO (0x00000074) is a serious Windows stop error strongly associated with Windows Registry and system-configuration problems. Microsoft specifically identifies corruption of the SYSTEM Registry hive or missing critical Registry keys and values as potential causes.

The error does not automatically mean that Windows must be formatted.

Start with Windows Recovery Environment and Startup Repair, then investigate Safe Mode, System Restore and recent system changes. For Windows corruption, run DISM followed by SFC. If the error persists, examine disk health, RAM stability, drivers, BIOS/UEFI settings, Event Viewer and crash dumps.

Avoid random Registry modifications and unnecessary BCD commands. If corruption repeatedly returns even after successful Windows repair, investigate the underlying SSD/HDD, RAM and hardware configuration before reinstalling Windows.

#tags

#BAD_SYSTEM_CONFIG_INFO #BadSystemConfigInfo #Windows11 #Windows10 #WindowsBSOD #BSOD #BlueScreen #BlueScreenOfDeath #WindowsError #WindowsTroubleshooting #WindowsRepair #WindowsRecovery #WindowsRecoveryEnvironment #WinRE #StartupRepair #WindowsStartup #WindowsBoot #BootError #WindowsBootRepair #WindowsRegistry #RegistryError #RegistryCorruption #SystemHive #WindowsSystemFiles #SystemFileChecker #SFC #SFCScannow #DISM #DISMRestoreHealth #WindowsRepairCommands #BCD #BootConfigurationData #Bootrec #WindowsSafeMode #SafeMode #SystemRestore #WindowsUpdate #WindowsDrivers #DriverError #WindowsMemoryDiagnostic #RAMError #MemoryTest #SSDHealth #HardDriveError #CHKDSK #WindowsCrash #StopCode #BugCheck #Error0x74 #WindowsTechnicalSupport