How to Fix ‘Hardware Problems Were Detected’ Error on Windows Memory Diagnostic
Some Windows users are reporting that upon running the Windows Memory Diagnostics Tool, the utility concludes that there’s an underlying issue affecting a hardware component (Hardware problems were detected). This type of error is reported on every recent Windows version and is often accompanied by random restarts and computer freezes.
After investigating this issue extensively, it turns out that there are several different underlying scenarios that might be causing this particular error code. Here’s a shortlist of potential culprits that might be responsible for this issue:
- Common hardware driver issue – If you see this error message because a non-essential hardware component is forced to run with a partially incompatible driver, you should be able to take care of the issue by running the Hardware and Devices Troubleshooter and applying the recommended fix.
- Overclocking makes the system unstable – If you recently overclocked the frequencies and voltages of some of your components, keep in mind that the Windows Memory Diagnostic tool can pick up on this and trigger the error to warn you that your components are at risk of overheating. Try reverting back to the default frequencies and voltages (or at least tone them down) and see if the error goes away.
- System file corruption – It’s not uncommon to face this type of issue due to some kind of system file corruption that is affecting memory management. If the issue is software-related, you should be able to fix it by performing a repair install or clean install procedure on your Windows installation.
- Failing RAM stick – If you’re unfortunate enough to be experiencing a failing RAM stick, this error message is typically the first sign that you’ll need to look for a replacement. But before you order one, take the time to deploy a Memtest scan and monitor the temperatures with HWMonitor to confirm your suspicions (hopefully not).
- Different failing hardware components – As it turns out, a failing RAM is not the only hardware component that might trigger this type of error with the Windows Memory Diagnostic tool. The issue can also be rooted to your motherboard or even your PSU. Because of this, the best course of action at this point is to take your PC to a certified technician for advanced investigations.
Now that we went over every potential scenario that might trigger the ‘Hardware Problems Were Detected‘ error, here’s a short list of fixes that other affected users have successfully used to get to the bottom of this issue.
Run the Hardware and Devices Troubleshooter
Before you try any of the other fixes below, you should start by checking if your Windows installation is not capable of pinpointing and fixing the issue by itself. If the error message is triggered by a non-essential component, running the Hardware and Devices Troubleshooter might allow you to discover which component is responsible.
Note: The Hardware and Device Troubleshooter contains a selection of automated fixes that can be auto-applied in case a familiar scenario is identified. Most of these fixes will fix issues related to file corruption and bad drivers. They’ll obviously not be effective in a situation where there’s something physically wrong with your hardware.
If you haven’t tried running the Windows Hardware and Devices Troubleshooter yet, follow the instructions below for step by step instructions on how to do this:
- Press Windows key + R to open up a Run dialog box. Inside the text box that just appeared, type ‘ms-settings:troubleshoot’ and press Enter to open up the Hardware and Device Troubleshooter.
- Once you’re inside the Troubleshooting tab, click on Other troubleshooters from the menu on the right-hand pane.
- Next, scroll down through the list of available options and click on the Run the troubleshooter button associated with Hardware and Devices.
- Once the troubleshooter has started, wait patiently until the investigation phase is complete. In case a viable repair strategy is identified, you’ll be presented with a window where you can click on Apply this fix to auto-apply the repair strategy.
- Once the fix has been successfully applied, reboot your PC before running the Windows Memory Diagnostic tool once again and seeing if the problem is now fixed.
In case the same kind of issue is still occurring, move down to the next potential fix below.
Disable Overclocked frequencies
Another potential cause that might be producing this issue and that is often overlooked is a situation where you previously overclocked GPU, CPU, or RAM frequencies and adjusted the voltages in a way that makes your PC unstable.
If you are currently using overclocked frequencies higher than what your system deems as safe, you can expect the Windows Memory Diagnostic tool to trigger the Hardware problems were detected.
Even if there’s no damage affecting the overclocked components, your system will throw this error to warn you against component overheating.
You can test if this is the source of the error message by temporarily disabling (or at least reducing) the overclocked frequencies and voltages. For the best results, return every overclocked frequency and voltage to their default values.
Once you’ve returned to your BIOS / UEFI settings and reverted the overclocked frequencies back to their default values, reboot normally and run the Windows Memory Diagnostic tool once again to see if the problem is now fixed.
In case the same kind of issue is still occurring or this scenario is not applicable (no component is overclocked), move down to the next potential fix below.
Check for Failing RAM with MemTest86
This particular error message is often times associated with a memory fault. If none of the methods above have brought you close to potential culprits, you should also take the time to test your RAM stick/s and see if there’s an issue with them that’s forcing the Windows Memory Diagnostic tool to trigger the ‘Hardware problems were detected’ error.
In case you are using a dual-channel RAM setup, start troubleshooting by taking out just one stick and see if the error stops occurring.
Additionally, you should use a utility like Memtest to verify the integrity of your RAM stick/s.
Important: If your RAM is currently overclocked, we recommend reverting any voltage overclocked frequency and use a utility like HWMonitor to keep an eye on your temperatures while running a stress test.
In case running a Memtest job on your RAM has revealed an underlying issue with your memory, you have little else to do than look for a replacement.
If the investigations you just didn’t reveal an underlying issue with your RAM, move down to the next potential fix below.
Perform a clean install or repair install
As it turns out, this particular issue can also be caused by some type of system file corruption that is affecting the Windows Memory Diagnostic tool or an associated kernel dependency.
For this particular case (where the issue is actually caused by a corrupted dependency), the best course of action is to replace every system file component with a healthy equivalent.
You can do this by clean installing your operating system, or you can go for a repair install (in-place repair) operation.
The main advantage of going for a repair install operation is that you will be spared from having to reinstall everything – this procedure will only touch system components, allowing you to keep personal files, data and even applications that are currently stored on the OS drive.
But keep in mind that the procedure of repair installing will be a bit different depending on which Windows version you’re currently using:
Take PC to a Certified Technician
If none of the methods above have proven to be effective in your particular case, the only thing you can do at this point is to take it to a certified PC technician so they can perform some advanced checks and pinpoint the hardware component that is causing the error.
In reality, there are a lot of other scenarios that might cause the Windows Memory Diagnostic tool to throw the ‘Hardware problems were detected’ error.
It’s not uncommon to see this error when the PSU used is not strong enough to supply electricity to every component or you can be dealing with some kind of motherboard issue.
These types of tests can only be performed in a specialized shop.