Community
cancel
Showing results for 
Search instead for 
Did you mean: 
L_Crane
Novice
7,201 Views

Is there going to a fix for the no HDMI signal issue?

At the beginning of July the NUC started intermittedly, what it seems like, turning of HDMI output, the monitor would display "no HDMI signal" but would come back, over the first week of July it got worse. The computer has been fine previously for years.

 

The setup is pretty simple since it's not my computer but my mothers' computer, specs as follows:

Intel NUC - NUC6i7KYK

Kingston DDR4 8gb ram (previously Cosair 16gb DDR4, but due to no boot issues I removed it)

Kingston SATA2 120gb M.2 SSD

Single display monitor ASUS VE248 (not HDMI 2.x)

USB Devices include two wireless HID keyboard and mouse (one usb for each)

Logitech Speakers connected to the rear audio out and a pair of headphones connected to the front audio out/in.

 

That's pretty much it, no Thunderbolt devices being used. After seeing the issues get worse I tried 3 different HDMI cables, same issue, tried two TV's and another monitor, same issue.

 

With the issue getting worse, making the computer unusable, well via HDMI monitor anyways, I installed teamviewer and proceed to backup the data on it.

 

My first thought was to update the BIOS from 41 to 63, which was a hassle in and out it self as I could only succeed by using the UEFI shell. Although I did same the same years ago when the Corsair memory caused a no boot issues and upgraded the BIOS to 41 at the time with no change, I brought more memory to try out and it succeeded booting up.

 

After some time looking to people with similar issues I found they all had bigger or more complicated setups, i.e. Dual Monitors, 4K TV's, HDMI/DP adaptors, etc.

 

Having no HDMI 2.x capable devices I can't upgrade the firmware so I decided if a fresh install would help. Setup was fine and Windows without drivers was fine until connected to the internet and it downloaded drivers, and yes I even opted to not automatically install drivers but Windows 10 1903 did it anyways, and the problem persisted. After many attempts without connecting to the internet and installed each driver one by one, the problem only occurred again when the graphic drivers were installed. However uninstalling the driver was fine. I did try every graphics driver for the NUC6i7KYK and Iris Pro Graphics 580, with no success, but uninstalling and returning to the Microsoft Basic driver the display was fine.

 

So this is were this video comes in, as proof.

https://youtu.be/WP9mK_MdN1o

In this video I showed the when Windows 10 versions 1903, 1809v2, 1809oct-nov, 1809oct, 1809 wont install due to requiring drivers at setup and after trying literally every driver for every NUC with no success, I think only an all in one would work but proceeded to 1803, each time I -only- installed graphics drivers and nothing else only for the problem to reoccur, each time. Of course with BIOS version 61 the problem is even worse than before, since the NUC was fine with BIOS version 41 and Windows 1803 and older now "legacy" driver, it was only when the updates started on the 1st of July 2019 that this occurred and forced updates were being applied.

 

So now we have a NUC that may need it's BIOS downgraded and/or Windows 10 v1803 without being connected to the internet, not a solution by all means, so the final tempory solution was to install Linux and VirtualBox to virtualise Windows 10. The NUC has being running fine with Ubuntu 19 with all updates applied for some time now.

13 Replies
Wanner_G_Intel
Moderator
6,152 Views

Hello L Crane,

 

Thank you for posting on this Intel Community.

 

Are you able to install Windows* and run the following tool to gather more information about your unit?

 

Intel® System Support Utility (Intel® SSU)

 

1. Download the Intel® System Support Utility and save the application in your computer.

2. Open the application and click "Scan" to see system and device information. The Intel® SSU defaults to the "Summary View" on the output screen following the scan. Click the menu where it says "Summary" to change to "Detailed View".

3. To save your scan, click Next and click Save. 

 

Is this the issue you are describing: HDMI* signal dropping out randomly.

 

Wanner G.

Intel Customer Support Technician

A Contingent Worker at Intel

L_Crane
Novice
6,152 Views

Sorry for the delay.

 

I used the SSU program on both Windows and Linux. Attached is the the Windows version.

 

"Is this the issue you are describing: HDMI* signal dropping out randomly."

That is more or less accurate.

 

Beingdinu
Beginner
6,152 Views

Did this ressolved the issue, Even i am facing the same issue after the 1903 update. my TV connected on HDMI is not been detected as a second monitor and as sson i connect the HDMI capble the Display Driver changes to Native drivers leaving all the icons huge.

L_Crane
Novice
6,152 Views

Attached to this reply is the Linux SSU log.

kishorm
Beginner
2,523 Views

I am facing the same problem with Intel NUC PC 10T700AHUK. It says No HDMI signal even when PC is powered ON. I tried removing the HDMI cable, restarting the PC and and then re-inserting HDMI cable. It worked once. But the problem resurfaced after 7 days. Tried the same trick again. But it didn't worked this time sadly.

Please help me to fix this.

Currently system is useless due to this problem. And the user is annoyed because he is not able to use it for any purpose.

n_scott_pearson
Super User Retired Employee
2,505 Views

First of all, you are responding to a more than 2-year old thread. Reality has changed significantly since then.

Secondly, that is not an Intel NUC product; that is a Lenovo ThinkCentre SFF PC. You need to contact Lenovo regarding this issue.

Are you saying that you see nothing on screen when you power on the PC? If so, that is a typical indicator for a hardware component failing or an issue with the BIOS. In either case, you need to contact Lenovo.

...S

Wanner_G_Intel
Moderator
6,152 Views

Hello L Crane,

 

Thank you for attaching the reports requested.

 

To better assist you, we would like to know exactly what the behavior/issue is.

 

1. Do you think that the HDMI* port on the Monitor/Intel® NUC stops working out of the blue?

2. Does the issue occur if you unplug the HDMI* cable and plug it back in?

3. Wiggle the cable where it connects to the unit and let us know if the problem persists.

4. Please let us know if you have installed the graphics driver version version: 26.20.100.6911 for testing purposes.

 

We recommend following these steps:

 

Load BIOS default settings:

 

1. Press F2 during boot to enter BIOS Setup.

2. Press F9 to set defaults.

3. Press F10 to save and exit BIOS.

 

Wanner G.

Intel Customer Support Technician

A Contingent Worker at Intel

L_Crane
Novice
6,152 Views

1. Do you think that the HDMI* port on the Monitor/Intel® NUC stops working out of the blue?

only when any graphics driver is installed, it seems the HDMI port turns off and on periodically

in the video I show that when a graphics driver is installed the monitor shows no hdmi signal

with the Microsoft Basic Display driver the HDMI works fine.

 

2. Does the issue occur if you unplug the HDMI* cable and plug it back in?

nothing changes in the slightest, only the monitor wakes up displaying "no hdmi signal"

 

3. Wiggle the cable where it connects to the unit and let us know if the problem persists.

there is a solid connection and very little wiggle room and has no effect

 

4. Please let us know if you have installed the graphics driver version version: 26.20.100.6911 for testing purposes.

thats the exact driver I used in the video I mentioned earlier I also tried

15.45.23.4860

25.20.100.6519

26.20.100.6911

And Iris Pro Graphics 580 drivers

15.40.14.4352

15.45.18.4664

15.45.19.4678

15.46.02.4729

15.46.05.4771

15.47.02.4815

25.20.100.6444

25.20.100.6471

25.20.100.6519

25.20.100.6577

25.20.100.6618

26.20.100.6708

26.20.100.6709

26.20.100.6861

26.20.100.6890

26.20.100.6912

The previous setup worked with Bios ver. 41 and driver 15.45.23.4860 until 1st july 2019 when the computer updated the driver and the issue presented.

With Bios ver. 63 all drivers present the problem

 

Load BIOS default settings:

The bios has been left on default setting since I updated to Bios ver. 63

 

Wanner_G_Intel
Moderator
6,152 Views

Hello L Crane, 

 

Thank you for your response. 

 

Based on the troubleshooting you have performed, this does not seem to be a driver issue. In other words, it is not a driver bug since it happens with a large number of driver versions. This could be caused by a faulty unit since it started happening more than a month ago.

 

We recommend performing the following steps below. If the issue persists, replacing the unit is the recommended solution unless you would like to continue running Windows* in a virtualized environment.

 

1. Check if a program or other software is causing this behavior by performing a clean boot in Windows*.

 

Note: This link is being offered for your convenience and should not be viewed as an endorsement by Intel of the content, products, or services offered there.

 

2. Try using other resolutions and refresh rate.

3. Disconnect all non-essential hardware from the Intel® NUC. Connected docks, dongles, adapters and other hardware can cause conflicts.

4. Use other video output ports.

 

Wanner G. 

Intel Customer Support Technician

A Contingent Worker at Intel

L_Crane
Novice
6,152 Views

So basically no idea just buy another computer then?

 

I certainly didn't appreciate that response, but it get me in the mood as at were to solve the problem.... and indeed I have.

 

After a lot of trying things out from updating inf files for the monitor (and signing them), editing the graphics registry to make sure the output matches etc.

I eventually came across a Windows 10 15xxx from 2015 I had stored away, and the same thing happened on it too.

 

Longer story short, it's the on board HDMI adaptor, although it's not completely broken, the Intel drivers must be trying to enforce something or another that causes the HDMI adaptor to falter.

So I think the firmware on it is somewhat broken, might've been modified somehow for some reason, I know Windows had some firmware/microcode drivers installed.

 

And had this even further confirmed when a complete passmark benchmark completed, no problems.

I went and brought a miniDP to HDMI cable and it worked.

 

So if and when they buy a 4k monitor, since HDMI 2.x seems to be only on 4k monitors, I'll see if the HDMI firmware can be updated with Intel's Firmware update.

 

So..... Thanks for your "help". I was hoping it was something else but there we have it.

 

Wanner_G_Intel
Moderator
6,152 Views

Hello Beingdinu,

 

The issue you are describing is different. Please submit a new question.

 

Wanner G.

Intel Customer Support Technician

A Contingent Worker at Intel

SWikl
Novice
6,152 Views

Hi,

 

Since I after two attempts, have been unable to create a new topic/post myself in this form (the webpage just says "You can't create a topic", or something like that), I have to ask mine here. Sorry.

 

Subject: NUC8i3BEH no signal from HDMI

 

Hi,

 

I bought a NUC8i3BEH 2019-08-23 and I'm running it with:

 

  • Corsair 16GB 2x8GB 2400Mhz / DDR4 / CL16 (CMSX16GX4M2A2400C16)
  • Samsung 960 EVO Series MZ-V6E250BW 250GB

 

It's connected to a Dell UltraSharp U2715H together with a work laptop. My NUC on HDMI-port 1 in the monitor, and the work laptop on HDMI-port 2. I've been able to switch image between the different computers since the installation in August.

 

Immediately after the purchace, I updated the BIOS and currently it's now "Intel Corp. BECFL357.86A.0073.2019.0618.1409, 2019-06-18"

 

It's been purring like a kitten since start but - my problem now is that a few days ago, (not really sure when, since it's switched on day and night), I suddenly wasn't able to get a signal from the NUC to the screen. The screen is just black.

 

I'm guessing this happened after an automatic update of either the graphics driver or something in Windows Update, but I'm unsure.

 

Luckily, I have TeamViewer installed on the NUC, so I can access it from the work laptop just beside it, but only once it's at the login screen for Windows - not before that.

 

I.e. I CANNOT enter BIOS or so. Only work from within Windows. I can't either - as far as I'm guessing - restart it in fail safe mode, since I can't get a signal/image on my monitor.

 

This is what I'ved tried:

 

  1. According to Windows Update, I'm fully updated
  2. The Intel® NUC power LED is not blinking
  3. I have switched HDMI cables back and forth between the NUC and the work laptop and both cables give me signal to the work laptop - so it's not the HDMI cable nor the monitor
  4. I have removed and re-installed the graphics driver, with no success and I am now running version: 26.20.100.7212

 

System configuration from Intel System Support Utility is attached in my post.

 

WHAT is the issue, HOW do I resolve it and HOW do I avoid the same issue again in the future? I'd rather not switch the unit to a similar one at a retailer, re-installing everything and then experience the same issue again a few weeks later.

 

All the best,

Sean

TDean
New Contributor II
6,152 Views

This may or may not work.......But I think there is some RF interference going on with the hdmi in NUC. I used to get resolution changes every time I booted or restarted and alot of time I would have the no signal issue, then about a month ago I purchased a certified 2.0 HDMI cable that has a 28awg cable and guess what? I don't have any of those issue again. Problem Solved so far. I'm not saying that's the fix for you but it sure fixed my issues. I also had another supposed quality hdmi cable, and I couldn't even get a screen with it. AND I used to have my logitech 2.4ghz wirelesss mouse fob plugged in the back.....and it would go in and out of service, so I moved it to the front and have had no issues since, and it's been over a year now. And If I was to use a USB device next to it in the front that isn't shielded properly, the mouse would start acting up again. SO I think some if not all of these connection issues have to do with a lack RF shielding on these connectors.

Reply