Archived from groups: alt.comp.hardware.homebuilt (More info?)
Hi,
I thought you might be interested in a recent saga.. I've put together
a new PC in the last 2 months using an Asus A8V-E Deluxe motherboard,
AMD 64 3500+ and 2 sticks of Crucial Ballistix 512Mb non-ECC,
unbuffered, DDR400 memory.
Everything went together fine, system up and running, Windows XP
installed, harddrives (2X SATA 80Gb Diamondmax 9) partitioned as needed
etc. Suse Linux 9.2 64 bit version installed via ftp as well, no
problems.
I used the machine like this for a few days then started having
problems with web access in suse linux. I couldn't get any internet
access, ping anything etc. even though eth0 seemed to be correctly
configuring via DCHP. I really started to pull my hair out over this!
WinXP was fine all along.
As a last resort, I decided to try and reinstall suse 9.2 today. So I
booted from the mini-installation CD and as it tried to load the Kernel
(for installation) into a RAMDISK, it failed with 'crc error'. Oh
dear... I started to suspect faulty RAM, and ran memtest-86 on each
stick of crucial 512Mb in turn. Lo and behold, one of them had loads of
errors at 3 different address locations. I am now getting a replacement
from my supplier. Suse linux is fine! (although currently running at
512Mb rather than 1Gb)
How weird is that? Has anyone else had a similar experience!?
The worrying thing is that the fault may have developed since putting
everything together, because at first everything was fine. Is there any
reason to suspect any problem other than dodgy memory? I was running in
dual channel (128 bit) mode with one stick of memory in each channel.
Would appreciate any feedback or similar experiences.
Dave
Hi,
I thought you might be interested in a recent saga.. I've put together
a new PC in the last 2 months using an Asus A8V-E Deluxe motherboard,
AMD 64 3500+ and 2 sticks of Crucial Ballistix 512Mb non-ECC,
unbuffered, DDR400 memory.
Everything went together fine, system up and running, Windows XP
installed, harddrives (2X SATA 80Gb Diamondmax 9) partitioned as needed
etc. Suse Linux 9.2 64 bit version installed via ftp as well, no
problems.
I used the machine like this for a few days then started having
problems with web access in suse linux. I couldn't get any internet
access, ping anything etc. even though eth0 seemed to be correctly
configuring via DCHP. I really started to pull my hair out over this!
WinXP was fine all along.
As a last resort, I decided to try and reinstall suse 9.2 today. So I
booted from the mini-installation CD and as it tried to load the Kernel
(for installation) into a RAMDISK, it failed with 'crc error'. Oh
dear... I started to suspect faulty RAM, and ran memtest-86 on each
stick of crucial 512Mb in turn. Lo and behold, one of them had loads of
errors at 3 different address locations. I am now getting a replacement
from my supplier. Suse linux is fine! (although currently running at
512Mb rather than 1Gb)
How weird is that? Has anyone else had a similar experience!?
The worrying thing is that the fault may have developed since putting
everything together, because at first everything was fine. Is there any
reason to suspect any problem other than dodgy memory? I was running in
dual channel (128 bit) mode with one stick of memory in each channel.
Would appreciate any feedback or similar experiences.
Dave