Not really a NUC specific question, we have had this working perfectly on NUCs under Linux, and we're getting there on the NUC7i5/NUC7i7 units under windows, too.

.

We're embedding NUC motherboards in units for film- sets, and the units don't even have a power on/off button... Actually there are no buttons at all.
Basically they turns on when power is present, and closes when power is off, and in-between they act like the small robots they are...
In linux we made this a dead robust solution. Had them on set for 18 months and they always worked.

There is no way to attach a screen to the unit (HDMI/display port is not exposed), they are remotely serviced and basically you interface with the units through web-apps.
we also really want to avoid the user hooking up a screen, a keyboard and a mouse and start playing solitaire on them. To the user, this is just a smart IoT device.

We're still early in the Windows testing, compared to our linux experiences, but any tips and tricks are advised. But BSOD at startup is a bugger if/when it happens, though it seems pulling the plug and re-plugging it solves most BSOD we have lately. (We have done a bit of config)

But what are your advices for this kind of setup. I am pretty certain we're not the only ones using windows like this.

We have to use Pro 64, not IoT

Gunleik

Hi

we're on win10 enterprise IoT.

The NUC is essentially a "BlackBox" to the end user.
It would be sweet to share a folder from the unit as a network-drive.

For the particular use we have in mind, a direct connection (computer-to-computer) would be preferable.
I can do that on my mac's (:) ), but haven't made that happen with the NUC yet...

Do I need a twisted-pair cable, or does it just "not work".

If it works, a pointer would be great.

Gunleik

Hi. I`m having issues with a recently buyed NUC6CAYH. The screen will randomly turn completely black for a second or two. (it happend once every 4 or 5 minutes or once every 4 to 5 seconds)

It has windows 10 Pro installed with latest bios (040) and drivers installed.

It is connected via VGA cable to a LCD display (resolution: 1440x900@60Hz).

The things i`ve tried so far:

• lowering the display resolution to other than the native display stops the flickering or at least makes it less frequent.
• I had keyboard, mouse and two printers connected to a back USB port through a 2.0 USB hub. removing the USB hub eliminate de flickering (or at least it has not flicker once in about an hour) [Hub works flawlessly in other PCs]
• Connecting mouse keyboard and two USB hdds makes the flickering happen at least once every 30 minutes.

Thanks in advance and excuse my english.

For 2 months I've tried to deploy a NUC7I3BNH without success as a result of random system freezes. I'm running Ubuntu 17.04 (GNU/Linux 4.10.0-28-generic x86_64)  - server edition in a headless configuration.

The first task I tried to run on this system is loading data via Bluetooth from my PV inverter. On the system's first day, I encountered Bluetooth problems, i.e. corrupted messages and a frozen Bluetooth stack that forced me to restart the BT service over and over again.

I tried the following:

• upgraded the BIOS to the (at the time) latest version: 0047

• upgraded the iwlwifi firmware to version 22.361476.0

• configured Monit to automatically check and if necessary restart the Bluetooth service
• log the CPU temperature in a database as the temperature increases significantly during a freeze:
  

All of the above did not result in any improvements as the system usually freezes (no longer responds to terminal commands or ping requests) after a few days but sometimes only after minutes. Today I noticed for the first time an anomaly in the dmesg output (see below): +0.001852] iwlwifi 0000:3a:00.0: Microcode SW error detected.  Restarting 0x2000000. (occurs multiple times).

I now have the following questions:

1. is this most likely a hardware or a software problem (i.e. iwlwifi driver)?
2. what else can I do to find the root cause?

Any help will be much appreciated.

Output from dmesg:

pi@eon:[~]: dmesg|grep iwlwifi

[  +0.000048] iwlwifi 0000:3a:00.0: enabling device (0000 -> 0002)

[  +0.004545] iwlwifi 0000:3a:00.0: Direct firmware load for iwlwifi-8265-26.ucode failed with error -2

[  +0.000019] iwlwifi 0000:3a:00.0: Direct firmware load for iwlwifi-8265-25.ucode failed with error -2

[  +0.000102] iwlwifi 0000:3a:00.0: Direct firmware load for iwlwifi-8265-24.ucode failed with error -2

[  +0.000013] iwlwifi 0000:3a:00.0: Direct firmware load for iwlwifi-8265-23.ucode failed with error -2

[  +0.003230] iwlwifi 0000:3a:00.0: loaded firmware version 22.361476.0 op_mode iwlmvm

[  +0.008316] iwlwifi 0000:3a:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230

[  +0.002038] iwlwifi 0000:3a:00.0: L1 Disabled - LTR Enabled

[  +0.000618] iwlwifi 0000:3a:00.0: L1 Disabled - LTR Enabled

[  +0.001193] iwlwifi 0000:3a:00.0 wlp58s0: renamed from wlan0

[  +0.001127] iwlwifi 0000:3a:00.0: L1 Disabled - LTR Enabled

[  +0.000254] iwlwifi 0000:3a:00.0: L1 Disabled - LTR Enabled

[  +0.115551] iwlwifi 0000:3a:00.0: L1 Disabled - LTR Enabled

[  +0.001171] iwlwifi 0000:3a:00.0: L1 Disabled - LTR Enabled

[  +0.006814] iwlwifi 0000:3a:00.0: L1 Disabled - LTR Enabled

[  +0.000630] iwlwifi 0000:3a:00.0: L1 Disabled - LTR Enabled

[  +0.115211] iwlwifi 0000:3a:00.0: L1 Disabled - LTR Enabled

[  +0.000261] iwlwifi 0000:3a:00.0: L1 Disabled - LTR Enabled

[Jul21 01:38] iwlwifi 0000:3a:00.0: Microcode SW error detected.  Restarting 0x82000000.

[  +0.000105] iwlwifi 0000:3a:00.0: CSR values:

[  +0.000050] iwlwifi 0000:3a:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)

[  +0.000090] iwlwifi 0000:3a:00.0:        CSR_HW_IF_CONFIG_REG: 0X00c89000

[  +0.000087] iwlwifi 0000:3a:00.0:          CSR_INT_COALESCING: 0X00000040

[  +0.000106] iwlwifi 0000:3a:00.0:                     CSR_INT: 0X00000000

[  +0.000085] iwlwifi 0000:3a:00.0:                CSR_INT_MASK: 0X00000000

[  +0.000074] iwlwifi 0000:3a:00.0:           CSR_FH_INT_STATUS: 0X00000000

[  +0.000075] iwlwifi 0000:3a:00.0:                 CSR_GPIO_IN: 0X00000010

[  +0.000074] iwlwifi 0000:3a:00.0:                   CSR_RESET: 0X00000000

[  +0.000074] iwlwifi 0000:3a:00.0:                CSR_GP_CNTRL: 0X08040005

[  +0.000075] iwlwifi 0000:3a:00.0:                  CSR_HW_REV: 0X00000230

[  +0.000074] iwlwifi 0000:3a:00.0:              CSR_EEPROM_REG: 0Xd55555d5

[  +0.000074] iwlwifi 0000:3a:00.0:               CSR_EEPROM_GP: 0Xd55555d5

[  +0.000075] iwlwifi 0000:3a:00.0:              CSR_OTP_GP_REG: 0Xd55555d5

[  +0.000074] iwlwifi 0000:3a:00.0:                 CSR_GIO_REG: 0X001f0044

[  +0.000076] iwlwifi 0000:3a:00.0:            CSR_GP_UCODE_REG: 0X00000000

[  +0.000109] iwlwifi 0000:3a:00.0:           CSR_GP_DRIVER_REG: 0X00000000

[  +0.000126] iwlwifi 0000:3a:00.0:           CSR_UCODE_DRV_GP1: 0X00000000

[  +0.000074] iwlwifi 0000:3a:00.0:           CSR_UCODE_DRV_GP2: 0X00000000

[  +0.000074] iwlwifi 0000:3a:00.0:                 CSR_LED_REG: 0X00000060

[  +0.000075] iwlwifi 0000:3a:00.0:        CSR_DRAM_INT_TBL_REG: 0X8826b7cc

[  +0.000074] iwlwifi 0000:3a:00.0:        CSR_GIO_CHICKEN_BITS: 0X07800200

[  +0.000074] iwlwifi 0000:3a:00.0:             CSR_ANA_PLL_CFG: 0Xd55555d5

[  +0.000074] iwlwifi 0000:3a:00.0:      CSR_MONITOR_STATUS_REG: 0Xc03803c0

[  +0.000074] iwlwifi 0000:3a:00.0:           CSR_HW_REV_WA_REG: 0X0001001a

[  +0.000074] iwlwifi 0000:3a:00.0:        CSR_DBG_HPET_MEM_REG: 0Xffff0010

[  +0.000072] iwlwifi 0000:3a:00.0: FH register values:

[  +0.000071] iwlwifi 0000:3a:00.0:         FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X27004b00

[  +0.000092] iwlwifi 0000:3a:00.0:        FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X027358c0

[  +0.000092] iwlwifi 0000:3a:00.0:                  FH_RSCSR_CHNL0_WPTR: 0X00000008

[  +0.000092] iwlwifi 0000:3a:00.0:         FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80801054

[  +0.000092] iwlwifi 0000:3a:00.0:          FH_MEM_RSSR_SHARED_CTRL_REG: 0X000000fc

[  +0.000094] iwlwifi 0000:3a:00.0:            FH_MEM_RSSR_RX_STATUS_REG: 0X07830000

[  +0.000092] iwlwifi 0000:3a:00.0:    FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000

[  +0.000092] iwlwifi 0000:3a:00.0:                FH_TSSR_TX_STATUS_REG: 0X07ff0000

[  +0.000092] iwlwifi 0000:3a:00.0:                 FH_TSSR_TX_ERROR_REG: 0X00000000

[  +0.000198] iwlwifi 0000:3a:00.0: Start IWL Error Log Dump:

[  +0.000062] iwlwifi 0000:3a:00.0: Status: 0x00000000, count: 6

[  +0.000063] iwlwifi 0000:3a:00.0: Loaded firmware version: 22.361476.0

[  +0.000071] iwlwifi 0000:3a:00.0: 0x000028AA | ADVANCED_SYSASSERT

[  +0.000074] iwlwifi 0000:3a:00.0: 0x000002F0 | trm_hw_status0

[  +0.000062] iwlwifi 0000:3a:00.0: 0x00000000 | trm_hw_status1

[  +0.000061] iwlwifi 0000:3a:00.0: 0x0000E258 | branchlink2

[  +0.000061] iwlwifi 0000:3a:00.0: 0x0002730C | interruptlink1

[  +0.001435] iwlwifi 0000:3a:00.0: 0x00000000 | interruptlink2

[  +0.000686] iwlwifi 0000:3a:00.0: 0x00000003 | data1

[  +0.000706] iwlwifi 0000:3a:00.0: 0x00000000 | data2

[  +0.000671] iwlwifi 0000:3a:00.0: 0x000332AD | data3

[  +0.000651] iwlwifi 0000:3a:00.0: 0x7EC123A1 | beacon time

[  +0.000657] iwlwifi 0000:3a:00.0: 0xAF17DC46 | tsf low

[  +0.000626] iwlwifi 0000:3a:00.0: 0x00000113 | tsf hi

[  +0.000621] iwlwifi 0000:3a:00.0: 0x00000000 | time gp1

[  +0.000616] iwlwifi 0000:3a:00.0: 0x4EE65329 | time gp2

[  +0.000614] iwlwifi 0000:3a:00.0: 0x00000000 | uCode revision type

[  +0.000625] iwlwifi 0000:3a:00.0: 0x00000016 | uCode version major

[  +0.000499] iwlwifi 0000:3a:00.0: 0x00058404 | uCode version minor

[  +0.000431] iwlwifi 0000:3a:00.0: 0x00000230 | hw version

[  +0.000375] iwlwifi 0000:3a:00.0: 0x00C89000 | board version

[  +0.000377] iwlwifi 0000:3a:00.0: 0x0000001C | hcmd

[  +0.000376] iwlwifi 0000:3a:00.0: 0x00022000 | isr0

[  +0.000374] iwlwifi 0000:3a:00.0: 0x00000000 | isr1

[  +0.000374] iwlwifi 0000:3a:00.0: 0x08001802 | isr2

[  +0.000371] iwlwifi 0000:3a:00.0: 0x004154C0 | isr3

[  +0.000366] iwlwifi 0000:3a:00.0: 0x00000000 | isr4

[  +0.000375] iwlwifi 0000:3a:00.0: 0x00000110 | last cmd Id

[  +0.000372] iwlwifi 0000:3a:00.0: 0x00000000 | wait_event

[  +0.000392] iwlwifi 0000:3a:00.0: 0x0000E22F | l2p_control

[  +0.000610] iwlwifi 0000:3a:00.0: 0x00000000 | l2p_duration

[  +0.000610] iwlwifi 0000:3a:00.0: 0x00000003 | l2p_mhvalid

[  +0.000498] iwlwifi 0000:3a:00.0: 0x00000020 | l2p_addr_match

[  +0.000363] iwlwifi 0000:3a:00.0: 0x0000000D | lmpm_pmg_sel

[  +0.000362] iwlwifi 0000:3a:00.0: 0x03071928 | timestamp

[  +0.000364] iwlwifi 0000:3a:00.0: 0x00000818 | flow_handler

[  +0.000408] iwlwifi 0000:3a:00.0: Start IWL Error Log Dump:

[  +0.000356] iwlwifi 0000:3a:00.0: Status: 0x00000000, count: 7

[  +0.000366] iwlwifi 0000:3a:00.0: 0x00000070 | ADVANCED_SYSASSERT

[  +0.000569] iwlwifi 0000:3a:00.0: 0x00000000 | umac branchlink1

[  +0.000501] iwlwifi 0000:3a:00.0: 0xC0082F64 | umac branchlink2

[  +0.000343] iwlwifi 0000:3a:00.0: 0xC0081000 | umac interruptlink1

[  +0.000335] iwlwifi 0000:3a:00.0: 0xC0081000 | umac interruptlink2

[  +0.000333] iwlwifi 0000:3a:00.0: 0x00000800 | umac data1

[  +0.000322] iwlwifi 0000:3a:00.0: 0xC0081000 | umac data2

[  +0.000314] iwlwifi 0000:3a:00.0: 0xDEADBEEF | umac data3

[  +0.000318] iwlwifi 0000:3a:00.0: 0x00000016 | umac major

[  +0.000304] iwlwifi 0000:3a:00.0: 0x00058404 | umac minor

[  +0.000301] iwlwifi 0000:3a:00.0: 0xC0886280 | frame pointer

[  +0.000313] iwlwifi 0000:3a:00.0: 0xC0886280 | stack pointer

[  +0.000474] iwlwifi 0000:3a:00.0: 0x0033010D | last host cmd

[  +0.000474] iwlwifi 0000:3a:00.0: 0x00000000 | isr status reg

[  +0.492710] iwlwifi 0000:3a:00.0: L1 Disabled - LTR Enabled

[  +0.000255] iwlwifi 0000:3a:00.0: L1 Disabled - LTR Enabled

[  +0.116244] iwlwifi 0000:3a:00.0: L1 Disabled - LTR Enabled

[  +0.000264] iwlwifi 0000:3a:00.0: L1 Disabled - LTR Enabled

[ +19.276917] iwlwifi 0000:3a:00.0: regular scan timed out

[  +0.001852] iwlwifi 0000:3a:00.0: Microcode SW error detected.  Restarting 0x2000000.

[  +0.001073] iwlwifi 0000:3a:00.0: CSR values:

[  +0.001127] iwlwifi 0000:3a:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)

[  +0.002015] iwlwifi 0000:3a:00.0:        CSR_HW_IF_CONFIG_REG: 0X00c89000

[  +0.001192] iwlwifi 0000:3a:00.0:          CSR_INT_COALESCING: 0X00000040

[  +0.000350] iwlwifi 0000:3a:00.0:                     CSR_INT: 0X00000000

[  +0.000366] iwlwifi 0000:3a:00.0:                CSR_INT_MASK: 0X00000000

[  +0.000497] iwlwifi 0000:3a:00.0:           CSR_FH_INT_STATUS: 0X00000000

[  +0.000355] iwlwifi 0000:3a:00.0:                 CSR_GPIO_IN: 0X00000010

[  +0.000352] iwlwifi 0000:3a:00.0:                   CSR_RESET: 0X00000000

[  +0.000352] iwlwifi 0000:3a:00.0:                CSR_GP_CNTRL: 0X08040005

[  +0.000353] iwlwifi 0000:3a:00.0:                  CSR_HW_REV: 0X00000230

[  +0.000350] iwlwifi 0000:3a:00.0:              CSR_EEPROM_REG: 0Xd55555d5

[  +0.000359] iwlwifi 0000:3a:00.0:               CSR_EEPROM_GP: 0Xd55555d5

[  +0.000353] iwlwifi 0000:3a:00.0:              CSR_OTP_GP_REG: 0Xd55555d5

[  +0.000346] iwlwifi 0000:3a:00.0:                 CSR_GIO_REG: 0X001f0044

[  +0.000354] iwlwifi 0000:3a:00.0:            CSR_GP_UCODE_REG: 0X00000000

[  +0.000362] iwlwifi 0000:3a:00.0:           CSR_GP_DRIVER_REG: 0X00000000

[  +0.000578] iwlwifi 0000:3a:00.0:           CSR_UCODE_DRV_GP1: 0X00000000

[  +0.000576] iwlwifi 0000:3a:00.0:           CSR_UCODE_DRV_GP2: 0X00000000

[  +0.000505] iwlwifi 0000:3a:00.0:                 CSR_LED_REG: 0X00000060

[  +0.000358] iwlwifi 0000:3a:00.0:        CSR_DRAM_INT_TBL_REG: 0X8826b7cc

[  +0.000355] iwlwifi 0000:3a:00.0:        CSR_GIO_CHICKEN_BITS: 0X07800200

[  +0.000362] iwlwifi 0000:3a:00.0:             CSR_ANA_PLL_CFG: 0Xd55555d5

[  +0.000362] iwlwifi 0000:3a:00.0:      CSR_MONITOR_STATUS_REG: 0Xc03803c0

[  +0.000363] iwlwifi 0000:3a:00.0:           CSR_HW_REV_WA_REG: 0X0001001a

[  +0.000373] iwlwifi 0000:3a:00.0:        CSR_DBG_HPET_MEM_REG: 0Xffff0010

[  +0.000610] iwlwifi 0000:3a:00.0: FH register values:

[  +0.000528] iwlwifi 0000:3a:00.0:         FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X27004b00

[  +0.000394] iwlwifi 0000:3a:00.0:        FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X027358c0

[  +0.000397] iwlwifi 0000:3a:00.0:                  FH_RSCSR_CHNL0_WPTR: 0X00000060

[  +0.000400] iwlwifi 0000:3a:00.0:         FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X00801054

[  +0.000403] iwlwifi 0000:3a:00.0:          FH_MEM_RSSR_SHARED_CTRL_REG: 0X000000fc

[  +0.000404] iwlwifi 0000:3a:00.0:            FH_MEM_RSSR_RX_STATUS_REG: 0X03030000

[  +0.000406] iwlwifi 0000:3a:00.0:    FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000

[  +0.000414] iwlwifi 0000:3a:00.0:                FH_TSSR_TX_STATUS_REG: 0X07ff0000

[  +0.000426] iwlwifi 0000:3a:00.0:                 FH_TSSR_TX_ERROR_REG: 0X00000000

[  +0.000791] iwlwifi 0000:3a:00.0: Start IWL Error Log Dump:

[  +0.000571] iwlwifi 0000:3a:00.0: Status: 0x00000000, count: 6

[  +0.000417] iwlwifi 0000:3a:00.0: Loaded firmware version: 22.361476.0

[  +0.000422] iwlwifi 0000:3a:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN

[  +0.000430] iwlwifi 0000:3a:00.0: 0x000002F0 | trm_hw_status0

[  +0.000429] iwlwifi 0000:3a:00.0: 0x00000000 | trm_hw_status1

[  +0.000425] iwlwifi 0000:3a:00.0: 0x0000E258 | branchlink2

[  +0.000445] iwlwifi 0000:3a:00.0: 0x00CCA90E | interruptlink1

[  +0.000712] iwlwifi 0000:3a:00.0: 0x0002730C | interruptlink2

[  +0.000518] iwlwifi 0000:3a:00.0: 0x00000000 | data1

[  +0.000418] iwlwifi 0000:3a:00.0: 0x00000080 | data2

[  +0.000408] iwlwifi 0000:3a:00.0: 0x07830000 | data3

[  +0.000401] iwlwifi 0000:3a:00.0: 0x1EC067F8 | beacon time

[  +0.000395] iwlwifi 0000:3a:00.0: 0xB047B7EA | tsf low

[  +0.000380] iwlwifi 0000:3a:00.0: 0x00000113 | tsf hi

[  +0.000382] iwlwifi 0000:3a:00.0: 0x00000000 | time gp1

[  +0.000385] iwlwifi 0000:3a:00.0: 0x01257EAF | time gp2

[  +0.000620] iwlwifi 0000:3a:00.0: 0x00000000 | uCode revision type

[  +0.000557] iwlwifi 0000:3a:00.0: 0x00000016 | uCode version major

[  +0.000380] iwlwifi 0000:3a:00.0: 0x00058404 | uCode version minor

[  +0.000378] iwlwifi 0000:3a:00.0: 0x00000230 | hw version

[  +0.000380] iwlwifi 0000:3a:00.0: 0x00C89000 | board version

[  +0.000378] iwlwifi 0000:3a:00.0: 0x0052019C | hcmd

[  +0.000374] iwlwifi 0000:3a:00.0: 0x00022000 | isr0

[  +0.000374] iwlwifi 0000:3a:00.0: 0x00800000 | isr1

[  +0.000394] iwlwifi 0000:3a:00.0: 0x08001802 | isr2

[  +0.000608] iwlwifi 0000:3a:00.0: 0x40400082 | isr3

[  +0.000557] iwlwifi 0000:3a:00.0: 0x00000000 | isr4

[  +0.000373] iwlwifi 0000:3a:00.0: 0x00800110 | last cmd Id

[  +0.000372] iwlwifi 0000:3a:00.0: 0x00000000 | wait_event

[  +0.000375] iwlwifi 0000:3a:00.0: 0x0000537E | l2p_control

[  +0.000372] iwlwifi 0000:3a:00.0: 0x00000020 | l2p_duration

[  +0.000374] iwlwifi 0000:3a:00.0: 0x00000000 | l2p_mhvalid

[  +0.000372] iwlwifi 0000:3a:00.0: 0x00000030 | l2p_addr_match

[  +0.000368] iwlwifi 0000:3a:00.0: 0x0000000D | lmpm_pmg_sel

[  +0.000372] iwlwifi 0000:3a:00.0: 0x03071928 | timestamp

[  +0.000586] iwlwifi 0000:3a:00.0: 0x00346070 | flow_handler

[  +0.000640] iwlwifi 0000:3a:00.0: Start IWL Error Log Dump:

[  +0.000357] iwlwifi 0000:3a:00.0: Status: 0x00000000, count: 7

[  +0.000352] iwlwifi 0000:3a:00.0: 0x00000070 | ADVANCED_SYSASSERT

[  +0.000352] iwlwifi 0000:3a:00.0: 0x00000000 | umac branchlink1

[  +0.000349] iwlwifi 0000:3a:00.0: 0xC0082F64 | umac branchlink2

[  +0.000341] iwlwifi 0000:3a:00.0: 0xC008940A | umac interruptlink1

[  +0.000335] iwlwifi 0000:3a:00.0: 0xC0081000 | umac interruptlink2

[  +0.000329] iwlwifi 0000:3a:00.0: 0x00000800 | umac data1

[  +0.000343] iwlwifi 0000:3a:00.0: 0xC0081000 | umac data2

[  +0.000516] iwlwifi 0000:3a:00.0: 0xDEADBEEF | umac data3

[  +0.000515] iwlwifi 0000:3a:00.0: 0x00000016 | umac major

[  +0.000420] iwlwifi 0000:3a:00.0: 0x00058404 | umac minor

[  +0.000302] iwlwifi 0000:3a:00.0: 0xC0886280 | frame pointer

[  +0.000309] iwlwifi 0000:3a:00.0: 0xC0886280 | stack pointer

[  +0.000299] iwlwifi 0000:3a:00.0: 0x0052019C | last host cmd

[  +0.000297] iwlwifi 0000:3a:00.0: 0x00000000 | isr status reg

[  +0.493849] iwlwifi 0000:3a:00.0: L1 Disabled - LTR Enabled

[  +0.000255] iwlwifi 0000:3a:00.0: L1 Disabled - LTR Enabled

[  +0.116124] iwlwifi 0000:3a:00.0: L1 Disabled - LTR Enabled

[  +0.000264] iwlwifi 0000:3a:00.0: L1 Disabled - LTR Enabled

pi@eon:[~]:

nuc7i7BNH

Intel® NUC

I have tried installing the Windows 10 Fall Creators Update (16299.15 and 16299.19) on a NUC5i7RYH both by using Microsoft's Windows 10 Installation Media Tool to create a USB stick and also by using the Windows 10 Update Assistant.

Both times after installing the Fall Creators Update, I have no internet connection.  Although Wi-Fi is switched on, it doesn't detect any Wi-Fi networks and just says 'No WiFi networks found' in Windows Action Centre.

The adapter settings in Control Panel > Network > Change Adapter Settings, shows a red cross next to Wi-Fi.

The Windows Network Diagnostics trouble-shooter is unable to fix the problem and just says "Problem with wireless adapter or access point - Not fixed".

In Device Manager > Properties > General Tab, it says "This device is working properly".

Wi-Fi details in Settings > Status > View Your Network Properties, show no MAC address and status as 'Not Operational':
Name: WiFi
Description: Intel(R) Dual Band Wireless-AC 7265
Physical address (MAC): 00:00:00:00:00:00
Status: Not operational
Maximum transmission unit: 1500
IPv4 address: 169.254.208.191/16
IPv6 address: fe80::<SNIPPED>/64
DNS servers: 192.168.1.1, 192.168.1.1
Connectivity (IPv4/IPv6): Disconnected

IPConfig from PowerShell shows 'Media disconnected':
Ethernet adapter Ethernet:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Wireless LAN adapter WiFi:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Wireless LAN adapter Local Area Connection* 10:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

The NUC5i7RYH has a Intel Dual Band Wireless-AC 7265 Wi-Fi card.  On Windows 10 15063.674 it was running driver version 19.51.5.3 (Windows Update version), but this doesn't work on Windows 10 16299.19.  I tried installing 'WiFi_20.0.2_PROSet64_Win10.exe' from the Intel Drivers section of the website (19.51.7.2), but that makes no difference and Wi-Fi still doesn't work on 16299.19.  At the moment I've had to restore 16299.19 back to 15063.674 so that I have internet access again.

I also went through all the steps HERE, but am unable to determine what's wrong.

As a side note, the Intel driver version and date HERE needs updating, as it still shows 19.70.0, 9/3/2017 as the latest driver, instead of 20.0.2, 10/17/2017.

I've got a Dell P2415Q connected to an NUC7i5BNH via DisplayPort.

The speakers is then connected to the 3.5mm jack on the back of the monitor.

Everything is fine if I set the resolution to 4k@30hz or anything lower than this.

But the first bits of any audio is almost always dropped when the display resolution is set to the maximum 4k@60hz.

This is not much a problem if I'm watching a film or something but it's really irritating when half of a notification sound is chopped off.

If I connect the 3.5mm jack to the Realtek sound card on the front of the NUC there is no audio drop instead I get the electrical noise problem described by other people.

Hi all,

We are aware of this issue and a bug was opened a couple weeks ago.  The developers/engineers are working on finding a solution and I will post any updates and/or solutions here.

Thank you for your patience.

Hi,

each time the NUC (NUC7i5BNH) reboots, this entry (source: TPM, ID: 15) is found in the event log (OS Windows 10 Pro 64 bit):

EN

The device driver for the Trusted Platform Module (TPM) has encountered an unrecoverable error in the TPM hardware that prevents the use of TPM services (such as data encryption). Please contact the computer manufacturer for more help.

DE:

Beim Gerätetreiber für das Trusted Platform Module (TPM) ist ein nicht behebbarer Fehler in der TPM-Hardware aufgetreten, der die Verwendung der TPM-Dienste (z. B. Datenverschlüsselung) verhindert. Wenden Sie sich an den Computerhersteller, um weitere Hilfe zu erhalten.

Is this a real hardware error in the NUC ?

Regards

Holger

This CIR is detected as "ITE8708 CIR transceiver" in Ubuntu and it's working fine with LIRC for receiving remote codes. Since I also need to send IR codes and I cannot configure it for that (irsend outputs fine, no error logs in syslog but code is not sent), does anyone know is this CIR capable of transmitting IR codes and if it is, what settings should be in hardware.conf?

Thanks!

Dear all,

When the NUC 5i5RYH is in S3 sleeping state, what electrical power is still available per back panel USB 3.0 port? Is there a particular setting in the BIOS to configure the back panel USB 3.0 ports 'power level' in S3 (I haven't found yet)? This would be a great extra feature for a future BIOS update ;-)

I'd like to use a gigabit network LAN switch [Renkforce gigabit network lan switch (RJ45) 1423415 4 Port, usb-powered], which is consuming less than 500 mA in total maximum (5 V). Its USB electrical power cable should be plugged into a USB 3.0 hub that is connected to one of the NUC's back panel USB 3.0 ports.

Two devices are already plugged into the USB hub: (1.) An archgon (Panasonic Matshita UJ-272) blu-ray player/recorder, which is used very rarely. In standby it consumes very little power. (2.) The USB extender cable with the small Blootooth sender/receiver for the Logitech Illuminated LR Keyboard K830. It has also very low energy consumption.

If the NUC isn't used, it turns into the S3 sleeping state. From a router (Fritz!Box 7490) a Wake on LAN magic packet can be send easily to activate the NUC quickly. If the router sends this WOL signal to the switch (instead of directly to the NUC), the WOL should still work properly. Therefore, the switch must receive sufficient power, even if the NUC is in S3 ;-)

Thanks in advance for your feedback.

Best regards,

Jochem

I've been using NUC6i5SYK to drive 3 DP displays via StarTech MSTMDP123DP. It works brilliantly. NUC6i5SYK is now getting hard to find, so I'm planning to switch to NUC7i5BNK and StarTech TB32DP2 but it appears the even though the tech spec for the NUC7i5BNK says it supports 3 displays, the Intel Thunderbolt 3 does not appear top support multi monitor - but I'm seeing conflicting information on the web so would like to know:

1) Is there any way I can drive 2 monitors out of Thunderbolt 3 on NUC7I5BNK other than just daisy chained cloned screens?

2) Is there a software or firmware update planned to add this capability?

3) Will the gen 8 equivalent support this capability?

4) Am I missing something? This seems to be a backward step.

Hello.

I just got the nuc from the title a day ago and today i set it up connecting it to my tv. I noticed a weird problem with the hdmi. Sometimes when i change the source on my tv to another hdmi and then switch back to the hdmi where the nuc is i have an image which is only a white noise video. I am attaching a picture of it. After a few reswitches it gets normal. If i dont reswitch the screen keeps flickering between no signal, that white noise stuff and nothing shown with the message that the resolution is not supported. If i start the nuc and i have the tv on that hdmi source from the start everything is ok. Same after it starts working. The problem occurs just if i switch sources while nuc is on or i start the nuc and i have the source on tv on another one and i switch to the nuc at a later time.

Any idea what might be happening?

Hello!

Is HDR support in windows 10 creators update supported for this model?

I cant find anything to activate it? In the HD control panel i cant change color depth and so on..

Do we need graphics driver with WDDM 2.2?

Kind reegards

Jake

I have a Nuc7i5BNK with Iris Plus640 Graphics but the latest driver, 4849 which should enable support for HDR, wont install and says the driver is not supported on my hardware. The Iris Plus640 is listed on on the supported hardware list for this driver on the download site but still wont install.

I am still running driver 4815 without any HDR. Should i wait for a specific driver for Nuc?

I have nuc version:5i5RYH.

Iam trying to install windows10 on it

I have flashdisk (SanDisk) Cruzer Glide 32GB which I prepared via my other macbook in order to burn window10 iso in it.

So i formatted the usb with FAT32(also tried fatExt) and burned  into it windows10(Win10_1709_English_x64)

After validating the flashdisk with the windows installation  I plugged it into my nuc the USB  and choose to boot from it -> Failed!

seems like NUC never manage to boot via that flashdisk.

I have no idea why.. i tried couple of times.

So what I did next?

upgrade the nuc's bios settings (using the same USB stick I downloaded an official bios version from intel website) and right now after the upgrade I have the following

BIOS VERSION:

RYBDWi35.86A.0367.2017.0929.1059

my current processor: Intel R i5-525ou CPU @ 1.6

Even after upgrading, again trying to boot via the USB stick which has the windows10 iso. no success.

inside the boot screen I have the boot order screen:

at the UEFI tab i see:

Boot driver order : No Boot drive

at the Legacy tab under the Boot drive order I do see the USB stick item in the list (sanDisk cruzer Glide 1.26), together with the SSD drive.

Any idea why (or how) can I actually install windows 10 on my NUC? what am I doing wrong?

(p.s before I tried to install WINDOWS i had a successfull installation of openELEC)

Thank you,

Message was edited by: Idan F

hello,

I got Ubuntu 16.04 installed on my NUC6i5 and it works fine, only the fans are too loud and cannot be detetcted by Ubuntu Software for this seems to be an Intel problem.

Now, I got an dualboot system installed - Windows 10 / Ubuntu 16.04 and the curious thing is, that under Windows the fan control of Bios/UEFI works fine-silent after correcting UEFI fan-settings, (newest bios), but does not work under Ubuntu correctly: much too loud!

Also curious: Starting windows immediately after Ubuntu, the fan is yet silent, the CPU seems to be very cold!

Please, please, is there a possibility to repair this, eventually by a bios update?

The sound of the fan under Ubuntu is very disturbing!

And I'm using Ubuntu most of the time. The NUC is such a fine computer, he has to get a real chance also for Linux!

Also, if anybody has a solution via Ubuntu yet, please let me know!

Thank you for your efforts, I hope to hear from you!

Hi there!

I'm trying to install ESXi 6.5 on my NUC7i7BHN but it does not recognize the network card. Ubuntu 17 server has the same issue. Anybody can help me with that?

Basic setup:

BOXNUC7I5BNK, 4GB Kingston Model KVR21S15S8/4, Samsung 960 500GB, Windows 10 x64 Pro.

Bought and installed back in August, has worked with some pretty common complaints--sometimes lose audio or display on wakeup, won't wake from BT keyboard, occasional crashes.

Had to walk over and reboot today to restore sound so started looking into drivers and everything's been updated since I bought so seemed worth a shot. Had a pretty common hassle--the installer for the new graphics driver wouldn't run "setup.exe", DSA crashed while trying to update itself and wouldn't restart and thus had to download manual drivers. Graphics, BT, HDMI and BIOS.

I start with the BIOs, agree to the license and reboot, and... no display. I wait a minute or two, do a hard reboot, and now it won't start. Just loops, 15 seconds blue, 3 seconds orange, flickers off and does it again. Never sends a display.

I expect I'll be on the phone about a warranty claim on Monday, but is there anything I can try in the meantime?

I have recently discovered a USB C hub that connects to my Thunderbolt port on the NUC7i7BNH. However it's only got an hdmi port, 2 usb ports and an sd card slot. I can daisy chain it with another hub, but there's no other USB C out on it, so can you daisy chain them together and retain the high power transfers?