Memtest86 errors with more then one stick installed

TekViper

Senior member
Jul 1, 2001
591
0
71
I got a lot of memtest86 errors when i installed 2 sticks of ram into my abit bg7 (845g chipset). The ram is a 256 and 512meg sticks of mushkin. When i install each ram seperately i have zero errors. but if i put in both (tried switching them around to different slots) i get anywhere from 400 to 4000 errors in memtest86. any ideas? i have tried different voltages and the most lax timings i could run, nothing seems to help.
 

bendixG15

Diamond Member
Mar 9, 2001
3,483
0
0
By your description, I'm not sure if you tested the slots.
I had a similiar problem and it ended up that one of the memory slots was bad.
I found it by putting a stick in slot one, testing it, then moved same stick to slot two and tested it, then into slot three which tested bad. Had to RMA the board.
Hey, thats all I got...................
 

jtusa

Diamond Member
Aug 28, 2004
4,188
0
71
I have the EXACT same problem. I have an Intel board with the 865 chipset and two sticks of Samsung 512MB PC2700. Since our hardware is pretty different it must be an error with that app.
 

TekViper

Senior member
Jul 1, 2001
591
0
71
my board says that dimm 1 is independant and dimm 2 and 3 are shared. it also says to install ram starting in dimm1. if i wanted to test dimm2, could i just install 1 stick in dimm2 and expect it to work even tho the manual says to start installing memory from dimm1? same goes for dimm3? any inherent problems of installing a single stick of ram in any slot beside dimm1?
 

TekViper

Senior member
Jul 1, 2001
591
0
71
i just got down trying each slot individually. no errors from either stick of ram when they are installed by themselves in each slot. only start getting errors when they are both installed.
 

boomerang

Lifer
Jun 19, 2000
18,883
641
126
You know, if you do a google search for "memtest" you come up with a multitude of pages with various different versions of this software.

I don't know if the original developer abandoned the app or what the story is.

I mention this because I get different results dependent on which version I use. I also get leary when the application can't report my chipset.

I still use it though, with every new build.