Windows based systems may come up with error messages like
'Memory could not be read Read
' and when this error message is closed, the entire system crashes. Windows, however, works if the error box is not closed. The '
Memory address could not be read
' error happens because of issues related to hardware problems in
or if the hard disk reaches its optimum level. If the
PC is affected with viruses
or if the OS update fails to work properly, these type of errors are generated. The
management of applications run
by the system must also be checked to avoid this issue.
Windows may prompt you with the following error message:
And on diagnosing the problem:
Faulting application svchost.exe, version 5.1.2600.2180, faulting module msi.dll, version 3.1.4000.2435, fault address 0x00******.
When you close this error, the system will freeze and XP will crash if you try to shut it down. However, if you ignore the error without closing the warning box the system will run as normal.
This problem may be due to several factors:
Hardware failure (RAM memory is not working properly or is damaged)
Your system is not effectively managing the active applications
The hard disk is full
Your PC is infected with malware or a virus
Windows Update is not working properly Check if the RAM is working properly
If your computer is not managing active applications effectively:
Boost your processor to its maximum output (99-100%) Hard disk and virtual memory status
Your system lacks memory or your hard disk is full and can't perform file swapping effectively.
Erase any unnecessary files on your hard drive (mostly "Temporary Internet Files") and stop all applications running in the background to save memory Your PC is infected
Your system memory has been infected (virus, malware, spyware). Scan your system for malware and if found clean them out.
Windows Update is not working properly
Reinstall Windows Update:
Open the =Start menu
1.Right click on " My Computer"
2.Click "Properties" then the " Automatic updates" tab
3.Choose " Turn off automatic updates"
4.Reboot your computer
5.Go back to the Start menu and in all programs go to " Windows Update" you have to be connected to the internet
6.Manually update Windows
7.Turn Automatic updates back on Repairing Windows update
Verifying Windows Update and BITS services parameters:
Click on the Start menu, select the Run tab and type in the following command: services.msc
Double click on Automatic Updates and in the window that appears select the Log on Tab
Ensure that the Allow service to interact option is enabled
Ensure that the hardware profile (usually Profile 1) is activated
Select the General Tab and verify that the Startup type option is set to Automatic
You should also find the Services status option - just click on the start button to activate the process
Repeat the same steps using the Background Intelligent Transfer Service (BITS) Re -Register Windows Update DLL files:
In the Run tab type in the following command: cmd
In the cmd console enter the following command REGSVR32 WUAPI.DLL and press Enter
Upon receiving the following message: DllRegisterServer in WUAPI.DLL succeeded, validate by clicking on the OK button
Repeat the operation using the following commands:
To stop the Windows update service, type in: net stop WuAuServ
Rename the Windows Update folder
In the Run Tab type in %windir% and press OK
In the new window that appears, rename the
Restart Windows update by typing WuAuServ in the Run Tab
Restart your PC
Go to the Windows update web site to manually upgrade the Microsoft utilities Add RAM memory:
If the problem persists, upgrading RAM memory could be a costly, but necessary step.
Latest update on February 20, 2012 at 05:09 AM by