Weird ram problems (old machine)

nameiwantisbanned

Reputable
Mar 6, 2015
3
0
4,510
Hi all,

First off thanks for reading my thread and any help would be much appreciated!
This is my first post here so please be nice ;')

Anyway to the problem:-

I have an old (read ancient) machine: xw600 (dont laugh too hard). Now, knowing its old, i dont expect much from it but ive recently run into this problem and due to present circumstances I CANT afford to to throw it out and upgrade (though ive been more than tempted to smash it into tiny little pieces..), so please dont suggest that because its not an option at the moment.

So whats been happening is I've been getting a couple BSODs a week as of last week: Memory parity, and some with what i can only explain as a pixilated pause symbol ( II ). At first i put them down to overheating as the machine is in the attic and it can get really toasty up there.

Anyway I start googling and after a couple hours research i put it down to bad ram so i download memtest start writing it to usb and in the middle of that.. Another BSOD.

On rebooting it i get a blank screen and a beep code, a few reboots later and everything is fine for 30 mins then bsod, reboot and beep codes ensue. Googling revealed that the beep code (1s, 2l) was indeed a memory issue.

Next course of action was to take out all the sticks and try them one by one. All worked fine on their own. So I started trying them in 2s and every combination possible and every combination besides 1 stick at a time failed.

At this point im confused and frustrated so i pull all the cords, sticks and the cmos battery hoping to reset it. Gave it 30 mins, came back, inserted everything, all 4 sticks and booted.. It worked! .. For about 10 @#&!ing minutes.

Now i pull all 4 sticks and clean(spotless) the contacts with ispropyl, a rubber and a cloth, reinsert and bingo! problem solved! ..or not : 1 hour later i had to go out so i shut it down
, when i come back to boot all i get is beep codes! even every stick singular is giving the same result now!

The bit i dont understand is how they can work fine then die, then fine after vleaning, then die after reboot to a state worse than before?

So, here I am, confused and so $@#!ing frustrated, hoping by some miracle one of you tech savvy people might have an idea of whats going on and kind enough to share the wisdom?
 
Solution
Could possibly be a motherboard issue, I had something similar to this happen to my old AM3 board a few years back. We spent a long time trying to diagnose it (swapping out parts that would alternately work and not work in certain combinations, about a minute of boot time before crashing).

Raising this as a possibility to other experts, I'm not qualified to make any statements on this one.

AdviserKulikov

Honorable
Jan 13, 2015
1,099
0
11,960
Could possibly be a motherboard issue, I had something similar to this happen to my old AM3 board a few years back. We spent a long time trying to diagnose it (swapping out parts that would alternately work and not work in certain combinations, about a minute of boot time before crashing).

Raising this as a possibility to other experts, I'm not qualified to make any statements on this one.
 
Solution