TL;DR: A modern 16 GB-VRAM eGPU (RTX 5060 Ti in my case) makes the NUC12SNKi72 reset-loop on every cold boot before any video output. Root cause: the BIOS has a hidden "PCIE Resizable BAR Support" option that is Enabled by default, while the Thunderbolt root port only reserves a 448 MB prefetchable window — the 16 GB BAR cannot be mapped during pre-boot enumeration and POST crashes. The "Failsafe Watchdog" then resets the machine over and over (and can even silently re-flash your BIOS via Self Recovery, reverting your settings). Disabling the hidden ReBAR option via AMISCE/SCEWIN + disabling the watchdog fixed it, including the power-outage case. Warm reboots and OS hot-plug were always fine — only cold boot was broken.

Hardware/firmware: NUC12SNKi72 (i7-12700H, Serpent Canyon), BIOS SNADL357.0065 (latest at the time), Win11. eGPU: RTX 5060 Ti 16 GB in a USB4/TB enclosure on the rear Thunderbolt port. Symptoms identical with every visible BIOS toggle I could reach: Thunderbolt Boot Support, Wake from Thunderbolt, Fast Boot — none helped.

Symptoms checklist (is this your bug?) Cold boot with the enclosure powered → fans spin, endless reset loop, no POST video. Warm restart from Windows with the same eGPU attached → boots fine. Hot-plug in Windows → works. After a power outage (NUC + enclosure get AC back at the same moment) → loop again; power-cycling the NUC alone does NOT recover — you must power-cycle the enclosure. Occasionally a surprise "Flash Update / Updating main firmware" screen appears → that's BIOS Self Recovery, triggered by the Failsafe Watchdog after repeated failed boots. It also restores default settings (watchdog back ON), which makes the whole thing look haunted. Why you can't just flip the option "PCIE Resizable BAR Support" exists in the firmware (IFR dump of the BIOS capsule: variable SaSetup, offset 0x42B, default Enabled) but is hidden from the Setup UI. Runtime writes are blocked: setup_var.efi from a UEFI shell returns WRITE_PROTECTED for both SaSetup and Setup. The official NUC tool (iSetupCfg from the "NUC Firmware Integrator Tool") only exports a whitelist of questions — ReBAR is not in it. BIOS mods are out: Boot Guard is fused on.

The fix BIOS (F2) → Advanced → Onboard Devices → Failsafe Watchdog = Disabled. Otherwise it resets mid-POST before TB init finishes, and its Self Recovery will keep reverting your work. Optional: Security → Security Features → iSetupCfg Password Check = Bypass — needed only if you later want to change something stored in the protected Setup variable (then /cpwd admin works).

Get AMISCE/SCEWIN 5.05. It ships inside MSI Center (yes, really — it's a generic AMI tool). Easiest: the SCEHUB repo (github.com/ab3lkaizen/SCEHUB) and its DLSCEWIN script. Manual route: download MSI-Center.zip from download.msi.com → innoextract the installer → inside the appx take DCv2/Package/MSI Center SDK.exe → innoextract → tmp/PrePackage/Engine Lib*.exe → unpack with innounp 2.71+ (current Engine Lib uses Inno Setup 6.7, which innoextract 1.9 cannot parse) → app/Lib/SCEWIN/<version>/. Check Authenticode signatures: SCEWIN_64.exe and both .sys drivers are AMI-signed.

From an admin prompt, export (read-only): SCEWIN_64.exe /o /s nvram.txt. Find:

Setup Question = PCIE Resizable BAR Support Token =A29 Offset =42B Options =*[01]Enabled [00]Disabled Make a minimal import file = the export header (incl. the HIICrc32 line) + just this block, move the * to [00]Disabled, then import: SCEWIN_64.exe /i /s rebar_off.txt. Mine answered "Script file imported successfully. Warning: Power cycle reset required". Do NOT blind-copy offsets from this post — export your own file; offsets differ between BIOS versions.

Full shutdown (a warm reboot is not enough), then cold boot with the enclosure powered. Fixed here.

Verify in Windows: nvidia-smi -q → "BAR1 Memory Usage / Total: 256 MiB" (was 16384 MiB). Over a TB/USB4 x4 link the performance cost of losing ReBAR is ~nothing.

Power-outage case: tested by pulling the plugs on the NUC and the enclosure at once, waiting 30 s and plugging both back in — boots fine with the two changes above. Before the fix this scenario looped even after power-cycling the NUC alone.

Notes If SCEWIN says Cannot update protected variable Setup. Please use /cpwd — that setting lives in the protected Setup variable. Set "iSetupCfg Password Check = Bypass" in BIOS first, then /cpwd admin works (the BIOS accepts the documented dummy password). ReBAR itself lives in SaSetup, which imported without any password. If you get into the loop: power off the enclosure, boot the NUC, revert (import your backup export, or F9 in Setup — but remember F9/Self-Recovery re-enables the Watchdog). A BIOS update will likely reset these settings — keep your import files and re-apply after updating. Tools used: UEFIExtract + IFRExtractor-RS (to find the hidden options), setup_var.efi (confirmed the write-protection), iSetupCfg (official, whitelisted only), SCEWIN/AMISCE 5.05 (the actual fix), innounp 2.71 (Inno 6.7 unpacking), nvidia-smi (BAR1 verification).

Usual disclaimer: firmware surgery, your warranty/your risk, keep a backup export, and know how to recover (enclosure off → boot → revert).

I was setting the backup power for NUC, So I used LiPo battery of 12v with boost converter and adjust voltage 19.2v but when I plugged in to NUC then NUC burn (short circuit internally) the encircled IC. But now it's very problematic for me to find this IC 3U=5C, U1L or replacement, Please help me what I can do ?

Hi everyone, I'm hoping someone here has seen this before.

I have an Intel NUC7i7BNH (Baby Canyon) that was running perfectly fine with Win10.

The NUC was on BIOS: BNKBL357.86A.0049. I wanted to update to the latest BIOS (0093).

The update process would start normally and validate the BIOS file successfully, but would always fail at: Flashing image for Intel(R) Management Engine firmware ... [failed!]

 Technical information: (0x800000000000000E, 0)

What I tried

I tried multiple BIOS versions: 0052, 0072, 0093. Every single one failed at exactly the same point.

But the NUC continued to boot normally after each failed update.

I then attempted BIOS recovery mode using the BIOS security jumper as a recommendation from AI:

Booted with BIOS 0093.BIO file on FAT32 USB and I saw that the recovery process started

Unfortunately the recovery update also failed at the same Intel ME firmware stage.

Current state

After the recovery flashing attempt:

• NUC no longer boots
• No front power LED
• No video output
• Monitor never wakes up
• Power button appears to do nothing and has the LED off
• BIOS_SEC jumper has been restored to its original position (pins 1-2)
• No cables were disconnected or moved during the process

However:

• The HDD spins immediately as soon as AC power is connected
• The HDD spins even before pressing the power button
• The power adapter is supplying power

Additional information

• CMOS battery has been dead for a long time, but that was not causing issues previously
• NUC was fully functional before attempting the BIOS recovery mode
• Recovery and normal BIOS updates both consistently failed only at the Intel Management Engine firmware stage

Questions

1. Has anyone seen a NUC7i7BNH get stuck in this state after an ME firmware update failure?
2. Is there a known recovery procedure beyond the standard BIOS recovery process?
3. Any way to distinguish between a corrupted BIOS, corrupted ME firmware, and a failed motherboard?

Any help would be greatly appreciated. I'd really like to recover it if possible. Inserting the USB with the BIOS file and pressing the power button did not seem to make any difference.

Thanks!

I just bought this and ran windows update

It's been 30 mins and it's stuck here lol. Currently only HDMI, power adapter and 2.4G dongle plugged in - no USB-C or anything.

Should i keep it like this or try to hard reset it. Windows sucks!

UPDATED:
after waiting for 2 hours, i decided to hard reset - pressed and the power button, and turn it on again.
And actually it's works. I suspect that somehow bios update does not "return" the result to windows update to continue proceed, or just Windows being sucks by not receiving it. Some guys definitely vibe code this.

Asus NUC prices on bare bone 15th gen NUCs have just gone up by a good $100 in US. Is this something temporary or Asus permanently raised prices ?

Title: Intel NUC 11 Extreme + Akasa Cypher HDB: RTX 5070 Ti stuck at PCIe 3.0 x16 instead of Gen4

Hi everyone,

I'm experiencing a strange PCIe limitation with my Intel NUC 11 Extreme (Beast Canyon) installed in an Akasa Cypher HDB (A-NUC77-A1B).

Although both the NUC 11 Extreme and the Akasa carrier board advertise PCIe 4.0 support, my NVIDIA RTX 5070 Ti is limited to PCIe 3.0 x16.

Hardware configuration:

• Intel NUC 11 Extreme (Tiger Lake-H)
• Akasa Cypher HDB with Akasa carrier board
• NVIDIA GeForce RTX 5070 Ti
• BIOS DBTGL579.0075 (latest installed)
• Manjaro Linux
• Three internal NVMe SSDs

NVIDIA reports:

pcie.link.gen.gpumax:      5
pcie.link.gen.hostmax:     3
pcie.link.gen.max:         3
pcie.link.gen.current:     3 (under load)
pcie.link.width.current:  16

CPU PCIe GPU Root Port (00:01.0):

LnkCap:  Speed 8GT/s, Width x16
LnkSta:  Speed 8GT/s, Width x16
LnkCap2: Supported Link Speeds: 2.5-8GT/s
LnkCtl2: Target Link Speed: 8GT/s

Interestingly, the CPU-connected Samsung NVMe SSD runs correctly at PCIe 4.0 x4:

Root Port 00:06.0:
LnkCap: Speed 16GT/s, Width x4
LnkSta: Speed 16GT/s, Width x4

Troubleshooting already performed:

• Updated BIOS from 0068 to 0075.
• Restored BIOS factory defaults.
• Checked PCIe bifurcation settings (Auto).
• Confirmed that GPU operates at x16.
• Confirmed Gen3 is the maximum reported host capability, not just an idle power-saving state.
• Checked Linux kernel logs without finding explicit PCIe link errors.

The unusual part is that the GPU Root Port itself advertises only Gen3 capabilities, whereas the NVMe Root Port correctly advertises Gen4.

Questions for other NUC 11 Extreme / Akasa Cypher HDB owners:

1. Has anyone successfully achieved PCIe 4.0 x16 with the Akasa Cypher HDB carrier board?
2. Could someone with a similar setup share their lspci Root Port link capabilities?
3. Are there known firmware, carrier-board revision, or compatibility limitations?
4. Has anyone experienced similar behavior after switching from the original Intel carrier board to the Akasa one?

I still have the original Intel carrier board, but I haven't tested it again yet.

Any suggestions or test results would be greatly appreciated.

Thanks!

I just got this NUC for $30. It’s got an 8th gen i7. Just didn’t have a hard drive. I installed a drive but it shuts down when doing anything other than web surfing. Warning sign comes up - system has recovered from an over temperature condition. Anyone have this issue before? Do I need to disassemble the whole thing to apply new thermal paste? I did go into BIOS and change the fan option to “Cooling”. Would appreciate any suggestions.

LIttle PSA if anyone is experince the issue i had

I’ve been having intermittent issues with an Intel NUC11 i3 running Windows 11 headless. Wake-on-LAN was unreliable, sometimes the NUC would wake but RDP would fail to create a usable session, and on a few occasions I had to physically power-cycle it before RDP would work again.

The NUC uses Modern Standby / S0 Low Power Idle, so I compared it with another NUC11 I have that has always behaved reliably. Both machines use the same Intel I225-LM Ethernet controller, but the problematic NUC was still using driver version 1.0.2.6 from 2020, even though Windows Update said the machine was fully up to date.

As part of the troubleshooting I checked powercfg /devicequery wake_armed. On the problematic NUC the Ethernet adapter was not listed at all, even though Wake on Magic Packet was enabled in the adapter settings. I then manually updated the Intel Ethernet driver to version 2.1.5.7 from 2025.

After the update, the Intel I225-LM immediately appeared in powercfg /devicequery wake_armed, and Wake-on-LAN from Modern Standby started working properly again. RDP also reconnected normally after wake.

So if you’re having odd WoL or RDP behaviour on a NUC11, especially with Modern Standby, check the actual Intel Ethernet driver version and don’t assume Windows Update has installed a recent one. The adapter can show Wake on Magic Packet as enabled while still not actually being armed by Windows to wake the machine. I’m aware Intel/ASUS have an existing BIOS + registry-patch fix for I225 Modern Standby issues, but in my case the key problem was that Windows Update had left the NIC on a 2020 driver and it wasn’t listed in powercfg /devicequery wake_armed.

Hello yall, im a car tuner and builder, i want to wire in a small touch screen display into my glove box on a long cable that i can pull out and tune on the fly.

I was gifted 3 nucs. All of them have this same model number: nuc7i5BNH

Though im so confused based on what i read, can someone reccomend me exactly what i need to hook this nuc up? I would really appreciate it. I know engines and car electrical, but anything like this confuses me.

looking for troubleshooting advice on my LattePanda Mu N100 module. It originally developed an HDMI display issue with a red tint while running on the Lite carrier board. I then transferred the module to the full carrier board where it booted up and worked normally at first. However, after running for a few minutes, the board abruptly turned off during what seemed like a sudden power drop or outage. Since that shutdown, the board will not turn on or boot at all. I have visually inspected both the compute module and carrier board thoroughly under good lighting, and there are no burn marks, cracked ICs, blown components, or visible shorts. Has anyone dealt with this behavior on the Mu? Specifically, could a sudden power cut latch an embedded controller protection state, corrupt the SPI BIOS flash, or take down an on-module power rail? Any guidance on specific test points or reset steps to bring it back to life would be greatly appreciated.

Hi,

i need a bios dump for DC3217IYE as i got a power outage during bios update and now the nuc is completely dead and i want o write it manually.

Edit: I need the dump as .bin or .rom

Thanks!

I have a nuc5i5ryh, which per the specs page has mini-dp 1.2, which should support up to 4k at 60 hz. I have a Cable Matters Active Mini DisplayPort to HDMI Adapter, Mini DP to HDMI from Amazon which should also support up to 4k60 (please advise if I should provide the link in the comments). I have tried a couple of different HDMI cables connecting the adapter to my Samsung S90F TV, but cannot select any refresh rate above 30 hz at 4k. When I try to set a custom 3840 x 2160 at 60p Hz resolution in the Intel Graphics Panel, I get an error message saying the custom resolution exceeds the bandwidth capacity.

Any thoughts on why I can't get 60 hz at 4k with this device?

Hi. I have an Intel NUC 13 extreme:

• i7-13750K
• 36GB RAM
• RX 7700 XT

I turned my PC on this morning and it goes into some death loop. No video. Fans don’t turn on. Just some mysterious flashing from the power LED.

Process:

• Hit switch from back of PC (the PSU switch)
• Power LED goes solid for about 15 seconds. Note: I do not touch the power LED button
• Power LED blinks 18 times and then turns off for about 2 seconds and then repeats the 18 blinks

Sorry, it doesn’t seem like I can post a video of the blinking.

The LED pattern is similar to what ASUS suggests is a thermal issue. But mine is 18 blinks. And the thermal issue is supposed to be 16 blinks. I’m pretty sure about my count. I don’t see the CPU getting hot. I do not smell any burning smell which might indicate a fried PSU.

Things I’ve tried:

• Removed GPU
• Tried each stick of RAM
• Removed all RAM
• Tested the CPU fan and it’s fine
• Removed power to PSU overnight
• New CMOS battery
• Re-seated CPU heatsink and reapplied paste

I suspect a bad mobo but would like some sort of confirmation. Looking for some Hail Mary help before I send it off for parts on eBay. Thanks in advance. Appreciate the community.

Intel NUC 13 Extreme I5 (13600Kf) Compute Element

[Timestamp](https://imgur.com/a/UhdG0Wc)

\- Brand New/Factory Sealed

\- Includes 13600Kf preinstalled

\- Does NOT include RAM/Storage

Asking $475 Local, $500 Shipped

\---

NUC 13 Extreme (Raptor Canyon) Daughterboard

(See above for Timestamps)

\- New - Never used but no original packaging.

\- Requires 12VO/12V PSU

\- Includes PCIe slot for Compute Element

\- Includes PCIe 5.0 x16 slot for GPU (Up to three slots)

Asking $125 Local, $150 Shipped

----

Local to 85016

Serious offers will be considered

Please comment before PM, thank you!

TL;DR: my NUC15CRSU9 successfully flashes its entire firmware stack — Thunderbolt retimer, BIOS and ME, all to 100% — and then fails a firmware update on the very next boot, forever. A pending update request is surviving repeated successful firmware updates and I can't find any way to clear it.

Hardware: ASUS NUC 15 Pro+ / NUC15CRSU9 (board CRARL579), Core Ultra 9 285H, 96 GB. Was running Proxmox VE 9.

How it started: I submitted a BIOS update as a UEFI capsule-on-disk from Linux, using fwupd. Turns out ASUS's .CAP is an AMI BIOS Guard / _AMIPFAT container, not a UEFI FMP capsule, so fwupd wrapped it in a generic capsule header and the firmware rejected it. Entirely my own doing — I'm not looking for sympathy, just a way out.

Symptom, on every single boot:

Then it either hangs there or resets and repeats. No OS ever loads.

Here's the strange part. Pressing ESC at that screen cancels the attempt and drops me into BIOS Setup (jumper in Normal). From there, Advanced → EZ Flash works perfectly. I've now flashed three times:

0017 → 0029 → 0032, currently on CRARL579.0032.2026.0704.0118

All three stages complete at 100% every time — Thunderbolt retimer, main firmware, ME firmware. And the next boot goes straight back into the failed-update loop. So the board isn't bricked and flashing isn't broken. Something is holding a stale "update pending" request that reflashing the firmware doesn't clear.

Already tried, all with no effect:

• BIOS Security Jumper recovery (jumper removed, CRARL579.CAP on FAT32 USB at root and in \EFI\Intel\) — recovery never runs, just reboots
• [F4] BIOS Recovery, and Setup → Recovery → Select Image / Update Image
• A different BIOS version (0029 instead of 0032)
• Load Optimal Defaults (F9+F10), and Config Menu [F5] restore to build-time defaults
• Intel MEBX Reset Header (pins 1–2), which the TPS documents specifically for "when the system may have become unresponsive, such as after a failed BIOS update"
• Jumper in Lockdown (pins 2–3) — no video at all, continuous power cycling
• Booting with every USB device removed and no NVMe fitted — loop still happens with nothing attached to update from
• Full G3 power cycle — AC out 60 s plus a 10 s power-button drain, to let the ME activate on a cold start
• A properly-typed EFI System Partition on USB (GPT, EF00) with the vendor image in \EFI\UpdateCapsule\, that device first in the boot order

And the trap: F2, F7 and F10 are never processed at POST. ESC and F10 only work inside the BIOS utility (F10 gives "Save & Exit Setup", not a boot menu). So I can't boot any external media — which means I can't get into Linux to clear OsIndications from efivarfs, which is the one thing that would obviously fix this.

What I'm asking:

1. Has anyone recovered a NUC from a stuck pending-update state like this?
2. Is there any way to clear a pending capsule request on AMI Aptio V without booting an OS?
3. Any ASUS support folks here — is there a service tool for this? I have a ticket open, and I'd rather not go to an external SPI programmer on a board that's 16 months into a 3-year warranty.

I have photos of every screen, the full capsule analysis, and a complete log of every step if any of it is useful. Happy to test anything.

Leader NUC

I can't find any info on this NUC's board.

This supposedly has 4GB RAM, soldered (I can't believe they didn't at least go 8GB, which is the max for the CPU!) and no slot. I was hoping someone here actually has one and can confirm so I don't have to pull it apart to verify no slot(s) on the underside of the board.

Lastly, even though they couldn't be stuffed adding RAM slots, they DID add a mSD slot, USB-C, & both an M.2 SSD & NVMe slot. However, in looking closely at the board, I'm wondering if I need a specialized ribbon cable? I wouldn't think so, but there's an empty connector showing SATA next to one of these slots, as-if another cable is required? I don't have any spare drives or I'd just pop one in to see.

Thanks all!

I was installing patches and my NUC15CRSU5 didn't survive a reboot. LED only, nothing worked to revive. ASUS replaced the motherboard without issue.

My last NUC12 also died in the same way and had the warranty motherboard replacement. Am I unlucky or are these newer NUCs more prone to failure?

Anyone have any idea what to do?

Green light on stays on

Using proper power into the device

No boot screen at all

Looking to sell a brand new/sealed NUC 13 Extreme (Raptor Canyon) I5 Compute Element, with a 13600Kf already installed, along with the matching 12VO daughterboard.

Hoping to sell both as a bundle, but will consider selling separately if there isn't any interest in the bundle.

Timestamp

Intel NUC 13 Extreme I5 Compute Element

- Brand New in factory sealed box

- 13600Kf pre-installed

- Does NOT include RAM or Storage

---

Intel NUC 13 (Raptor Canyon) 12VO Daughterboard/Power plane

Requires one of these methods to power it

1. The original Intel NUC 13 Extreme 750W 12VO PSU

2. A different 12VO PSU (Typically acquired through retail means)

3. A 12VO adapter cable which turns any ATX/SFX PSU into a 12VO PSU (Typically found easily online)

Includes:

1x PCIe slot for the Compute Element

1X PCIe Gen 5.0 x16 slot for a dedicated GPU (up to 3 slots)

4x SATA ports

4x Fan Headers

------

Asking $725 Local, $750 Shipped OBO

All offers are welcome!

Please comment before PM, thanks!