From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] The memory gremlin
Date: Thu, 09 Aug 2018 19:00:28 +0100 [thread overview]
Message-ID: <3999333.8RUdipszLB@dell_xps> (raw)
In-Reply-To: <2c25ca7c-f2fc-9528-0d63-ef2f5edfea50@verizon.net>
[-- Attachment #1: Type: text/plain, Size: 1369 bytes --]
On Thursday, 9 August 2018 17:32:33 BST Alan Grimes wrote:
> [resend, list was down...]
>
> I've been meditating on the memory gremlin on my system...
>
> The ram is Corsair, 3000mhz. (never had any problem with their sticks in
> any system ever.)
>
> Motherboard is an early release mini-ATX B350 board from Asus...
>
> Chip is a R7 1800X
>
> The pattern is: all cells test good on memcheck but occasionally there
> is a bit error somewhere. I think it is a signaling issue between the
> ram module and the memory interface in the cpu.
>
> After meditating on it, I don't think there's anything I can do about it
> given the STUPID settings the BIOS goes to... The problem with the BIOS
> is that it considers only what the RAM tells it, it does not take into
> account that the CPU is rated at 2667mhz... Well there's the answer,
> this is AMD's first product with DDR4 support, and it's not super
> awesome so simply acknowledging the limitation there, and setting the
> memory interface to 2666 (which is what the BIOS offers), it won't be
> super fast but it damn well should work. =|
Keep an eye on MoBo firmware updates, Asus are usually OK in providing updates
to stabilise their chipsets, as long as the bugs are fixable in software.
Also, if the BIOS offers DRAM timing settings increase the latency a notch and
see if that helps.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-08-09 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 16:32 [gentoo-user] The memory gremlin Alan Grimes
2018-08-09 18:00 ` Mick [this message]
2018-08-09 21:48 ` Bill Kenworthy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3999333.8RUdipszLB@dell_xps \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox