When bad RAM is installed in a computer, you may encounter the following issues on a computer:
The most common cause of these issues is Bad RAM which only needs to be replaced. RAM can go bad at any time. When encountering a STOP ERROR, I would first recommend replacing the RAM to see if this resolves the issue.
Potential causes of bad RAM:
Bad RAM is often the only problem with the computer. I would also recommend examining the Windows Event Viewer. However, a Stop Error is very generic which can be caused by any of the following:
Methods to resolve this issue:
http://www.smartnetadmin.com
- Computer locks up.
- Computer reboots at random intervals.
- Computer reboots when attempting to use Microsoft Internet Explorer 8 and Windows Update.
- Microsoft Internet Explorer displays the error message: "This tab has been recovered."
- Computer displays a Blue Screen of Death possibly including Stop Error or Bad Pool Caller, Stop: 0x000000C2 or Stop: Ox0000007E (0x0000005).
- Microsoft Security Essentials installation fails with the error code: "0x80070643"
- Microsoft Windows Defender fails with the error code: "0x80040154"
- Microsoft Windows Update fails with the error code: "0xC800044E"
- Microsoft Windows displays the error message: "something.exe has encountered a problem and needs to close."
- Microsoft Windows displays the error message: "Invalid Page Fault."
- Microsoft Windows displays the error message: "Windows recovered from a serious error."
The most common cause of these issues is Bad RAM which only needs to be replaced. RAM can go bad at any time. When encountering a STOP ERROR, I would first recommend replacing the RAM to see if this resolves the issue.
Potential causes of bad RAM:
- The RAM is physically defective and should be returned or discarded.
- One or more of the DIMMs slots on the motherboard are bad. If possible, try using different DIMMs slots.
- The RAM has not been installed in pairs.
- The RAM is the wrong type.
- The RAM is the wrong speed.
- The BIOS RAM Frequency is not set to Auto.
Bad RAM is often the only problem with the computer. I would also recommend examining the Windows Event Viewer. However, a Stop Error is very generic which can be caused by any of the following:
- Bad RAM
- Bad CPU Fan or Bad Case Fan
- Bad Video Card
- Bad Hard Drive
- Bad CDROM Drive
- Bad CPU
- Bad Motherboard
- Bad Device Driver
- Spyware
Methods to resolve this issue:
- To identify Bad RAM, boot from the MemTest CD and scan for RAM Errors. You may also wish to try MemTest Pro.
- To upgrade your Video Driver, download the latest version from the manufacturer's driver website.
- To possibly resolve a hard drive problem, perform a CHKDSK /R. Some versions of Spyware Doctor prevent CHDSK /R from running automatically. It is important that the Windows Operating System is able to run CHKDSK in order to maintain the integrity of the hard drive. I would recommend that you remove Spyware Doctor and delete the file C:\WINDOWS\SYSTEM32\DRIVERS\ikhlayer.sys.
- Scan and remove spyware using a combination of Ccleaner, Malwarebytes Antimalware and Kaspersky TDSSKiller. In this particular instance however, you will need to go one step further and install the latest version of the Microsoft Malicious Software Removal Tool, Microsoft Windows Defender and Microsoft Security Essentials. The trojan, Bamital.H, should then be automatically detected and quarantined by Microsoft Security Essentials.
- A STOP ERROR is often followed by a message which states: Physical memory dump complete. To examine, a memory dump also called a mini dump, you must convert the dump file to an ASCII text file which you can then open. The text file will identify the exact issue that caused the problem. To convert the mini dump to ASCII text, please perform the following steps:
- Install Nirsoft BlueScreenView.
- Download the appropriate Debugging Tools for your operating system: Debugging Tools for Windows 32-bit Version or Debugging Tools for Windows 64-bit Version.
- Install the application. The 32-bit version is installed to C:\Program Files\Debugging Tools for Windows (x86).
- Open Windows Explorer and browse to C:\WINDOWS\Minidump. In this location you will see the phsyical memory dump filename. For example, Mini102411-01.dmp. Write down the filename located in C:\WINDOWS\Minidump.
- Click Start - Run.
- Type: cmd
- Click OK.
- Type: cd "C:\Program Files\Debugging Tools for Windows (x86)"
- Hit Enter.
- Type: kd -z C:\WINDOWS\Minidump\[Filename]. For example: kd -z C:\WINDOWS\Minidump\Mini102411-01.dmp
- Hit Enter. The prompt will change to kd>.
- Type: .logopen c:\debuglog.txt
- Hit Enter.
- Type: .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
- Hit Enter.
- Type: .reload;!analyze -v;r;kv;lmnt;.logclose;q
- Wait until the command prompt displays the following: "Closing open log file c:\debuglog.txt
quit:" The ASCII text log file has been created at c:\debuglog.txt. Close the command box. - Open Windows Explorer and browse to C:\.
- Double-click debuglog.txt, scroll down the text file to display which item caused the computer to crash such as: Bad RAM, Bad Video Card, Bad Hard Drive, Bad CDROM Drive, Bad Device Driver, etc.
http://www.smartnetadmin.com
Comments
Post a Comment