EU ASRock Rack B450D4U-V1LQ5 mATX AM4

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

luckylinux

Active Member
Mar 18, 2012
711
175
43
actually the command we're supposed to use is this below, since the other also show the ECC of L1, L2, L3 cache of the cpu

Code:
dmidecode -t memory | grep -i 'error correction'
without ECC: Error Correction Type: None

Code:
dmidecode -t memory | grep -i 'error correction'
with ECC: Error Correction Type: Multi-bit ECC
Yeah 3/4 vs 4/4, either Way it's the same. ECC works with the 3000 Series (or at least 3700X), NOT with the 5000 Series (or at least 5700X).

I also thought that maybe Aliexpress sent me a fake or something ...
 

luckylinux

Active Member
Mar 18, 2012
711
175
43
well I haven't checked if it actually does update but it thinks it can, some 202502xx update i believe on Debian 12.1 (underlying the proxmox)

Proxmox VE Helper-Scripts
Isn't it just to install the amd64-microcode Package and possibly removing the Blacklisting in e.g. /etc/modprobe.d/amd64-microcode-blacklist.conf ?

Why do we need a custom Script just for that :oops: ?
 

dbram

Member
Mar 3, 2021
78
49
18
Isn't it just to install the amd64-microcode Package and possibly removing the Blacklisting in e.g. /etc/modprobe.d/amd64-microcode-blacklist.conf ?

Why do we need a custom Script just for that :oops: ?
it does more than that I think...
msg_info "Downloading AMD processor microcode package $microcode"
curl -fsSL "https://ftp.debian.org/debian/pool/non-free-firmware/a/amd64-microcode/$microcode" -o $(basename "https://ftp.debian.org/debian/pool/non-free-firmware/a/amd64-microcode/$microcode")
msg_ok "Downloaded AMD processor microcode package $microcode"

msg_info "Installing $microcode (this might take a while)"
dpkg -i $microcode &>/dev/null
msg_ok "Installed $microcode"
 
Last edited:

luckylinux

Active Member
Mar 18, 2012
711
175
43
You are on BIOS L2.12 with the AMD Ryzen 3700X ? just to make sure it will still work with AMD Ryzen 3700X if I upgrade the BIOS now
 

dbram

Member
Mar 3, 2021
78
49
18
FYI: the same memory module on the Gigabyte MC12LE0's using a 5600X
Code:
sudo dmidecode -t memory | grep -i 'error correction'
    Error Correction Type: Multi-bit ECC
 

luckylinux

Active Member
Mar 18, 2012
711
175
43
FYI: the same memory module on the Gigabyte MC12LE0's using a 5600X
Code:
sudo dmidecode -t memory | grep -i 'error correction'
    Error Correction Type: Multi-bit ECC
Yeah I also have ECC working on an ASUS ROG STRIX B550-A GAMING with AMD Ryzen 5950X :) .

NOT the same DIMM but I don't think it's the DIMM Module. This is really the BIOS hiding the entire Overclock / Memory Frequency-Timings and most of the CBS Submenu ...

I just tried with L2.12 (latest). No joy. Even after trying to patch the settings again :(.
 

azee

Member
Jan 7, 2017
57
19
8
Stockholm, Sweden
I received my 4 sticks of "ATP X4C16QE8BNRCSE-7-LI1" in the morning. I plugged the 2 stick and wanted to verify ECC, but I can't find any ECC menu at all.
I don't even see Advanced -> AMD CBS -> UMC Common Options

I am running on Ryzen 5600x at L2.11.

I don't have any good cooler at the moment for long testing, currently using an old AM3 based cooler for verification, temp jumped to mid 60C.

imgur link
 
Last edited:

luckylinux

Active Member
Mar 18, 2012
711
175
43
I received my 4 sticks of "ATP X4C16QE8BNRCSE-7-LI1" in the morning. I plugged the 2 stick and wanted to verify ECC, but I can't find any ECC menu at all.
I don't even see Advanced -> AMD CBS -> UMC Common Options

I am running on Ryzen 5600x at L2.11.

I don't have any good cooler at the moment for long testing, currently using an old AM3 based cooler for verification, temp jumped to mid 60C.
If you read what me & ALinden recently said (I know, it can be a lot of Posts, since we also attempted to fix it) then it seems that for 5000 Series CPUs A LOT of Options in the BIOS are disabled. This includes Memory Overclocking (where DRAM Timings/Frequency/ECC Configuration Settings are located) as well as General Overclocking in the Common CBS Menu.

And ECC Memory is also disabled (by default) for this "Server" Motherboard on 5000 Series CPUs for whatever reason. Maybe to prevent Hetzner or 2nd Hand Market from using 5000 Series CPUs instead of upgrading to a more expensive Solution :( .

As @dbram confirmed, AMD Ryzen 3700X is working with proper ECC Support, so I think that the only Option (unless somebody can reverse Engineer x86 Code in the BIOS, since "Hacking" and forcing the Setting with setup_var.efi did NOT work with neither me nor ALinden) is to use a 3000 Series CPU. It sucks BIG Time :(.
 

luckylinux

Active Member
Mar 18, 2012
711
175
43
What the Hell now :oops: :oops: :oops: ?

I unplugged the Graphics Card from the x8 Slot (the non-Bifurcated one, the one closest to the Edge of the Board - the x16 wouldn't work anyways as it Bifurcates by Default and the GPU doesn't like that apparently) and installed a NIC and now ECC seems to be recognized !!

I see this:
Code:
root@LiveUbuntu02:~# dmesg | grep -i edac
[    0.647246] EDAC MC: Ver: 3.0.0
[    6.823044] EDAC MC0: Giving out device to module amd64_edac controller F19h_M20h: DEV 0000:00:18.3 (INTERRUPT)
[    6.823047] EDAC amd64: F19h_M20h detected (node 0).
[    6.823051] EDAC MC: UMC0 chip selects:
[    6.823052] EDAC amd64: MC: 0:     0MB 1:     0MB
[    6.823054] EDAC amd64: MC: 2:     0MB 3:     0MB
[    6.823057] EDAC MC: UMC1 chip selects:
[    6.823058] EDAC amd64: MC: 0:     0MB 1:     0MB
[    6.823059] EDAC amd64: MC: 2:  8192MB 3:  8192MB
And
Code:
root@LiveUbuntu02:~# sudo dmidecode -t memory | grep -i 'error correction'
    Error Correction Type: Multi-bit ECC
So MAYBE it's just a matter of a Consumer GPU being the cause of all of this ????

@azee, @ALinden : please UNPLUG your GPU from the x8 Slot (the non-Bifurcated one, the one closest to the Edge of the Board - the x16 wouldn't work anyways as it Bifurcates by Default and the GPU doesn't like that apparently) and try to boot Ubuntu/Debian, then try again the dmesg | grep -i edac and sudo dmidecode -t memory | grep -i 'error correction' Commands.

EDIT 1: Full dmidecode ... I cannot believe my Eyes !

Code:
root@LiveUbuntu02:~# dmidecode
# dmidecode 3.5
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.
Table at 0x000E6CC0.

Handle 0x0000, DMI type 0, 26 bytes
BIOS Information
    Vendor: American Megatrends International, LLC.
    Version: L2.12
    Release Date: 08/30/2024
    Address: 0xF0000
    Runtime Size: 64 kB
    ROM Size: 16 MB
    Characteristics:
        PCI is supported
        BIOS is upgradeable
        BIOS shadowing is allowed
        Boot from CD is supported
        Selectable boot is supported
        BIOS ROM is socketed
        EDD is supported
        Japanese floppy for NEC 9800 1.2 MB is supported (int 13h)
        Japanese floppy for Toshiba 1.2 MB is supported (int 13h)
        5.25"/360 kB floppy services are supported (int 13h)
        5.25"/1.2 MB floppy services are supported (int 13h)
        3.5"/720 kB floppy services are supported (int 13h)
        3.5"/2.88 MB floppy services are supported (int 13h)
        Print screen service is supported (int 5h)
        Serial services are supported (int 14h)
        Printer services are supported (int 17h)
        CGA/mono video services are supported (int 10h)
        USB legacy is supported
        BIOS boot specification is supported
        Targeted content distribution is supported
        UEFI is supported
    BIOS Revision: 5.17

Handle 0x0001, DMI type 1, 27 bytes
System Information
    Manufacturer: To Be Filled By O.E.M.
    Product Name: To Be Filled By O.E.M.
    Version: To Be Filled By O.E.M.
    Serial Number: To Be Filled By O.E.M.
    UUID: 00000000-0000-0000-0000-f3ee00f0f3ee
    Wake-up Type: Power Switch
    SKU Number: To Be Filled By O.E.M.
    Family: To Be Filled By O.E.M.

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
    Manufacturer: ASRockRack
    Product Name: B450D4U-V1L
    Version:                     
    Serial Number:                     
    Asset Tag:                     
    Features:
        Board is a hosting board
        Board is replaceable
    Location In Chassis:                     
    Chassis Handle: 0x0003
    Type: Motherboard
    Contained Object Handles: 0

Handle 0x0003, DMI type 3, 22 bytes
Chassis Information
    Manufacturer: To Be Filled By O.E.M.
    Type: Desktop
    Lock: Not Present
    Version: To Be Filled By O.E.M.
    Serial Number: To Be Filled By O.E.M.
    Asset Tag: To Be Filled By O.E.M.
    Boot-up State: Safe
    Power Supply State: Safe
    Thermal State: Safe
    Security Status: None
    OEM Information: 0x00000000
    Height: Unspecified
    Number Of Power Cords: 1
    Contained Elements: 0
    SKU Number: To Be Filled By O.E.M.

Handle 0x0004, DMI type 10, 6 bytes
On Board Device Information
    Type: Video
    Status: Enabled
    Description:    To Be Filled By O.E.M.

Handle 0x0005, DMI type 11, 5 bytes
OEM Strings
    String 1: To Be Filled By O.E.M.

Handle 0x0006, DMI type 32, 20 bytes
System Boot Information
    Status: No errors detected

Handle 0x0007, DMI type 44, 9 bytes
Unknown Type
    Header and Data:
        2C 09 07 00 FF FF 01 01 00

Handle 0x0008, DMI type 18, 23 bytes
32-bit Memory Error Information
    Type: OK
    Granularity: Unknown
    Operation: Unknown
    Vendor Syndrome: Unknown
    Memory Array Address: Unknown
    Device Address: Unknown
    Resolution: Unknown

Handle 0x0009, DMI type 16, 23 bytes
Physical Memory Array
    Location: System Board Or Motherboard
    Use: System Memory
    Error Correction Type: Multi-bit ECC
    Maximum Capacity: 128 GB
    Error Information Handle: 0x0008
    Number Of Devices: 4

Handle 0x000A, DMI type 19, 31 bytes
Memory Array Mapped Address
    Starting Address: 0x00000000000
    Ending Address: 0x000BFFFFFFF
    Range Size: 3 GB
    Physical Array Handle: 0x0009
    Partition Width: 1

Handle 0x000B, DMI type 19, 31 bytes
Memory Array Mapped Address
    Starting Address: 0x00100000000
    Ending Address: 0x0043FFFFFFF
    Range Size: 13 GB
    Physical Array Handle: 0x0009
    Partition Width: 1

Handle 0x000C, DMI type 7, 27 bytes
Cache Information
    Socket Designation: L1 - Cache
    Configuration: Enabled, Not Socketed, Level 1
    Operational Mode: Write Back
    Location: Internal
    Installed Size: 512 kB
    Maximum Size: 512 kB
    Supported SRAM Types:
        Pipeline Burst
    Installed SRAM Type: Pipeline Burst
    Speed: 1 ns
    Error Correction Type: Multi-bit ECC
    System Type: Unified
    Associativity: 8-way Set-associative

Handle 0x000D, DMI type 7, 27 bytes
Cache Information
    Socket Designation: L2 - Cache
    Configuration: Enabled, Not Socketed, Level 2
    Operational Mode: Write Back
    Location: Internal
    Installed Size: 4 MB
    Maximum Size: 4 MB
    Supported SRAM Types:
        Pipeline Burst
    Installed SRAM Type: Pipeline Burst
    Speed: 1 ns
    Error Correction Type: Multi-bit ECC
    System Type: Unified
    Associativity: 8-way Set-associative

Handle 0x000E, DMI type 7, 27 bytes
Cache Information
    Socket Designation: L3 - Cache
    Configuration: Enabled, Not Socketed, Level 3
    Operational Mode: Write Back
    Location: Internal
    Installed Size: 32 MB
    Maximum Size: 32 MB
    Supported SRAM Types:
        Pipeline Burst
    Installed SRAM Type: Pipeline Burst
    Speed: 1 ns
    Error Correction Type: Multi-bit ECC
    System Type: Unified
    Associativity: 16-way Set-associative

Handle 0x000F, DMI type 4, 48 bytes
Processor Information
    Socket Designation: AM4
    Type: Central Processor
    Family: Zen
    Manufacturer: Advanced Micro Devices, Inc.
    ID: 12 0F A2 00 FF FB 8B 17
    Signature: Family 25, Model 33, Stepping 2
    Flags:
        FPU (Floating-point unit on-chip)
        VME (Virtual mode extension)
        DE (Debugging extension)
        PSE (Page size extension)
        TSC (Time stamp counter)
        MSR (Model specific registers)
        PAE (Physical address extension)
        MCE (Machine check exception)
        CX8 (CMPXCHG8 instruction supported)
        APIC (On-chip APIC hardware supported)
        SEP (Fast system call)
        MTRR (Memory type range registers)
        PGE (Page global enable)
        MCA (Machine check architecture)
        CMOV (Conditional move instruction supported)
        PAT (Page attribute table)
        PSE-36 (36-bit page size extension)
        CLFSH (CLFLUSH instruction supported)
        MMX (MMX technology supported)
        FXSR (FXSAVE and FXSTOR instructions supported)
        SSE (Streaming SIMD extensions)
        SSE2 (Streaming SIMD extensions 2)
        HTT (Multi-threading)
    Version: AMD Ryzen 7 5700X 8-Core Processor           
    Voltage: 1.1 V
    External Clock: 100 MHz
    Max Speed: 4650 MHz
    Current Speed: 3400 MHz
    Status: Populated, Enabled
    Upgrade: Socket AM4
    L1 Cache Handle: 0x000C
    L2 Cache Handle: 0x000D
    L3 Cache Handle: 0x000E
    Serial Number: Unknown
    Asset Tag: Unknown
    Part Number: Unknown
    Core Count: 8
    Core Enabled: 8
    Thread Count: 16
    Characteristics:
        64-bit capable
        Multi-Core
        Hardware Thread
        Execute Protection
        Enhanced Virtualization
        Power/Performance Control

Handle 0x0010, DMI type 18, 23 bytes
32-bit Memory Error Information
    Type: OK
    Granularity: Unknown
    Operation: Unknown
    Vendor Syndrome: Unknown
    Memory Array Address: Unknown
    Device Address: Unknown
    Resolution: Unknown

Handle 0x0011, DMI type 17, 92 bytes
Memory Device
    Array Handle: 0x0009
    Error Information Handle: 0x0010
    Total Width: Unknown
    Data Width: Unknown
    Size: No Module Installed
    Form Factor: Unknown
    Set: None
    Locator: DIMM 0
    Bank Locator: P0 CHANNEL A
    Type: Unknown
    Type Detail: Unknown

Handle 0x0012, DMI type 18, 23 bytes
32-bit Memory Error Information
    Type: OK
    Granularity: Unknown
    Operation: Unknown
    Vendor Syndrome: Unknown
    Memory Array Address: Unknown
    Device Address: Unknown
    Resolution: Unknown

Handle 0x0013, DMI type 17, 92 bytes
Memory Device
    Array Handle: 0x0009
    Error Information Handle: 0x0012
    Total Width: 72 bits
    Data Width: 64 bits
    Size: 16 GB
    Form Factor: DIMM
    Set: None
    Locator: DIMM 1
    Bank Locator: P0 CHANNEL A
    Type: DDR4
    Type Detail: Synchronous Unbuffered (Unregistered)
    Speed: 2400 MT/s
    Manufacturer: Samsung
    Serial Number: 35A871F8
    Asset Tag: Not Specified
    Part Number: M391A2K43BB1-CRC 
    Rank: 2
    Configured Memory Speed: 2400 MT/s
    Minimum Voltage: 1.2 V
    Maximum Voltage: 1.2 V
    Configured Voltage: 1.2 V
    Memory Technology: DRAM
    Memory Operating Mode Capability: Volatile memory
    Firmware Version: Unknown
    Module Manufacturer ID: Bank 1, Hex 0xCE
    Module Product ID: Unknown
    Memory Subsystem Controller Manufacturer ID: Unknown
    Memory Subsystem Controller Product ID: Unknown
    Non-Volatile Size: None
    Volatile Size: 16 GB
    Cache Size: None
    Logical Size: None

Handle 0x0014, DMI type 20, 35 bytes
Memory Device Mapped Address
    Starting Address: 0x00000000000
    Ending Address: 0x003FFFFFFFF
    Range Size: 16 GB
    Physical Device Handle: 0x0013
    Memory Array Mapped Address Handle: 0x000B
    Partition Row Position: Unknown
    Interleave Position: Unknown
    Interleaved Data Depth: Unknown

Handle 0x0015, DMI type 18, 23 bytes
32-bit Memory Error Information
    Type: OK
    Granularity: Unknown
    Operation: Unknown
    Vendor Syndrome: Unknown
    Memory Array Address: Unknown
    Device Address: Unknown
    Resolution: Unknown

Handle 0x0016, DMI type 17, 92 bytes
Memory Device
    Array Handle: 0x0009
    Error Information Handle: 0x0015
    Total Width: Unknown
    Data Width: Unknown
    Size: No Module Installed
    Form Factor: Unknown
    Set: None
    Locator: DIMM 0
    Bank Locator: P0 CHANNEL B
    Type: Unknown
    Type Detail: Unknown

Handle 0x0017, DMI type 18, 23 bytes
32-bit Memory Error Information
    Type: OK
    Granularity: Unknown
    Operation: Unknown
    Vendor Syndrome: Unknown
    Memory Array Address: Unknown
    Device Address: Unknown
    Resolution: Unknown

Handle 0x0018, DMI type 17, 92 bytes
Memory Device
    Array Handle: 0x0009
    Error Information Handle: 0x0017
    Total Width: Unknown
    Data Width: Unknown
    Size: No Module Installed
    Form Factor: Unknown
    Set: None
    Locator: DIMM 1
    Bank Locator: P0 CHANNEL B
    Type: Unknown
    Type Detail: Unknown

Handle 0x0019, DMI type 13, 22 bytes
BIOS Language Information
    Language Description Format: Long
    Installable Languages: 1
        en|US|iso8859-1
    Currently Installed Language: en|US|iso8859-1

Handle 0x001A, DMI type 127, 4 bytes
End Of Table
It really looks like UNPLUGGING the GPU from the x16 Slot made ECC Work. I cannot state the BIOS Menu because, well, now I cannot access it. I didn't check if the Onboard VGA Port worked, it did NOT with the 2600X before though. I didn't test with the 5700X though ...
 

RolloZ170

Well-Known Member
Apr 24, 2016
7,996
2,508
113
germany
microcode of BIOS can be updated with a Hex editor, but will not be accepted by AFU flash tools after mod. i guess.
the microcode are located in a padding after AmiNvramMainAreaGuid

Base: 57000h, Offset: 57000h
Full size: 8F8000h (9404416)
the microcodes have a size of 0xC80 or 0x15C0
the first microcode ( cpu00800F82_ver0800820D_2019-04-16_B0DE605C ) is located at 24D000h
 
  • Like
Reactions: luckylinux

luckylinux

Active Member
Mar 18, 2012
711
175
43
microcode of BIOS can be updated with a Hex editor, but will not be accepted by AFU flash tools after mod. i guess.
the microcode are located in a padding after AmiNvramMainAreaGuid

Base: 57000h, Offset: 57000h
Full size: 8F8000h (9404416)
the microcodes have a size of 0xC80 or 0x15C0
the first microcode ( cpu00800F82_ver0800820D_2019-04-16_B0DE605C ) is located at 24D000h
But the weird thing is that now ECC started working as soon as I unplugged the Graphics Card I was using to troubleshoot.

Let me try that onboard VGA Sucker now with the 5700X instead of the 2600X where it didn't want to work at all ...
 

luckylinux

Active Member
Mar 18, 2012
711
175
43
unpowered the CPU the first time ? ( standby power to PCH / SoC )
Possible as well ... But the VGA only outputs a blinking Cursor now. The VGA was working fine though before in Linux Lightdm Login Manager I rebooted the System (which I previously booted without GPU and with NIC).

Weird weird weird ... Maybe still good after all though :)

EDIT 1: VGA Output works also in BIOS. Took FOREVER to start displaying anything, was stuck at BIOS Code B2 !

EDIT 2: Proof. But I still cannot see anything more than before

1744478825012.png

But at least for the 2nd Time it still works
Code:
root@LiveUbuntu02:~# sudo dmidecode -t memory | grep -i 'error correction'
    Error Correction Type: Multi-bit ECC
root@LiveUbuntu02:~# dmesg | grep -i edac
[    0.648230] EDAC MC: Ver: 3.0.0
[    6.599318] EDAC MC0: Giving out device to module amd64_edac controller F19h_M20h: DEV 0000:00:18.3 (INTERRUPT)
[    6.599321] EDAC amd64: F19h_M20h detected (node 0).
[    6.599325] EDAC MC: UMC0 chip selects:
[    6.599326] EDAC amd64: MC: 0:     0MB 1:     0MB
[    6.599328] EDAC amd64: MC: 2:     0MB 3:     0MB
[    6.599331] EDAC MC: UMC1 chip selects:
[    6.599332] EDAC amd64: MC: 0:     0MB 1:     0MB
[    6.599333] EDAC amd64: MC: 2:  8192MB 3:  8192MB
EDIT 3: I actually just wanted to test a NIC before throwing it away, that's why I wanted to use the Riser ... I will try to Power Off again later and try with the PCIe GPU once more to see if it's the GPU or if it's as you @RolloZ170 suggest (Complete Power Off).
 
Last edited:

luckylinux

Active Member
Mar 18, 2012
711
175
43
OK, so it is like @RolloZ170 said.

You need a COMPLETE Poweroff (don't know for how long exactly, give it at least 30 Seconds with the Power Cord DETACHED).

I rebooted with the Graphics Card installed and it still works with ECC. And I still can't see these Menus that should exist in the BIOS ...

Note that I am on BIOS L2.12 now. But BIOS update alone did NOT fix this !

Code:
root@LiveUbuntu02:~# sudo dmidecode -t memory | grep -i 'error correction'
    Error Correction Type: Multi-bit ECC
root@LiveUbuntu02:~# dmesg | grep -i edac
[    0.650354] EDAC MC: Ver: 3.0.0
[    6.543072] EDAC MC0: Giving out device to module amd64_edac controller F19h_M20h: DEV 0000:00:18.3 (INTERRUPT)
[    6.543076] EDAC amd64: F19h_M20h detected (node 0).
[    6.543080] EDAC MC: UMC0 chip selects:
[    6.543082] EDAC amd64: MC: 0:     0MB 1:     0MB
[    6.543084] EDAC amd64: MC: 2:     0MB 3:     0MB
[    6.543088] EDAC MC: UMC1 chip selects:
[    6.543089] EDAC amd64: MC: 0:     0MB 1:     0MB
[    6.543091] EDAC amd64: MC: 2:  8192MB 3:  8192MB
I used the Scripts inside the SSP Subfolder. Boot into UEFI Shell. Run patch.nsh. Reboot with reset. Boot into UEFI Shell. Run read.nsh. Shutdown. Disconnect Power Cord for at least 30 Seconds. Boot into Debian/Ubuntu and check dmesg / dmidecode.

Note: feel free to download setup_var.efi from the Official Github Page, you don't need to use the one that I provided if you don't trust it. I just don't want starting to have to edit Subfolders and whatnot or Upload the 8 Patch + Read Scripts individually depending on what CPU we want to test against.

It still sucks that nothing shows up in the BIOS Menu. But I guess this is better than nothing, right :) ?

EDIT 1: maybe also worth trying with JUST the BIOS Update + Poweroff. But from what I recall from @ALinden, that didn't seem to work. Not sure if he did a complete Power Off though ...

EDIT 2: @ALinden, @azee: can you try the Procedure with the Poweroff as Indicated in this Post ? I'm NOT getting the Menu showing up in BIOS but ECC seems to have started working now !

EDIT 3: Procedure now Copied and somewhat better formatted on GitHub Repository
 

Attachments

Last edited:
  • Love
Reactions: RolloZ170

gb00s

Well-Known Member
Jul 25, 2018
1,321
714
113
Poland
In my humble opinion and being retarded for life, why a motherboard shall support ECC w/3700x but won't with 5700X. If I'm not mistaken these were HETZNER boards for AX41 environments that were offered with Ryzen 5 3600 and 5600's with ECC. They are still in business .... with ECC.
 
  • Like
Reactions: b3rrytech and dbram

azee

Member
Jan 7, 2017
57
19
8
Stockholm, Sweden
OK, so it is like @RolloZ170 said.

You need a COMPLETE Poweroff (don't know for how long exactly, give it at least 30 Seconds with the Power Cord DETACHED).

I rebooted with the Graphics Card installed and it still works with ECC. And I still can't see these Menus that should exist in the BIOS ...

Note that I am on BIOS L2.12 now. But BIOS update alone did NOT fix this !

Code:
root@LiveUbuntu02:~# sudo dmidecode -t memory | grep -i 'error correction'
    Error Correction Type: Multi-bit ECC
root@LiveUbuntu02:~# dmesg | grep -i edac
[    0.650354] EDAC MC: Ver: 3.0.0
[    6.543072] EDAC MC0: Giving out device to module amd64_edac controller F19h_M20h: DEV 0000:00:18.3 (INTERRUPT)
[    6.543076] EDAC amd64: F19h_M20h detected (node 0).
[    6.543080] EDAC MC: UMC0 chip selects:
[    6.543082] EDAC amd64: MC: 0:     0MB 1:     0MB
[    6.543084] EDAC amd64: MC: 2:     0MB 3:     0MB
[    6.543088] EDAC MC: UMC1 chip selects:
[    6.543089] EDAC amd64: MC: 0:     0MB 1:     0MB
[    6.543091] EDAC amd64: MC: 2:  8192MB 3:  8192MB
I used the Scripts inside the SSP Subfolder. Boot into UEFI Shell. Run patch.nsh. Reboot with reset. Boot into UEFI Shell. Run read.nsh. Shutdown. Disconnect Power Cord for at least 30 Seconds. Boot into Debian/Ubuntu and check dmesg / dmidecode.

Note: feel free to download setup_var.efi from the Official Github Page, you don't need to use the one that I provided if you don't trust it. I just don't want starting to have to edit Subfolders and whatnot or Upload the 8 Patch + Read Scripts individually depending on what CPU we want to test against.

It still sucks that nothing shows up in the BIOS Menu. But I guess this is better than nothing, right :) ?

EDIT 1: maybe also worth trying with JUST the BIOS Update + Poweroff. But from what I recall from @ALinden, that didn't seem to work. Not sure if he did a complete Power Off though ...

EDIT 2: @ALinden, @azee: can you try the Procedure with the Poweroff as Indicated in this Post ? I'm NOT getting the Menu showing up in BIOS but ECC seems to have started working now !
will this file works with 5600X, or do i need to change any thing? i am quite new with bios mod, so i just want to be sure.
and i attached no graphic or lan card in either of pcie slots. with stock L2.11 (complete power off)
Code:
 sudo dmidecode -t memory | grep -i 'error correction'
output was
Code:
Error Correction Type: None
 

luckylinux

Active Member
Mar 18, 2012
711
175
43
In my humble opinion and being retarded for life, why a motherboard shall support ECC w/3700x but won't with 5700X.
It's completely Stupid, I agree. There is IMHO no Technical Reason why a Motherboard should not work with ECC Enabled with a 5700X ...

After all, the Memory Controller these Days (and for a long Time actually) it's on/in the CPU !

There can be several Reasons, with higher or lower degree of Intent and Incompetence:
- Possibly some Size Limitation on the BIOS Chip (I didn't check myself, but L2.12 is claimed to only Support 3000/5000), although I doubt this explains why a HUGE Menu is getting hidden by this CPU
- Somebody ***** up the BIOS and nobody checked if ECC was actually enabled (via dmidecode or dmesg | grep -i edac)
- Some Sales Person decided to hold off ECC Support as a "smart" Way to get Hosting Company to forcefully upgrade their Motherboards when they started buying Ryzen 5000 Series CPU. IMHO they shot themselves in the Foot doing that ...

At the End of the Day does it really Matter if it's Evil, Stupid or Evil+Stupid ?

Either you go on live with it (your Choice !), ask ASRock for a BIOS Fix (which, to another User on Reddit, said they are NOT going to do, since this is a Custom Motherboard for Hetzner) or try to fix it yourself (like I tried).

We can argue all Day long why this is ********, we will not solve it like that. It is NOT working with ECC on 5600X and 5700X by Default, tested on L2.09 (me & ALinden), L2.11 (azee) and L2.12 (me & ALinden). That is a Fact. If you want, you can try ask ASRock why their Quality Department is non-existent.

If I'm not mistaken these were HETZNER boards for AX41 environments that were offered with Ryzen 5 3600 and 5600's with ECC. They are still in business .... with ECC.
I don't know, I have a AX101 at Hetzner and that is on an ASUS Motherboard, not ASROCK, so not sure ...
Did anybody check if ECC was actually working ? The problem is that the System boots correctly with ECC Memory, it just won't have the ECC Feature enabled.

And unless you happen to catch it while you are having 1 Bit Flip once per year (which, in most Cases, is not *that* Critical, unless it happens at exactly the wrong Place, as in Murphy's Law) causing some Serious Corruption in your 100 Million EUR Mission Critical Database or whatever, then it will go unnoticed. The other Scenario of course is if your Memory is faulty and has A LOT OF ERRORS, then your entire Server will start corrupting Data in Memory and on Disk all the Time. If that didn't happen or if somebody didn't notice, then again the Issue went unnoticed.
 
Last edited:
  • Like
Reactions: RolloZ170