Intel NUC8i5BEH Graphics Issue with latest drivers | Daisy Chained / MST displays don't work at all

[HSagg]

Hi,

This is a follow up to the OLD Support case, which was archived as I didn't responded back on time.

So, I am creating a new case.

OLD CASE: https://forums.intel.com/s/question/0D50P00004Pb4s9SAB/intel-nuc8i5beh-graphics-issue-with-latest-drivers-usbc-displays-dont-work-at-all

Summary:

The latest intel drivers has some Issues. Daisy Chained / MST Displays don't work at all when I use the latest driver. As investigated, CPU usage remains high and displays are contantly flickering in background, with no display at all.

If I disable Daisy Chaining (from Dell Monitor - by disabling 'DisplayPort 1.2'), latest driver works. But this totally ruins our standard setups.

NUC: NUC8i5BEH2

BIOS Version: Latest - 0073 - ECFL357.86A.0073.2019.0618.1409

OS: Win 10 1809 [Semi-Annual Channel Release | Business Stable Release]

Displays: 2x Dell UltraSharp U2414H

Display Connection type: DisplayPort 1.2 over USB-C (with MST / Daisy Chaining)

Graphics: Iris Plus 655

Graphics Drivers with Total failure: 26.20.100.6912

Graphics Drivers with Intermittent Display Issue: 25.20.100.6519

Graphics Drivers working fine: 24.20.100.6345

When I revert back to OLD drivers (24.20.100.6345), displays work perfectly well. No Issues with Daisy Chaining, everything works as expected, unlike 6519 (which flickers intermittently) and 6912 (Total Failure).

Kindly investigate and fix the Issue ASAP.

Let me know if you need any logs/dumps from my end.

NOTE Regarding COLLECTING LOGS:

On 6912, system hangs a lot. So as a workaround, I have to turn off the displays , then remote into system (RDP) and remove 6912 drivers, reverting back to stable release - 6345.

As investigated today with 6912 version. It turns out that if I disable MST / DaisyChaining (display port 1.2) on the Primary Monitor, 6912 driver works.

But as soon as I enable MST/DaisyChaining (display port 1.2), Issue re-appears.

Same goes for 6519, albeit 6519 is affected to a lesser extent.

Since on version 6912, I can't even login, can you advise how can I collect the logs?

Physical Devices are not properly enumerated in RDP Session, so logging will probably not be OK via RDP Session.

As a workaround, I could disable MST/DaisyChaining while running version 6912, solely to collect logs, but then, the collected logs will not be from NOT OK Scenario. What do you suggest as far as Logging goes?

NOTE regarding Monitors: My other Intel PCs (Thinkpad T480 [HD Graphics 630] and T450) works fine with latest drivers. NO Issues at all while I use Daisy Chaining Setup with the aforementioned monitors.

Same is also evidenced since Daisy Chaining works fine on NUC itself with OLD Driver version - 6345.

So Displays looks OK.

Regards

Harman

[n_scott_pearson]

FYI @ChrisV_Intel​, @Bryce@Intel​, @LeoC_Intel​ -- I can attest that this issue is reproducible.

...S

[Leonardo_C_Intel]

Hello everybody

Thank you for posting in the Intel Community and for pointing this out allow me to test this on my end, I will be posting back as soon as possible.

Regards,

Leonardo C.

Intel Customer Support Technician

A Contingent Worker at Intel

[Ronny_G_Intel]

Hi HSagg,

We set up the NUC to be similar to the configuration of your failing system (driver 6912, Win10 1809). Please see the system details below.

Hardware:

System: NUC8i5BEH

CPU: i5-8259U

Gfx: Intel Iris Plus Graphics 655

RAM: 16 GB

Monitor(s): Dell U3014t (USB-C to DP), Dell U2713Hb (DP to DP) [Daisy chain configuration]

Software:

Gfx Driver: 26.20.100.6912

BIOS Version: 0073

OS: Windows 10 Pro Version 1809 Build 17763.107

Steps to Reproduce:

Set up daisy chain configuration using the following link as a reference: https://www.dell.com/support/article/us/en/04/sln293813/how-to-daisy-chain-multiple-monitors-using-displayport-multi-stream-transport-mst?lang=en

Observe CPU usage and observe if displays flicker or have no display and found no issues

Notes:

We also tested driver 25.20.100.6519 (reported intermittent issue with this driver) and we were also unable to reproduce the issue that you are reporting.

Can you please clarify if you are using an MST Hub, not a daisy chain configuration?

Regards,

Ronny G

[HSagg]

Hi,

I don't use MST HUB.

Daisy Chaining configuration is as specified in DELL KB. It has been such since last 2 years or so.

My Win 10 OS Build version is 10.0.17763.678 and yours is 17763.107

Should i record and share video with 6912 drivers?

Regards

Harman

[Ronny_G_Intel]

Let me see if I can try Windows 10 Build: 10.0.17763.678 and I will get back to you.

Regards,

Ronny G

[n_scott_pearson]

Ronny (@Ronny_Intel​),

I heard this week, in discussion with the NUC TMEs/PMEs, that certain ports cannot support certain types of MST Hubs (or MST Hubs in general). We have many NUCs with mini-DisplayPort connections and/or USB-C connections (with or without Thunderbolt support) across the NUC product line and I am sure this is (or soon will be) a point of much confusion. Can you explain what the issues are that affect this and document, perhaps on a NUC-by-NUC and/or port-by-port basis, what types of multi-monitor connections a particular port will support?

Thanks,

...S

[Ronny_G_Intel]

Hi HSagg,

It was difficult to get a hold of that particular build revision number <Windows 10 Build: 10.0.17763.678>. We were only able to find one 1809 version that was Windows 10 Enterprise with Build 17763.1 (we got this from our internal Windows repository) and we were unable to reproduce with it.

We also tested the latest Windows 10 Version 1903 Build 18362 and the issue was still not occurring. Is it possible that you update your Windows build version to the latest one? And once you get your system updated, can you please reinstall the latest Graphics driver, version 7158?

Regards,

Ronny G 

[Ronny_G_Intel]

Hi Scott,

Let me investigate about the MST Hubs comments that you heard from the TMEs and I will get back to the community.

Regards,

Ronny G

[n_scott_pearson]

Thank you very much!

...S

[Ronny_G_Intel]

Hi HSagg,

I am just doing a quick follow up on this issue. Did you test it with the latest Windows 10 update? If yes, and still having the same issue, can you please provide me with the following information:

1. Has this issue happened since day 1 or did it just start happening?
2. How many units are affected?,
3. What's the impact for your organization?

Regards,

Ronny G

[HSagg]

1. Has this issue happened since day 1 or did it just start happening?
   1. since 6912 releaase [with 6519, displays flicker like every minute but they do come back. With 6912 and later releases, its totally dead.]. We have to roll back to 24.20.100.6345 to get Dell Daisy Chained displays working again.
2. How many units are affected?,
   1. 5 - users are in remote location
3. What's the impact for your organization?
   1. Montoring team is not able to work properly when latest drivers are installed. Obsivously, they rely on Multiple displays. Monitor setup and cabling has been designed to drive 3 monitors via single cable.

Windows 1903 has a lot of Issues yet and most the organizations, including ours is still not rolling out 1903 feature update. Even as per MS, 1903 is still nor ready for businesses (see here https://docs.microsoft.com/en-us/windows/release-information/) as of now.

Today I tried Latest Driver version (26.20.100.7158) and still the same Isssue.

However, this time, I was also running xPerf/WindowsPerformanceRecorder trace session while keeping the NUC connected to another display via HDMI.

As soon as I connected the USB-C display cable [Daisy Chained display], issue triggered. System went into hung state at this point, As soon I disconnected USB-C cable, its back to normal.

Latencymon (DPC analyser) also reports very high interrupt execution times.

From the ETL trace, i can see that most of the CPU time is spent by igdkmd64.sys calliing exFunction to stall system. Since igdkmd64 symbols are not public, I don't see the entire call stack.

Can you get the ETL file analyzed?

 Video recording depicting the Issue: https://photos.app.goo.gl/EdfXRwKUEmEdphdn6

I can share the ETL trace file with you or upload it to your workspace, please send me an email. I can also regenerate ELT trace more information or with different profile scenarios, if necessary.

I will now rollback driver to 24.20.100.6345

Regards

Harman

[Chris_V_Intel]

Hi @HSagg​ 

My name is Chris and I help Ronny investigate issues.

I watched your video, thank you for sharing, it was really helpful!

I know above you noted that this issue all began with the GFX driver that ends in 6912. However, in the video you shared, the two GFX drivers you are using are: 6345 and 7158. A screenshot from the video:

I mention this for a couple reasons.

1. The latest GFX driver that we have posted for your system is 6912. 6345 nor 7158 have been tested and while I would hope they'd work, it's not always a given.
2. I tested this in our lab using GFX version 6912. I was able to hot-plug the Type-C daisy-chained displays without issue.

Lastly, I see you're using a Type C adapter from the NUC to your displays. Can you tell me who makes the adapter? And any chance you've tried a cable vs an adapter? When I tested it, I also used an adapter, but we have seen several instances of adapters not working as expected.

Thanks for your patience and helping us figure this out!

[HSagg]

Hello Chris,

In an earlier post, Ronny mentioned about latest release (ending with 7158). So that's why I did a comparison with 6345 and 7158 releases and skipped 6912. But the same issue also exists with 6912 release.

The adapter that I use is https://www.komplett.no/product/905884/pc-nettbrett/pc-tilbehoer/adapter/svive-usb-c-til-dp-adapter?noredirect=true?noredirect=true and two others from Office. I don't have the link for one's which I got from office.

I don't have any USB-C to DP cables.

Earlier, I was also assuming that there is something wrong with adapter. Then I got 2 more adapters from Office and same issue. But if I revert to OLD driver (6345), everything starts working. So I was convinced that adapter is OK but not the latest driver.

Same adapters also work with my three work pc's (Thinkpad T480, L480 and L380).

Do you need ETL tracing files?

Regards

Harman

[Chris_V_Intel · Accepted solution]

Hi Harman @HSagg​ 

Thanks for the prompt response and letting me know why you tested those two versions. :)

I'm with you, if you've tried 3 adapters, it's HIGHLY unlikely all 3 are bad. A couple more questions.

1. What's the large display that you're running via HDMI and at what frequency?
2. Just to make sure we're on the same page. When you say daisy chaining that means, into one Dell monitor, out of that same monitor, into a second Dell monitor, correct?
3. I see hot-plugging isn't working, any chance it works if you turn off the NUC, connect the Type C adatper, then turn on the NUC?

I was able to test this myself. I used a Dell P2845Qf connected via HDMI @4K. Then I used two Dell U2413f monitors, @1080p, to daisy-chain. I only tested version 6912 and as you can see in the attached video, everything worked correctly.

I will say, this took me longer to setup than I anticipated and I had to swap out a monitor that wasn't working correctly, but once I swapped out that monitor, no issues. I must say, I'm a bit flummoxed here.

[HSagg]

@Ronny_Intel​  @n.scott.pearson​ 

Did you guys saw previous my post/recording? Are there any clues from Screenshot Call stack?

I can share the Event trace file so that you can analyze yourself with your private symbols. Do let me know.

Regards

Harman

[n_scott_pearson]

Gee, I'd have to have driver source for that, which I don't, so not much I can do here. I would think that the same goes for Ronny; he is not going to have the source either. He can report issue to driver team and, if they need any additional information, Ronny will contact you then.

...S