This happens over and over and over. Only 2133MHz memory is supported; do not purchase faster memory. Quite simply, the KY NUC is not designed for nor is it warranted to work with faster memory. No testing of operation with faster memory is being or will be performed; it is simply not supported. This isn't an overclocking platform and using memory speeds faster than 2133MHz is considered overclocking.
If you have faster memory and it happens to work at full speed with a particular KY NUC, do not expect it to continue to work (at least not at speeds above 2133MHz). As the machine and the memory age, I guarantee that the memory will eventually begin to fail to work. If you know how (there are many who don't and many who thought they did - and failed), you can try using this faster memory dialed down to operate at 2133MHz (and with appropriate wait states, etc.). I personally recommend that you return this memory and get proper 2133MHz memory instead.
Bottom line (specifically answering your question), there is nothing wrong with your NUC. It is simply incompatible memory.
Sorry, but this is reality,
First of all, since you are using a custom configuration, I would boot and run something like MemTest86+ for a couple of hours (overnight, for example) and make sure that it is going to operate consistently at this configuration.
Secondly, F2 not working can, in some case, be an indication that the NUC is (still) having problems getting the memory to initialize. Having it eventually boot would then be an indication that it was finally able to do so - but it is possible that the configuration it actually ended up using is different from what you set. Displaying the memory configuration from within Windows will tell you (if you can find a tool that can do so; try something like RWEverything (it's a free tool)).
Ok, other possibilities. When you were in BIOS Setup (Visual BIOS) changing the memory configuration, you didn't accidently enable anything like the Fast Boot feature, did you? This would, for sure, prevent you from entering BIOS Setup using F2. I don't find that the feature is particularly useful anyway.
When hitting F2, depending upon how fast the monitor (or TV) initializes, you may be missing the window for doing so. The thing to try is starting to hit the F2 button immediately after pressing the power button and keep doing it, over and over (approximately once per second), until it either starts BIOS Setup or it starts Windows booting. If it starts booting Windows, it means that, even though you were there with a press during the time window, it was not accepted - and this is another indication that something else is going wrong (like the memory initialization issue I mentioned above).
The next thing to try is powering on the NUC but holding the power button down for 3 full seconds. If you hold it for too long (4 seconds), this will power the system back off (in this case, just try again). This should result in the power button recovery menu being displayed. If it does display, you can then press F2 to enter BIOS Setup (this, BTW, is the standard method for entering BIOS Setup when you have the Fast Boot feature enabled).
Let me know how it goes...
I agreed with N. Scott Pearson the Intel® NUC works with 2133MHz memory, some customer might be able to run it at 3000 but I don’t think the NUC will last too long and probable they can run it at that speed but most likely it will not be stable from the beginning, button line the unit will work with 2133MHz, please see NUC specs here:
You can see System Memory for Intel® NUC Kit NUC6i7KYK
There are two common causes that BIOS Setup will not open:
- Fast Boot has been enabled
- The HDMI resolution of the monitor is not supported.
Fast Boot enabled:
Fast Boot is a feature in BIOS that reduces the time it takes to boot your computer. If it's enabled, you cannot press F2 to enter BIOS Setup because USB mice and keyboards will not be available until after the operating system loads.
Disabling Fast Boot from the power button menu:
The power button can be used to recover if you encounter Fast Boot problems. The power button menu is accessible via the following sequence:
- Make sure the system is off, and not in Hibernate or Sleep mode.
- Press the power button and hold it down. The system emits three short beeps from the PC speaker. You can plug headphones into the front panel audio jack to hear the beeps.
- After the beeps, release the power button before the 4-second shutdown override. The power button menu displays.
- Press F3 to disable Fast Boot or press F2 to access the bios, once you’re in the BIOS press F9 to set the BIOS to defaults and then press F10 to save the changes, the system will restart.
I had the same Problem, with the same RAM, (except I have a 960 EVO 1TB) in my Skull Canyon.
I read another post from N. Scott Pearson saying pretty much the same thing he said here, so I bought some G.Skill Ripjaws 2133 that was on sale, end of problem.
I have NEVER had an issue with going a notch above RAM spec, don't know if the SPD on the RAM didn't have the proper info in it's JEDEC table, or if the Skull Canyon motherboard doesn't care, but any time I've put RAM that was "too fast" for the motherboard, the motherboard would just fall back to an acceptable JEDEC number listed in the RAMs SPD, so that you could alter timings in the BIOS.
1 of 1 people found this helpful
This is because most boards are designed to support at least a minimum level of overclocking. The KY board is specifically not designed to support any level of overclocking. Why? Well, IMHO, I believe that this is because of the issues that they went through providing a working cooling solution for a kick a$$ processor being crammed into such a small chassis. When you overclock - even just the memory buses - you are raising the average temperature of the processor and increasing the rate of temperature change that can occur within the processor's silicon. In this design, there simply isn't enough headroom in the cooling solution to absorb this. When placed under heavy load, this can result in temperature overshoots that allow the processor to reach temperature levels that could, over time, result in damage to (degradation within) the processor's silicon. At the same time, rapid changes in temperature can itself also, over time, result in damage to (degradation within) the processor's silicon. Bottom line, they designed for, tested for and warrant operation only at 2133MHz.
I agree that it would be a not-unreasonable workaround having the BIOS automatically default to the 2133MHz configuration in the SPD's table. The BIOS does NOT currently work this way because industry expectations (it isn't a requirement, per se) are that the highest (default?) entry in the table will be automatically used. This workaround is definitely something that Intel needs to think about including in their BIOS. Unfortunately, because of industry expectations, they would then have to display a warning to the user informing them that this was happening and they would have to track whether this warning has been presented to the user (and acknowledged) or not - and this will complicate the implementation (though not unduly and not anything that hasn't been done before).