I have an Intel NUC7i7DNB running ROCK. The unit was working normally, then suddenly stopped booting. There was no HDMI output, and the device was no longer visible on the network. To troubleshoot, I opened the unit and tried the following: What I observed: When the NVMe SSD is installed → the NUC does not show any video output, USB ports stop working, and I cannot enter BIOS. When I remove the NVMe SSD → BIOS opens normally, USB and HDMI work correctly. I tested two different NVMe SSDs (one new, one old) — both cause the same behavior. A 2.5" SATA SSD works and is detected normally. The NVMe drive warms up slightly when installed, meaning it receives power. Disabling the NVMe slot in BIOS allows the system to boot, but obviously the drive cannot be used. What this suggests: It appears the NVMe slot / PCIe lanes may be causing the system to freeze during initialization, preventing boot, video output, and USB activity. What I need help with: Could this be a known hardware issue with the NUC7i7DNB NVMe slot? Is there any firmware/BIOS fix that forces boot past PCIe initialization? Does ROCK rely on specific NVMe compatibility requirements for NUC7 models? Any guidance on how to proceed would be appreciated.
NVMe model: Samsung 970 EVO Plus 500GB
Describe your network setup
My network setup is as follows: ISP: Superonline Fiber Modem/Router: Huawei (ISP-provided fiber modem/router) Switch: Netgear GS105v5 (wired connection to audio system) Connections: NUC was connected directly to the router via Ethernet (no Wi-Fi on the NUC) No extenders, no mesh networks All audio gear is connected via wired LAN through the switch The issue occurs regardless of using the switch or connecting the NUC directly to the router.
There “should” be a “halt on error” setting that you can disable in the BIOS. It wont fix the m.2 socket issue if there is one.
To change the “halt on error” setting in an NUC’s BIOS, you need to enter the BIOS by pressing F2 during boot. Inside the BIOS, look for a setting called “Halt on” or “Halt on Error,” which is often in the “Miscellaneous Settings” or “Advanced” menus, and change it to “Disabled” or “None” to prevent the system from stopping on errors.
Have you tried resetting the BIOS to default settings and then install the NVME to see if that helps?
You might also check Intel (or Asus?) website for a BIOS update? Or a method to restore your current BIOS? (there are several videos on YT about recovering the bios on nucs)
Does the NUC show up in your router at all?
Beyond the above, if the socket itself is damaged not sure what can be done to fix that other than sending it to a repair service.
Thanks for the suggestions — here are the results of those tests:
I already reset the BIOS to factory defaults (F9 → Restore Defaults → Save & Exit) and then installed the NVMe again. When the M.2 slot is enabled, the NUC will not POST — no HDMI output, USB ports stop working, and I cannot enter BIOS.
When the M.2 slot is disabled in BIOS, the system boots normally (even with the NVMe physically installed), which strongly suggests a bus initialization issue and not a boot-order problem.
I also tested with multiple NVMe drives (one brand new Samsung 970 EVO Plus and the original Kingston), both cause the same behavior.
The device does not appear in the router when NVMe is installed, but does appear when using the 2.5" SATA SSD.
Regarding “halt on error”:
I’m able to access BIOS only when the M.2 slot is disabled. When enabled, the system does not reach a state where BIOS can be accessed or where keyboard/USB is initialized, so I cannot change POST error behavior with the NVMe installed. I’ll look again to locate this setting.
Next steps:
I will check for the latest available BIOS update from Intel and attempt a recovery-mode BIOS flash to see if PCIe lane initialization improves.
At this point, since the system works perfectly whenever the M.2 slot is disabled, it seems likely the issue is on the PCIe lanes or power management for the M.2 slot, not the SSD itself.
Thanks for your response.
Before I take the NUC to a repair service, I want to clarify whether there are any additional diagnostic steps that can further confirm that this is a hardware-level PCIe/M.2 failure rather than a firmware/BIOS configuration issue.
Summary of the behavior again:
The NUC boots normally, shows HDMI video output, USB/keyboard works, and BIOS is accessible only when the M.2 slot is disabled in BIOS.
When the M.2 slot is enabled and an NVMe drive is installed, the system does not POST, there is no HDMI output, no USB power, and I cannot enter BIOS.
I have tried two different NVMe SSDs (one brand new), and the behavior is identical.
SATA 2.5" drive works normally and ROCK installs correctly.
The NVMe drive warms slightly, so power is being supplied, but PCIe initialization appears to fail at boot.
If there are any recommended BIOS-level troubleshooting steps for NUC7 models specific to PCIe initialization, I would like to try those first.
Thanks again and I appreciate any further guidance before moving to hardware repair.
If the system POSTs at Gen2 but not Gen3, the root cause is degraded signal integrity—still a hardware fault, but a specific one (PHY lane damage / bad equalization).
If it still fails at Gen2 → strongly indicates total PCIe lane failure.
4. Boot with M.2 Slot Enabled but No Drive Installed
You said the problem occurs only when a drive is installed. A few more granular checks:
Test:
Enable M.2 slot.
Leave the socket physically empty.
Attempt POST.
Interpretation:
POST works → BIOS configuration accepts the device, but enumeration of an actual NVMe device is what kills POST. This would point to shorted sideband signals or broken REFCLK/WAKE lines.
POST fails even with no drive → the fault is on the board itself, even before device enumeration.
Thanks a lot for your help. Following your guidance, I was able to resolve the issue. With the new NVMe installed, the NUC now boots properly again and Roon is running without any problems.
Your detailed instructions regarding BIOS settings and the security jumper/CMOS reset were especially helpful.
Really appreciate your support—thank you!
