Bad RAM causes

[Star6966]

I have a client who dropped his laptop recently. Its an Everex Stepnote running Phoenix Bios. When I boot up the computer, it returns a beep code of 1 pause 4 pause 1 pause 1. I believe that means bad ram, and every now and then it will boot, but it never gets past the bios screen

I want to be sure before I buy any ram, because I am on a tight budget at the moment, so does anyone know if dropping a computer can cause Bad RAM, or if there is some other possibility?

 

[Morrison5891]

How hard was the fall? It could be a number of things wrong with it. Have you tested the RAM?

 

[Star6966]

I've got no way of testing the ram, and I don't know how hard it fell

 

[Morrison5891]

Get a copy of Memtest

Boot it from a CD ... have you taken the memory out and try re-setting it?

 

[Alan22]

....have you taken the memory out and try re-setting it?

Just what I was going to suggest. System fell, hmmmmmmm.

 

[Star6966]

It won't even POST
I get a beep code and a black screen

And re-setting the RAM was the first thing I tried

 

[iptech]

I'd do a strip-down on that machine before ordering any parts. If the boot to BIOS problem is random it's unlikely to be the memory SODIMM.

It doesn't sound like you done a lot of diagnostics to be honest. RAM is unlikely to be damaged with a shock unless it was very heavy and that would leave the computer casing damaged.

 

[Styxbound]

bad ram

I've seen ram blown from coming unseated in a drop and then being turned on.

 

[Star6966]

Iptech
You're right in saying I haven't done a lot of diagnostics yet, I am still in a preliminary stage I am just trying to eliminate variables, I obviously won't buy anything until I am either sure it is the RAM or am out of ways to prove it's something else
I am wary however in terms of fully dismantling the computer, as I do find laptops to be risky in that respect
This is mostly due diligence, persuing every theory

Styxbound,
Your point is an interesting one, as I know that my client turned his computer on once he dropped it, so that could have easily blown the RAM

I think I will attempt to find some test RAM in order to effectively diagnose the problem

 

[Thedog]

If its a drop and it doesnt boot past bios my first guess would be the motherboard.

Do you have any sort of Boot CD:s? I would try to boot to Mini Windows XP from Hiren, if that boots the ram should be fine (it runs from the ram).

On the other hand even if you are on a tight budget, keeping a couple of ram types available will save you loads of time in the future so its an investment. And come on, memory is not expensive these days.

 

[iptech]

If its a drop and it doesnt boot past bios my first guess would be the motherboard.

Do you have any sort of Boot CD:s? I would try to boot to Mini Windows XP from <link removed>, if that boots the ram should be fine (it runs from the ram).

On the other hand even if you are on a tight budget, keeping a couple of ram types available will save you loads of time in the future so its an investment. And come on, memory is not expensive these days.

Hiren's contains warez software, it's not permissable to post links to illegal downloads or encourage its use on Technibble. There are many legitimate boot environments that could be used and they are often discussed on Technibble - search is your friend.

I'd edit your post before you get slapped by the mods.

 

[controlfreak]

You really need to invest in testing equipment ie. have a variety of tested ram available to help you in these situations

try booting to a live cd like linux knoppix
run memtest but when running test ram individually also be sure to test both slots

take the hdd out attach it to another machine and run BSOD tool
check for errors like
IRQ LESS THEN OR EQUAL TO
MEMORY MANAGEMENT
or google your BSOD error to get more info

Faulty RAM is usually caused by power issues which can be caused by power supply a bad ground

 

[Star6966]

So, as an update on this one.

It did in fact turn out to be a motherboard issue.

I am wondering what you guys think of my fix.

I determined that when a certain amount of pressure was applied under one of the panels, the computer would boot, but when the pressure came off, it crapped out again.

I got a couple pieces of cardboard (yeah, cardboard) and I placed it between the panel and the motherboard. It kept the pressure on the board and the computer worked.

I told the client that this wasn't a permentant fix, and that he REALLY needed to get a new computer, but it would work for long enough to get his data off.

Is it wrong to use a crude fix if it works, and you explain it to the client?

 

[atlanticjim]

Is it wrong to use a crude fix if it works, and you explain it to the client?

I think that it is a personal/professional decision.

Professionally, I never do half-fixes. I can never be sure that the client will not mis-interpret it as a fix. I only do full fixes. In this case I would have offered the client a mobo replacement and data backup to DVD if he needed the data now.

 

[Star6966]

I only do full fixes. In this case I would have offered the client a mobo replacement and data backup to DVD if he needed the data now.

I absolutely agree, but in this case, the laptop would probably be better to be replaced at that point than attempt to replace the mobo.

Also, I knew that the client would never agree to an expensive repair like that. His preference was that it worked, so that his mother wouldn't find out.

But I agree with your principal of full fixes only.

 

[atlanticjim]

I absolutely agree, but in this case, the laptop would probably be better to be replaced at that point than attempt to replace the mobo.

Also, I knew that the client would never agree to an expensive repair like that. His preference was that it worked, so that his mother wouldn't find out.

But I agree with your principal of full fixes only.

But I will say that I would still not do it. "I have found the cause of your problem, it will require a motherboard replacement to fix it. If you would rather transfer data to a new computer, I would be glad to help you with that."