Graphics
Intel® graphics drivers and software, compatibility, troubleshooting, performance, and optimization
20495 Discussions

Intel HD Graphics 620 / Win10 (Fast Ring): Error Code 43 with 15.60.01.4877 & 15.60.2.4901

DFink1
Beginner
4,163 Views

Hello Intel team,

I would like to use the "Enhanced performance in HEVC/H.265 video playback on 7th Gen Intel® Core™ Processors or higher", because of my DVB-T2 USB stick (german tv with 1080p60 HEVC), but get always error code 43 (device manager) after installation.

Both "Intel® Graphics Driver for Windows* [15.60]" drivers are not working:

15.60.01.4877 & 15.60.2.4901

Steps I have done:

1. downloaded the intel drivers

2. disabled the internet connection

3. uninstalled the driver 22.20.16.4836 (comes from Windows Update / recommend by Lenovo)

4. reboot my device, so that only the "Microsoft Display Adapter" is active

5. installed 15.60.01.4877 or 15.60.2.4901 (No error message while installing. Resolution is also changing to 1920x1080, but the brightness of the display is at maximum and at device manager I see error code 43)

I also tried it a few weeks ago with win64_15.60.0.4849.exe (working) and win64_15.60.01.4877.exe (error code 43) on Windows 10 Build 17046. So some changes between version 4849 and 4877 has broken the drivers for me.

Windows Insider Feedback-Hub (en-us): https://aka.ms/Kdtc11 https://aka.ms/Kdtc11

Device:

Lenovo Yoga 710-14IKB Type 80V4

BIOS Version: 2XCN32WW(V2.07)

DualCore Intel Core i5-7200U

Intel HD Graphics 620 (without a second graphics card)

Display (built-in): LG Philips LP140WF7-SPB1 / 14" LCD (FHD) / 1920 x 1080

Microsoft Windows 10 Home x64 / Version 10.0.17083.1000 (Win10 RS4 Insider Preview)

Windows Problem record:

Quelle

Windows

Zusammenfassung

Hardwarefehler

Datum

‎03.‎02.‎2018 17:18

Status

Der Bericht wurde gesendet.

Beschreibung

Aufgrund eines Hardwareproblems ist Windows nicht mehr voll funktionsfähig.

Problemsignatur

Problemereignisame: LiveKernelEvent

Code: 193

Parameter 1: 804

Parameter 2: ffffffffc000000d

Parameter 3: 114b

Parameter 4: fffff800a6c0f9a0

Betriebssystemversion: 10_0_17083

Service Pack: 0_0

Produkt: 768_1

Betriebsystemversion: 10.0.17083.2.0.0.768.101

Gebietsschema-ID: 1031

Weitere Informationen über das Problem

Bucket-ID: 0x193_DxgkrnlLiveDump:804_Status_0xC000000D_WD_LOG,Caller:_DpiFdoStartAdapter,_Function:_DpiFdoConnectInterrupt,_Status:_0x%I64x_DpiFdoConnectInterrupt_failed_for_the_FDO._dxgkrnl!DxgCreateLiveDumpWithWdLogs

Serverinformationen: c4d2ed5f-3c49-4099-ab2b-5885c507fda4

0 Kudos
9 Replies
DFink1
Beginner
1,794 Views

I have created now a new Feedback-Hub entry and recorded the installation:

Windows Insider Feedback-Hub (en-us): https://aka.ms/Twsdih https://aka.ms/Twsdih

Source

Windows

Summary

Hardwarefehler

Date

‎2/‎4/‎2018 12:24 PM

Status

Not reported

Description

Aufgrund eines Hardwareproblems ist Windows nicht mehr voll funktionsfähig.

Problem signature

Problem Event Name: LiveKernelEvent

Code: 193

Parameter 1: 804

Parameter 2: ffffffffc000000d

Parameter 3: 114b

Parameter 4: fffff800a18ff9a0

Betriebssystemversion: 10_0_17083

Service Pack: 0_0

Produkt: 768_1

Betriebsystemversion: 10.0.17083.2.0.0.768.101

Gebietsschema-ID: 1031

Files that help describe the problem (I have attached these files)

WATCHDOG-20180204-1224.dmp

sysdata.xml

WERInternalMetadata.xml

WERInternalRequest.xml

WPR_initiated_DiagTrackMiniLogger_One Trace User Logger_20180131 Event Collector_inject.etl

WPR_initiated_DiagTrackMiniLogger_One Trace User Logger_20180131 Event Collector.etl

memory.csv

sysinfo.txt

--------------------------

Source

Windows

Summary

Hardwarefehler

Date

‎2/‎4/‎2018 12:24 PM

Status

Report sent

Description

Aufgrund eines Hardwareproblems ist Windows nicht mehr voll funktionsfähig.

Problem signature

Problem Event Name: LiveKernelEvent

Code: 193

Parameter 1: 804

Parameter 2: ffffffffc000000d

Parameter 3: 114b

Parameter 4: fffff800a18ff9a0

Betriebssystemversion: 10_0_17083

Service Pack: 0_0

Produkt: 768_1

Betriebsystemversion: 10.0.17083.2.0.0.768.101

Gebietsschema-ID: 1031

Extra information about the problem

Bucket ID: 0x193_DxgkrnlLiveDump:804_Status_0xC000000D_WD_LOG,Caller:_DpiFdoStartAdapter,_Function:_DpiFdoConnectInterrupt,_Status:_0x%I64x_DpiFdoConnectInterrupt_failed_for_the_FDO._dxgkrnl!DxgCreateLiveDumpWithWdLogs

Server information: fd6c484d-5f46-477d-85ce-5d5396943c56

0 Kudos
DFink1
Beginner
1,794 Views

Hi, thank you for the two driver hyperlinks. I have tested both, but I have also problems with these drivers.

Driver 4905

Problemsignatur

Problemereignisame: LiveKernelEvent

Code: 187

Parameter 1: 1

Parameter 2: 0

Parameter 3: 0

Parameter 4: 0

Betriebssystemversion: 10_0_17083

Service Pack: 0_0

Produkt: 768_1

Betriebsystemversion: 10.0.17083.2.0.0.768.101

Gebietsschema-ID: 1031

Dateien zur Beschreibung des Problems

WATCHDOG-20180204-1913.dmp

sysdata.xml

WERInternalMetadata.xml

WERInternalRequest.xml

WPR_initiated_DiagTrackMiniLogger_One Trace User Logger_20180131 Event Collector_inject.etl

WPR_initiated_DiagTrackMiniLogger_One Trace User Logger_20180131 Event Collector.etl

memory.csv

sysinfo.txt

--------------------

Quelle

Windows

Zusammenfassung

Hardwarefehler

Datum

‎04.‎02.‎2018 19:13

Status

Der Bericht wurde gesendet.

Beschreibung

Aufgrund eines Hardwareproblems ist Windows nicht mehr voll funktionsfähig.

Problemsignatur

Problemereignisame: LiveKernelEvent

Code: 187

Parameter 1: 1

Parameter 2: 0

Parameter 3: 0

Parameter 4: 0

Betriebssystemversion: 10_0_17083

Service Pack: 0_0

Produkt: 768_1

Betriebsystemversion: 10.0.17083.2.0.0.768.101

Gebietsschema-ID: 1031

Weitere Informationen über das Problem

Bucket-ID: 0x187_dxgkrnl!DxgCreateLiveDumpWithWdLogs

Serverinformationen: 8e533a35-b69b-45a1-a0d5-61b245166f90

0 Kudos
DFink1
Beginner
1,794 Views

Driver 4911

Problemsignatur

Problemereignisame: LiveKernelEvent

Code: 187

Parameter 1: 1

Parameter 2: 0

Parameter 3: 0

Parameter 4: 0

Betriebssystemversion: 10_0_17083

Service Pack: 0_0

Produkt: 768_1

Betriebsystemversion: 10.0.17083.2.0.0.768.101

Gebietsschema-ID: 1031

Dateien zur Beschreibung des Problems

WATCHDOG-20180204-1831.dmp

sysdata.xml

WERInternalMetadata.xml

WERInternalRequest.xml

WPR_initiated_DiagTrackMiniLogger_One Trace User Logger_20180131 Event Collector_inject.etl

WPR_initiated_DiagTrackMiniLogger_One Trace User Logger_20180131 Event Collector.etl

memory.csv

sysinfo.txt

--------------------------------

Quelle

Windows

Zusammenfassung

Hardwarefehler

Datum

‎04.‎02.‎2018 18:31

Status

Der Bericht wurde gesendet.

Beschreibung

Aufgrund eines Hardwareproblems ist Windows nicht mehr voll funktionsfähig.

Problemsignatur

Problemereignisame: LiveKernelEvent

Code: 187

Parameter 1: 1

Parameter 2: 0

Parameter 3: 0

Parameter 4: 0

Betriebssystemversion: 10_0_17083

Service Pack: 0_0

Produkt: 768_1

Betriebsystemversion: 10.0.17083.2.0.0.768.101

Gebietsschema-ID: 1031

Weitere Informationen über das Problem

Bucket-ID: 0x187_dxgkrnl!DxgCreateLiveDumpWithWdLogs

Serverinformationen: e2706b9c-b534-4ab7-8ce8-ee793541957b

0 Kudos
Stefan3D
Honored Contributor II
1,794 Views

Normally i would have suggested a BIOS update now, but a web search exposes:

Version 2XCN34WW(V2.08)

Update Nvidia Formal VBIOS to 82.08.73.00.4A

That's odd, as you mentioned not to have a second GPU?

Otherwise upload a report from https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility Intel® System Support Utility for Windows* (enable incl. third party logs), so that an Intel support engineer can take a look at it.

0 Kudos
idata
Employee
1,794 Views

Hello MrX1980,

 

 

Thank you for contacting us.

 

 

Your thread captured my attention since I was able to notice that you have issues with our HD Graphics 620 that seems to display a 43 Error Code. Please accept our apologies for the inconvenience that this could be causing.

 

 

While checking on your case, we read that you already tried our latest generic graphics driver from Intel, Version 15.60.2.4901 (Latest) and the previous version (15.60.01.4877)

 

By doing some research on your machine and the system components on it, we found out that your machine (Lenovo Yoga 710-14IKB Type 80V4) might be missing drivers, that according to Lenovo's webpage, you'll be able to update here:

 

https://pcsupport.lenovo.com/us/en/products/LAPTOPS-AND-NETBOOKS/YOGA-SERIES/YOGA-710-14IKB/80V4/000GUS/downloads/DS118365 https://pcsupport.lenovo.com/us/en/products/LAPTOPS-AND-NETBOOKS/YOGA-SERIES/YOGA-710-14IKB/80V4/000GUS/downloads/DS118365

 

Please test them and monitor the outcome, since you already tried our drivers this might be an easy fix for your issue.

 

If the issue persists after installing Lenovo's drivers, the root of the issue could be caused from an Operating System Level. If that's the case please let us know so we can try to redirect you with the right group from Microsoft's Tech Support.

 

(You may need to copy and paste the links provided into a separate tab in case that you have issues when clicking on them)

 

 

 

Hope to hear from you soon.

 

 

Best regards,

 

Diego S.

 

0 Kudos
DFink1
Beginner
1,794 Views

Hello, thank you so far.

The (Intel) graphics driver 4836 from Lenovo / Windows Update (are the same) are working, but as far as I know they don't have the new HEVC optimizations of the newer drivers from you (Intel).

These optimizations was added after driver 4877 and before 4901. The last working driver from you (Intel) was 4849. All newer drivers have the Code 43 problem.

I hope that the error reports, that was automatically send to Microsoft, will help to identify the root cause for this and could be fixed soon. But this will be (sadly) after my holidays.

I have attached now the SSU log with driver 4901.

0 Kudos
idata
Employee
1,794 Views

Hello MrX1980 ,

 

Thank you for your patience.

 

I really appreciate your response and the report that you attached to the thread.

 

As you shared with us, yes, the HEVC optimizations of the newer drivers were added after driver 4877.

 

The last driver released, 4849 includes these optimizations, however depending on the system that is installing the driver, the error code may show up or not, due to the fact that these are only generic drivers.

 

On your specific case scenario since you have an OEM machine, I strongly suggest, as shared before, to get in touch with Lenovo support for the OEM drivers, or to ask if they are planning to release newer drivers fully optimized for your machine.

 

 

Hope this helps.

 

 

Best Regards,

 

Diego S.

 

0 Kudos
DFink1
Beginner
1,794 Views
0 Kudos
Reply