1 Rookie

 • 

2 Posts

 • 

2 Points

252

February 11th, 2026 08:29

Dell R640 Memory Incompatible Error (mixed Dimm)

Hello guys,

I need your advise why I received an error message on a Dell R640 with latest BIOS and iDRAC firmware.

We had originally 8 Samsung Dimms with Part number M393A8G40AB2 (64GB 2Rx4 PC4-3200AA) in the server.

We ordered new Dimm modules Dell certified from a reseller with the same part Number (Samsung M393A8G40AB2 - Dell par number SNPP2MYXC/64G), but somehow the server refuses to boot when mixing both new and original RAM modules.

Server boots fine with 2 or 4 or 8 new dimms. And boots fine with the old 2, 4 or 8 original dimms of course.

But when mixing original+ new dimms, it gives an error. Tried 8+8, 4+4, 2+2, nothing works.


Of course I followed the Dell memory population guide. Even with minimal boot (1 dimm per CPU) when mixing it does not boot.

Part numbers are the same except the last 5 characters (that seems the revision number, shoud not gives a difference?):

  • original Dimms: M393A8G40AB2 – CWEC0 (64GB 2Rx4 PC4-3200AA - RA2 - 12 - MH1)

  • new Dimms : M393A8G40AB2 - CWEBY (64GB 2Rx4 PC4-3200AA - RA2 - 12 - DC1)

Any ideas whats could cause the problem ? Any solutions you are thinking about?

CDN media

CDN media

Moderator

 • 

3.8K Posts

 • 

25.4K Points

February 13th, 2026 10:18

Hi,

  1. Likely causes (ranked)

    • Memory rank/firmware/PCB trace differences between manufacturing revisions (the CWEC0 vs CWEBY suffixes). Even with same main P/N, Samsung/ODM changes (SPD firmware, minor timing/PCB layout, ECC/thermal/resistor packing) can make modules incompatible when mixed.
    • SPD/EEPROM mismatch causing the memory controller to reject a mixed configuration.
    • Subtle voltage/timing differences (one set running at a different default/tighter timing) causing training failure when mixed.
    • Broken or counterfeit modules (less likely since new set boots alone, but could be a subtle compatibility variant).
    • CPU memory controller sensitivity — some Skylake/Skylake-SP controllers are picky about mixing ranks/manufacturers even if P/N matches.
    • Slot/trace or seating issue revealed only with mixed population (less likely if pure sets work).
  2. Quick tests to narrow down

    • Boot with only one module per CPU: try one old in CPU1 and one new in CPU2 (and vice versa). You said 1 per CPU fails — confirm combinations (old in slot A1, new in slot A1, old in A1 + new in B1, new A1 + old B1). Document which specific slot combos fail or pass.
    • Swap CPUs (if you have two) to rule out one CPU’s IMC being sensitive to a module revision.
    • Update/verify microcode + BIOS again (you said updated; confirm exact BIOS/CPLD/iDRAC versions and post codes).
    • Check iDRAC/System event logs for memory training errors or SPD read errors — capture the exact error message or POST code.
    • Use one old + one new in same channel (A1 and A2) vs across channels to see if channel mixing matters.
    • Try lowering memory speed in BIOS (set to 2666 or manual timings) and test mixed population — if training succeeds at lower speed, it’s a timing/gear issue.
    • Run Memtest/Diagnostics with homogeneous sets (already pass) then with mixed sets if you can get it to POST with conservative settings.
  3. Settings to try

    • Force memory speed to a lower JEDEC rate (e.g., 2666) and set conservative timings.
    • Disable any XMP/overclock/gear settings and set voltages to nominal 1.2V (or the JEDEC voltage shown by SPD).
    • If BIOS has “memory training” options, enable/disable extended training or clear NVRAM/CMOS.
  4. If tests point to SPD/firmware mismatch or persistent incompatibility

    • Return/exchange the new modules for the exact same lot/revision as the originals (ask reseller to match the revision suffix).
    • Ask reseller/Dell for an RMA/exchange and supply the module FRU, part number, serial numbers and the server service tag; reference that mixing same P/N but different revision prevents boot — request testing on a R640 or validated compatibility confirmation.

4 Apprentice

 • 

1.1K Posts

February 11th, 2026 18:11

The only thing that comes to mind is to update the bios, idrac and CPLD.
https://dl.dell.com/FOLDER13682275M/2/BIOS_9M80P_WN64_2.25.0_01.EXE
https://dl.dell.com/FOLDER13740382M/1/iDRAC-with-Lifecycle-Controller_Firmware_VP556_WN64_7.00.00.183_A00.EXE
https://dl.dell.com/FOLDER05667810M/3/CPLD_Firmware_9N4DH_WN64_1.0.6_A00_02.EXE


Rey
#Iwork4Dell

(edited)

1 Rookie

 • 

2 Posts

 • 

2 Points

February 11th, 2026 19:18

@DELL-Rey G​ Thanks for your reply, unfortunately everything is already up to date to the latest firmware version, including BIOS, iDRAC and CPLD, first thing I did.

No Events found!

Top