Re: The build is ON

From	Paul <nospam@needed.invalid>
Newsgroups	alt.comp.hardware.pc-homebuilt
Subject	Re: The build is ON
Date	2025-01-31 21:09 -0500
Organization	A noiseless patient Spider
Message-ID	<vnjvom$3piao$1@dont-email.me> (permalink)
References	(1 earlier) <GDOdnZIT8ZE6Kgb6nZ2dnZfqn_GdnZ2d@giganews.com> <vngl48$33h9n$1@dont-email.me> <e8KdnUszLpf7Zgb6nZ2dnZfqn_WdnZ2d@giganews.com> <1mcqpj1nb8d16322tabso5m9ciivs6ldfb@4ax.com> <3cqcnZlT2-wFoQD6nZ2dnZfqn_SdnZ2d@giganews.com>

Show all headers | View raw

On Fri, 1/31/2025 4:11 PM, bad sector wrote:
> I'm also posting about this on the asus rog forum as towbar.
> 
> Yes, it's been about 12-15 years. I had to bury my younger son in the middle of this one, the same one with whom we did two identical builds that last time. Being more than a little scatter-brained I need a Department-of-Corrections addendum here:
> 
> The power comes ON but the fans stop, i.e. a shutdown when the yellow Q-LED light illuminates. That's the second one from inboard and the manual just says "DRAM".  It took me MONTHS to get an OK from Asus about my ddr5 ECC cards being approved for this board, another month to actually get them.
> 
> https://www.amazon.ca/dp/B0BH95T7K7?ref=ppx_yo2ov_dt_b_fed_asin_title
> 
> I've reseated them several times, also tried just either one in slot-1 alone. They're otherwise in slots 2 & 4.

( ASUS X870E ProArt Creator WiFi )

*******

The picture seems wrong to me.

https://www.amazon.ca/dp/B0BH95T7K7?ref=ppx_yo2ov_dt_b_fed_asin_title

*******

https://www.kingston.com/en/memory/search/model/110021/asus-proart-x870e-creator-wifi

   "This system supports ECC or non-ECC memory depending on which processor is installed.

    Mixing ECC and non-ECC modules is not recommended. Please refer to manual or
    CPU specifications for additional information."

*******

The Kingston part,

https://www.kingston.com/en/memory/search/discontinuedmodels?partid=KSM48E40BD8KM-32HM

    Part Number: KSM48E40BD8KM-32HM   Replaced by KSM48E40BD8KI-32HA   <=== not important at the moment

    https://www.kingston.com/datasheets/KSM48E40BD8KM-32HM.pdf

    The replacement:

    https://www.kingston.com/datasheets/KSM48E40BD8KI-32HA.pdf

    The difference between the two is A-die versus M-die of Hynix.

I got a picture of a 48GB stick. I was mainly interested in whether the
chip markings are all the same (4x8+1x4 as a part of a 72-bit scheme
versus 5x8 used on 80-bit setups).

   KSM56E46BD8KM-48HM

   https://www.ebay.com/itm/204907615991

       https://i.ebayimg.com/images/g/8doAAOSwxLVmvqWS/s-l1600.png

*******

Summary:

1) Check CPU spec is for the ECC ones.

2) Check the Asus Support page for the tested memory table.
   See if the tested memory table includes mention of the CPU model used to test.
   If CPU model is never mentioned, then their ECC results (that is, if any are offered),
   are not valid without the CPU info as some sort of "hint" the combo worked.

3) When going out on a limb like this, *always* buy a single stick
   of the smallest capacity regular UDIMM (in this case NOT AN ECC),
   as test materials for your motherboard verification. This gives you
   materials for checking the end two slots (one channel at a time) for
   successful channel or slot operation.

Since you got a DRAM code, via the handy state LEDs, even without
a SPKR connected, we know it's a-beeping right now, and it's
not happy. This means either the BIOS code is too old for the CPU
(check Support page for the CPUSupport document and verify versus
whatever visible info is offered on the mobo). Or, there is some
error in the knowledge about what an AMD CPU supports for ECC sticks.

The amd.com site, you may need to do a site search in Google:

   site:amd.com   xxxx CPU

and try to get to their spec page. At one time, you could trace down
all sorts of useful stuff there, like a PDF for a bulldozer, but
the info today is a lot harder to find.

  Paul

Back to alt.comp.hardware.pc-homebuilt | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

The build is ON bad sector <forgetski@_INVALID.net> - 2025-01-30 11:36 -0500
  Re: The build is ON bad sector <forgetski@_INVALID.net> - 2025-01-30 12:32 -0500
    Re: The build is ON Paul <nospam@needed.invalid> - 2025-01-30 14:49 -0500
      Re: The build is ON bad sector <forgetski@_INVALID.net> - 2025-01-30 17:21 -0500
        Re: The build is ON John B Smith <crasso@nycap.rr.com> - 2025-01-31 15:41 -0500
          Re: The build is ON bad sector <forgetski@_INVALID.net> - 2025-01-31 16:11 -0500
            Re: The build is ON Paul <nospam@needed.invalid> - 2025-01-31 21:09 -0500
              Re: The build is ON bad sector <forgetski@_INVALID.net> - 2025-01-31 23:32 -0500
                Re: The build is ON Paul <nospam@needed.invalid> - 2025-02-01 05:31 -0500
                Re: The build is ON bad sector <forgetski@_INVALID.net> - 2025-02-01 07:31 -0500
                Re: The build is ON bad sector <forgetski@_INVALID.net> - 2025-02-01 08:39 -0500
                Re: The build is ON Paul <nospam@needed.invalid> - 2025-02-01 12:52 -0500
                Re: The build is ON bad sector <forgetski@_INVALID.net> - 2025-02-05 10:18 -0500
                Re: The build is ON Paul <nospam@needed.invalid> - 2025-02-05 12:47 -0500
                Re: The build is ON bad sector <forgetski@_INVALID.net> - 2025-02-06 08:49 -0500
                Re: The build ..chatGPT scrapped the board and/or the CPU Paul <nospam@needed.invalid> - 2025-02-06 16:01 -0500
                Re: The build ..chatGPT scrapped the board and/or the CPU bad sector <forgetski@_INVALID.net> - 2025-02-06 20:20 -0500
                Re: The build ..chatGPT scrapped the board and/or the CPU Paul <nospam@needed.invalid> - 2025-02-07 00:02 -0500
                Re: The build ..x870e ProArt-Creator in Limbo bad sector <forgetski@_INVALID.net> - 2025-02-28 09:19 -0500
                Re: The build ..x870e ProArt-Creator in Limbo Paul <nospam@needed.invalid> - 2025-02-28 10:45 -0500
                Re: The build ..x870e ProArt-Creator, Scene-1, take N bad sector <forgetski@_INVALID.net> - 2025-03-04 07:41 -0500
                Re: The build ..x870e ProArt-Creator, Scene-1, take N Paul <nospam@needed.invalid> - 2025-03-04 13:37 -0500
                Re: The build ..x870e ProArt-Creator, Scene-1, take N bad sector <forgetski@_INVALID.net> - 2025-03-21 12:49 -0400
                Re: The build ..x870e ProArt-Creator, Scene-1, take N Paul <nospam@needed.invalid> - 2025-03-21 13:52 -0400
                Re: The build ..x870e ProArt-Creator, Scene-1, take N bad sector <forgetski@_INVALID.net> - 2025-03-21 14:39 -0400
                Re: The build ..x870e ProArt-Creator, Scene-1, take N bad sector <forgetski@_INVALID.net> - 2025-03-21 16:17 -0400
                Re: The build ..x870e ProArt-Creator, Scene-1, take N Paul <nospam@needed.invalid> - 2025-03-21 23:18 -0400
                Re: The build ..x870e ProArt-Creator, Scene-1, take N bad sector <forgetski@_INVALID.net> - 2025-03-22 07:52 -0400
                Re: The build ..x870e ProArt-Creator, Scene-1, take N Paul <nospam@needed.invalid> - 2025-03-22 13:23 -0400
                Re: The build ..x870e ProArt-Creator, Scene-1, take N John B. Smith <crasso@verizon.net> - 2025-03-23 09:09 -0400
                The never-ending Asus FUBAR ___Re: The build ..x870e-Creator bad sector <forgetski@_INVALID.net> - 2025-05-05 20:25 -0400
                Re: The never-ending Asus FUBAR ___Re: The build ..x870e-Creator Paul <nospam@needed.invalid> - 2025-05-06 03:37 -0400
                Re: The never-ending Asus FUBAR ___Re: The build ..x870e-Creator bad sector <forgetski@_INVALID.net> - 2025-05-06 18:13 -0400
                Re: The never-ending Asus FUBAR ___Re: The build ..x870e-Creator Paul <nospam@needed.invalid> - 2025-05-06 19:17 -0400
                Re: The never-ending Asus FUBAR ___Re: The build ..x870e-Creator bad sector <forgetski@_INVALID.net> - 2025-05-10 09:46 -0400
                Re: The never-ending Asus FUBAR ___Re: The build ..x870e-Creator Paul <nospam@needed.invalid> - 2025-05-10 13:58 -0400

csiph-web