Xeon w5-3425X usable memory size issue

[Ramon2]

We encountered a issue regarding the usable memory size.

When using a Xeon x5-2465X CPU with eight 64GB memory modules, the total available memory was 512GB usabled. However, with a Xeon x5-3425X CPU and the same memory configuration, while the total available memory was 512GB, bug only 64GB could be used.

Please find the attached zip was SMBIOS log. The above log is for your reference. How can we improve this problem?

[MACM]

Hi Ramon2,

Greetings of the day.

Hope you are doing great.

Could you please share us the below details.

1) Complete model name of the Processor.

2) Is this a Boxed or a Tray processor.

We will go ahead and proceed further accordingly.

Best Regards,

Mohammed Ali CM

Intel Customer Support Technician

[MACM]

Hi Ramon2

Thank you for contacting Intel.

This is the follow-up regarding the issue you reported to us

.

We wanted to inquire whether you had the opportunity to share us the requested details.

Feel free to reply to this email, and we'll be more than happy to assist you further.

Regards,

Mohammed Ali CM

Intel Customer Support Technician

[Ramon2]

Hi Mohammed Ali CM

Based on the experimental results with the CPU 3425, the correct usable memory size can be released in the OS after the Enforce Population POR setting is set to Disabled, and the Type 19 addressing is confirmed to be correct.

We are currently conducting related memory stability tests.
We would like to ask if there are any associated risks or known issues with this modification (Enforce Population POR [Disabled]), or if there is a more suitable alternative solution for reference.

Best Regards,

Ramon Huang

[Fikri_Intel]

Hi Ramon2,

Thank you for your response.

To assist you further, kindly let us know if you purchase the CPU separately or comes together with the system. If it comes with the system, please let us know the model and brand.

Additionally, have you checked the motherboard compatibility for the CPU?

Looking forward to your response.

Regards,

Fikri_Intel

[Ramon2]

Hi Fikri

According to our test information, the following four CPUs were found to have the same problem:

Any CPU in the 3400 series will trigger this issue:
Q2NV Intel® Xeon® w7-3465X
Q19R Intel® Xeon® w9-3495X
Q19U Intel® Xeon® w7-3455
Q19X Intel® Xeon® w5-3425

MICROCODE: m_87_806f8_2b000643.pdb
ME: 16.11.20.1870v2

The motherboard was designed and developed by our company. We didn't encounter this issue with the 2-series CPUs in the early stages; however, this problem has only emerged recently when customers upgraded to the 3-series CPUs.

We would like to leverage your experience to help determine whether our proposed solutions have any problems or have caused additional issues.

Thanks a lot!!

Best Regards,

Ramon Huang

[Azhari_Intel]

Hello Ramon2,

Thank you for reaching out.

Regarding the "Enforce Population POR" solution, we recommend checking with your motherboard design team as it was mentioned to be developed and designed from your side.

Nonetheless, we recommend raising an IPS case for further support from URL below.

https://premiersupport.intel.com

Generally, disabling "Enforce Population POR / Enforce POR" settings in BIOS, may cause system instability in the long run.

Please note that this would need to be confirmed by the motherboard design team for a sure answer.

Please let us know if you have any issue raising an IPS case, else we shall proceed to close this forum case from our end if there are no further concerns.

Best Regards,

Azhari_Intel

[Azhari_Intel]

Hello Ramon2,

Good day to you!

It has been a while since we last heard from you.

As we had recommended raising an IPS case for further support, we shall proceed to close this forum case.

https://premiersupport.intel.com

Please proceed to accordingly, and if you need any additional information, please submit a new question as this thread will no longer be monitored.

Best Regards,

Azhari_Intel

[Ramon2]

Hi Azhari

Thanks for your concern.

I submitted an IPS service request for further support on 11/24. I have not yet received a response. I agree that closing this forum post is appropriate. Thank you for your response and support.

Best Regards,

Ramon