Prev: Web Cam
Next: sound problem in 12.1
From: ray on 1 Feb 2008 16:48
Arun Dev wrote:
> Am 01.02.2008 14:13, Arun Dev schrieb:
>>
>> In any case memtest was stuck (no reaction to Esc, c, etc.) That's
>> not good ;-(
>>
>> I restarted memtest and it froze after 14 Sec.!
>>
>> Stole the RAM from another identical model, and memtest is running
>> again. We'll see.
>
> No use. memtest would freeze anything between 10 sec to couple of
> minutes. I give up.
>
> Thanks to everybody.
>
> Arun

what kind of hardware is it running on?
can you mess with ram timings and slow it down?
I've seen 3 athlon xp machines of various vintages pop the caps on their
mobos in the last 3 months.
(there was a rash of bad caps a few years ago.)

From: Mark South on 2 Feb 2008 05:02
On Fri, 01 Feb 2008 21:46:37 +0000, ray wrote:

> For me, a machine needs to be able to run memtest/some other benchmark
> for 72 hours before I consider it stable.

The question is whether one counts the wall time or the number of passes
as the more important criterion. Fast machines do run memtest faster.
From: Helmut Hullen on 2 Feb 2008 05:11
Hallo, Mark,

Du meintest am 02.02.08:

>> For me, a machine needs to be able to run memtest/some other
>> benchmark for 72 hours before I consider it stable.

> The question is whether one counts the wall time or the number of
> passes as the more important criterion. Fast machines do run memtest
> faster.

But time counts, too. Some memory fails after many hours of correct
working (please excuse my gerlish).

Viele Gruesse
Helmut

"Ubuntu" - an African word, meaning "Slackware is too hard for me".

From: Mark South on 2 Feb 2008 06:31
On Sat, 02 Feb 2008 11:11:00 +0100, Helmut Hullen wrote:

> Hallo, Mark,
>
> Du meintest am 02.02.08:
>
>>> For me, a machine needs to be able to run memtest/some other benchmark
>>> for 72 hours before I consider it stable.
>
>> The question is whether one counts the wall time or the number of
>> passes as the more important criterion. Fast machines do run memtest
>> faster.
>
> But time counts, too. Some memory fails after many hours of correct
> working

I don't pretend to know which is the better criterion. Just the the
longer it runs without error, the better, and that's true of passes and
walltime.

It can be heavily machine dependent. I have an old stick of PC-133 that,
when inserted in one machine, prevents the machine from booting, yet the
machine runs fine for weeks on end with other memory. In another
machine, that same stick has passed memtest for 100+ hours with no
errors, and the machine runs fine for weeks on end.

> (please excuse my gerlish).

Like most Europeans, you speak better English than the Anglophones :-)

> Viele Gruesse

Danke Schön. An sie auch.
From: Arun Dev on 2 Feb 2008 07:23
Hi ray

Am 01.02.2008 22:48, ray schrieb:
> Arun Dev wrote:
>>
>> No use. memtest would freeze anything between 10 sec to couple of
>> minutes. I give up.
>
> what kind of hardware is it running on?

Two old notebooks, make CLAXMAN Pentium-MMX 266.7 MHz, one 32 MB the
other 64 MB, both 2 GB HD.

> can you mess with ram timings and slow it down?

Good point! Next time I'm in the office I'll check that.

My original idea was to install Linux and donate to a school in
my home county in Asia.

Arun



First  |  Prev  | 
Pages: 1 2 3 4 5 6
Prev: Web Cam
Next: sound problem in 12.1