Solve a Physical Memory Dump Problem
The Physical Memory Dump error is one of the dreaded “blue screen of death” errors and is Windows response to a problem determined so disruptive the only option was to shut everything suddenly down.
What Causes the Physical Memory Dump Error?
There are many different reasons that may lead to Windows needing to default to a Physical Memory Dump error, and it usually occurs when you are in the middle of several important tasks. If this occurs as a fluke, there may not be a larger problem, however there are some simple steps that can be taken to correct this.
How to Fix the Physical Memory Dump
A Physical Memory Dump error can occur as the result of faulty hardware, software, conflicting programs or applications, and registry errors. It is important to correct this error by cleaning up your computer and verifying that these are not issues affecting your system. Make a note of any new hardware or software used at the time of the error, as this will be important for making corrections.
Solution: Cleaning up your system
- Begin by addressing any new hardware you have installed or added to your system. Remove the hardware, regardless of how insignificant it may seem (like a mouse or flash drive).
- Either return or replace the hardware, or you can reinstall the software and drivers associated with it.
- Uninstall software that was used or running at the time or the Physical Memory Dump error, and then reinstall it.
- Remove any installed software or applications that are not used, and if the error continues relating to a particular program there may be an issue of compatibility with that particular program.
- An additional possibility for creating the Physical Memory Dump error is a registry error. Run the file scanregw.exe to scan and repair any possible registry errors.
Thank you for visiting our site and I hope that this has been a help to you and your Physical Memory Dump Error. Good luck in making these corrections and please let me know if I can help in any other way.
You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.