Segmentation Fault, Should I try new memory

M$ISBS · 07-02-2006, 09:28 PM

System crashed, just installed new HD and was compiling 2.6 kernel and got seg fault. I had been getting that alot before the crash. SHould I try new memory before buiding whole new system?

SLack 10.2 No X

dalek · 07-03-2006, 12:54 AM

This may not be your problem but I ran into this once before. I had compiled in the wrong chipset for the IDE controller and it was erroring out during heavy drive usage. If you want to test this, you can use something like this:

Code:

hdparm -Tt /dev/<your drive here> && hdparm -Tt /dev/<your drive here> && hdparm -Tt /dev/<your drive here> && hdparm -Tt /dev/<your drive here> && hdparm -Tt /dev/<your drive here>

Again, that may not be what is happening to you but it is easy to test if you have hdparm installed. It may not fail until the forth or fifth set though. Mine would do three with no errors but usually fail on the forth and would always fail on the fifth.

Hope that helps.

DaneM · 07-03-2006, 01:25 AM

To find out whether you have bad memory, you should download MemTest86. The easiest way to get it up and running is by downloading and burning a copy of Knoppix. If, for some reason (slow connection, etc.) you don't want to download the Knoppix CD, you can get MemTest86 from here:

http://www.memtest86.com/#download0

Just boot the disk, tell it to test, and wait a few hours. If you get errors, you have either bad RAM, CPU or motherboard (but most likely bad RAM).

Good luck!

--Dane

Wim Sturkenboom · 07-03-2006, 01:25 AM

Run memntest86 and see if there are problems (you might have to download it). If memtest86 does not reveal problems, your MB/RAM combination is OK.

M$ISBS · 07-03-2006, 09:23 PM

Thanks, I downloaded the iso, burned it as an image and its running now. Its already found errors. That sucks because this ram was pricey, Kingston hyperX for gaming.

Its less than 1 1/2 old.

DaneM · 07-03-2006, 11:29 PM

Bummer that the memory's bad, but this might cheer you up (from http://www.kingston.com/hyperx/products/khx.asp):

Quote:

KHX:DDR - Kingston HyperX memory is designed based on the latest DDR specifications available, and is 100% tested at Kingston's flagship factories. Plus, these Kingston modules come with the standard Kingston lifetime warranty and toll-free Tech Support. Built with the best-quality components, Kingston HyperX is competitively priced and is the choice for the serious gamer. HyperX is available in single and dual channel memory kits.

Have a good one.

--Dane

Wim Sturkenboom · 07-04-2006, 03:38 AM

It is not said that memory is bad. It might be anything used during the test. As memtest is a program, it will use the CPU. The CPU reads/writes from/to memory via the motherboard. So the following might be components that can be faulty (in my opinion):
CPU
Motherboard
RAM
You have to eliminate the possible causes.

Further you can check the memory timings and try to relax them a bit and stop overclocking (if applicable).

M$ISBS · 07-04-2006, 11:43 AM

I ran memtest without changing the ram configuration, how they were installed. Then I removed one stick and ran it again and got no errrors, then I removed the second stick, replaced it with the first in the same slot and thats when I got massive errors right off the bat.
Would it be safe to remove all the simms and run memtest to check the cpu and caches?

dalek · 07-04-2006, 01:33 PM

I'm not sure it will run with no memory. After all, the CD has to load to something. You can try it but I doubt it will boot.

M$ISBS · 07-04-2006, 03:55 PM

Oh,yea,

I was wondering how I could check the L1 and L2 cache to see if the MB and CPU are ok. Memtest doesnt seem to show when it checks those.

DaneM · 07-04-2006, 04:49 PM

I think that since memtest only produces errors when you have a particular stick installed, it's safe to assume that it's a RAM problem and not a CPU/Motherboard problem. Also, the computer will not boot if no RAM is installed; it will just beep at you. As far as I know, memtest was not designed to test the CPU's onboard memory.

--Dane