ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY is a Windows Blue Screen of Death (BSOD) error with the bug check value:

0x000000FC

Microsoft defines Bug Check 0xFC as a condition in which Windows detected an attempt to execute code from a region of memory that was marked as non-executable.

In simple terms, Windows detected that kernel-level code—often involving a device driver—attempted to run instructions from an area of memory where executable code should not be running. Windows stops the operating system to prevent further memory corruption, instability, or a possible security violation.

A typical blue-screen message may display:

Stop code: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY

or debugging tools may report:

BugCheck FC / 0x000000FC

This error should not automatically be interpreted as defective RAM. Driver bugs and memory corruption caused by kernel-mode software are important possibilities.

What Does Bug Check 0xFC Mean Technically?

The bug check contains four parameters.

Parameter 1: Virtual address whose execution was attempted

Parameter 2: Contents of the Page Table Entry (PTE)

Parameter 3: Reserved

Parameter 4: Reserved

For advanced troubleshooting, these parameters can be examined using a Windows crash dump and WinDbg.

The most important question is:

Which driver, kernel component, or memory corruption event caused Windows to attempt execution from the non-executable page?

Microsoft's debugging guidance notes that Windows may sometimes identify the responsible driver directly. Otherwise, examining the stack trace and current instruction pointer can help locate the offending driver.

Common Symptoms

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

• Sudden blue screen followed by automatic restart
• Random crashes during normal Windows use
• BSOD during startup
• BSOD immediately after login
• Crashes after installing a driver
• Crashes after Windows Update
• BSOD while gaming
• Crashes during heavy GPU activity
• Crashes when connecting USB devices
• BSOD while accessing storage devices
• Random application crashes before the BSOD
• System freezes followed by a restart
• Repeated boot loops
• Crashes after waking from Sleep or Hibernate

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

Major Causes of ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY

1. Faulty or Incompatible Device Driver

Device drivers are among the first things to investigate.

Kernel-mode drivers operate with extensive privileges. A defective driver can corrupt memory, use invalid memory addresses, reference previously freed memory, or incorrectly manipulate executable/non-executable memory.

Potential drivers include:

• Graphics drivers
• Network/Wi-Fi drivers
• Storage controller drivers
• NVMe drivers
• SATA/RAID drivers
• Chipset drivers
• USB drivers
• Audio drivers
• Bluetooth drivers
• Printer drivers
• VPN drivers
• Antivirus/filter drivers
• Virtualization drivers
• Backup software drivers

If the BSOD started immediately after updating a particular driver, that driver should receive particular attention.

2. Corrupted Driver Installation

The driver itself may be compatible but its installation could be damaged.

This may happen because of:

• Interrupted driver installation
• Failed Windows Update
• Improper driver upgrade
• System crash during installation
• Incorrect OEM driver
• Third-party driver-update utilities

Reinstalling the affected driver may resolve the problem.

3. Memory Corruption

A kernel driver may write data to an incorrect memory location.

The actual BSOD may occur later when Windows attempts to use the corrupted memory.

This makes memory-corruption BSODs particularly difficult to diagnose because the component visible at the point of the crash is not necessarily the component that originally damaged the memory.

4. Faulty RAM

Defective RAM can also produce memory corruption.

Possible symptoms include:

• Different BSOD codes appearing randomly
• Application crashes
• File corruption
• Installation failures
• Browser crashes
• System freezing
• BSOD during heavy workloads

RAM should therefore be tested when software and driver troubleshooting does not reveal the cause.

5. Unstable XMP or EXPO Memory Profile

High-performance memory profiles can sometimes cause instability.

A system may work normally for weeks or months but begin crashing because of:

• Marginal RAM stability
• BIOS changes
• CPU memory-controller limitations
• Mixed RAM modules
• Aggressive memory timings
• High memory frequency

Temporarily disable XMP/EXPO and test the system using standard memory settings.

6. CPU or GPU Overclocking

CPU, GPU or RAM overclocking can create subtle memory errors.

Temporarily return:

• CPU
• GPU
• RAM
• Memory controller

to manufacturer/default settings.

Also remove undervolting while troubleshooting.

7. Corrupted Windows System Files

Damaged Windows components can contribute to instability.

Possible causes include:

• Failed Windows updates
• Improper shutdown
• Storage corruption
• Malware
• Disk errors
• Previous BSODs

SFC and DISM should therefore be included in the troubleshooting process.

8. BIOS/UEFI or Firmware Problems

Older BIOS/UEFI firmware may contain compatibility or stability issues involving:

• CPU microcode
• RAM compatibility
• PCIe devices
• NVMe devices
• Power management
• Resizable BAR
• Virtualization
• Sleep/resume functionality

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

Important: BIOS updates should only be performed using the manufacturer's documented procedure. An interrupted or incorrect firmware update can prevent the computer from booting.

9. Antivirus, VPN or Security Software

Security applications often install low-level kernel components such as:

• File-system filters
• Network filters
• Endpoint protection drivers
• Web filtering modules

A defective or incompatible filter driver can contribute to BSODs.

If crashes started after installing or upgrading security software, temporarily removing that software may help isolate the problem.

Do not leave a production computer unnecessarily unprotected.

10. Virtualization Software

Virtual-machine and virtualization-related products may install kernel drivers.

Examples include software associated with:

• Hypervisors
• Virtual network adapters
• Virtual storage
• Sandbox software
• Android emulators
• Endpoint isolation

Update or temporarily remove recently installed virtualization products if the timing matches the start of the BSOD.

How to Fix ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY

Solution 1: Identify What Changed Before the BSOD Started

Before making major changes, determine what happened immediately before the first crash.

Ask:

• Was a driver updated?
• Was Windows updated?
• Was new hardware installed?
• Was antivirus software changed?
• Was a VPN installed?
• Was virtualization software installed?
• Was BIOS updated?
• Was RAM upgraded?
• Was XMP/EXPO enabled?
• Was CPU/GPU overclocking enabled?

If the problem started immediately after one specific change, reversing that change is often the fastest troubleshooting step.

Solution 2: Boot into Safe Mode

If Windows crashes repeatedly during normal startup, try Safe Mode.

One method is:

Settings → System → Recovery → Advanced startup → Restart now

Then navigate to:

Troubleshoot → Advanced options → Startup Settings → Restart

Select Safe Mode.

Safe Mode loads a reduced set of Windows drivers and services.

If the computer becomes stable in Safe Mode, a third-party driver, service, startup application, or related software component becomes a stronger suspect.

Solution 3: Update Problematic Drivers

Open:

Device Manager

Review important categories such as:

• Display adapters
• Network adapters
• Storage controllers
• Sound, video and game controllers
• Bluetooth
• USB controllers
• System devices

For important hardware, prefer drivers supplied by:

• Computer manufacturer
• Motherboard manufacturer
• GPU manufacturer
• Hardware manufacturer

Avoid random third-party driver-download websites.

Pay particular attention to drivers installed shortly before the BSOD started.

Solution 4: Roll Back a Recently Updated Driver

If the error appeared after a driver update:

1. Open Device Manager.
2. Right-click the affected device.
3. Select Properties.
4. Open the Driver tab.
5. Select Roll Back Driver, if available.
6. Restart Windows.

This is particularly useful when a new GPU, network, audio, chipset or storage driver causes instability.

Solution 5: Completely Reinstall a Suspected Driver

If updating does not help:

1. Download the correct driver from the device/OEM manufacturer.
2. Open Device Manager.
3. Locate the affected device.
4. Right-click it.
5. Select Uninstall device.
6. Restart Windows when appropriate.
7. Install the known-good manufacturer driver.
8. Restart again.

Be especially careful when uninstalling storage, RAID, chipset or network drivers on remotely managed or production computers.

Solution 6: Repair Windows with SFC

Open Command Prompt or Windows Terminal as Administrator and run:

sfc /scannow

System File Checker scans protected Windows system files and attempts to repair corrupted files.

Allow the process to reach 100%.

Restart the computer afterward.

Solution 7: Repair the Windows Component Store with DISM

Open an elevated Command Prompt and run:

DISM /Online /Cleanup-Image /ScanHealth

Then:

DISM /Online /Cleanup-Image /RestoreHealth

After DISM completes successfully, run:

sfc /scannow

Restart Windows.

DISM is particularly useful when corruption exists in the Windows component store used for servicing and system-file repair.

Solution 8: Check Windows Memory

Press:

Windows + R

Enter:

mdsched.exe

Choose:

Restart now and check for problems

Windows will restart and perform a memory test.

For intermittent or difficult memory problems, technicians may also use a dedicated bootable memory-testing utility for longer testing.

A single successful short memory test does not absolutely prove that RAM is fault-free.

Solution 9: Test RAM Modules Individually

If memory problems remain suspected and the computer has multiple RAM modules:

1. Shut down Windows.
2. Disconnect power.
3. Follow appropriate anti-static precautions.
4. Remove all but one RAM module.
5. Test the system.
6. Repeat with the other module(s).
7. If appropriate, test different memory slots.

This can help identify:

• Defective RAM module
• Defective motherboard slot
• Mixed-memory compatibility problem

Only perform physical hardware work if you are comfortable servicing the computer.

Solution 10: Disable XMP/EXPO Temporarily

Enter BIOS/UEFI and locate the memory-profile option.

Depending on the platform it may be called:

• XMP
• Intel XMP
• EXPO
• DOCP
• Memory Profile

Disable the performance profile temporarily and run RAM at default settings.

If BSODs disappear, investigate memory compatibility, BIOS version, voltage, timings and supported memory frequency.

Solution 11: Remove CPU/GPU Overclocking

Restore BIOS settings to default values or manually remove overclock settings.

Also restore GPU overclocking in applications such as tuning utilities.

Test Windows again.

Do not assume an overclock is stable simply because games or benchmarks run successfully. Kernel workloads may expose instability differently.

Solution 12: Check Reliability Monitor

Windows Reliability Monitor provides a useful timeline of crashes and software changes.

Press Windows + R and run:

perfmon /rel

Look for:

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

Check events around the time ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY occurred.

This can reveal patterns that are difficult to identify from Event Viewer alone.

Solution 13: Check Event Viewer

Press:

Windows + X → Event Viewer

Navigate to:

Windows Logs → System

Look around the time of the crash for:

• Critical events
• Driver failures
• Disk errors
• WHEA hardware errors
• Service failures
• Unexpected shutdown events

Do not assume that every error immediately before a BSOD caused the crash. Many events are secondary effects of the system failure.

Solution 14: Configure Windows to Create Minidumps

Crash dumps are extremely useful when the error occurs repeatedly.

Open:

System Properties → Advanced → Startup and Recovery → Settings

Under Write debugging information, select an appropriate dump type such as:

Small memory dump (256 KB)

Typical minidumps are stored under:

C:\Windows\Minidump

Larger crash dumps may be stored as:

C:\Windows\MEMORY.DMP

These files can be analyzed to identify suspicious drivers.

Solution 15: Analyze the Crash Dump with WinDbg

For professional diagnosis, analyze the dump with Microsoft's Windows debugging tools.

After loading the dump into WinDbg, a commonly used initial command is:

!analyze -v

Review fields such as:

• BUGCHECK_CODE
• MODULE_NAME
• IMAGE_NAME
• FAILURE_BUCKET_ID
• PROCESS_NAME
• STACK_TEXT

For Bug Check 0xFC, the stack trace and current instruction location can be particularly useful when Windows does not directly identify the offending driver.

However, do not automatically uninstall software simply because its module appears somewhere in the stack. Stack analysis requires context.

Solution 16: Use Driver Verifier – Advanced Users Only

Windows includes Driver Verifier, which can deliberately stress and monitor kernel-mode drivers to expose improper behavior.

Microsoft documents checks including:

• Special Pool
• Force IRQL Checking
• Pool Tracking
• I/O Verification
• Deadlock Detection
• DMA Verification
• Security Checks
• Miscellaneous Checks
• DDI compliance checking

Driver Verifier can intentionally cause additional crashes when it detects driver violations.

Therefore, it should be treated as a diagnostic/debugging tool rather than a general performance or repair utility.

Starting Driver Verifier

Open an elevated Command Prompt and run:

verifier

For targeted troubleshooting, it is generally safer to test suspected non-Microsoft/third-party drivers rather than indiscriminately stressing every driver on a production PC.

After configuring Driver Verifier, restart the computer.

If it exposes a defective driver, Windows may generate a more diagnostically useful crash dump.

Important Driver Verifier Warning

Driver Verifier can make a computer unstable or even produce repeated BSODs.

Before using it:

• Back up important data.
• Make sure you know how to access Safe Mode or Windows Recovery Environment.
• Do not casually enable aggressive verification on critical production servers.
• Prefer targeted driver testing.

To clear Driver Verifier settings, run from an elevated Command Prompt:

verifier /reset

Then restart Windows.

Solution 17: Perform a Clean Boot

A clean boot can help determine whether third-party services or startup software contribute to the crash.

Press:

Windows + R

Run:

msconfig

Under Services:

1. Select Hide all Microsoft services.
2. Disable remaining third-party services for testing.

Then disable unnecessary startup applications through Task Manager.

Restart the PC.

If the system becomes stable, re-enable items gradually until the problematic component is identified.

Solution 18: Uninstall Recently Installed Software

Pay particular attention to applications that install low-level components, including:

• Antivirus software
• VPN clients
• Backup software
• Disk utilities
• RGB/control utilities
• Hardware monitoring software
• Virtual-machine software
• System optimization tools
• Driver-update software
• Encryption software

If the BSOD began immediately after installing one of these applications, uninstall it temporarily and test.

Solution 19: Check Windows Updates

Install applicable Windows quality and security updates.

Go to:

Settings → Windows Update

Check for updates and restart if required.

However, if the BSOD started immediately after a particular Windows or driver update, investigate that update rather than assuming that installing additional updates will necessarily fix the issue.

Solution 20: Update BIOS/UEFI and Firmware

Check the official support page for the exact PC or motherboard model.

Look for:

• BIOS/UEFI updates
• Chipset updates
• SSD/NVMe firmware
• Thunderbolt firmware
• Device firmware

Read the manufacturer's release notes before updating.

Firmware updates are particularly worth investigating if the release notes mention:

• Stability
• Memory compatibility
• CPU microcode
• PCIe compatibility
• NVMe compatibility
• Sleep/resume issues

Solution 21: Check Storage Health

Although Bug Check 0xFC specifically describes attempted execution of non-executable memory, storage problems can indirectly contribute to corrupted system or driver files.

Check:

• SSD/NVMe health
• SMART status
• Manufacturer diagnostics
• File-system errors
• Firmware version

If the drive reports health warnings or critical SMART errors, back up important data immediately.

Solution 22: Check Temperatures

Monitor CPU and GPU temperatures during normal operation and load.

Investigate:

• Blocked air vents
• Dust accumulation
• Failed fans
• Loose heatsink
• Poor airflow
• Excessive CPU/GPU temperatures

Severe hardware instability can produce seemingly unrelated BSOD codes.

Solution 23: Restore BIOS Defaults

If several BIOS settings have been changed, load optimized/default settings.

Then test before re-enabling:

• XMP/EXPO
• CPU overclock
• Undervolting
• Custom RAM timings
• PCIe tuning

This provides a known baseline for hardware troubleshooting.

Solution 24: Use System Restore

If the problem began recently and an appropriate restore point exists:

Search for:

Create a restore point

Open:

System Restore

Choose a restore point from before the BSOD began.

System Restore can reverse certain system, registry, driver and software changes without being equivalent to deleting normal personal documents.

Still, important data should always be backed up before major recovery operations.

Solution 25: Repair Windows Using an In-Place Repair Installation

If drivers and hardware appear healthy but Windows remains corrupted, an in-place repair installation may be considered.

This can reinstall core Windows components while preserving applications and data when the correct repair/upgrade procedure and compatible Windows media are used.

Back up important files before proceeding.

Recommended Troubleshooting Order

For most systems, use this sequence:

1. Identify recent changes.
2. Check the crash dump/minidump if available.
3. Update, roll back or reinstall suspicious drivers.
4. Remove recently installed low-level software.
5. Run SFC.
6. Run DISM.
7. Test RAM.
8. Disable XMP/EXPO and overclocking.
9. Check Reliability Monitor and Event Viewer.
10. Update BIOS/chipset/firmware if applicable.
11. Perform a clean boot.
12. Use targeted Driver Verifier only if necessary.
13. Perform deeper hardware diagnostics.
14. Consider an in-place Windows repair if corruption remains.

This approach avoids immediately reinstalling Windows before determining whether the actual problem is a driver or hardware component.

Advanced Troubleshooting for IT Professionals

When troubleshooting multiple occurrences of ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY, collect crash dumps rather than relying only on the blue-screen message.

Create a table containing:

Date/Time | Bug Check | IMAGE_NAME | MODULE_NAME | Process | Recent Change

If every crash identifies the same third-party driver, that driver becomes a strong suspect.

If every crash identifies a different component, investigate broader memory corruption, RAM instability, CPU/memory-controller instability or another driver corrupting unrelated memory.

Important: ntoskrnl.exe Is Not Automatically the Cause

Crash-analysis utilities frequently display:

ntoskrnl.exe

This does not automatically mean that the Windows kernel itself is defective.

The kernel may simply be the component that detected the invalid operation and stopped the computer.

The real cause may be:

• Third-party driver
• RAM corruption
• Hardware instability
• Antivirus filter
• Storage driver
• Network filter
• GPU driver
• Firmware issue

Proper dump analysis is required before assigning blame to a module.

Can ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY Be Caused by Malware?

It is possible for malicious or compromised kernel-level software to create memory-related instability, but malware should not automatically be assumed simply because Bug Check 0xFC occurred.

Run a reputable security scan if:

• Unknown drivers are installed
• Security software was disabled unexpectedly
• Suspicious startup items exist
• System files have been modified
• Other signs of compromise are present

Driver bugs and hardware instability are generally more practical areas to investigate first when there are no other signs of compromise.

How to Prevent the Error from Returning

After resolving the problem:

• Keep Windows reasonably updated.
• Install drivers from trusted OEM/manufacturer sources.
• Avoid unnecessary driver-update utilities.
• Keep BIOS and important firmware current when updates address relevant issues.
• Avoid unstable overclocking.
• Test XMP/EXPO stability.
• Do not mix incompatible RAM modules.
• Monitor storage health.
• Keep sufficient free disk space.
• Investigate recurring BSODs instead of repeatedly forcing restarts.
• Keep important data backed up.

Frequently Asked Questions (FAQ)

1. What is ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY?

It is Windows Bug Check 0x000000FC, indicating that an attempt was made to execute memory that was marked as non-executable.

2. Is ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY a hardware error?

Not necessarily. It may result from faulty drivers, memory corruption, unstable RAM, firmware issues or other low-level software/hardware problems.

3. Can faulty RAM cause 0xFC?

Yes. Faulty or unstable RAM can corrupt memory and contribute to this type of crash.

4. Can a device driver cause this BSOD?

Yes. Kernel-mode driver problems are an important cause to investigate.

5. Can a graphics driver cause ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY?

Yes. GPU drivers operate in kernel-related components and can contribute to memory corruption or invalid execution conditions.

6. Can antivirus software cause this error?

Potentially. Some antivirus and endpoint-security products install kernel drivers and filter drivers. A defective or incompatible component can cause system instability.

7. Can VPN software cause this BSOD?

Potentially. VPN software commonly installs network-filter or virtual-adapter drivers. Updating or temporarily removing a recently installed VPN can help isolate the issue.

8. What does stop code 0x000000FC mean?

It means Windows detected an attempted execution from memory marked as non-executable.

9. Should I disable Data Execution Prevention to fix it?

Generally, no. Disabling security protections merely to suppress the symptom is not a proper first-line fix. Find the faulty driver, corrupted software or unstable hardware instead.

10. Should I reinstall Windows immediately?

Usually not. First investigate drivers, memory, system corruption, firmware and crash dumps.

11. How can I identify the driver causing the BSOD?

Analyze the Windows memory dump using WinDbg. Driver Verifier can also be useful for advanced targeted driver testing.

12. Where are Windows minidumps stored?

They are commonly stored in:

C:\Windows\Minidump

provided that Windows is configured to create them.

13. What WinDbg command should I run first?

A commonly used starting command is:

!analyze -v

It provides detailed bug-check and stack information.

14. What if WinDbg shows ntoskrnl.exe?

Do not automatically conclude that Windows itself is defective. The kernel may simply have detected corruption caused by another driver or hardware component.

15. Is Driver Verifier safe?

Driver Verifier is a diagnostic tool that intentionally stresses drivers and can cause crashes when violations are detected. It should be used carefully, particularly on production systems.

16. How do I turn Driver Verifier off?

Run Command Prompt as Administrator:

verifier /reset

Then restart Windows.

17. Can XMP cause this BSOD?

Yes. An unstable XMP/EXPO memory configuration can contribute to memory corruption. Disable it temporarily for testing.

18. Can overclocking cause the error?

Yes. Unstable CPU, GPU or memory overclocking can cause unpredictable memory errors and BSODs.

19. Can outdated BIOS cause ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY?

Potentially. BIOS/UEFI updates sometimes address memory, CPU, PCIe and hardware compatibility issues. Check the manufacturer's release notes.

20. Does SFC fix this error?

SFC can repair corrupted protected Windows files, so it can help when system-file corruption contributes to the problem. It will not repair defective hardware or a fundamentally faulty third-party driver.

21. Does DISM fix BSOD errors?

DISM can repair Windows component-store corruption. It is useful when Windows servicing or system files are damaged, but it does not directly repair defective RAM or hardware.

22. Why does the computer show different BSOD codes every time?

Changing bug-check codes can be a sign of broad memory corruption. Investigate RAM stability, overclocking, firmware and kernel drivers.

23. What if the BSOD started after installing new RAM?

Disable XMP/EXPO, verify module compatibility, reseat the modules, test them individually and run memory diagnostics.

24. What if the error only occurs while gaming?

Investigate GPU drivers, GPU/CPU temperatures, RAM stability, power stability and overclocking. Check crash dumps before assuming the GPU itself is defective.

25. What if the computer cannot boot normally?

Use Windows Recovery Environment or Safe Mode to remove problematic drivers/software, disable Driver Verifier if enabled, perform recovery operations or access troubleshooting tools.

Conclusion

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (0x000000FC) is a serious Windows bug check indicating that code attempted to execute from a non-executable memory region.

The error does not automatically mean that the RAM or Windows installation is defective. A faulty or incompatible kernel-mode driver, memory corruption, unstable RAM settings, overclocking, low-level security software, firmware problems or damaged Windows components may be responsible.

The most effective troubleshooting strategy is to preserve and analyze the crash dump, correlate the crash with recent system changes, investigate third-party drivers, repair Windows files, test memory and return hardware to stable default settings.

For repeated occurrences, WinDbg crash-dump analysis is considerably more useful than repeatedly reinstalling drivers or Windows without first identifying the likely source of the memory corruption.

#tags

#ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY #0x000000FC #BugCheck0xFC #BSOD #BlueScreen #BlueScreenOfDeath #WindowsBSOD #Windows11 #Windows10 #WindowsTroubleshooting #WindowsError #WindowsCrash #WindowsRepair #PCRepair #ComputerRepair #TechnicalSupport #ITSupport #WindowsSupport #DriverError #DriverTroubleshooting #FaultyDriver #DeviceDriver #MemoryError #MemoryCorruption #RAMError #RAMTesting #WindowsMemoryDiagnostic #SystemCrash #KernelError #KernelDriver #WinDbg #CrashDump #Minidump #MemoryDump #DriverVerifier #SFC #DISM #SystemFileChecker #WindowsRecovery #SafeMode #ReliabilityMonitor #EventViewer #BIOSUpdate #FirmwareUpdate #XMP #EXPO #Overclocking #HardwareDiagnostics #Windows11Fix #BSODFix