There can be many reasons for this BSOD with a Faulty Hardware Corrupted Page message. If the problem happened right after an update or upgrade to Windows 10 then it is highly likely that the issue is caused by either Microsoft’s end, which they will solve in an upcoming update, or because of incompatible drivers. Most of the BSODs are actually caused by incompatible drivers and if you recently upgraded to Windows 10 then the chances of having an incompatible driver is really high as well. This specific BSOD with a Faulty Hardware Corrupted Page message is generally caused by either a faulty driver or a faulty RAM. Since there are many things that can cause this issue, there are multiple methods mentioned below to solve this error. So, go through each method until the problem is solved.

Tips

The problem can be caused by faulty hardware. So, if you recently installed new hardware on your system then it is recommended that you remove that hardware and check if the BSOD occurs or not.Since the problem can be caused by faulty drivers, there is a chance that your computer might be infected. This is highly unlikely but isn’t entirely out of the question. So, it is advised that you perform a full scan of the system before following the methods given below. If you don’t have an antivirus program installed on your machine then we will recommend Malwarebytes. It is a very popular and very good anti-malware software that is trusted by many. You can get it by clicking here and download a free version.

Method 1: Update Drivers

The first thing that you should do is to update the drivers especially the Display Drivers. This should be your priority especially if the problem started after a Windows 10 upgrade. Updating your drivers is pretty easy and takes only a few minutes. Follow the steps given below to update your drivers.

Once you are done, restart your computer and check if the BSOD shows up again. If this doesn’t work then you should uninstall your drivers and rely on Windows to handle it. Windows, basically, install the most suitable drivers automatically if it doesn’t find any installed drivers for your device. Since Windows has its own generic drivers, it’s not a bad idea to uninstall your drivers and let Windows handle the drivers. Follow the steps given below and see if this works

Once the driver is uninstalled, restart the PC. Windows will automatically install a generic driver on the restart. Check if the problem persists after these steps. If there are no BSODs then that means the problem was with your drivers. You can either keep the generic ones or try to install an older version of the driver provided by your manufacturer (since the latest version was causing the BSOD).

Method 2: Turn off Fast Startup

Turning off fast startup works for a lot of users as well. This option, basically, makes your computer startup a lot quicker as compared to a normal startup. This can create problems because the fast startup might not be giving your drivers or programs enough time to load up properly.

Restart your PC and check if the error is still there or not.

Method 3: Using SFC and DISM to fix Corrupted Window Files

You can use Windows built-in repair commands such as SFC and DISM to get this issue resolved. These commands will fix the corrupted drivers and files of your Windows. To execute these commands properly, follow these steps below:-

Method 4: Restore Point

If you are fortunate enough that you have made a restore point before having this issue then you can fully restore your Previous state of Windows. Simply follow the steps shown below if you have created a Restore point before.

Method 5: Check RAM

A lot of users have solved this problem by checking the RAM and taking out or replacing the faulty RAM. In the majority of the cases, there was a faulty RAM. So, it’s advised to check your RAM as well. The first thing that you should do is to take out the RAM, clean the RAM, make sure there isn’t any dust in the slots, and put the RAM back. Make sure the RAM is properly connected. Once done, turn on the system and check if the problem persists. If the problem is solved then consider yourself lucky as it was a simple troubleshooting process. But, if the problem is still there then get prepared to spend some time checking the RAM conditions with the help of the memtest. Windows Memory Diagnostic Since Memtest is a third-party tool and you might be hesitant to use it, you can use the Windows own built-in memory diagnostic tool for checking the memory. Although it isn’t seen as the most accurate tool when it comes to memory testing, however, it does provide some sort of diagnostics for your RAM. So, it is worth a try especially if you don’t want to jump right to the Memtest or if you don’t have a lot of time. Follow the steps given below to start the Windows Memory Diagnostic tool

Note: If it gives any errors or if it doesn’t work then follow the steps below

The Windows will restart automatically and the testing will begin. You will be able to see the testing and its results on the screen. Once the testing is finished, your computer will automatically restart and you will see the test results when you log on to Windows again. You will be able to determine whether your need to change your RAM or not from the test results. Memtest Memtest is basically a program that is used to test the conditions of your RAM. It takes a lot of time but it is quite useful in determining the condition of your RAM. Go to Your computer has a memory problem and follow the steps in method 1 to check your RAM. Manual Testing Since Memtest takes a lot of time, you also have another option if you aren’t patient enough and you have a spare RAM. You can replace your RAM with a new or another RAM (from another computer) and check if your system still gives the error. Make sure the RAM is in working condition and it is compatible with your system. If replacing your RAM works fine and doesn’t give the BSOD then your RAM is most likely the cause behind the issue. You can still use the Memtest just to make sure, though. Once you are done testing, replace the RAM with a newer one or another working one (if the problem was caused by the RAM).

What to do next

If the problem started right after a Windows update then revert back to the older build and check if it solves the issue. You will have the option to revert back to the older build for 10 days. You can revert back from your Settings -> Update & Recovery options.If nothing worked and you are certain that it isn’t a hardware issue then performing a System Restore is also an option. Keep in mind that you will only be able to do a system restore if you have a restore point. It’s best to perform a system restore to a point before the problem started. Note: A System Restore will erase all the data and changes you made after the point you are restoring to. So, do it at your own risk.If the problem happens at a specific task then that might help you troubleshoot the issue. For example, if the problem happens during or after you play games then the most likely cause of the problem is heat or GPU problems. In that case, make sure your system is not overly heated. Check these articles: computer randomly restarts article and low CPU temperature article to get guidance on how to check your PC for overheating issues.

BEST GUIDE: Page Up and Page Down on a Mac OS XFIX: Outlook Crashes Because of Faulty pstprx32.dll ModuleFix: Connectivity Issues due to Faulty WPD Update (2/22/2016)How to fix Windows successfully loaded the device driver for this hardware but… Fix  Faulty Hardware Corrupted Page - 11Fix  Faulty Hardware Corrupted Page - 61Fix  Faulty Hardware Corrupted Page - 32Fix  Faulty Hardware Corrupted Page - 38Fix  Faulty Hardware Corrupted Page - 93Fix  Faulty Hardware Corrupted Page - 94Fix  Faulty Hardware Corrupted Page - 80Fix  Faulty Hardware Corrupted Page - 14Fix  Faulty Hardware Corrupted Page - 92Fix  Faulty Hardware Corrupted Page - 18Fix  Faulty Hardware Corrupted Page - 67Fix  Faulty Hardware Corrupted Page - 56Fix  Faulty Hardware Corrupted Page - 7Fix  Faulty Hardware Corrupted Page - 87Fix  Faulty Hardware Corrupted Page - 61Fix  Faulty Hardware Corrupted Page - 50Fix  Faulty Hardware Corrupted Page - 99Fix  Faulty Hardware Corrupted Page - 96Fix  Faulty Hardware Corrupted Page - 41Fix  Faulty Hardware Corrupted Page - 43