I own a NUC8i7BEH and recently replaced its memory to a couple of Hyperx HX424S14IBK2 SODIMMs, which are suposed to be CL14, but the BIOS sets them to CL17 and I'm not able to change this setting (neither the rest of settings regarding with RAM). I tried by entering into configuration mode by removing the yellow jumper on the motherboard, but the memory setting are locked and can't be changed.
I ran some tests and all of them read CL17, as it's fixed into the BIOS.
Link Copied
Hello RErre
Thank you for posting in the Intel Community.
Can you access the BIOS (F2 during post) go to advance> performance> memory> general settings and on this tab change the memory profile to manual- User-defined and the option for memory multiplayer select the CL to one the available options.
Hope this help.
Regards,
Leonardo C.
Intel Customer Support Technician
Under Contract to Intel Corporation
Hi Leonardo:
Thank you very much for your help.
I reached to the point where I have to change my profile to manual, but I can't see how to do it.
Regards
Hello RErre
Thank you for the details, let me investigate this on my end, I will be posting back as soon as possible.
Regards,
Leonardo C.
Intel Customer Support Technician
Under Contract to Intel Corporation
Hello RErre
Thank you for waiting.
The reason why the memory multiplier si gray out is because the Intel® Bean Canyon doesn't support Intel XMP, to be able to configure the memory settings as you are looking for, your system has to support Intel XMP and the Memory has to be XMP as well. For this case only the memory is XMP and Intel® Bean Canyon is not.
Regards,
Leonardo C.
Intel Customer Support Technician
Under Contract to Intel Corporation
Thank you Leo. I see what's the point.
It's also thoroughly explained here: https://www.reddit.com/r/intelnuc/comments/bemu0o/samsung_64_gib_ddr4_2666mhz_kit_installed_to_bean/... where they compare the Hades Canyon's and the Bean Canyon's BIOS' capabilities regarding to XMP.
I wish Bean Canyon's BIOS was so configurable as Hades Canyon's, but I know they're in a different class.
Regards
For more complete information about compiler optimizations, see our Optimization Notice.