public inbox for [email protected]
help / color / mirror / Atom feedFrom: Justin Clift <[email protected]>
To: jack <[email protected]>
Cc: [email protected]
Subject: Re: constant crashing hardware issue and thank you TAKE AWAY
Date: Thu, 18 Apr 2024 02:19:17 +1000
Message-ID: <[email protected]> (raw)
In-Reply-To: <dW4aboom8PhJ2SGrC0j20Cl-vbr-TSIO1Qpt25cX9ALawY5rwLOUd3HkUJK5cCEVFS5ZS1AiGVzMpMW7FCFytxKhZZNTHkHyBzlJo3xVw9A=@a7q.com>
References: <dW4aboom8PhJ2SGrC0j20Cl-vbr-TSIO1Qpt25cX9ALawY5rwLOUd3HkUJK5cCEVFS5ZS1AiGVzMpMW7FCFytxKhZZNTHkHyBzlJo3xVw9A=@a7q.com>
On 2024-04-17 23:06, jack wrote:
<snip>
> As a result of this I will be checking the RAM on all my machines once
> a month or the moment a machine starts to act strange.
Once a month is overkill, and unlikely to be useful. :)
With server or enterprise grade hardware, it'll support "ECC" memory.
That has extra memory chips + supporting circuity on the memory board
so it can detect + correct most errors which happen without them causing
problems.
For the errors that it can't *correct*, it'll still generate warnings
to your system software to let you know (if you've configured it).
If you do get such a warning - or if the system starts acting funny like
you saw - that's when you'd want to run memtest on the system.
---
The other time to run memtest on the system is when you first buy or
receive a new server. You'd generally do a "burn in" test of all the
things (memory, hard disks/ssds, cpu, gpu, etc) just to make sure
everything is ok before you start using it for important stuff.
Regards and best wishes,
Justin Clift
view thread (3+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: constant crashing hardware issue and thank you TAKE AWAY
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox