What do errors in MEMTEST-86 mean?
- WarAdvocat
- DBB Defender
- Posts: 3035
- Joined: Sun Jun 23, 2002 2:01 am
- Location: Fort Lauderdale, FL USA
What do errors in MEMTEST-86 mean?
I did an overnight memtest run (18+ hours...from bedtime until I got home from work) on a computer that's been bluescreening on us, and it got a crapload of errors.
Last night I ran a baseline for comparison on a nearly identical computer, and after 8 hours have no errors.
My next step is to transfer the RAM from the error giving computer into mine and run more tests, I suppose.
Could a problem processor generate Memtest errors? Also of concern is the cheapie power supply in that box, haven't gotten around to upgrading it yet.
Last night I ran a baseline for comparison on a nearly identical computer, and after 8 hours have no errors.
My next step is to transfer the RAM from the error giving computer into mine and run more tests, I suppose.
Could a problem processor generate Memtest errors? Also of concern is the cheapie power supply in that box, haven't gotten around to upgrading it yet.
- Flatlander
- DBB Fleet Admiral
- Posts: 2419
- Joined: Thu Apr 15, 1999 2:01 am
- Location: Pennsylvania
- Contact:
- Testiculese
- DBB Material Defender
- Posts: 4689
- Joined: Sun Nov 11, 2001 3:01 am
- WarAdvocat
- DBB Defender
- Posts: 3035
- Joined: Sun Jun 23, 2002 2:01 am
- Location: Fort Lauderdale, FL USA
- WarAdvocat
- DBB Defender
- Posts: 3035
- Joined: Sun Jun 23, 2002 2:01 am
- Location: Fort Lauderdale, FL USA
- Mobius
- DBB_Master
- Posts: 7940
- Joined: Sun Jun 03, 2001 2:01 am
- Location: Christchurch, New Zealand
- Contact:
MEMTEST86 --- we are talking the command-line-boot-from-a-floppy version aren't we? Because the version which runs in windows isn't worth spit.
If you encounter a single error - then you have bad RAM and it needs replaced.
Often, you can function with a bad stick, and it'll only fail (and crash the PC with the "IRQ NOT EQUAL", or the classic "ERROR AT #xxxxxxxx" BSOD) during certain tasks, like a software install.
You *can* run like this - but it's not recommended.
Remember, a retailer will probably accept a bad stick back, even outside the warranty period. Give it a go anyway.
If you encounter a single error - then you have bad RAM and it needs replaced.
Often, you can function with a bad stick, and it'll only fail (and crash the PC with the "IRQ NOT EQUAL", or the classic "ERROR AT #xxxxxxxx" BSOD) during certain tasks, like a software install.
You *can* run like this - but it's not recommended.
Remember, a retailer will probably accept a bad stick back, even outside the warranty period. Give it a go anyway.
- Krom
- DBB Database Master
- Posts: 16137
- Joined: Sun Nov 29, 1998 3:01 am
- Location: Camping the energy center. BTW, did you know you can have up to 100 characters in this location box?
- Contact:
Oh shut up already, if you encounter an error the first thing you try is check and make sure the ram is running in spec. Try relaxing the latency or upping the voltage and see if it fixes it before you run out getting new RAM. I had errors in my old BH5 RAM, all I did was boost it from 2.6 to 2.7v and the errors were gone.Mobius wrote:If you encounter a single error - then you have bad RAM and it needs replaced.