Announcement

Collapse
No announcement yet.

Memtest Not showing Manufacturer’s Identification Code (89 49) in RDIMM

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Memtest Not showing Manufacturer’s Identification Code (89 49) in RDIMM

    Jedec Manufacturer’s Identification Code of OM nanotech Pvt.LTD hex byte is 89 49, all udimm & sodimm are showing om nanotech Pvt. Ltd during testing in Memtest. But when we put in 16GB DDR4 2GX8 8chips RDIMM same code it does not show company name (showing Unknown) .Spd byte we put byte no 320 321 & 350 , 351.Other Hex code like sk hynix (80 AD) it is showing SK Hyinix.Please guide us

  • #2
    Maybe the SPD data is wrong in the RDIMM?
    Or maybe the system you are using with the RDIMMs doesn't allow the reading of any SPD data?

    Comment


    • #3
      Same spd if we only change sk hynix or micron jedec code it is showing company name in memtest.So spd data have no problem.System also allow because other company name is showing.
      When we put our company name it doesn't showing (unknown) in RDIMM But same code working fine in UDIMM & SODIMM modules.

      Comment


      • #4
        Can we get the logs. There's a chance that we couldn't read the SPD and the info is from smbios (and not from SPD, so the issue is with BIOS).

        See,
        https://www.memtest86.com/tech_debug-logs.html

        Comment


        • #5
          Screen photo
          Attached Files

          Comment


          • #6
            Same spd only micron hex code it shows, attached
            Attached Files

            Comment


            • #7
              Log file (as requested) would be more useful than a photograph of a photograph of a screen.

              But I can see you are using V10.7 and not the latest release. Can you try V11 and collect the log if it isn't correct.

              Comment


              • #8
                Log file memtest 11
                Attached Files

                Comment


                • #9
                  Log file memtest 10.7
                  Attached Files

                  Comment


                  • #10
                    Log doesn't show any SPD data being collected.

                    When SPD data can not be found, SMBios data is used instead.
                    SMBios is less accurate (due to buggy BIOS), but using it is better than showing nothing.

                    This is the SMBios data in the log. This is the data from the log from the SMBios structures.
                    2024-09-24 12:55:25 - [Slot 5] DeviceLocator: DIMM 3, BankLocator: P0 CHANNEL C, Manufacturer: Unknown, S/N: 00000000, AssetTag: , PartNumber: V1D4R816GB2G82G83200

                    As you can see the Manufacturer is Unknown.

                    SMBios data is filled out by the BIOS running on the motherboard at boot time. MemTest86 only displays what is reported by BIOS for SMBios (we don't have the hex values).

                    So this would appear to be a BIOS bug.

                    We'll also have a deeper look at the log to see if something can be done to make the SPD data collection possible. (But there are some Dell and Lenovo machines where access is blocked).


                    Comment


                    • #11
                      Lenovo laptops are known to have access to the SPD module blocked. So this is the likely cause of being unable to obtain the manufacturer info from the SPD and thus falling back to the manufacturer information populated in the SMBIOS.

                      You can check if the SPD is truly inaccessible by confirming with other tools such as CPU-Z, HWiNFO, etc.

                      Comment


                      • #12
                        However when same module with manufacturer hex code as Micron & sk hynix is tested then Micron name is displayed.spd file if your required will send to you.

                        Comment


                        • #13
                          Yes, which means the Lenovo BIOS only does the decode correctly for some memory sticks. So if you need this fixed, you need to talk to Lenovo. Either Lenovo need to allow access to the SMBus (to read SPD data) or Lenovo need to fix their buggy BIOS to decode your RAM stick data and then populate the SMBios data correctly.

                          Comment


                          • #14
                            The width of memory chips x4 ECC DDR4 rdimm & x8 ECC DDR4 rdimm , which one is better in stability & performance wise.
                            Why Maximum DDR4 server Ram are made from x4 bit chips ?
                            From which chips (x4 or x8 ) we can make maximum capacity memory modules.
                            Testing memtest in x4 bis ram or x8 bits ram have any difference. How customer can know modules are
                            made from which type of memory width (DQ lines of each memory chip)during memtest.
                            Please guide me​

                            Comment


                            • #15
                              The terms "x4" and "x8" in memory modules refer to the data width of the memory chips used on the module. Here's a breakdown of the differences and their implications: x4 vs. x8 Memory
                              1. Data Width:
                                • x4 Memory: Each memory chip on the module has a data width of 4 bits.
                                • x8 Memory: Each memory chip on the module has a data width of 8 bits.
                              2. Chip Count:
                                • x4 Memory: Typically requires more chips to achieve the same capacity as x8 memory. For example, a 4GB module might use 16 x 4 chips.
                                • x8 Memory: Uses fewer chips for the same capacity. A 4GB module might use 8 x 8 chips. In both cases 64bits in total are required. But for x8 fewer chips are needed on the stick (for the same overall capacity).
                              3. Error Correction:
                                • x4 Memory: Often used in server environments where error correction is critical. x4 modules are more common in ECC (Error-Correcting Code) memory configurations. Having just 4 bits per chips can make it easier to deal with the failure of an entire chip via the ECC redundancy. But this also depends on the ECC scheme in use.
                                • x8 Memory: More common in consumer-grade memory where ECC is not a requirement.
                              4. Reliability and Fault Tolerance:
                                • x4 Memory: Offers better fault tolerance in ECC configurations. If a single chip fails, the system can still function correctly.
                                • x8 Memory: Less fault-tolerant in ECC configurations compared to x4.
                              Performance Differences
                              • Performance Impact: There is generally no direct performance difference between x4 and x8 memory in terms of speed or latency. The performance is more influenced by other factors such as memory speed (measured in MHz), CAS latency, and the overall architecture of the system. The data width isn't usually the important factor.
                              • Use Case Considerations: The choice between x4 and x8 is more about availability of chips, cost, reliability and the specific requirements of the system rather than performance. For example, servers and workstations that require high reliability and error correction might prefer x4 memory, while consumer desktops and laptops might use x8 memory for cost-effectiveness.
                              Memtest86 can test either type of RAM.

                              Comment

                              Working...
                              X