Tippyz

Last night I upgraded my old Compaq R3120US to 2 GB (PC2100 - 200 pin RAM). After I completed the installation, I restarted the machine and it was running perfectly fine (and quite a bit faster!).

When my battery reached a low charge state, I plugged the laptop in. Shortly after doing this, Windows froze completely. No mouse movement, no keyboard interaction, nothing. I shut it down, and after allowing the battery to charge for a bit, I restarted it on battery power. Once again, it was running fine until I plugged it back in -- at that point it froze up again within a minute. It was running perfectly fine again this morning on battery before I came into work. It seems running it on AC with the new memory causes it to become unstable.

I have not tried running it on a single 1GB memory module (will do that tonight). The memory is from Crucial and matches the spec provided by HP (Compaq). I am currently running Windows XP, SP 3. Would appreciate any suggestions on resolving this. While the machine is functional, having to always run on battery power is limiting.

TriggerFinger

Assuming it is caused by a defective RAM. Run Memtest on each individual (remove one) module for 2 passes (2 to 3 hours for each stick).

Post back any results.

Tippyz

I will do this tonight --- not sure I will have the battery life to get through 2 complete passes if it takes 2-3 hours per stick. I will let you know how it goes.

TriggerFinger

I suggest you run the test with AC adapter and NOT with battery. If the RAM checks out, try a new or good/working battery.

Tippyz

I was able to run the Memtest on one of the sticks last night -- and it completed 2 passes without error. I will need to swap them out today to run the test against the second stick.

On a side note -- I am currently running on AC on the single stick, without issue. Makes me curious what the results of the second stick will show.

Tippyz

Pass 2 just completed on the second stick of memory --- also no errors. I don't have another battery / AC unit I can use with this laptop.

I am going to run the memory test overnight with both sticks of memory in -- should get through 3 to 5 passes, I would think. Will report the results in the morning.

If this also comes back clean, could it be my Windows installation? I am planning on backing up all the data, and rebuilding the hard drive, making the PC a dual boot with XP and Ubuntu. I may take this as a next step, if there are no other ideas.

TriggerFinger

Just a wild idea... why not put back the old RAM and run the laptop on battery just to test if you still get the persistent freeze. If it is Windows related I am quite sure it would happen again. The same thing would happen if it is caused by the battery. Now if it is RAM related, then obviously it won't.

Tippyz

While running the test with both modules in place, an Error was found, here are the details.

Test 5: Block Move, 64 Moves
Testing: 120K - 2047M

Error Confidence Value: 45
Lowest Error Address: 000000001fff (0 MB)
Highest Error Address: 00039f6895f (927 MB)
Bits in Error Mask: 39ffffff
Bits in Error Total: 28 Min: 8 Max: 24 Avg: 5
Max Contiguous Errors: 1

Error Count:
Slot 0 -- was increasing without end
Slot 1 -- 0

Prior to installing the memory, I was able to run Windows without error - on AC and on Battery. I was able to also run Windows on a single stick yesterday morning -- given that and the results above, I am fairly certain it is a RAM error.

TriggerFinger

Good job. What memory diagnostic did you use? Hmmm I think the only problem now is knowing which is Slot 0. After knowing which is Slot 0 then you can replace the RAM there.

Tippyz

I used Memtest86 v3.4a. I was happy to see that is was a memory checker that runs outside of Windows.

I reran the above test on Battery Power -- got the same error on Test 5, except this time the count only went to 1, and it moved on to Test 6. When I was on AC power, it never moved past Test 5.

I have an idea which slot is Slot 0. I have a couple of ideas on how to verify it --

• Check the BIOS settings for the memory slot names.

• Replace what I believe is Slot 1 with one of my old 256 MB chips and rerun the test.

I have also sent a question to Crucial Tech support -- I used their Memory Adviser Tool to select the memory -- I have heard that some HP laptops and Crucial memory do not play well together. Since my laptop is a Compaq, but it was built after the merger, I am wondering if it is suffering from a compatibility problem that their adviser tool did not raise.

TriggerFinger

--If you have not physically moved the RAM sticks yet after doing the tests, then just remove ONE (choose either one of course) and rerun Memtest86+. Now Memtest as you saw previously should (I hope) tell you which slot is being tested. From that information, you can now identify which is the defective stick.

Tippyz

I have not moved either of the sticks yet, so I can try that tonight as well. I have also heard back from Crucial -- they are suggesting a BIOS update to see if it makes a difference. I think my BIOS is several years old, so that is probably a good idea as well.

TriggerFinger

I think, it would be safer and better for you to do the BIOS update once you got the freezing sorted out. You may try the DOS version of the BIOS update but if you have some questionable hardware components like for instance the RAM, it would do more harm than good.

Tippyz

Oh, I agree. I want to fully identify and resolve the RAM issue first. Thanks for keeping me honest, however!

Tippyz

By changing some of the settings in Memtest 86, I am able to recreate the error condition on Test 5 with either chip. Memtest did indicated during a single stick run, which slot it was in. I will be returning them to NewEgg for another set. I will likely go with a different manufacture, as I am not convinced that this is 2 defective units as much as it is a compatibility issue with my laptop.

I did check my BIOS, by the way, and I am current. The last release for it was in 2005 - which I have.

I am going to mark this thread as solved, but I will come back and post the results when I get a new set of memory installed. Thanks for all of your help!

TriggerFinger

Try this one too http://oca.microsoft.com/en/windiag.asp

If both sticks still get an error using this tool then you can be assured it is the sticks and not Memtest being flaky.