Tweet
The RAM SPD information collection is performed on BurnInTest startup and is highly dependent on the system hardware, in particular, the CPU and baseboard chipset.
The most likely reason for the RAM SPD information missing from the System Information is due to an unsupported CPU/baseboard chipset. If this is the case, we may be able to add support for your particular chipset if we are provided with the debug logs generated when running BurnInTest in debug mode.
If your system contains an Intel Xeon chipset which supports Temperature Sensor on DIMM (TSOD), there is the possibility that TSOD polling is interfering with the SPD data collection process. The result is missing or incorrect RAM information appearing in the System Information page. BurnInTest attempts to temporarily disable TSOD polling while collecting the SPD data but in may not possible in some cases. As a workaround, TSOD polling can be disabled in the BIOS by disabling the "Closed Loop Thermal Throttling" option.
For server platforms with a large number of RAM slots (ie. > 16 slots), it is likely that a special mechanism is required to access the large number of SPD modules. BurnInTest supports a small number of these systems (Supermicro/ASUS), but for most cases, the mechanism to access the SPD modules is unknown and would require access to the platform's internal specifications.
Finally, certain chipset vendors (eg. Lenovo) implement an unspecified mechanism for hiding the SPD modules on platform initialization. Unfortunately, there is no workaround in this case as this mechanism is internal to the vendor and not disclosed to the public.
The most likely reason for the RAM SPD information missing from the System Information is due to an unsupported CPU/baseboard chipset. If this is the case, we may be able to add support for your particular chipset if we are provided with the debug logs generated when running BurnInTest in debug mode.
If your system contains an Intel Xeon chipset which supports Temperature Sensor on DIMM (TSOD), there is the possibility that TSOD polling is interfering with the SPD data collection process. The result is missing or incorrect RAM information appearing in the System Information page. BurnInTest attempts to temporarily disable TSOD polling while collecting the SPD data but in may not possible in some cases. As a workaround, TSOD polling can be disabled in the BIOS by disabling the "Closed Loop Thermal Throttling" option.
For server platforms with a large number of RAM slots (ie. > 16 slots), it is likely that a special mechanism is required to access the large number of SPD modules. BurnInTest supports a small number of these systems (Supermicro/ASUS), but for most cases, the mechanism to access the SPD modules is unknown and would require access to the platform's internal specifications.
Finally, certain chipset vendors (eg. Lenovo) implement an unspecified mechanism for hiding the SPD modules on platform initialization. Unfortunately, there is no workaround in this case as this mechanism is internal to the vendor and not disclosed to the public.