Several of you have mentioned finding bad RAM with memtest86 lately. How long to you usually let it run?
On Sunday 5 June 2005 11:40, Jonathan Hutchins wrote:
Several of you have mentioned finding bad RAM with memtest86 lately. How long to you usually let it run?
In my experience, if it's going to find something, it finds it in less than an hour.
I would usually start it before I went on a lunch break and if it didn't find anything by the time I returned, I figured the memory was good.
Jason Clinton wrote:
On Sunday 5 June 2005 11:40, Jonathan Hutchins wrote:
Several of you have mentioned finding bad RAM with memtest86 lately. How long to you usually let it run?
In my experience, if it's going to find something, it finds it in less than an hour.
I would usually start it before I went on a lunch break and if it didn't find anything by the time I returned, I figured the memory was good.
That leaves some variables that have squicked better than us . The case example of personal note was thermal- server not re-installed into place it lived when in real use. A eurostyle wall unit - lacking good breathing room. Passed FINE overnight in a cool shop basement.
This is of course completely dependent on how much memory you have and how fast your machine is. ;-)
The better question would be how many passes do you allow it to perform. I usually say about 2 since that should give the machine plenty of time for the machine to warm up from a cold boot.
On Sun, 5 Jun 2005, Jonathan Hutchins wrote:
Several of you have mentioned finding bad RAM with memtest86 lately. How long to you usually let it run?
//========================================================\ || D. Hageman [email protected] || \========================================================//
================================================================== On Sun, Jun 05, 2005 at 11:40:40AM -0500, Jonathan Hutchins wrote:
Several of you have mentioned finding bad RAM with memtest86 lately. How long do you usually let it run?
I let memtest86 run for about 5 minutes, then it started reporting errors. Shortly after that it locked up. So in my experience, 10 minutes proved to be adequate.
-- Hal
On Sun, Jun 05, 2005 at 11:40:40AM -0500, Jonathan Hutchins wrote:
Several of you have mentioned finding bad RAM with memtest86 lately. How long to you usually let it run?
I have seen some RAM pass 5-7 times before failing, so I usually let it run that long, maybe even 10 passes to be safe. And as mentioned, the amount of time for each pass will vary with the processor and amount of RAM.
Jeremy
-
D. Hageman -
Hal Duston -
Jason Clinton -
Jeremy Turner -
Jonathan Hutchins -
Oren Beck