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

0x0000013A

Microsoft defines bug check 0x13A as a condition where the Windows kernel-mode heap manager detects corruption in a heap. In practical terms, Windows has detected that memory being managed at the kernel level has been altered or used in a way that should not have occurred.

A typical blue screen may display:

Stop code: KERNEL_MODE_HEAP_CORRUPTION

or crash analysis may report:

BugCheck 13A – KERNEL_MODE_HEAP_CORRUPTION

Because kernel-mode code includes hardware drivers and other highly privileged components, this error frequently points toward a bad or incompatible device driver, although unstable RAM, overclocking, BIOS problems, system-file corruption and other hardware/software issues can also contribute.

What Does “Heap Corruption” Actually Mean?

Windows applications and drivers frequently need temporary blocks of memory. A heap is one mechanism Windows uses to dynamically allocate and release these blocks.

Kernel-mode components such as device drivers can request memory, use it and later release it.

Problems occur when software performs an invalid memory operation—for example:

• Writing beyond an allocated memory block
• Writing before the beginning of an allocated block
• Accessing memory after it has already been freed
• Freeing the same memory incorrectly
• Damaging heap metadata
• Passing an invalid heap object
• Corrupting a neighboring memory block

Because this happens in kernel mode, Windows cannot safely continue operating. It stops the system to prevent additional corruption.

Common Symptoms of KERNEL_MODE_HEAP_CORRUPTION

A computer affected by this problem may experience:

• Sudden Blue Screen of Death
• Random restarts
• Crashes while gaming
• Crashes when launching GPU-intensive applications
• BSOD after installing a graphics driver
• BSOD after Windows Update
• Crashes while waking from sleep
• Screen freezing before the BSOD
• Display going black temporarily
• Applications crashing unexpectedly
• BSOD during startup
• BSOD shortly after logging into Windows
• Crashes during video rendering
• Crashes while using multiple monitors
• Random instability under heavy CPU/GPU load

The computer may work normally for hours before crashing, which can make diagnosis difficult.

Common Causes of KERNEL_MODE_HEAP_CORRUPTION

1. Faulty or Incompatible Device Drivers

Drivers are one of the most important areas to investigate.

Kernel-mode drivers have direct access to critical operating-system resources. A defective driver can write to memory incorrectly and corrupt the kernel heap.

Potentially involved drivers include:

• Graphics drivers
• Network drivers
• Storage/NVMe drivers
• Chipset drivers
• Audio drivers
• USB drivers
• Printer drivers
• Virtualization drivers
• Security/antivirus filter drivers
• VPN drivers

If the BSOD started immediately after a driver update, that update should be investigated first.

2. Graphics Driver Problems

Graphics drivers deserve special attention when the BSOD occurs during:

• Gaming
• Video editing
• 3D rendering
• GPU benchmarking
• Browser hardware acceleration
• Multiple-monitor operation
• GPU-intensive software

Systems using NVIDIA, AMD or Intel graphics can experience instability if the installed graphics driver is damaged, incompatible or incorrectly upgraded.

3. Faulty or Unstable RAM

Heap corruption can also occur when memory contents are altered because of hardware instability.

Possible causes include:

• Defective RAM
• Poor DIMM contact
• Incorrect memory timing
• Unstable XMP/EXPO settings
• Mixed RAM modules
• Incorrect voltage
• Memory-controller instability

This is especially important when different BSOD stop codes appear on different crashes.

4. CPU, RAM or GPU Overclocking

An apparently stable overclock can occasionally produce memory corruption.

This includes:

• CPU overclocking
• GPU overclocking
• VRAM overclocking
• RAM XMP
• AMD EXPO
• Manual memory timings
• Undervolting
• Aggressive motherboard performance profiles

For troubleshooting, return the machine to stock settings.

5. Corrupted Windows System Files

Damaged Windows components may contribute to overall system instability.

Common causes include:

• Interrupted Windows updates
• Improper shutdown
• Storage errors
• Failed software installations
• Malware
• File-system corruption

Microsoft provides DISM and System File Checker for checking and repairing Windows components and protected system files.

6. BIOS/UEFI or Firmware Problems

Outdated firmware can sometimes contribute to:

• Memory compatibility problems
• CPU stability problems
• PCIe problems
• Power-management problems
• GPU compatibility issues

A BIOS update may therefore help when the motherboard or PC manufacturer specifically documents stability or compatibility fixes relevant to your system.

7. Third-Party Kernel-Level Software

Some applications install low-level drivers.

Examples include:

• Antivirus products
• VPN software
• Hardware monitoring tools
• RGB utilities
• Overclocking utilities
• Virtual-machine software
• Disk encryption software
• Backup applications
• Motherboard utilities

If the crashes started after installing such software, temporarily uninstalling it can be an important diagnostic test.

Understanding Bug Check 0x13A Parameters

For technicians analyzing memory dumps, Microsoft documents four parameters for KERNEL_MODE_HEAP_CORRUPTION:

Parameter 1: Type of corruption detected
Parameter 2: Address of the heap reporting corruption
Parameter 3: Address where corruption was detected
Parameter 4: Reserved

Parameter 1 is particularly useful because it identifies the type of heap problem detected.

Some important values include:

Parameter 1	Meaning
0x3	Corrupt entry header
0x4	Multiple corrupt entry headers
0x5	Corrupt entry header in a large allocation
0x6	Characteristics consistent with buffer overrun
0x7	Characteristics consistent with buffer underrun
0x8	Operation for busy block attempted on free block
0xB	Characteristics consistent with use-after-free
0xC	Wrong heap specified
0xD	Corrupt free list
0xE	Heap list corruption
0xF	Illegal operation performed on a free block
0x10	Invalid internal heap state; buffer overflow may be involved
0x11	Invalid state; double-free or heap corruption may be involved
0x12	Invalid state; use-after-free or adjacent overflow may be involved
0x13	NULL heap handle supplied
0x14	Allocation exceeds current allocation limit
0x15	Commit request exceeds current commit limit
0x16	Internal heap error/bad address or memory corruption
0x17	Corruption detected in a delay-free list

This information is especially useful when debugging a recurring 0x13A crash.

How to Fix KERNEL_MODE_HEAP_CORRUPTION

The following troubleshooting sequence is recommended because it starts with common and relatively safe fixes before moving to advanced diagnostics.

Solution 1: Restart the Computer

If the BSOD occurred only once, restart the computer and monitor it.

A single crash does not automatically mean that hardware has failed.

If KERNEL_MODE_HEAP_CORRUPTION repeatedly occurs, continue troubleshooting.

Solution 2: Identify What Changed Recently

Determine whether the problem started after:

• Windows Update
• Graphics-driver update
• New GPU installation
• RAM upgrade
• BIOS update
• New antivirus installation
• VPN installation
• New peripheral
• New software
• Hardware overclocking
• XMP/EXPO activation

The timing of the first crash is often an important clue.

Solution 3: Update the Graphics Driver

Download the appropriate driver from your GPU or computer manufacturer.

Before updating, identify the graphics adapter:

Right-click Start → Device Manager → Display adapters

You may see:

• NVIDIA GeForce
• AMD Radeon
• Intel Graphics

Install a current driver compatible with your Windows version and exact GPU model.

Restart Windows afterward.

Solution 4: Roll Back the Graphics Driver

If KERNEL_MODE_HEAP_CORRUPTION started immediately after a GPU driver update:

Open:

Device Manager → Display adapters → GPU → Properties → Driver

Select:

Roll Back Driver

Restart Windows.

If the Roll Back Driver button is unavailable, manually install a previously stable driver supplied by the GPU or PC manufacturer.

Solution 5: Perform a Clean Graphics Driver Reinstallation

If simply updating the driver does not work:

1. Download the correct graphics driver.
2. Disconnect unnecessary peripherals.
3. Remove the existing graphics driver.
4. Restart Windows if required.
5. Install the freshly downloaded driver.
6. Restart again.
7. Test the system.

Avoid installing random driver packages from unknown third-party websites.

Solution 6: Update Other Important Drivers

Update drivers for:

• Chipset
• Storage controller
• NVMe
• Network adapter
• Wi-Fi
• Bluetooth
• Audio
• USB controller
• Thunderbolt
• GPU

For branded desktops and laptops, check the PC manufacturer's driver-support page first.

For custom-built PCs, check the motherboard and component manufacturers.

Solution 7: Run Windows Update

Open:

Settings → Windows Update → Check for updates

Install applicable Windows updates and restart.

Also check optional driver updates carefully. If the BSOD began immediately after a particular driver update, however, rolling that driver back may be more appropriate than installing additional versions blindly.

Solution 8: Repair Windows Using DISM

Open Command Prompt or Windows Terminal as Administrator.

Run:

DISM.exe /Online /Cleanup-Image /RestoreHealth

Wait until the process completes.

DISM can repair corruption in the Windows component store. Microsoft recommends DISM as part of the system-file repair process.

Restart the computer if repairs are performed.

Solution 9: Run System File Checker

After DISM, run:

sfc /scannow

Do not close the window until verification reaches 100%.

System File Checker checks protected Windows system files and attempts to replace corrupted versions.

Possible results include:

Windows Resource Protection did not find any integrity violations.

No protected system-file corruption was detected.

Or:

Windows Resource Protection found corrupt files and successfully repaired them.

Restart the computer and test again.

Solution 10: Check the File System

Open Command Prompt as Administrator and run:

chkdsk C: /scan

For problems requiring offline repair, Windows may recommend additional CHKDSK operations.

Storage problems should be investigated carefully if you also experience:

• File corruption
• Slow disk access
• Applications disappearing or becoming damaged
• Disk-related Event Viewer errors
• Windows failing to boot

Solution 11: Test the RAM

Press:

Windows + R

Enter:

mdsched.exe

Select:

Restart now and check for problems

Windows will restart and perform a memory diagnostic.

If errors are detected, investigate the RAM configuration.

For deeper diagnostics, a dedicated bootable memory-testing utility may also be useful.

Solution 12: Test RAM Modules Individually

If the computer has multiple DIMMs and crashes continue:

1. Shut down the computer.
2. Disconnect AC power.
3. Follow proper anti-static precautions.
4. Remove all but one RAM module.
5. Test the computer.
6. Repeat with each module.
7. Test appropriate motherboard slots if necessary.

This can help identify:

• Faulty RAM
• Faulty DIMM slot
• Memory compatibility problem

Do not open a laptop or system where doing so would violate service or warranty procedures; follow the manufacturer's instructions.

Solution 13: Disable XMP or EXPO Temporarily

Enter BIOS/UEFI and temporarily disable:

Intel XMP

or:

AMD EXPO

Allow RAM to operate at default supported settings.

If crashes stop, investigate memory timing, voltage, BIOS compatibility and RAM support.

Solution 14: Remove All Overclocking

Return the following to factory/default settings:

• CPU frequency
• CPU voltage
• RAM timings
• RAM frequency
• GPU core frequency
• GPU memory frequency
• GPU voltage

Also temporarily disable automatic motherboard overclocking profiles.

If the error disappears at stock settings, system instability rather than Windows itself may be responsible.

Solution 15: Reset BIOS/UEFI to Default Settings

Enter BIOS/UEFI setup and choose an option such as:

Load Optimized Defaults

or:

Load Setup Defaults

Save changes and restart.

The exact wording differs between motherboard manufacturers.

Solution 16: Update BIOS/UEFI Carefully

Check the support page for your exact motherboard, desktop or laptop model.

Review BIOS release notes for fixes involving:

• Memory stability
• CPU compatibility
• GPU compatibility
• PCIe stability
• System crashes
• Power management

Important: BIOS updates should not be performed casually. Use the manufacturer's documented procedure and ensure stable power during the update.

Solution 17: Boot Windows in Safe Mode

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

If the system remains stable in Safe Mode but crashes during normal startup, suspect:

• Third-party drivers
• Startup software
• Security applications
• GPU software
• Hardware utilities

Safe Mode is therefore useful for narrowing the problem.

Solution 18: Perform a Clean Boot

A clean boot can help identify conflicts caused by third-party services or startup applications.

If the BSOD stops under clean-boot conditions, gradually re-enable applications and services until the problematic component is identified.

Do not permanently disable necessary security or business services without understanding their purpose.

Solution 19: Temporarily Remove Recently Installed Software

Pay particular attention to software that installs kernel-level components, including:

• Third-party antivirus
• VPN clients
• Virtualization platforms
• Disk utilities
• RGB software
• Hardware monitoring utilities
• Motherboard tuning utilities
• Backup software
• Encryption products

If the crashes began after installing one of these, uninstall it temporarily and test.

Solution 20: Check Reliability Monitor

Press:

Windows + R

Enter:

perfmon /rel

Reliability Monitor provides a timeline of:

• Windows failures
• Application crashes
• Driver installations
• Updates
• Software installations

Look at events immediately before the first KERNEL_MODE_HEAP_CORRUPTION crash.

This can provide an excellent clue about what changed.

Solution 21: Check Event Viewer

Press:

Windows + X → Event Viewer

Navigate to:

Windows Logs → System

Look for critical and error events around the crash time.

Useful categories can include:

• BugCheck
• Kernel-Power
• Disk
• Display
• WHEA-related hardware errors

Remember that an event occurring after a crash may merely describe the unexpected shutdown rather than identify its original cause.

Solution 22: Locate Windows Minidump Files

Windows may create crash dumps in:

C:\Windows\Minidump

A full or kernel memory dump may also exist as:

C:\Windows\MEMORY.DMP

These files can contain much more useful information than the BSOD screen itself.

Solution 23: Analyze the Dump with WinDbg

Advanced technicians can use Microsoft's debugger to analyze crash dumps.

A commonly used command is:

!analyze -v

Microsoft specifically recommends the !analyze debugger extension as a useful starting point when investigating bug check 0x13A.

The analysis may reveal:

• BugCheck code
• BugCheck parameters
• Failure bucket
• Process involved
• Call stack
• Driver/module names
• Memory corruption indicators

Do not automatically assume that the first driver name displayed in a dump is defective. Memory corruption may occur earlier and only be detected later by another component.

Solution 24: Use Driver Verifier – Advanced Users Only

Windows includes Driver Verifier for detecting problematic driver behavior. Microsoft describes it as a troubleshooting and validation tool capable of detecting driver issues that can lead to corruption, crashes and unpredictable behavior.

Run:

verifier

However, Driver Verifier deliberately stresses drivers and can cause additional BSODs when it detects a violation.

Therefore, it should be used only when:

• Important files are backed up
• You know how to access Safe Mode or Windows Recovery
• You understand how to disable Driver Verifier
• Normal troubleshooting has failed

To reset Driver Verifier from an elevated command prompt:

verifier /reset

Restart afterward.

For troubleshooting, selecting suspected third-party drivers is generally more controlled than indiscriminately stressing every driver.

Solution 25: Inspect Recently Added Hardware

If the BSOD appeared after hardware installation, inspect:

• GPU
• RAM
• NVMe SSD
• PCIe expansion card
• USB device
• Docking station
• Network card

Temporarily remove the newly installed component where practical and safe.

If the system becomes stable, investigate:

• Driver compatibility
• Firmware
• BIOS compatibility
• Power requirements
• Hardware defects

Solution 26: Check GPU Stability

If crashes occur mainly during gaming or rendering:

1. Restore GPU clocks to factory defaults.
2. Disable GPU undervolting.
3. Check GPU temperatures.
4. Check power connectors.
5. Reinstall the GPU driver.
6. Test another known-good driver version.
7. Test the GPU in another compatible system where possible.

A failing GPU or unstable VRAM can sometimes manifest as memory-corruption-related crashes.

Solution 27: Check System Temperatures

Monitor:

• CPU temperature
• GPU temperature
• Motherboard temperature
• SSD/NVMe temperature

Inspect:

• Fans
• Heat sinks
• Airflow
• Dust buildup
• Cooling system

Excessive temperature can make otherwise marginal hardware unstable.

Solution 28: Check Power Stability

Power problems may indirectly create system instability under heavy load.

Inspect:

• PSU capacity
• GPU power connectors
• Motherboard power connectors
• Laptop AC adapter
• Docking station
• Loose connections

This is especially relevant if crashes occur only when the CPU and GPU are heavily loaded.

Solution 29: Use System Restore

If the problem started recently and a restore point exists:

Search for:

Create a restore point

Open:

System Restore

Select a restore point created before the crashes started.

System Restore can revert system-level changes without normally deleting personal documents, although recently installed applications or drivers may be affected.

Solution 30: Consider Windows Repair/Reinstallation

If:

• Hardware tests pass
• Drivers have been correctly reinstalled
• BIOS is stable
• DISM/SFC do not resolve the issue
• Dumps do not reveal a clear third-party cause

then a Windows repair installation or clean installation may be considered.

Back up important data first.

If KERNEL_MODE_HEAP_CORRUPTION continues even after a clean Windows installation with only essential drivers installed, hardware becomes a much stronger suspect.

Recommended Troubleshooting Order

For most users, use this order:

1. Identify recent changes
↓
2. Update or roll back graphics driver
↓
3. Update chipset and important device drivers
↓
4. Install appropriate Windows updates
↓
5. Run DISM
↓
6. Run SFC
↓
7. Disable XMP/EXPO and overclocking
↓
8. Test RAM
↓
9. Check temperatures and hardware
↓
10. Analyze minidump files
↓
11. Investigate suspected third-party drivers
↓
12. Use Driver Verifier only when necessary
↓
13. Consider Windows repair/reinstallation

This prevents unnecessary Windows reinstallation when the real problem is simply a driver or unstable memory setting.

Commands Quick Reference

Repair Windows component store

DISM.exe /Online /Cleanup-Image /RestoreHealth

Scan Windows system files

sfc /scannow

Scan file system

chkdsk C: /scan

Windows Memory Diagnostic

mdsched.exe

Reliability Monitor

perfmon /rel

Driver Verifier

verifier

Disable Driver Verifier

verifier /reset

KERNEL_MODE_HEAP_CORRUPTION After NVIDIA Driver Update

If the problem begins immediately after updating an NVIDIA driver:

1. Boot into Windows or Safe Mode.
2. Roll back or remove the recently installed driver.
3. Restart.
4. Install a known-good compatible NVIDIA driver.
5. Disable GPU overclocking.
6. Test the system.
7. Analyze the dump if crashes continue.

Do not assume that every 0x13A crash on a system with an NVIDIA GPU is caused by NVIDIA. The dump and timing of the failure should guide diagnosis.

KERNEL_MODE_HEAP_CORRUPTION After AMD Driver Update

Use a similar process:

1. Remove or roll back the recent AMD display driver.
2. Restart.
3. Install the appropriate stable driver.
4. Restore GPU settings to default.
5. Disable overclocking/undervolting.
6. Test gaming and normal desktop operation.

KERNEL_MODE_HEAP_CORRUPTION While Gaming

When the error appears primarily while gaming, prioritize:

• GPU driver
• GPU temperature
• GPU overclock
• VRAM stability
• RAM stability
• XMP/EXPO
• PSU stability
• Game-related kernel-level software
• Anti-cheat drivers
• Hardware-monitoring tools

Gaming places considerably more load on the CPU, GPU, memory and power supply than normal desktop use, which can expose marginal hardware stability.

KERNEL_MODE_HEAP_CORRUPTION After Installing New RAM

If the error begins after a RAM upgrade:

1. Disable XMP/EXPO.
2. Reseat the RAM.
3. Confirm the modules are installed in recommended slots.
4. Test each DIMM individually.
5. Check motherboard RAM compatibility.
6. Update BIOS if the manufacturer provides relevant memory compatibility improvements.
7. Run extended memory tests.

If reinstalling the old RAM makes the BSOD disappear, investigate the new RAM or its configuration.

Frequently Asked Questions (FAQ)

1. What is KERNEL_MODE_HEAP_CORRUPTION?

It is a Windows BSOD indicating that the kernel-mode heap manager detected corruption in kernel-managed heap memory. Its bug check value is 0x0000013A.

2. What is error code 0x13A?

0x13A is the hexadecimal bug check number assigned to KERNEL_MODE_HEAP_CORRUPTION.

3. Is KERNEL_MODE_HEAP_CORRUPTION a hardware problem?

Not necessarily. It can result from faulty drivers, unstable RAM, overclocking, firmware problems or other software/hardware instability.

4. Can a graphics driver cause KERNEL_MODE_HEAP_CORRUPTION?

Yes. Graphics drivers operate at privileged levels and should be investigated especially when crashes occur during gaming, rendering or after a GPU driver update.

5. Can faulty RAM cause this BSOD?

Yes. Defective or unstable RAM can corrupt data in memory and cause BSODs.

6. Can XMP cause KERNEL_MODE_HEAP_CORRUPTION?

Potentially. XMP increases memory performance using predefined profiles, and a configuration that is unstable on a particular CPU/motherboard/RAM combination can cause memory errors.

Disable XMP temporarily to test.

7. Can AMD EXPO cause the error?

An unstable EXPO memory profile can contribute to memory corruption. Test at default RAM settings.

8. Can overclocking cause KERNEL_MODE_HEAP_CORRUPTION?

Yes. CPU, GPU and memory instability can result in corrupted data and crashes.

9. Should I reinstall Windows immediately?

Usually not.

Investigate drivers, RAM, overclocking, Windows corruption and dump files first.

10. Which command repairs Windows system files?

Run:

DISM.exe /Online /Cleanup-Image /RestoreHealth

followed by:

sfc /scannow

Microsoft documents DISM and SFC as Windows image/system-file repair tools.

11. Where are Windows BSOD dump files stored?

Minidumps are commonly stored in:

C:\Windows\Minidump

A larger dump may be stored as:

C:\Windows\MEMORY.DMP

depending on the configured crash-dump settings.

12. How do I determine which driver caused the BSOD?

Analyze the memory dump with WinDbg and inspect the bug-check parameters, stack and involved modules.

The command:

!analyze -v

is a useful starting point.

13. What is Driver Verifier?

Driver Verifier is a Windows diagnostic facility designed to detect improper behavior in drivers.

14. Is Driver Verifier safe?

It is a legitimate Windows troubleshooting tool, but it intentionally places additional checks and stress on drivers and can trigger BSODs when problems are detected.

It is intended mainly for advanced troubleshooting.

15. How do I disable Driver Verifier?

Run Command Prompt as Administrator:

verifier /reset

Then restart Windows.

16. Why does the BSOD occur only while gaming?

Gaming places heavy load on the GPU, VRAM, CPU, RAM and power supply. It can expose unstable drivers, overclocking, overheating or marginal hardware.

17. Why did the error start after Windows Update?

An update may coincide with changes to Windows components or drivers. Check Windows Update history and driver versions, and investigate the specific change rather than automatically uninstalling all updates.

18. Can an antivirus cause KERNEL_MODE_HEAP_CORRUPTION?

Potentially. Some security products install kernel-mode filter drivers. If crashes began after installing or updating one, it is worth investigating.

19. Can an SSD cause this BSOD?

An SSD is not the most obvious cause of heap corruption, but storage or data corruption can contribute to system instability. Check storage health when other disk-related symptoms are present.

20. How do I permanently fix KERNEL_MODE_HEAP_CORRUPTION?

There is no universal single fix because 0x13A describes the type of failure detected, not necessarily the component that originally caused it.

The permanent solution is to identify and correct the underlying source—commonly a defective/incompatible driver, unstable memory configuration, faulty RAM or other hardware/software instability.

Conclusion

KERNEL_MODE_HEAP_CORRUPTION (0x0000013A) means Windows detected corruption within a kernel-mode heap. Microsoft documents multiple forms of corruption associated with this bug check, including buffer overruns, buffer underruns, use-after-free conditions, invalid heap state and corrupted heap lists.

For normal troubleshooting, start with the most likely and least disruptive possibilities: check what changed immediately before the crashes, update or roll back suspect drivers, repair Windows with DISM/SFC, disable overclocking and XMP/EXPO, and test the RAM.

If the problem persists, the most valuable next step is often memory-dump analysis. A properly analyzed dump can turn a vague blue-screen message into actionable evidence about the driver or subsystem involved.

For advanced cases, Driver Verifier can help expose defective driver behavior, but because it can deliberately trigger additional crashes when violations are found, it should be used carefully and preferably only after ordinary troubleshooting has failed.

#Tags

#KERNEL_MODE_HEAP_CORRUPTION #KernelModeHeapCorruption #BSOD #BlueScreen #WindowsBSOD #Windows11 #Windows10 #WindowsTroubleshooting #WindowsError #WindowsRepair #BugCheck13A #0x0000013A #KernelError #HeapCorruption #MemoryCorruption #DriverError #DriverTroubleshooting #GraphicsDriver #GPUDriver #NVIDIADriver #AMDDriver #IntelGraphics #DriverUpdate #DriverRollback #WindowsDrivers #RAMError #MemoryError #WindowsMemoryDiagnostic #MemTest86 #FaultyRAM #XMP #EXPO #Overclocking #SystemCrash #WindowsCrash #DISM #SFC #SystemFileChecker #WinDbg #Minidump #CrashDump #DriverVerifier #WindowsSafeMode #WindowsUpdate #BIOSUpdate #GPUCrash #GamingBSOD #ComputerRepair #PCRepair #TechSupport