Intel NUC9 Extreme and 64GB Memory?

[DukeNUCem]

Just got my NUC9i9QNX and a 64GB memory kit from G.Skill Ripjaws F4-3200C22D-64GRS since the ones recommended on intels compatibility tool from Kingston is not availible where I am.

To bad,
it will not boot with the G.Skill memory.

I've tested with the memory from my Hades Canyon, HyperX 32GB (2x16) 2666MHz and it boots fine.

In the compitabilitylist there are intel validated G.Skill Memory og lower density so I thought it would be a match here, but unfortunately not. These have to be returned.

So, what other kits with 64GB memory is confirmed compatible with the NUC9i9QNX?
The 32GB CT32G4SFD8266 is listed as 3rd Party Validated and is a single stick. I assume that CT2K32G4SFD8266, which ist just a kit of 2 CT32G4SFD8266 will be compatible, but it is not listed.

Anyone else have 64GB memory in NUC 9 Extreme that can confirm compatibility with CT2K32G4SFD8266 or other brands of 64GB?

"NUC 9 Extreme, NUC9i9QNX, RAM, MEMORY, 64GB"

[DukeNUCem]

So, I am responding to myself here

Noticed I couldn't find any Kingston HyperX memory when I was looking for intel validated HX432S20IBK2/64 (Kingston 64GB 3200MHz). So, I assume I have been living under a rock the last years since I was not aware that Kingston had sold the HyperX brand to HP in 2021 and therefore had to rebrand theire HyperX memory to Fury. I noticed the intelvalidated HX432S20IBK2/64 has the same number as Kingston Fury memory KF432S20IBK2/64, only difference is the first two letters HX(HyperX) and KF (Kingston Fury).

I assume these are the exact same and I have ordered a kit op 64GB KF432S20IBK2/64.

Hopefully these will be pnp.

[Steven_Intel]

Hello DukeNUCem,

Thank you for posting on the Intel® communities.

I am sorry you are having issues finding a compatible RAM module for your NUC. I will be glad to help you with that.

Just to clarify, the memory modules in the Intel Product Compatibility lists are proven to work with the NUC, however there are many that are not in the list and have not been tested yet, but they still may work with the NUC.

If the memory module(s) complies with the NUC specifications (DDR4 2666 MHz 1.2V SO-DIMM, DDR4 2666 MHz 1.35V SO-DIMM) it should work just fine, although we cannot assure that. 

The Crucial 64GB Kit (2 x 32GB) DDR4-2666 SODIMM (CT2K32G4SFD8266) in question, seems to comply with the specifications for the Intel® NUC 9 Extreme Kit - NUC9i9QNX. 

Please be aware that if the memory modules are not letting the NUC to boot, we can always troubleshoot in order to find out the cause of the issue.

Best regards,

Steven G.

Intel Customer Support Technician.

[Steven_Intel]

Were you able to check the previous post?

Let us know if you still need assistance.

Best regards,

Steven G.

Intel Customer Support Technician.

[DukeNUCem · Accepted solution]

Hello Steven G, thanks for replying. I just got my new memorykit today, 64GB Kingston 3200MHz (KF432S20IBK2/64).

At first I had the same issue as with the G.Skill Ripjaws (F4-3200C22D-64GRS), just a blank screen. I have never had any issues with Kingston so I was fed up with the situation and instead of starting troubleshooting I pulled the CMOS battery and power cable to the board for 5 min. After that it booted fine and automatically set up XMP profile 1. I now have 64GB memory running perfectly at 3200MHz confirmed.

I think this situation occured because I was exited to try my new NUC and ran the nuc 9 kit for the first ever startup with 1 x Kingston 2666MHz 16GB stick from my Hades Canyon. Somehow this prevents it from recognizing the new density and faster sticks. Therefore it might well be that the G.Skill Ripjaws (F4-3200C22D-64GRS) also would have booted fine if I had taken the CMOS battery that time too. To bad I cannot test it now as I have returned them.

Anyways, all good here, running 64GB Fury Impact (KF432S20IBK2/64) with XMP 1 @ 3200MHz confirming also that the intel validated HX432S20IBK2/64 is the same as KF432S20IBK2/64 after Kingstons sale of HyperX brand and rebranding the kit Fury Impact.

[Steven_Intel]

We are glad to know the issue is now solved. 

Thank you for taking the time to share this fix, and hopefully, it may help other community members experiencing similar behavior. Since the thread is now solved, we will proceed to close it. 

Please keep in mind that this thread will no longer be monitored by Intel. Thank you for your understanding.  

Best regards,

Steven G.

Intel Customer Support Technician.