Random BSOD - urgent

Hi everyone. I've been getting random BSOD and I'm trying to narrow it down to either my laptop motherboard 'which means' dead laptop (manufacture says a replacement motherboard is 400) or just memory. Here's what I've done so far.

I originally thought it might be a software issue. So I took out my old hard drive and put in a brand new one. I tried installing WINXP, but along the way after the first part of formating the drive, where you actually get to the installation part, I got a BSOD.

Suspecting it to be a memory problem, I used MEMTEST to test it out. I don't get consistant results. Sometimes, it finds a fault, sometimes it runs fine for hours on end. I suspect it might actually be the slot where it accepts the memory on the motherboard. Possible? Could I test this memory somewhere else to make sure it is good? Or do I just by another stick and try it out.

Third - could the BSOD be a result of overheating? My laptop does get hot, but I've never had this problem before.

Background information.
I've had my laptop die on me once because of a hard drive failure. I fixed that
BSOD hits up things like PAGE, or some .sys file. I'm not certain.

HELP!
viperboy333Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MarkCommented:
What is the laptop model.
 Try running ultimate boot cd http://www.ultimatebootcd.com/
 and run the Windows memory diagnostic program. or download it from here http://oca.microsoft.com/en/windiag.asp
As far as heat is concerned, if you have windows up and running you might ant to try mobmeter http://tamaru.homeip.net/~shingo/mobilemeter/mobilemeterreadme-e.htm
or speedfan http://www.almico.com/speedfan.php
to monitor temps.
rindiCommented:
Do you have more than one memory slots? If you sometimes get errors when running memtest there is something wrong with either the RAM or it's slots, but there is no way to really know which is bad except by testing the modules in another PC and also testing other modules in those slots. If you have more than one slot, try the other, and sometimes, if there is a problem with the slot, you can try reseating the module so that it fits better, or by putting some padding between the module and the cover of the memory bay, so that it gets pressed into place more.
Zuhir ElgmatiApplications and Systems AdministratorCommented:
why u think that the problem is from the memory ....as i understand from your Q .. the problem start when u replace your Random BSOD .... so ... why you don't back to u r supplier from where you bay that and ask him support
or try to change other hard drive to make sure where's the problem Exactly  
Exploring SQL Server 2016: Fundamentals

Learn the fundamentals of Microsoft SQL Server, a relational database management system that stores and retrieves data when requested by other software applications.

rindiCommented:
One think I forgot to ask you, what is the stop error you get when it BSOD's?
nobusCommented:
for the heat : clean all fans and vents, and check if the fans run normally - around 3000 rpm
tech_sup_execuCommented:
First you've to determine what type of error it is:

1)UNMOUNTABLE_BOOT_VOLUME

When booting or restarting a notebook using Windows XP without Service Pack 2 installed, the following error message may appear on a blue screen:

STOP 0x000000ED (0xaaaaaaaa,0xbbbbbbbb,0xcccccccc,0xdddddddd) UNMOUNTABLE_BOOT_VOLUME

Notebooks that use Microsoft Windows XP without XP Service Pack 2 installed may start with the following error:

STOP 0x000000ED (0xaaaaaaaa,0xbbbbbbbb,0xcccccccc,0xdddddddd) UNMOUNTABLE_BOOT_VOLUME

This error is related to the way Windows XP interacts with the hard drive during an unexpected shutdown. Sometimes the contents of the cache are not written to the drive properly causing the error to appear when the notebook restarts.


Preventing the Unmountable Boot error from occurring

Microsoft Knowledge Base Article - "STOP 0x000000ED UNMOUNTABLE_BOOT_VOLUME" Error Message When You Restart Your Computer or Upgrade to Windows XP

--------------------------------------------------

2)PAGE_FAULT_IN_NONPAGED_AREA
When booting or restarting a notebook, the following error message may appear on a blue screen:

PAGE_FAULT_IN_NONPAGED_AREA *** STOP: 0X00000050

Solution
This blue screen error is due to a downlevel version of Utilities software for Windows XP.

Press and hold down the Power button for 5 seconds to turn off the computer. Then press and release the Power button to turn on the computer.

Press and hold the F8 key after the HP or Compaq logo screen appears, but before the Windows logo screen is displayed.

From the Windows Advanced Options Menu Select Safe Mode. When the Windows XP Desktop opens, Safe Mode will be displayed in the four corners.

Click Start then Control Panel

Select Add or Remove Programs.

Remove all utilities and reistall.

Restart the PC.
-------------------------------------------------------------
3)MULTIPL_IRP_COMPLETE_REQUEST
When booting or restarting a notebook, the following error message may appear on a blue screen:

Multipl_IRP_Complete_Request

Solution
Download and install the latest BIOS update for your notebook
-------------------------------------------------------------------
4)IRQL_NOT_LESS_OR_EQUAL STOP
When booting or restarting a notebook using Norton Anti-Virus version 11.2.1.2, the following error message may appear on a blue screen:

Error Message: IRQL_NOT_LESS_OR_EQUAL STOP: 0X0000000A (0X0000000B,0X00000002,0X00000000,0X804EA7AB)

Solution
This was caused by a problem with the downloaded update file. The problem has been fixed, and a new SymEvent file is now available through LiveUpdate.

To resolve this problem see Symantec Knowledge Article: Error: "ErrorMessage: IRQL_NOT_LESS_OR_EQUAL STOP. . ." occurs after installing the Symantec Event Manager Driver on Windows XP (In English)

------------------------------------------------------------------
5)Windows Unsafe or Sudden Shutdown
When booting or restarting a notebook, an error message referring to a Windows Unsafe or Sudden Shutdownmay appear on a blue screen.

Description
Windows XP may not start and the following error message may appear on a blue screen:

Windows Unsafe or Sudden Shutdown

This error occurs after Windows was not shutdown using a safe method. The notebook may have been truned off without clicking Shut Down or briefly pressing the computers Power button. The power may have been suddenly disconnected from the computer or the Power button may have been held for more than 5 seconds.

An unsafe shutdown can damage some of the Windows system files, preventing the computer from starting properly.

Solution
If the error occurs allow the operating system to complete a check of the hard disk. Windows will prompt your to run CHKDSK. CHKDSK scans the hard drive for damaged files and repairs the files if necessary. The scan may take up to an hour depending on the size of the hard drive and the number of damaged files. The computer will restart when the scan is complete and Windows should start normally.

-------------------------------------------------------------
6)Missing or corrupt LSASS.sys
When booting or restarting a notebook affected by the Sasser worm, an error message from NT/Authority referencing LSASS may appear on a blue screen. Prior to the Microsoft Security Update MS04-011 on 13 April 2004, the Sasser worm exploited a vulnerablility in the Local Security Authority Subsystem Service (LSASS).

Issue Description
During startup, the error message “Missing or Corrupt LSASS” is displayed. The computer halts and stops responding.

Cause
The Sasser worm virus exploits the Local Security Authority Subsystem Service (LSASS) vulnerability in Windows XP.

Solution
Microsoft Security Update MS04-011 released on 13 April 2004 addresses this issue. The links below will take you to tools and information provided by Microsoft and Symantec to assist in the removal of and protection against any further Sasser virus attacks.
--------------------------------------------------------
7)Missing NTLDR.dll
When booting or restarting a notebook after installing a program or application, an error message referring to "NTLDR" may appear on a blue screen.

Description
An error message referring to "NTLDR" may appear when Windows is starting. This may occur after installing a program or application.

Solution
Follow these steps to repair the Windows XP operating system:


Connect the notebook to the AC adapter plugged into the wall.

Press the Power button to start the notebook.
Immediately insert the Operating System CD-ROM (OSCD) into the notebook. The OSCD was included with your notebook when it was purchased.

Press the Power button for five seconds to power off the notebook.

Press the Power button again to start the notebook.

When prompted, press any key to boot from the CD. After a few minutes, the Welcome to Setup screen is displayed.

Press the Enter key to continue. A Licensing Agreement screen is displayed.

Press F8 to accept the agreement and continue. The Setup window is displayed.

Press R to repair the selected Windows installation. This process may take 30 minutes to an hour to complete.

The notebook restarts in Windows after the process is complete.


To prevent this issue from occurring in the future, download and install all Critical and Recommended updates using Microsoft Windows Update (In English).

-----------------------------------------------

Hope this resolves your issue.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
viperboy333Author Commented:
I want to thank everyone for the help. It turns out that the problem was a result of 1)bad memory slot 2)bad memory and 3)corrupt software of winxp. I had ot repeated run the memory tests to find out what was wrong. I had bad memory, but because of the bad slot, I got bad memory for just about every stick I tried, even good sticks from other laptops. This took a long time to work out. But thanks everyone.
MarkCommented:
You forgot to reward rindi's post, he came up with the bad slot answer.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Laptops Notebooks

From novice to tech pro — start learning today.