JarG0n said: I still don't understand why it never attempts to use 100% though. It's kindof disappointing really. I thought linux was supposed to be less resource intensive.
Well, linux uses more ram than windows does because there is no point in leaving ram free for the sake of leaving ram free (like windows seems to do).
It's just a fact of life that you will always have to keep a small amount free so that you can actually do new stuff at any time. It's not always feasable to fit the chunks of ram you need to fill 100 percent.
RJARRRPCGP said: But, be careful. You may be required to take the 256 MB RAM module out for the OS to not get corrupted.
I was working on a PC and added 2 256MB RAM modules and then after I was done working on it, the owner complained about it rebooting over and over again.
Also, another PC, which I still own, after I added another 128 MB PC133 SDRAM module, after I turned it on one day, which had Windows XP or Windows 2000 on it, got the dreaded STOP: INACCESSIBLE_BOOT_DEVICE BSOD. Both of the PCs that crashed recently had a RAM module added.
It seems that even when Memtest86 passes, the OS can silently get corrupted.
I don't know what you mean by "OS gets corrupted". If you put in faulty ram, your computer won't boot regardless of the OS.
And memtest will properly assess your ram. It is the most reliable and sensitive way to check ram. I suggest you had hardware problems after you checked the ram.
You won't convince me that you have faulty ram that will pass memtest86. That can't be.