Quantcast
Channel: Intel Communities : Discussion List - Intel® NUC
Viewing all 18668 articles
Browse latest View live

Frequent screen blanking with Intel Graphics driver on Win10-1803

$
0
0

I have seen several topics about people experiencing different forms of the screen blanking to black with NUCs. One of them with the NUC6CAYH, which was solved with v.45 of the BIOS.

 

It now also manifests after installing the latest Intel Graphics driver v.15.65.4.4944 with Windows 10 v.1803 on a NUC6CAYH with all the latest drivers and the latest BIOS v.49. Pretty frequently the screen blanks for about 1.5 seconds. Downgrading the BIOS to v.48 or v.47 has no effect. Uninstalling the Intel driver and reverting to the Microsoft Driver removes the screen blanking again. Version 45 of the BIOS is not available for downloading anymore but of course the problem shouldn't have been re-introduced in later versions. For the purpose of elimination I had wanted to test that version.

 

For the moment it would appear this might be caused by the recent v.1803 of Windows 10 for which the BIOS fix may not work anymore. I believe I experienced it shortly too with Win10-1709 which was then solved by upgrading the BIOS to the then latest v.47 but with the latest Windows 10 version it seems to be back.


The BIOS did not correctly communicate with the Trusted Platform Module (TPM)

$
0
0

Hi,

 

I'm trying to deploy  more than 50 NUCs with SCCM.

A lot of NUCS are succesfully deployed but a few others aren't.

An error occurs during the last step of the sequence: Enable Bitlocker.

2150694914: The BIOS did not correctly communicate with the Trusted Platform Module (TPM). Contact the computer manufacturer for BIOS upgrade instructions.

 

Manually:

When i try to enable Bitlocker manually from Windows, the following error is shown: The BIOS did not correctly communicate with the Trusted Platform Module (TPM).

 

unreliable Workaround:

The problem goes (not always) away after disabling and enabling UEFI BOOT and SECURE BOOT, followed by Clear Secure Boot Data.

 

Its possible that the NUCs were previously deployed with bitlocker, but i can't verify this.

 

How can i prevent this error in the future, and upcoming deployments?

 

Thanks in advance,

 

Jerome

M.2 SSD Not Recognized NUC5i5RYK

$
0
0

I'm on my third NUC and second Kingston memory stick. For whatever reason the devices refuse to acknowledge the memory stick for any length of time.

 

We purchased a few of these NUC5i5RYKs in 2017 with no issues at all. We needed one more this year and I've had nothing but problems over the past 7 weeks. I ordered a new NUC (same model as previous purchases) in April, installed memory (same memory - Kingston 120GB M.2). At first the drive showed up as expected, began the Win8 install and partway through install failed. There was no longer a drive to install to. Opened up the device, reseated the M.2. Now it comes up as 2GB? Reseated several more times. Doesn't show up at all now. I sent the NUC back as defective. Took 3 weeks to get the replacement. Second unit has the same exact issue. I figure it's the stick. Sent the stick back, got a replacement. Same issue. Sent second NUC back, got replacement. Same issue.

 

This same memory is working fine in two other RYKs at the office. I'm not sure what's changed in the past 8 months, but this is incredibly frustrating. We still need another computer so I can't just return it and wash my hands of the entire situation. Does anyone have any idea what the issue is?

 

I've reset the BIOS defaults (F9) on two different units. I've updated the BIOS to the latest version downloaded from the Intel site. No fix. I can only reseat the memory so many times. It fits perfect. It's right side up. AHCI is enabled. UEFI is enabled. Devices - PCI - SATA shows Not Populated. I'm at a complete loss how to proceed.

 

Thank you in advance for anyone who has any ideas.

Update never happens

$
0
0

NUC5CPYH     8GB RAM     500GB HDD

 

Using Intel's Driver and Support Assistant I get an update for the

 

Intel Serial IO I2C ES Controller ----- Driver for Win 10

Latest Version 1.3

Installed Version: 604.15063.3024.59921

 

It has been for a while this update appears but never seems to change after the installation happens.

 

Can you let me know if there is an issue with my hardware or the updating software?

 

Thank you....

Problems with Distributor supplied Team Elite 8Gb DDR4 SoDIMM and BIOS 63

$
0
0

Just letting you all know I just had an issue with the new BIOS 63. The system shipped with 61 and we always upgrade to latest before shipping. BUT.

 

The system was working perfectly. Immediately after upgrading to 63, the system would take up to 30 seconds to start booting. This is unacceptable to ship to customer. I also saw a weird FV Downgrade message and something failed a few times (could not read it quick enough).

 

This unit has a single Team Elite 8Gb SoDIMM (DDR4 2133 code TED48G2133C15-S01). I've also tried moving it from the bottom slot to the top.

 

We normally always use Kingston ValueRAM which never provides an issue but for the last few builds we've used this RAM as it came as a PROMOTION from the Australian Distributor Synnex with the NUC.

 

This has not provided any issues in the last few builds but obviously the BIOS version of those were pre-63.

 

This is the first with 63 and the problem has arisen.

 

Now, I ran a downgrade to 62 and immediately the problem was solved. The NUC starts booting (with Intel logo) within seconds again.

 

Something in 63 obviously broke compatibility withe the memory (as again, was shipped with the NUC as promotion).

 

I suggest NOT upgrading to 63 until Intel provide a BIOS without this problem, if you use this memory.

 

INTEL: Please take note of this. There's an issue with 63 and the RAM provided as a promotion through your distributor. Not good enough.

NUC8i7HVK faulty usb-c video drivers

$
0
0

I've setup my hades canyon nuc (NUC8i7HVK) with all the latest drivers and bios and the performance of my monitors when driven by the thunderbolt/usb-c output is awful. The monitors have a native resolution of 2650x1440, but the NUC will only drive them at 2048x1080. Using the mini-display ports doesn't fair any better. In both cases the rendering lag is 300ms - 2 seconds depending on the task.

 

Also, the time to negotiate the connection takes 4-10 seconds (if it even displays at all).

 

The monitors work perfectly and instantly when plugged into the usb-c on my macbook pro.

Screen sporadically becomes black on Intel NUC (NUC7i5BNH)

$
0
0

Another problem I noticed and which is very annoying is the screen sporadically becomes black for a second on my Intel NUC. It does not seem the graphic driver crashes as there is no error message by Windows and the screen is only black for a second or two – after that all is as before.

 

  • This behaviour only appears when I use both monitors. When I only use Monitor 1 I don't have this problem.
  • When I put a YouTube video into fullscreen on Monitor 2 (Google Chrome) the behaviour appears. When I move a Window from Monitor 1 over this fullscreen on Monitor 2 (e. g. Windows Task Manager) the behaviour is no longer present. When I change to fullscreen again so the Windows is minimized the screen sporadically becomes black again. That is very mysterious.

 

Model: NUC7i5BNH (Date of Manufacture: 06/2017), SA J3**** - 305

SSD: Samsung 960 Evo M.2

RAM: 8GB Crucial DDR4-2133 SO-DIMM CL15 Single (CT8G4SFD8213)

Monitor 1: Dell P2715Q (3840x2160), DisplayPort over USB-C

Monitor 2: Dell U2715H (2560x1140), HDMI

Drivers: Up to date. I use BIOS version 0062.

NUC6CAYH unable to boot, ring led status stuck in fade mode, BIOS defaults does not solve

$
0
0

Hi,

 

I've been using a linux based tool (GitHub - milesp20/intel_nuc_led: Intel NUC7i[x]BN and NUC6CAY LED Control for Linux ) to change the Ring LED on the NUC6CAYH to different colors and modes.

I may have stumbled upon a situation where the NUC is unable to boot after the ring led has been set to fade instead of being on solid.

 

To create the problem:

-     Set the ring led to "sw controlled" in the Visual Bios

-     Boot into linux

-     Load the driver and set the ring led to fade slowly in color white

-     Reboot the NUC, it is completely stuck, the ring led is fading slowly white but the UEFI does not seem to go past POST or even offer any options to enter the setup menu

 

To temporary fix the problem, clear CMOS as suggested here: Clearing CMOS on Intel® NUC

-     Plug AC power in

-     3 second power button trick to get into "safe mode"

-     Enter setup, load defaults (F9) and save

This sets the ring led back to "power status" and makes the NUC bootable again.

 

Here comes the tricky part:

 

After booting successfully with the new BIOS settings I rebooted the NUC again and set the ring led back to "SW controlled", thinking it would be back to defaults (off) and boot.

But after saving and rebooting the NUC the ring led is fading slowly white again, I hoped the setting (and possibly bug) would be gone.

 

Now I am unable to ever set the ring LED back to "SW controlled" since it renders the NUC unbootable.

Could this be a BIOS issue?

 

I'm running the latest version: "AYAPLCEL.86A.0042.2017.1117.1918"

 

Sincerely, Koen


Case for NUC6I7KYK

$
0
0

I am the owner of Intel NUC6I7KYK

Fastening for the screw was scattered, it is possible where that separately to buy the case for this device?

NUC won't boot - tips

$
0
0

My MS-Windows 10 crashed during an update and became corrupted. Got stuck in a continuous loop unable to progress beyond "preparing automatic repair". Took me ages to discover a fix. Here are a few remarkable tips!

 

1. One solution is to repair or reinstall  Windows having made repair media on another Win10 machine. But you need to boot from it. You may need to access F2 during Start Up.

 

2.  But if your NUC is connected to a 720p (HD) monitor, oddly, it won't offer you F2 on start up. It doesn't even appear in the boot menu. Adopt a higher resolution monitor and it will appear, but only if directly connected HDMI to HDMI (not via an adapter).

 

3.  Your NUC also won't offer F2 with a wireless keyboard until Windows drivers will boot. So once you have got passed foible (1) and can see the option on screen you can still press F2 frantically with no response. You need to use a wired keyboard to get going again.

 

Took me four days to discover this, so thought I should share the knowledge.

Regarding Supported Device list and Average turn around for repairs

$
0
0

Hello there everyone I have two queries I am hopping i can find the answer for here. I am really interested buying the Intel® NUC Kit NUC8i7HVK

 

1. in the 2x8gb ram configuration I cannot find any for sale that are in stock within Australia (Victoria) that are supported, Am I better off to import one from the device list or will the Corsair CMSX16GX4M2A2400C16 (2400mhz 1.2v) function? I would prefer to purchase within Australia. The 1 TB SSD 2280 by WD is supported, would there be any reason the 2TB version would not work?

 

2. As I will depend on this NUC for work related tasks with the adobe suite, if for the unfortunate reason this unit is in need of repair or is faulty, what is the average turn around time for a unit to be fixed and sent back? I do heavy work loads so using a random computer as a temp may not cut it.

 

Thanks in advance to anyone with advice, I really do like the idea of heavily compacted desktop, seems to be a good solution between a laptop and desktop.

NUC7i5BNH clone booting problem

$
0
0

Hi all!

 

I had 2 nuc (NUC7i5BNH). I installed Xubuntu 16.04 in one of them and cloned the hd into the other nuc. Everything worked well. I did the cloning thing a lot of times.

 

Now I bought other NUCs (NUC7i5BNH) with the same BIOS version (BNKBL537.86A.0045.2017.0417.1728).

If I put an SSD with Xubuntu from my 2 old nucs in those new NUC it doesn't boot. It says: "A bootable device has not been detected".

 

I tried to install ubuntu 18.04 in the new one and cloned it, but the new installation doesn't work on others NUC but the one where I installed the OS and the old 2.

 

Is there some kind of option in the bios that prevent from boot an SSD installed from another pc?

Help me please. I can't install ubuntu and a lot of stuff in 20+ NUC. I need to clone it... 

Power Management for USB

$
0
0

When I shut down nuc normally, its usb interfaces have no current, which is correct. However, when I have my NUC  forced shutdown, its usb interfaces are still powered on.

Possible to adjust console screen size for Ubuntu? NUC7i5

$
0
0

I am running Ubuntu Server 18.04 on my new NUC and it does not have a GUI console, just text. I've found several ways to adjust the HDMI when X is running but nothing for a straight text console. The problem is overscan such that the outside edge of the text screen is painted off the screen and is hidden. The most annoying is that the last line and the first few columns of text are missing.

 

Is there any way of adjusting that?

 

Bill W

 

Message was edited by: Bill Waggoner - typo

NUC7CY* Software Controlled Led?

$
0
0

Hi,

 

We are using the rectangle led on NUC6CAY to show system status to customers. Now I noticed that NUC7CY* miss this feature and show a little HDD led instead. Is it possible to change setting in bios to "software control" this led?

 

Thanks


The BIOS did not correctly communicate with the Trusted Platform Module (TPM)

$
0
0

Hi,

 

I'm trying to deploy  more than 50 NUCs with SCCM.

A lot of NUCS are succesfully deployed but a few others aren't.

An error occurs during the last step of the sequence: Enable Bitlocker.

2150694914: The BIOS did not correctly communicate with the Trusted Platform Module (TPM). Contact the computer manufacturer for BIOS upgrade instructions.

 

Manually:

When i try to enable Bitlocker manually from Windows, the following error is shown: The BIOS did not correctly communicate with the Trusted Platform Module (TPM).

 

unreliable Workaround:

The problem goes (not always) away after disabling and enabling UEFI BOOT and SECURE BOOT, followed by Clear Secure Boot Data.

 

Its possible that the NUCs were previously deployed with bitlocker, but i can't verify this.

 

How can i prevent this error in the future, and upcoming deployments?

 

Thanks in advance,

 

Jerome

GSkill Memory on NUC7 question

$
0
0

Hello!

 

Please, can I use the GSkill memory code F4-2400C16D-32GRS on NUC7i7BNH, without problems?

I couldn't find it listed on Intel's compatibility list nor GSkill QVL.... by the way, the Set is 2 x 16 GB.

 

Thank you!

Sideways Vesa Mount

$
0
0

This is perhaps a silly question. Are there any issues with Vesa mounting the NUC8i7HVK sideways on the back of the monitor?

 

If I install the bracket with the arrows pointing up, then the computer covers the power and HDMI jacks on the back of my monitor. Installed sideways (with the narrow part of the keyholes down) everything fits. I can't really imagine what problems this could cause.

NUC 2820 doesn't wake on scheduled time

$
0
0

Hello,

 

my nuc DN2820FY is running a Windows 8.1 and goes in hibernate mode every night. In the morning it's triggerd to wake up via BIOS (S5 wake) at 8:00 am.

This worked fine for years.

 

Now I've updated the old BIOS version from 2016 to the new BIOS Version from 03/2018 (FYBYT10H.86A.0063.2018.0314.1612).

Since then the nuc doesn't wake on the scheduled time I've set in the BIOS. But as soon as I try to access a network share of the nuc, it wakes up.

 

I've tried this, but it doesn't helped: https://www.intel.com/content/www/us/en/support/articles/000020534/mini-pcs.html

Any ideas? Is it a known issue?

 

Thanks.

Eddy

NUC7i5BNK Thermal Event Hibernation

$
0
0

I am getting this error when i visit certain sites or use Steam: "The system was hibernated due to a critical thermal event."

 

All the drivers and BIOS are updated.

 

I just disabled Boost in the BIOS, but its still happening.

 

The system was hibernated due to a critical thermal event.

Hibernate Time = 2018-01-28T06:47:51.992734900Z            

ACPI Thermal Zone = \_SB.PCI0.LPCB.H_EC.TZ0            

_HOT = 200K

 

 

Amy recommendations?  This thing is brand new.

Viewing all 18668 articles
Browse latest View live


Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>