I had a new Hades Canyon purchased from Amazon Dec 2019. All was running well when 33 days later on power up it complained that a "bootable device has not been detected". Panic! Pressing power on/off had the same result.
Removed the power supply and plugged back in and now no power lights at all.
After some argument with Amazon after advice from Intel to register for support and it would take at least two weeks to send for a fix I convinced Amazon to send me a replacement Hades Canyon.
After receiving the second Hades Canyon A few hours later after swapping memory and storage to the new Hades the same thing happened!
I ordered new storage as the error message was the same and points to faulty storage drive
However, I noticed that plugging power adaptor in the two leds at the front would blink white for a fraction of a second. Something smelled fishy and I thought this was unlikely to be a storage issue if I couldn't even boot to the bios
I thought of visiting this forum and bingo! Removed the CMOS plug into the motherboard and waited 15 minutes and after plugging back in all is well again. Question is HOW TO ENSURE PERMANENT FIX. this is definitely a bios related issue. Seems caused by some windows start/up or shut down
So in brief
1) On boot error stating no boot disk
2) after unplugging power cable only brief 2 led blink and then nothing
3) Nothing to do with the storage
4) temporary fix remove the CMOS batter (you need to look for teh notch in the plastic clip and pull up and wait for 15 minutes
5) re-connect and power up
Waiting to see if anyone has permanent fix?
bios is 0059 (so latest)
windows 10 pro 1909
Samsung 1TB 970 EVO Plus
u may not have seen it on your NUCs but there are others on this forum with the exact same behaviour/experience
In my opinion nothing to do with the RAM since both the original NUC and the replacement work as expected for more than a month and its working fine currently with the RAM installed. I guess its possible.
Here's the link to the RAM
Your RAM is compatible with NUC8i7HVK. I'm glad that the NUC is working now. Since you wrote that you can't boot into Bios, I've suspected that failure in RAM may be the cause. The Bios program is loaded into ram from flash memory. The storage drive is used only when Windows is loading. Let's hope that it will stay this way. If again you NUC will fail to start POST, I suggest that you should run some memory tests. Other thing what you may try if failure reoccurs, is to remove and reinstall the SO DIMMs (instead of disconnecting CMOS battery). Any way, the brief LED flash after reconnecting Power Adapter is normal.
We have a storm here in the UK today which led to a brief power cut. The PC was switched on at the time of the power cut. the EXACT same thing has happened again. This is definitely something to do with shutdown process. Annoyingly I have lost the key to open the NUC. Why the heck haven't they used standard Philips screws??? I'm REALLY starting to hate this PC!!!
Yes. New power supply.
The first time this happened on the first NUC I left it un-powered for a long time and tried removing memory and storage one by one without any joy.
I took a deep dive into the garage and found an Allen key that fits so I'm back to removing the CMOS cable
If I do get it up and running again I'll run some memory tests. Any advice on software to test the memory?
The only time I have seen something like this is with a Dell Alienware Steam Machine. That was more complicated to reset the CMOS but the symptoms were the same. There I narrowed down the root cause to a USB peripheral. Once I stopped using the peripheral it never happened again.
I have HDMI, DP and all four USB ports in use at the back as well as ethernet cable. On the front I have 1 usb device (unifying usb receiver)
I'd agree this NUC in theory is great. there's nothing else on the market quite like it. But exactly as stated in this thread having the thing reliably switch on is mu number 1 requirement (by the way the guy was also encouraged to open up his own thread. is there a risk Intel are not connecting common issue by forcing district threads)
You may perform some testing using Windows Memory Memory Diagnostic Tool: Click on Windows +R key. In the Run Windows, enter command mdsched and press OK. Click on "Restart now..." and let the computer reboot and finish this test (it will take about 1 hour).
thank you. One other piece of anecdotal. This has only happened since I swapped to a new monitor which is now connected via DP
Monitor in question is AMD FreeSync compatible 1440p. Its a fantastic monitor by the way https://smile.amazon.co.uk/gp/product/B07X8HBHJP/ref=ppx_yo_dt_b_asin_title_o05_s01?ie=UTF8&psc=1
After reset of CMOS its back up and running. I have shot down from windows and powered back on and aok. I've restarted from windows and aok. So the only difference from when it fails is the PC was left powered off overnight and then we had a power cut.
Thank you for the tip. I also checked Event Viewer and spotted a bunch of Kernel-Power Critical Error (Event ID 41) including one from 10am this morning which Is when I think my son probably tried to switch the NUC on?
Anyway, I followed some settings from here:-
Sort of true. When the NUC first fails it will display the "no bootable device found" error. At that point you can boot to the BIOS by restarting with the power button and hitting F2. The bios will show no EFI boot device. If I then remove the power adaptor and replug the power adaptor the NUC at that point will not post (brief flash from LEDs behaviour). Only unplugging the CMOS battery cable and leaving for 15 mins gets me back to a booting NUC.
So, I did this test. I tested what is the effect of depleted/failed CMOS battery on NUC8i7HVK. In this forum I saw few reports for older NUC models, that with depleted battery, NUC couldn't boot. For this test, I've disconnected the Power Adapter and the CMOS battery connector for 15 minutes. Then I connected the Power Adaptor only, leaving CMOS battery disconnected. After depressing on Power Switch, the NUC8i7HVK booted into Windows, showing some warnings about Bios checksum (which is normal after disconnecting battery). In the end I may conclude that the CMOS battery is not your problem.
by the way. Son is currently playing on the PC so hard for me to run the memory test. I'm Alsop away with work from this evening so if I go quiet for a few days its only that I'm travelling
is there any chance users are experiencing the same symptoms but they are all separate issues? Seems to me some common issue with the NUC but the responses from (I think Intel) do seem to consistently point the people reporting this their storage or memory as failing. I read and re-read these threads and there doesn't seem to be any 'fix'. closest I've seen is someone swapped out their Evo Pro for non pro (I have 1TB Evo Pro)
I am soooo cheesed off with this I can't describe it. the stress of replacing and fixing £1000 worth of PC is unbelievable. Luckily Amazon so far have accommodated.
I have an update. I have tried software restarting and powering down multiple times without any issue. However, if I remove the power adaptor from the NUC and then plug the power adaptor back in then bang, quick flash of the two leds (I think) and the NUC is now in its bricked state needs battery cable pull.
This is the NUC with the increased power consumption I believe? Seems this is definitely connected to a power supply issue. I have swapped out the memory because...well leave no stone unturned, but I don't think for a second its memory related.
The NUC does NOT like the power adaptor being removed and re-plugged. I wonder if in connection/combination with other IO being plugged in. I could experiment but its a total pain having to open the thing up and repeat the CMOS reset multiple times.
Further update. NUC failed again today when trying to wake from sleep. Usual 'no bootable device found'. Resolved with usual battery cable pull. This is brand new memory so that's ruled out. I may try swapping for different type of storage as I see another user with the same issue also thinking this may be issue with compatibility with Evo Pro storage. My son is convinced this only started when we swapped to new monitor and plugged in via display port. He's pretty upset. His Christmas present has become a total nightmare.
I'm so indescribably fed up with this thing. If I could easily give up on this thing I would