I second this. Quick Tech is the program that I recommend. It is
available from http://www.uxd.com as was mentioned below. It is
amazing. Well worth the money. Worth its weight in gold actually.
Although I do disagree with always keeping BIOS defaults. Definately
keep them for ram timings and speeds but other settings need to be
adjusted to achive stable peak performance from your hardware. As an
example: An Asus A7V (if you have no usb devices) will boot twice as
fast with "legacy USB Support" disabled and it is enabled by default.
Abe "I test more ram and motherboards in an afternoon then most people
touch in their entire lives"
olson ;-)
Linux Tests wrote:
>
> Sorry, I respectfully disagree with some of this. A techs time is too
> expensive to go through BIOS settings. Always stick with the BIOS defaults.
> Period. DO NOT make changes to your BIOS.
>
> Plus simplify the testing process.
>
> Keep the BIOS at default.
> Use RST - and OS independent tester - which will test compatibility issues
> for the complete system as well as locate any bad memory modules.
>
> In less than 3 minutes you will know if the memory is bad.
>
> http://www.uxd.com
>
> Don't waste your time swapping and pulling etc. Just get the program and be
> happy.(No, I'm not affiliated with Ultra-X. I just happen to use the program)
>
> On Wed, 21 Feb 2001, you wrote:
> ##On Wednesday 21 February 2001 02:24 pm, Heather wrote:
> ##> On this subject of RAM incompatibility...
> ##>
> ##> I have a stick of RAM that someone gave me to boost me up past 64mb.
> ##> When I first installed it it would do ok, but then it would get where
> ##> sometimes it would show on boot up and others it wouldn't then (in
> ##> evil windows since i haven't put it back after installing LM) my
> ##> computer started popping up more errors and illegals than it ever had
> ##> before. When I pulled the RAM it went back to normal (for windows).
> ##> Is there a way for me to find out if the 2 sticks are just
> ##> incompatible or if the 1 stick is just borked up?
> ##
> ## Not really. The only way to actually test ram is on a _very_
> ##expensive, purpose built machines that very few people would ever have
> ##access to (lab equipment). What is more important to understand is
> ##just how much ram can be affected by other parts of the system.
> ##Particularly the motherboard, cpu, cache, etc. The best ram test apps
> ##like 'memtest86', actually test the whole system, so the appearance of
> ##errors are not necessarily due to bad ram. Also important to
> ##consider, is that ram is very heat and voltage tolerant, especially
> ##when compared to the other system components. IOW's, it's usually not
> ##the culprit.
> ##
> ## Most often there's no problem mixing ram sizes or "labels" (eg pc66,
> ##100, 133, etc). I've got two 128mb sticks, one pc100, one pc133
> ##that'll run 'memtest86', L2 disabled, together for an extended time at
> ##155 mhz with -0- error at 3.55V. So is my pc100 mislabeled? No, ram
> ##is what it'll do with -0- errors over time. But I digress ....
> ##
> ## First check your bios settings. The settings easiest on the ram are
> ##the 'slow' settings. (eg, cas3-3-3, precharge disabled, no ECC for
> ##sdram). Then most ram problems can often be solved by moving the sticks
> ##to different slots and/or changing the order they're installed in.
> ##Sometimes just reseating the ram cures the problem. Next most likely
> ##culprit is the motherboard. A stick of pc66 ram that will run without
> ##errors at 133mhz (twice it's rated speed) in one motherboard, might not
> ##work reliably at all in a different (lesser) motherboard even at it's
> ##default 66mhz. It's just another situation that illustrates how
> ##important it is to base a system on a good quality motherboard and a
> ##good power supply. Many of the better motherboards (eg, Asus, Soyo,
> ##Abit, Epox, MSI, etc) provide more than the standard IO voltage to the
> ##ram by default (about +10%). This greatly enhances ram stability and
> ##performance at, or even far above it's manufacturers rating.
> ##
> ## So what'a you do? Try reseating (clean the contacts), swappin
> ##around, tryin in other motherboards (ie, see if it works in a different
> ##system), give it some more voltage (if you've got a good motherboard).
> ##'memtest86' is a good check in that you can toggle the L2 cache off/on.
> ##Many cache error problems often get blamed on the ram. If none of that
> ##fixes the problems, then give the ram to somebody you don't like ;)
> ##..... and try again with a better motherboard/power supply and some new
> ##ram ;>
