Incorrect memory display in memory populated information.

[Mace]

Hi,

I met a Memory display incorrect problem that using Burn-in V7.1 build 1012 to test Grantley Sever Platform.
In Burn-in tool description sheet, the total memory size is correct but wrong display in memory devices.

Here is I captured the log file that test in my platform.
Please check how to fix this issue.
Thanks.

-----------------------------------------------------------------
BurnInTest V7.1 Pro 1012 (64-bit)


System summary:
Windows Server 2008 R2 Server Enterprise Edition (full installation) Service Pack 1 build 7601 (64-bit),
2 x Genuine Intel(R) CPU @ 2.10GHz [2908.4 MHz],
95.8GB RAM,

Memory
Total Physical Memory: 98138MB
Available Physical Memory: 93549MB
Memory devices:
:
- 4096MB,
:
- 4096MB,
2:
- Not populated
3:
- Not populated
:
- 4096MB,
:
- 4096MB,
6:
- Not populated
7:
- Not populated
:
- 4096MB,
:
- 4096MB,
10:
- Not populated
11:
- Not populated
:
- 4096MB,
:
- 4096MB,
14:
- Not populated
15:
- Not populated
:
- 4096MB,
:
- 4096MB,
18:
- Not populated
19:
- Not populated
:
- 4096MB,
:
- 4096MB,
22:
- Not populated
23:
- Not populated

[David (PassMark)]

What is the motherboard model?
What is the CPU model?

RAM detection is highly dependent on the motherboard & CPU in your system, and while it can handle the most common ones, once in a while we encounter a really new, really old or some what rare motherboard that isn't supported.

For the RAM detection, can you see if RAMMon detects the modules?
http://www.passmark.com/products/rammon.htm

There is a DEBUGMODE command line argument that will produce a couple of logs files.
Running RAMMon in debug mode will generate a couple of logfiles that can help troubleshoot the issue. The two logfiles that are created are RAMMon.txt and SysInfoLog.txt. They will be located in program folder RAMMon was installed to.

The help file that comes with RAMMon has more details of running in DEBUGMODE.

Can you E-mail us these files.

[Mace]

David,

My platform is supported DDR4 type and Intel_Haswell-EP series,LGA 2011-3 socket.

QPI 9.6G / TDP145W.

The RAMMon doesn't support while I running tool as below pic.

[David (PassMark)]

Can you run it in debug mode and E-mail us the RAMMon.txt and SysInfoLog.txt files.
This will help us a lot.

[Mace]

Sent the two files to info [at] passmark this email.

[estelzer]

I'm seeing similar issues with the memory status in BIT 7.1 Pro build 1017 on new DIMMs from our DIMM vendor that appear to have byte 1 in the SPD set to 'Revision 1.2' now instead of 'Revision 1.1'.

The only other changes in the SPDs between the modules that I can tell is the raw card version and the date, serial number, and part number info.

System is an Ivy Bridge / Panther Point with two SO-DIMMs.

I've got the files from RAMMon in DEBUGMODE with both the new (slot 1) and the old (slot 3) modules installed. I'll email them.

Thank you!

Eric Stelzer.

[David (PassMark)]

We'll E-mail you with details of a new build to try out.

[estelzer]

David -

The latest build you sent us fixes the issue with SPD V1.2 SO-DIMMs.

Thank you!

Eric Stelzer.