MACHINE_CHECK_EXCEPTION is a serious Windows Blue Screen of Death (BSOD) error indicating that Windows has received information about a low-level hardware problem detected by the processor.

The traditional bug check associated with MACHINE_CHECK_EXCEPTION is:

Bug Check: 0x0000009C

Stop Code: MACHINE_CHECK_EXCEPTION

Unlike many BSOD errors caused primarily by software or device drivers, MACHINE_CHECK_EXCEPTION frequently points toward a problem involving the CPU, memory subsystem, motherboard, power delivery, system temperatures, firmware configuration, or another hardware component.

Modern processors contain hardware-error-detection mechanisms collectively associated with Machine Check Architecture (MCA). These mechanisms can detect certain internal processor, cache, bus, memory-controller, and system hardware errors.

When Windows receives a machine-check condition that cannot safely be recovered from, it may stop the system to protect data and prevent further corruption.

Therefore, repeated MACHINE_CHECK_EXCEPTION errors should not be treated as ordinary Windows crashes.

MACHINE_CHECK_EXCEPTION vs WHEA_UNCORRECTABLE_ERROR

An important point for modern Windows systems is that you may encounter WHEA_UNCORRECTABLE_ERROR (0x124) instead of MACHINE_CHECK_EXCEPTION.

Windows Hardware Error Architecture (WHEA) is Microsoft's framework for reporting hardware errors.

Depending on the Windows version, processor architecture, firmware, and type of hardware fault, similar underlying hardware problems may appear as:

• MACHINE_CHECK_EXCEPTION
• WHEA_UNCORRECTABLE_ERROR
• CLOCK_WATCHDOG_TIMEOUT
• Hardware-related random restarts
• WHEA-Logger events in Event Viewer

Therefore, if you are troubleshooting MACHINE_CHECK_EXCEPTION, checking WHEA-related Event Viewer records can also be extremely useful.

Common Symptoms of MACHINE_CHECK_EXCEPTION

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

• Blue screen displaying MACHINE_CHECK_EXCEPTION
• Stop code 0x0000009C
• Sudden restart without warning
• System freezes before restarting
• BSOD during Windows startup
• Crash while gaming
• Crash during video rendering
• Crash during CPU-intensive operations
• Crash while installing Windows
• Random system instability
• Computer shutting down under heavy load
• BSOD shortly after installing new RAM
• BSOD after CPU replacement
• BSOD after enabling XMP or EXPO
• BSOD after CPU overclocking
• BSOD after undervolting
• BSOD after a BIOS/UEFI update
• WHEA hardware errors appearing in Event Viewer

The timing of the crash can provide an important troubleshooting clue.

For example, crashes occurring mainly during heavy CPU loads may point toward CPU stability, cooling, motherboard VRM, overclocking, or power-supply issues.

What Causes MACHINE_CHECK_EXCEPTION?

There is no single cause. The error may originate from several components.

1. CPU or Processor Instability

The processor is one of the first components to investigate.

Possible CPU-related causes include:

• Failing processor
• CPU overheating
• Incorrect CPU voltage
• Aggressive overclocking
• Unstable undervolting
• CPU cache errors
• Internal processor errors
• CPU memory-controller instability
• Incorrect BIOS CPU settings

A processor does not necessarily need to be completely dead to cause MACHINE_CHECK_EXCEPTION.

A marginally unstable processor can work normally during light workloads but fail when placed under sustained load.

2. CPU Overclocking

Overclocking is a common cause of hardware-related BSODs.

Even an overclock that appeared stable previously can become unstable because of:

• Higher ambient temperature
• Aging components
• BIOS changes
• Different workloads
• Memory configuration changes
• Voltage adjustments
• Cooling degradation

For troubleshooting, always return the CPU to its manufacturer-supported default configuration.

3. CPU Undervolting

Reducing processor voltage can reduce heat and power consumption, but excessive undervolting can create computational instability.

If MACHINE_CHECK_EXCEPTION started after changing:

• Core voltage
• CPU offset voltage
• Curve Optimizer
• Intel voltage settings
• AMD PBO settings

restore the settings to defaults before investigating other components.

4. CPU Overheating

Excessive temperature can cause instability and hardware protection events.

Possible causes include:

• Dust-blocked heatsink
• Failed CPU fan
• Incorrect cooler mounting
• Dried or poorly applied thermal compound
• Failed liquid cooling pump
• Restricted airflow
• Extremely high ambient temperature

Check both idle and load temperatures.

A CPU that looks normal at idle can overheat rapidly under load.

5. Faulty or Unstable RAM

Memory problems can also contribute to machine-check conditions.

Possible causes include:

• Defective RAM module
• Incompatible RAM
• Mixed memory kits
• Incorrect memory voltage
• Excessive memory frequency
• Incorrect memory timings
• Faulty DIMM slot
• Memory-controller instability

If the issue started after adding or replacing memory, RAM should be considered a high-priority suspect.

6. XMP or EXPO Memory Profiles

XMP and EXPO allow memory to operate using performance profiles rather than conservative default settings.

Although commonly used, enabling such a profile can expose instability depending on the:

• CPU memory controller
• Motherboard
• BIOS version
• RAM kit
• Number of installed DIMMs
• Memory frequency and timings

For diagnosis:

1. Enter BIOS/UEFI.
2. Disable XMP or EXPO.
3. Run the memory at default supported settings.
4. Test the computer again.

If the crashes disappear, investigate memory-profile stability rather than assuming Windows is damaged.

7. Motherboard Problems

A defective motherboard can generate hardware errors that appear to originate from other components.

Possible motherboard-related causes include:

• Defective VRM
• Damaged CPU socket
• Bent socket pins
• Failing capacitors
• Damaged traces
• Faulty DIMM slots
• PCIe instability
• BIOS corruption
• Power-delivery instability

Motherboard diagnosis is particularly important when multiple otherwise-known-good components behave unpredictably in the same system.

8. Power Supply Problems

A weak, failing, or inadequate PSU can cause system instability.

Symptoms may include:

• Random restart
• BSOD under load
• Shutdown while gaming
• Crash when GPU usage increases
• Instability when both CPU and GPU are heavily loaded

Check whether the PSU is appropriately sized and whether its power connections are secure.

A PSU can also deteriorate over time even if its rated wattage appears sufficient.

9. BIOS/UEFI Problems

Firmware plays a major role in processor initialization, memory training, power management, and hardware configuration.

MACHINE_CHECK_EXCEPTION may occur because of:

• Outdated BIOS
• Problematic BIOS update
• Incorrect BIOS settings
• Unstable CPU configuration
• Memory compatibility problems
• Incorrect voltage settings
• Firmware bugs

Updating BIOS can help in some situations, but firmware updates should be performed carefully.

10. GPU or PCIe Device Problems

Although MACHINE_CHECK_EXCEPTION often focuses attention on the CPU, other hardware can also contribute to low-level instability.

Potential components include:

• Graphics card
• PCIe expansion card
• NVMe controller
• RAID controller
• Network adapter
• PCIe riser
• External hardware connected through expansion controllers

If the problem began after installing new hardware, temporarily remove that hardware and retest.

11. Storage Hardware Problems

Storage is not usually the first component associated with a processor machine-check event, but storage and controller problems can contribute to system instability.

Check:

• SSD health
• NVMe temperature
• SATA cables
• Storage controller
• Firmware
• PCIe/NVMe slot
• SMART status

12. Chipset or Low-Level Drivers

MACHINE_CHECK_EXCEPTION is strongly associated with hardware, but software should not be completely ignored.

Low-level drivers and firmware can influence hardware operation.

Important components include:

• Motherboard chipset drivers
• Intel chipset components
• AMD chipset drivers
• Storage controller drivers
• GPU drivers
• BIOS/UEFI firmware

Use drivers supplied by the hardware manufacturer or other trusted official sources.

Step-by-Step Troubleshooting MACHINE_CHECK_EXCEPTION

Step 1: Identify What Changed

Before changing Windows settings, determine whether anything changed shortly before the crashes began.

Ask:

• Was RAM recently upgraded?
• Was a new CPU installed?
• Was the graphics card changed?
• Was BIOS updated?
• Was XMP/EXPO enabled?
• Was CPU overclocking enabled?
• Was CPU undervolting configured?
• Was a new SSD/NVMe installed?
• Was the PSU changed?
• Was the computer physically moved or serviced?

This can dramatically reduce troubleshooting time.

Step 2: Reset BIOS/UEFI to Default Settings

For hardware-related BSOD troubleshooting, removing custom performance settings is one of the most important steps.

Enter BIOS/UEFI and select an option such as:

• Load Optimized Defaults
• Load Setup Defaults
• Restore Defaults

The exact wording varies by manufacturer.

Save the settings and restart.

Test Windows before making additional BIOS changes.

Step 3: Disable Overclocking

Disable all manual or automatic overclocking temporarily.

This includes:

• CPU multiplier overclock
• Base clock changes
• Manual voltage tuning
• Automatic motherboard enhancement features
• GPU overclocking
• Memory overclocking

The objective is to establish a stable baseline.

Step 4: Disable XMP or EXPO

If XMP or EXPO is enabled, turn it off temporarily.

Run the memory at conservative/default settings and observe the system.

If MACHINE_CHECK_EXCEPTION disappears after disabling the profile, investigate memory compatibility and stability.

Step 5: Check CPU Temperature

Monitor CPU temperature while the system is idle and while performing normal workloads.

Look for:

• Rapid temperature increases
• Thermal throttling
• CPU fan failure
• Pump failure
• Abnormally high idle temperature

If overheating is detected:

1. Shut down the computer.
2. Disconnect power.
3. Inspect the CPU cooler.
4. Remove dust.
5. Verify fan operation.
6. Verify pump operation on liquid cooling systems.
7. Reseat the cooler if necessary.
8. Replace thermal compound where appropriate.

Do not continue stress testing a system that is clearly overheating.

Step 6: Check RAM

Start with Windows Memory Diagnostic.

Press:

Windows + R

Enter:

mdsched.exe

Select:

Restart now and check for problems

For deeper diagnosis, a dedicated bootable memory-testing utility can be used.

Remember that intermittent memory errors may require extended testing.

Step 7: Test RAM Modules Individually

If multiple RAM modules are installed:

1. Shut down the PC.
2. Disconnect power.
3. Remove all but one RAM module.
4. Test the system.
5. Repeat with each module.
6. Test different DIMM slots if necessary.

This can help distinguish between:

• Faulty RAM
• Faulty DIMM slot
• Memory-controller problem
• Memory configuration problem

Always follow the motherboard manufacturer's recommended slot configuration.

Step 8: Check Event Viewer

Windows may record hardware-related information before or around the crash.

Open:

Event Viewer → Windows Logs → System

Look for entries involving:

• WHEA-Logger
• Hardware Error
• Machine Check
• Processor
• PCI Express
• Memory

Pay attention to events immediately before the BSOD.

A WHEA event may provide clues about whether the reported problem relates to the processor, cache hierarchy, memory, or PCI Express subsystem.

Step 9: Check Reliability Monitor

Press:

Windows + R

Enter:

perfmon /rel

Reliability Monitor provides a timeline of:

• Windows failures
• Application crashes
• Hardware errors
• Driver failures
• Updates
• Unexpected shutdowns

Check whether the first MACHINE_CHECK_EXCEPTION coincides with a driver, Windows update, BIOS change, or software installation.

Step 10: Update BIOS/UEFI Carefully

Check the PC or motherboard manufacturer's support resources for BIOS updates.

A BIOS update may include:

• CPU microcode updates
• Memory compatibility improvements
• Stability fixes
• Processor support changes
• PCIe fixes

However, do not update BIOS casually on a severely unstable computer.

An interrupted firmware update can make the motherboard unbootable.

Use the manufacturer's recommended firmware-update procedure and ensure stable power.

Step 11: Update Chipset Drivers

Install current chipset/platform drivers appropriate for your system.

This is particularly relevant after:

• Fresh Windows installation
• Motherboard replacement
• Major Windows upgrade
• CPU upgrade

Avoid random third-party "driver updater" utilities for critical platform drivers.

Step 12: Inspect Power Connections

Turn off and unplug the PC before physically inspecting internal components.

Check:

• 24-pin motherboard connector
• CPU EPS power connector
• GPU power connector
• Modular PSU-side connections
• Loose adapters
• Damaged cables

A partially seated power connector can produce intermittent instability.

Step 13: Check the PSU

If possible, test with a known-good PSU that is correctly rated for the system.

This is especially important when the computer crashes:

• During gaming
• During rendering
• During CPU stress
• During simultaneous CPU/GPU load

Do not open a PSU enclosure. Internal capacitors can retain dangerous voltages even after power is disconnected.

Step 14: Reseat Hardware

If the machine has recently been moved, serviced, or upgraded, reseat appropriate components.

Examples include:

• RAM
• Graphics card
• PCIe cards
• Storage connectors

CPU reseating should generally be reserved for experienced technicians because socket damage can occur if handled incorrectly.

Step 15: Remove Recently Installed Hardware

Temporarily disconnect nonessential recently added hardware.

Examples:

• New GPU
• Additional RAM
• PCIe network card
• Capture card
• NVMe SSD
• USB expansion card

If the crashes stop, reconnect components systematically to isolate the source.

Step 16: Run System File Checker

Although MACHINE_CHECK_EXCEPTION is often hardware-related, checking Windows system files can rule out additional operating-system corruption.

Open Command Prompt or Terminal as Administrator and run:

SFC /scannow

Wait until verification reaches 100%.

Restart Windows afterward.

Step 17: Run DISM

On supported Windows versions, run:

DISM /Online /Cleanup-Image /RestoreHealth

After DISM completes, run:

SFC /scannow

again.

These commands repair Windows components, but they cannot repair physically defective hardware.

Step 18: Check the System Drive

Run:

chkdsk C: /scan

For deeper repair, CHKDSK may require an offline/restart operation.

Also inspect SSD or HDD health using the drive manufacturer's diagnostic software where available.

Step 19: Analyze the Crash Dump

Windows may create dump files after a BSOD.

Common locations include:

C:\Windows\Minidump\

and:

C:\Windows\MEMORY.DMP

Microsoft WinDbg can be used for advanced analysis.

A common initial command is:

!analyze -v

For hardware-related crashes, dump analysis may provide information about:

• Bug check parameters
• Processor involved
• Machine-check records
• Hardware error structures
• Suspected subsystem

However, do not assume that a driver name appearing in a dump automatically means that driver caused the hardware failure.

MACHINE_CHECK_EXCEPTION During Gaming

If the error happens primarily during gaming, investigate:

1. CPU temperature
2. GPU temperature
3. PSU capacity and condition
4. CPU overclock
5. GPU overclock
6. XMP/EXPO
7. RAM stability
8. GPU seating and power connections
9. BIOS stability
10. Chipset and GPU drivers

Gaming can expose marginal hardware because the CPU, GPU, RAM, motherboard, and PSU may all experience substantial load simultaneously.

MACHINE_CHECK_EXCEPTION During Windows Startup

If Windows cannot boot normally:

1. Enter BIOS and load defaults.
2. Disable XMP/EXPO.
3. Disable overclocking.
4. Remove recently installed hardware.
5. Test RAM.
6. Attempt Windows Recovery Environment.
7. Try Safe Mode if accessible.
8. Check hardware connections.
9. Run offline diagnostics where available.

If the BSOD occurs even while booting installation or diagnostic media, suspicion shifts more strongly toward hardware or firmware.

MACHINE_CHECK_EXCEPTION After Installing New RAM

If the error began immediately after a memory upgrade:

• Confirm RAM compatibility.
• Verify modules are fully seated.
• Check recommended DIMM slots.
• Disable XMP/EXPO.
• Test each module individually.
• Run memory diagnostics.
• Update BIOS if the manufacturer documents relevant memory compatibility improvements.

Mixed memory kits can be particularly difficult to stabilize even when their advertised specifications appear similar.

MACHINE_CHECK_EXCEPTION After BIOS Update

If the problem started immediately after updating BIOS:

1. Load BIOS defaults.
2. Reconfigure only essential settings.
3. Leave overclocking disabled.
4. Disable XMP/EXPO temporarily.
5. Check CPU and RAM detection.
6. Review the motherboard manufacturer's BIOS notes.
7. Consider BIOS recovery or rollback only when officially supported.

Do not flash random or unofficial firmware.

MACHINE_CHECK_EXCEPTION After CPU Upgrade

Check:

• Whether the motherboard supports the CPU
• Required BIOS version
• CPU power requirements
• CPU cooler compatibility
• Socket condition
• EPS CPU power connection
• Memory compatibility
• CPU temperature

If the previous processor works correctly in the same machine while the new processor consistently fails, CPU compatibility, firmware, power, cooling, or the replacement CPU itself requires investigation.

Advanced Diagnosis: WHEA-Logger

Event Viewer may contain WHEA-Logger events providing additional hardware information.

The event may reference components such as:

• Processor Core
• Cache Hierarchy
• Memory
• PCI Express
• Bus/Interconnect

These details can significantly narrow the investigation.

For example, repeated cache hierarchy errors associated with the same processor/core under stock settings deserve closer investigation of CPU stability, temperature, motherboard power delivery, and the processor itself.

Can Reinstalling Windows Fix MACHINE_CHECK_EXCEPTION?

Sometimes—but it should not be your first assumption.

A Windows reinstall may help when the problem is actually related to:

• Corrupted system files
• Problematic low-level drivers
• Incorrect chipset drivers
• Software conflicts

However, reinstalling Windows will not fix:

• Defective CPU
• Faulty RAM
• Failed motherboard
• Bad PSU
• CPU overheating
• Damaged CPU socket
• Unstable overclock
• Hardware-level electrical instability

If the same error occurs during a fresh Windows installation, hardware diagnosis becomes even more important.

Recommended Troubleshooting Order

For an efficient diagnosis, use approximately this order:

1. Load BIOS defaults

2. Disable CPU/GPU overclocking

3. Disable XMP/EXPO

4. Check CPU temperature and cooling

5. Check Event Viewer for WHEA events

6. Test RAM

7. Update appropriate BIOS/chipset firmware and drivers

8. Inspect PSU and power connections

9. Remove recently installed hardware

10. Analyze BSOD dump files

11. Test with known-good components

12. Investigate motherboard or CPU failure

This order avoids unnecessarily reinstalling Windows before obvious hardware-instability causes have been eliminated.

When Should You Suspect a Failing CPU?

CPU failure is less common than configuration, cooling, memory, or power problems, but it can happen.

CPU failure becomes more plausible when:

• Errors occur at completely stock settings.
• CPU temperatures are normal.
• Known-good RAM has been tested.
• A known-good PSU has been tested.
• BIOS is correctly configured.
• Motherboard compatibility is confirmed.
• Crashes consistently occur under CPU load.
• Hardware error records repeatedly implicate the processor.
• Another compatible processor works correctly in the same platform.

Component substitution by an experienced technician is often the most conclusive test.

When Should You Suspect the Motherboard?

Consider motherboard failure when:

• Different RAM modules fail in the same slot.
• PCIe devices behave unpredictably.
• CPU power delivery appears unstable.
• There is visible physical damage.
• CPU socket pins are damaged.
• Known-good CPU/RAM/PSU components still produce hardware errors.
• BIOS behavior is abnormal.
• The computer fails POST intermittently.

Motherboard problems can imitate CPU, RAM, storage, and GPU faults, so diagnosis should be systematic.

Important Data Protection Advice

Repeated hardware crashes can eventually lead to:

• File corruption
• Filesystem damage
• Application database corruption
• Interrupted Windows updates
• Damaged user profiles

If the computer still operates long enough to copy data, back up important information before performing prolonged stress tests or extensive hardware troubleshooting.

This is particularly important for servers and business systems containing accounting, database, email, or application data.

FAQ

1. What does MACHINE_CHECK_EXCEPTION mean?

It means Windows received a serious machine-check/hardware error indication and stopped because continuing operation could be unsafe.

2. What is the MACHINE_CHECK_EXCEPTION bug check code?

The traditional bug check code is:

0x0000009C

3. Is MACHINE_CHECK_EXCEPTION a hardware problem?

Very often, yes. Common areas include CPU stability, RAM, motherboard, cooling, PSU, BIOS settings, and hardware overclocking. Firmware and low-level software should also be checked.

4. Can RAM cause MACHINE_CHECK_EXCEPTION?

Yes. Faulty or unstable memory, incorrect timings, XMP/EXPO instability, bad DIMM slots, or memory-controller problems can contribute to hardware errors.

5. Can overheating cause this BSOD?

Yes. CPU overheating or unstable hardware caused by excessive temperature can produce severe system instability.

6. Can overclocking cause MACHINE_CHECK_EXCEPTION?

Yes. CPU, memory, or GPU overclocking can destabilize the system. Restore default settings during diagnosis.

7. Can undervolting cause MACHINE_CHECK_EXCEPTION?

Yes. An overly aggressive undervolt can make a CPU unstable even when temperatures are low.

8. Should I disable XMP or EXPO?

Temporarily disabling XMP/EXPO is an excellent diagnostic step when investigating hardware-related BSODs.

9. Can a bad PSU cause MACHINE_CHECK_EXCEPTION?

Yes. Unstable or insufficient power can produce hardware instability, especially under heavy workloads.

10. Can a faulty motherboard cause this error?

Yes. Motherboard power delivery, CPU socket, DIMM slots, PCIe subsystem, or other board-level failures can contribute.

11. Can a graphics card cause MACHINE_CHECK_EXCEPTION?

Potentially. GPU, PCIe, motherboard, and PSU problems can cause low-level system instability, although the CPU and memory subsystem are usually high-priority areas to investigate.

12. Should I reinstall Windows?

Not initially. First investigate BIOS settings, overclocking, temperatures, RAM, PSU, and hardware errors. Reinstall Windows only when evidence suggests operating-system or driver corruption.

13. Can BIOS cause MACHINE_CHECK_EXCEPTION?

Yes. Incorrect settings, firmware bugs, unstable memory configuration, CPU settings, or compatibility problems can contribute.

14. Should I update BIOS?

A relevant BIOS update can improve CPU compatibility, memory stability, and firmware behavior. Follow the motherboard or computer manufacturer's instructions carefully.

15. Can MACHINE_CHECK_EXCEPTION damage my computer?

The BSOD itself is a protective response. However, the underlying hardware problem may be serious, and repeated crashes can contribute to data or filesystem corruption.

16. Where are BSOD dump files stored?

Common locations are:

C:\Windows\Minidump\

and:

C:\Windows\MEMORY.DMP

depending on Windows crash-dump configuration.

17. How can I analyze MACHINE_CHECK_EXCEPTION?

Use Event Viewer, Reliability Monitor, hardware diagnostics, temperature monitoring, memory testing, and Microsoft WinDbg for crash-dump analysis.

18. Why does MACHINE_CHECK_EXCEPTION happen only while gaming?

Gaming places heavy load on the CPU, GPU, memory, motherboard, cooling system, and PSU. Marginal hardware may therefore fail only under gaming workloads.

19. Why did the error start after installing new RAM?

The new memory may be defective, incompatible, incorrectly installed, or unstable at its configured XMP/EXPO frequency.

20. What if MACHINE_CHECK_EXCEPTION continues after reinstalling Windows?

If the error continues on a clean Windows installation—especially with BIOS defaults—it strongly justifies deeper hardware, firmware, temperature, RAM, motherboard, CPU, and PSU testing.

Final Technical Summary

MACHINE_CHECK_EXCEPTION (0x0000009C) is a serious Windows stop error that should trigger a hardware-first troubleshooting strategy.

Do not immediately assume Windows itself is damaged.

Start by restoring BIOS defaults and removing all overclocking, undervolting, XMP/EXPO, and other performance tuning. Then inspect CPU temperatures, test memory, review WHEA-Logger events, verify BIOS and chipset support, inspect power connections, and investigate the PSU.

If the error persists at manufacturer-supported default settings with normal temperatures and known-good RAM and power, component-level diagnosis of the CPU and motherboard may be required.

For business PCs and servers, back up important data before extensive testing because repeated hardware-related crashes can lead to filesystem or application-data corruption.

#tags

#MACHINE_CHECK_EXCEPTION #MachineCheckException #BSOD #BlueScreen #WindowsBSOD #Windows11 #Windows10 #WindowsServer #StopCode #BugCheck #BugCheck9C #0x0000009C #WindowsError #WindowsTroubleshooting #HardwareError #HardwareFailure #CPUError #ProcessorError #CPUFailure #CPUOverheating #CPUOverclock #Overclocking #Undervolting #RAMError #MemoryError #FaultyRAM #MemoryDiagnostic #XMP #EXPO #Motherboard #MotherboardFailure #PowerSupply #PSU #BIOS #UEFI #BIOSUpdate #WHEA #WHEAError #WHEALogger #WindowsEventViewer #WinDbg #CrashDump #Minidump #HardwareDiagnostics #PCRepair #ComputerRepair #WindowsRepair #SystemCrash #WindowsSupport #BSODFix