Groups | Search | Server Info | Login | Register

Groups > alt.comp.hardware.pc-homebuilt > #43949

Re: The never-ending Asus FUBAR ___Re: The build ..x870e-Creator

Show all headers | View raw

On 5/6/25 19:17, Paul wrote:
> On Tue, 5/6/2025 6:13 PM, bad sector wrote:
>> On 5/6/25 03:37, Paul wrote:
>>> On Mon, 5/5/2025 8:25 PM, bad sector wrote:
>>>> On 2/28/25 10:45, Paul wrote:
>>>>> On Fri, 2/28/2025 9:19 AM, bad sector wrote:
>>>>>
>>>>>> The saga continues..
>>>>>>
>>>>>> Couldn't get the 30-day refund at amazon because my sun's death preoccupied the family and I missed the deadline by 3 days. So it went back to the shop on RMA, after some weeks they advised that 'although it posted OK' they were sending me a new one. More weeks later I pulled on their chain and they replied _NIL-STOCK_ but that I could get a comparable board instead (some ROG gaming board): declined. I have a feeling that an upgrade version of the same board might become the replacement candidate (xY70e?).
>>>>>>
>>>>>
>>>>> The time to do a build and test it, is pretty limited.
>>>>>
>>>>> It's one of the reasons I spent extra time "single sourcing"
>>>>> builds in the past. So a complete kit of parts would
>>>>> arrive on Day 0 and the testing could begin as soon
>>>>> as I could find time to assemble it.
>>>>>
>>>>> It's a lot harder to be timely on stuff, if the sellers
>>>>> are sending items "as they have them". Your effective
>>>>> test window can be a lot shorter that way. But these
>>>>> days, I guess that's unavoidable. Newegg.ca, I don't think they
>>>>> single ship any more. They seem to operate in dribble mode.
>>>>>
>>>>>       Paul
>>>>
>>>> Having just received the long-awaited edcc cards testing revealed that booting hangs on the DRAM (yellow) LED if either #3 or #4 ddr5 slot is occupied. I got identical cards as reported in my ECC thread but can only use them in slots #1 & #2 which is unaceptable. UP TO HERE with Asus sending me defective or returned scrap.
>>>>
>>>> Come to think of it... when a customer buys a new product and that product breaks in use but during the warranty period then repair service under warranty applies. HOWEVER if the product is defective on receipt, considering that what the customer had paid for was a NEW and defect-free product, the only acceptable remedy is ANOPTHER NEW (sealed) product and not a repaired one or a previously delivered to some other customer good or reopaired one!
>>>>
>>>
>>>                 A-Bus   B-Bus
>>>                   |       |
>>>             A1 ------   ------ B1
>>>                   |       |
>>>             A2 ------   ------ B2  <=== fill the end of each bus first, A2 and B2 are to be filled first.
>>>
>>> When laid out on the board, they are arranged as two buses, one after the other.
>>> The first pair, have no common electrical signals with the second pair.
>>> And as in the other diagram, A2 and B2 are to be filled first. The CPU
>>> is the source of the "A" and "B" parts.
>>>
>>>       B -----------------+--+
>>>                          |  |
>>> CPU          A1  A2   B1  B2
>>>                 |  |
>>>       A --------+--+
>>
>> The manual says to populate A2 & B2 first, by deduction A2 & B2 ONLY if there are only 2 cards. This is the combination I tried 1st but it led to no boot. The manual also states that the cards should be the same make and model (they are, both 5600).
>>
>>> But when they're drawn as buses, they look like the first drawing.
>>>
>>> The A2 and B2 sticks, have programmable terminators. If the bus
>>> impedance was 55 ohms or 35 ohms, it is up to the BIOS to set the
>>> termination inside the memory chip to match that.
>>
>> By 'sticks' here do you mean the slots?
>>
>> I cannot find anything in the BIOS for RAM cartd sequencing or calibration other than RAM speed and I'm happy with 5600 which I presume comes automatically.
>>
>>
>>> Then, there are
>>> no reflections off the end of the bus, and the signal quality is
>>> undisturbed. When four sticks are present, and especially at high
>>> speed, the "compromise" terminator settings (a percentage type
>>> setting), the compromise is not sufficient for 5600 or 6400 speeds.
>>> Apparently only lower bus speed choices settle in time with four sticks.
>>>
>>> On older memory standards, the resistors were external, and right
>>> after the A2 and B2 stick. The resistors were not programmable,
>>> and if the engineer was wrong about the value, then "too bad".
>>>
>>>      Paul
>>
>> At first I thought I had bad cards, it rather seems that I have a bad board (AGAIN!).
>>
> 
> You can try one DDR5 stick in A2 slot or one DDR5 stick in B2 slot.
> 
> It should work with just one stick.
> 
> The keying and slot shape are supposed to be part of verifying
> they are the right kinds of items.
> 
> You would also want to review again, whether it is possible
> a BIOS version issue is present. On my first Zen3, it would not
> work until I presented a newer version of BIOS. This is necessary,
> when the boards have been sitting in inventory for a while
> (part of "first batch" for the board). And as I explained before,
> I misinterpreted the red flashing LED as meaning it was in the
> middle of flashing, when in fact the flashing red LED was an
> error indicator. The manual did not say.
> 
> My last AM4 purchase, the motherboard is at least 2 years old.
> And it is now flashed up to date. It's missing one security update,
> but, it won't be getting that either. No problem.
> 
> *******
> 
> I seem to remember you had a "test stick" you were using before.
> Do you have anything like that ? An ordinary DDR5, smallest one
> they make like 8GB or so. Something cheap you can use for test
> of A2 slot and B2 slot. This would be a non ECC, something you
> can use to "verify" the motherboard core is functional.
> 
> In the old days, I never had to flash a BIOS. But from ten years
> ago onwards, BIOS flashing is at least 50% of boards. The board ten
> years ago, had a microcontroller for flashing, and it could even
> flash the empty motherboard with no CPU inserted or DRAM inserted.
> All the "computing" for the BIOS flash, was done by a small microcontroller
> which just flashed an SPI. The interface was USB key only, and that
> is all it could read. It was push button activated. Insert stick.
> Push button. These usually have a red status LED placed in a
> random location :-)
> 
> The motherboards today, may want the items (CPU/DRAM) inserted while
> you do that, as the flashing is done by the main CPU. All that
> to save a buck on the microcontroller.
> 
> If the LED indicators (progress indicators) are working,
> that means some amount of the system is operational. If
> the SPKR is beeping the missing RAM sequence (could be three beeps),
> then you'll need to flash up the BIOS to ensure the very latest
> RAM parsing and initialization code is present. The BIOS
> needs to read the SPD on each DIMM and decide what to do.
> 
> I never expect a modern board, to just "work" right away.
> There is always an evening of time wasted at this stuff.
> And I don't think changing brands will make that much
> different -- the builds are intended for "experienced"
> burnt-out employees to assemble :-) They're used to having
> to flash the boards.
> 
> You should also do a Google on the board model number,
> and check the comments for a "common theme". If everyone seems
> to have the same problem on the build, that could be your
> problem as well.
> 
>     Paul

Having just ended an exchange with Asus support, and having somewhere 
stated that these cards are compatible with the board, I now feel 
obliged to clarify that midleading statement. Asus have advised me that 
this memory is NOT compatible as it is not listed on the Asus 
compatibility list.

Kingston KSM56E46BD8KM-48HM ecc ddr5 cards are NOT
compatible with the Asus x870e proart creator board!

They 'work' but NOT in the recommended A2/B2 layout.

NO ddr5/ecc cards go above 32gb or 4800 on the Asus support site 
compatibility list. *Buyers beware*, I made the mistake of believing the 
Kingston site where these cards are listed as compatible with this 
board. With identical revenues one could just as justifiably state that 
it is the Asus motherbord that is incompatible with the Kingston memory.

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