Intel HD Graphics driver fails to start after Windows 10 creators update

DSuvo · ‎02-10-2018

Hi there,

After installing creators update to Windows10 x64 pro Intel HD Graphics 4000 card stopped to work, system falled back to Microsoft basic driver. The symptoms are very similar to - playing with driver versions from Lenovo or Intel does not help.

Need to note, if secondary monitor is attached, it works until Windows login screen is shown, then driver fails.

Does anybody knows any workarounds available?

Details:

Category

Questions

Answers (N/A if not applicable)

Description

Provide a detailed description of the issue

driver crashes (see above)

Please place an X to the right of the option showing how often you see this issue using specific steps. (Ex: 'Every few times a game is started it flickers.' <- This would be "Often")

Always (100%):

Hardware (HW)

Brand and Model of the system.

Lenovo T430s 2356FW4, I5-3320M, HD Graphics 4000

Hybrid or switchable graphics system?

ie Does it have AMD or NV graphics too?

Only Intel HD Graphics 4000 in the system.

Make and model of any Displays that are used to see the issue (see note2 below).

LFP = Local Flat Panel (Laptop panel)

EFP = External Flat Panel (Monitor you plug in)

LFP, optionally secondary monitor connected via DP.

How much memory [RAM] in the system (see note2 below).

16GB

Provide any other hardware needed to replicate the issue.

ie: Cables&brand, cable type [vga, hdmi, DP, etc], dock, dongles/adapters, etcNA<p style="margin-bottom: .0001pt;...

Stefan3D · ‎02-10-2018

Looks like your BIOS is out-of-date

BIOS Version/Date:"LENOVO G7ETA1WW (2.61 ) , 01.09.2014 12:00"

2.69 Current release

...

CHANGES IN THIS RELEASE Version 2.63

[Important updates]

- Added support for Windows 10 64-bit.

source: https://pcsupport.lenovo.com/de/de/products/LAPTOPS-AND-NETBOOKS/THINKPAD-T-SERIES-LAPTOPS/THINKPAD-T430S/2356/downloads/DS029724 Products :: laptops and netbooks :: thinkpad t series laptops :: thinkpad t430s :: 2356 :: downloads :: ds029724 content…

If you need assistance on BIOS flashing, ask Lenovo support

DSuvo · ‎02-11-2018

Good catch! Flashed BIOS 2.69, but nothing changed.

Also tried driver recommended by Lenovo (10.18.10.4425). No effect as well.

Attached the ssu log.

DSuvo · ‎02-11-2018

No success with latest 10.18.10.4885 driver. ssu log attached.

Same error at the same offset 0x589f4 in dwm.exe.

# - <System>

<Channel>Application</Channel>

</System>

# - <EventData>

<<span ...

Stefan3D · ‎02-11-2018

Here is driver 9.17.10.4459 from Microsoft if you like to try

http://download.windowsupdate.com/d/msdownload/update/driver/drvs/2017/03/200042688_200a683c8b3223be5bf2e0ef0e147f2e1c945f2f.cab http://download.windowsupdate.com/d/msdownload/update/driver/drvs/2017/03/200042688_200a683c8b3223be5bf2e0ef0e147f2e1c94…

Install driver via have disk method as described at:

https://www.windowscentral.com/how-install-intel-beta-graphics-drivers-surface

(ignore prolog about MS surface, treat CAB like ZIP)

BTW the information from WER report is quite insufficient.

A crash dump from c:\Windows\LiveKernelReports\WATCHDOG\ contains some more infos for educated guessing.

DSuvo · ‎02-11-2018

Thanks! Attached a crash dump, though it seem to be winlogon.exe, not dwm.exe. Cannot find dwm dumps in the folder.

DSuvo · ‎02-11-2018

The Microsoft version of the driver (9.17.10.4459) does not help as well.

Collected the crash dump https://www.dropbox.com/s/655kc5bask3ligg/dwm.exe.6988.zip?dl=0 Dropbox - dwm.exe.6988.zip .

Stefan3D · ‎02-12-2018

Here is the info that's exposed by https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/index WINDBG.

Loading Dump File [C:\Temp\WATCHDOG-20180211-1910.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 16299 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0xfffff800`93606000 PsLoadedModuleList = 0xfffff800`9396cfd0

Debug session time: Sun Feb 11 17:10:46.324 2018 (UTC + 1:00)

System Uptime: 0 days 0:00:32.319

Loading Kernel Symbols

..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.

Run !sym noisy before .reload to track down problems loading symbols.

.............................................................

................................................................

............

Loading User Symbols

Mini Kernel Dump does not contain unloaded driver list

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 187, {1, 0, 0, 0}

Probably caused by : dxgkrnl.sys ( dxgkrnl!DxgCreateLiveDumpWithWdLogs+38 )

Followup: MachineOwner

---------

0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

VIDEO_DWMINIT_TIMEOUT_FALLBACK_BDD (187)

Video fell back to BDD rather than using the IHV driver. This always generates a live dump.

(This code can never be used for a real bugcheck.)

Arguments:

Arg1: 0000000000000001, Reason Code.

1 DWM failed to initialize after retries, stopping display adapters and falling back to BDD.

Arg2: 0000000000000000, Reserved.

Arg3: 0000000000000000, Reserved.

Arg4: 0000000000000000, Reserved.

Debugging Details:

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

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.16299.192 (WinBuild.160101.0800)

DUMP_TYPE: 2

BUGCHECK_P1: 1

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

CPU_COUNT: 4

CPU_MHZ: a22

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3a

CPU_STEPPING: 9

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x187

PROCESS_NAME: winlogon.exe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-AQALUL5

ANALYSIS_SESSION_TIME: 02-12-2018 07:53:15.0517

ANALYSIS_VERSION: 10.0.16299.91 amd64fre

LAST_CONTROL_TRANSFER: from fffff80c508ad38b to fffff80c508ad4ec

STACK_TEXT:

ffffd20e`17cfb470 fffff80c`508ad38b : ffffd20e`17cfbad0 00000000`00000000 ffffd20e`17cfbb80 00000000`00000040 : watchdog!WdDbgReportRecreate+0x10c

ffffd20e`17cfb4c0 fffff80c`50a82bd8 : 00000000`00000010 fffff80c`50a82ba0 00000000`00000010 00000000`00010246 : watchdog!WdDbgReportCreate+0x2b

ffffd20e`17cfb510 fffff80c`50a4cfc3 : ffffd481`ecb54010 ffffd20e`17cfbb80 ffffd20e`17cfbad0 00000000`00000040 : dxgkrnl!DxgCreateLiveDumpWithWdLogs+0x38

ffffd20e`17cfb550 ffffad9c`9842682c : ffff994c`a65327f8 00000000`00000000 ffffd20e`17cfbad0 ffff993f`fc002520 : dxgkrnl!DxgkEscape+0x7c783

ffffd20e`17cfba70 ffffad9c`98426735 : ffffd20e`17cfbad0 00007ff7`7428f670 00000000`00000000 00007ff8`00c17380 : win32kbase!DrvProcessWin32kEscape+0xec

ffffd20e`17cfbab0 fffff800`9378e203 : ffffd481`ed02c080 00000000`ffffffff ffffd481`ed02c080 00000000`00000001 : win32kbase!NtGdiDdDDIEscape+0x55

ffffd20e`17cfbb00 00007ff8`004a46e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

00000033`d038ebc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`004a46e4

THREAD_SHA1_HASH_MOD_FUNC: 842bc8efa4d42d35f554fad88dbff6e562284a49

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 6c29f80d2eec730cd39b148fdcfb03ac10f6938e

THREAD_SHA1_HASH_MOD: c2be3fde7438da7d82d82bf8a50391bfdf17fab5

FOLLOWUP_IP:

dxgkrnl!DxgCreateLiveDumpWithWdLogs+38

fffff80c`50a82bd8 488be8 mov rbp,rax

FAULT_INSTR_CODE: 48e88b48

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: dxgkrnl!DxgCreateLiveDumpWithWdLogs+38

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION: 10.0.16299.98

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 38

FAILURE_BUCKET_ID: 0x187_dxgkrnl!DxgCreateLiveDumpWithWdLogs

BUCKET_ID: 0x187_dxgkrnl!DxgCreateLiveDumpWithWdLogs

PRIMARY_PROBLEM_CLASS: 0x187_dxgkrnl!DxgCreateLiveDumpWithWdLogs

TARGET_TIME: 2018-02-11T16:10:46.000Z

OSBUILD: 16299

OSSERVICEPACK: 192

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0<...

DSuvo · ‎02-12-2018

Stefan, thanks! As expected, no much use of winlogon dump. Installed the windbg and here is the dwm. exe analysis - seem to be null pointer dereference:

*******************************************************************************

* *

* Exception Analysis *

* *

*******************************************************************************

GetUrlPageData2 (WinHttp) failed: 12002.

DUMP_CLASS: 2

DUMP_QUALIFIER: 400

CONTEXT: (.ecxr)

rax=0000000000000001 rbx=000000ac54afdf98 rcx=0000023371ce53d8

rdx=0000000000000000 rsi=0000023371a4d180 rdi=0000000000000000

rip=00007ff8c1fc6828 rsp=000000ac54afde10 rbp=0000000000000000

r8=000000ac54afdf98 r9=0000000000000000 r10=0000000000000000

r11=0000023371ce53d8 r12=00000233707f4860 r13=0000000000000000

r14=0000023371ce53d8 r15=0000023370834680

iopl=0 nv up ei pl zr na po nc

cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246

igd10umd64!OpenAdapter10+0xe768:

00007ff8`c1fc6828 488b4720 mov rax,qword ptr [rdi+20h] ds:00000000`00000020=????????????????

Resetting default scope

FAULTING_IP:

igd10umd64!OpenAdapter10+e768

00007ff8`c1fc6828 488b4720 mov rax,qword ptr [rdi+20h]

EXCEPTION_RECORD: (.exr -1)

ExceptionAddress: 00007ff8c1fc6828 (igd10umd64!OpenAdapter10+0x000000000000e768)

ExceptionCode: c0000005 (Access violation)

ExceptionFlags: 00000000

NumberParameters: 2

Parameter[0]: 0000000000000000

Parameter[1]: 0000000000000020

Attempt to read from address 0000000000000020

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_READ

PROCESS_NAME: dwm.exe

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000020

FOLLOWUP_IP:

igd10umd64!OpenAdapter10+e768

00007ff8`c1fc6828 488b4720 mov rax,qword ptr [rdi+20h]

READ_ADDRESS: 0000000000000020

WATSON_BKT_PROCSTAMP: 7f22d77c

WATSON_BKT_PROCVER: 10.0.16299.15

PROCESS_VER_PRODUCT: Microsoft® Windows® Operating System

WATSON_BKT_MODULE: igd10umd64.dll

WATSON_BKT_MODSTAMP: 573dfc81

WATSON_BKT_MODOFFSET: 266828

WATSON_BKT_MODVER: 9.17.10.4459

MODULE_VER_PRODUCT: Intel Graphics Accelerator Drivers for Windows 8(R)

BUILD_VERSION_STRING: 10.0.16299.15 (WinBuild.160101.0800)

MODLIST_WITH_TSCHKSUM_HASH: 896d94c0ba1113028dc5cb77bfcfaf6ef30b3159

MODLIST_SHA1_HASH: c41d85b66f8bc974f8376d444b781ca1f930be66

NTGLOBALFLAG: 0

APPLICATION_VERIFIER_FLAGS: 0

PRODUCT_TYPE: 1

SUITE_MASK: 272

DUMP_FLAGS: 8000c07

DUMP_TYPE: 3

ANALYSIS_SESSION_HOST: PC-001-00606

ANALYSIS_SESSION_TIME: 02-13-2018 08:15:40.0221

ANALYSIS_VERSION: 10.0.16299.15 x86fre

THREAD_ATTRIBUTES:

OS_LOCALE: RUS

PROBLEM_CLASSES:

ID: [0n301]

Type: [@ACCESS_VIOLATION]

Class: Addendum

Scope: BUCKET_ID

Name: Omit

Data: Omit

PID: [Unspecified]

TID: [0x1be8]

Frame: [0] : igd10umd64!OpenAdapter10

ID: [0n273]

Type: [INVALID_POINTER_READ]

Class: Primary

Scope: BUCKET_ID

Name: Add

Data: Omit

PID: [Unspecified]

TID: [0x1be8]

Frame: [0] : igd10umd64!OpenAdapter10

ID: [0n298]

Type: [NULL_CLASS_PTR_READ]

Class: Primary

Scope: DEFAULT_BUCKET_ID (Failure Bucket ID prefix)

BUCKET_ID

Name: Add

Data: Omit

PID: [0x1bc8]

TID: [0x1be8]

Frame: [0] : igd10umd64!OpenAdapter10

BUGCHECK_STR: APPLICATION_FAULT_NULL_CLASS_PTR_READ_INVALID_POINTER_READ

PRIMARY_PROBLEM_CLASS: APPLICATION_FAULT

LAST_CONTROL_TRANSFER: from 00007ff8c1fb94c3 to 00007ff8c1fc6828

STACK_TEXT:

000000ac`54afde10 00007ff8`c1fb94c3 : 000000ac`00000000 00007ff8`c1fd009c 00000233`71a4d180 00000000`00000000 : igd10umd64!OpenAdapter10+0xe768

000000ac`54afded0 00007ff8`c29de2b8 : 00000233`71a570a8 00000233`6eb858a8 00000233`6eb85760 00000233`71ce6d3c : igd10umd64!OpenAdapter10+0x1403

000000ac`54afdf10 00007ff8`c758cb31 : 3f800000`00000000 00000000`00000000 00000032`00000032 3f800000`00000000 : mctux!OpenAdapter+0x1158

000000ac`54afdf40 00007ff8`c776f6e7 : 00000000`00000000 00000233`70821130 000000ac`54afe1a0 00007ff8`c29e026e : d3d11!CContext::TID3D11DeviceContext_ClearRenderTargetView_<1>+0x121

000000ac`54afdff0 00007ff8`c7771023 : 00000233`70823640 000000ac`00000000 00000233`70823a60 000000ac`54afe1a0 : d2d1!CD3DDeviceLevel1::ClearView+0x14f

000000ac`54afe0a0 00007ff8`c77a2b9c : 00000000`00000000 00000233`70838d68 00000000`00000003 00000000`00000000 : d2d1!CD3DDeviceLevel1::ProcessDeferredOperations+0x913

000000ac`54afe3a0 00007ff8`c77a34dd : 00000233`7083e5c8 00000000`00000000 00000233`707f8ee0 000000ac`54afe800 : d2d1!CHwSurfaceRenderTarget::FlushQueuedOperations+0x3ac

000000ac`54afe6b0 00007ff8`c77be74f : 00000000`ffffffff 00000000`00000000 00000233`71aaf3a0 00000233`717f9700 : d2d1!CHwSurfaceRenderTarget::ProcessBatch+0x1ad

000000ac`54afe760 00007ff8`c77ba00e : 00000233`71a8eb00 00000233`71a8ebb0 000000ac`54afe9d0 00000000`00000000 : d2d1!CBatchSerializer::FlushInternal+0x13f

000000ac`54afe7f0 00007ff8`c77b139b : 00000233`707f4880 000000ac`54afe929 00000233`7083e190 00000000`00000000 : d2d1!DrawingContext::Flush+0x96

000000ac`54afe850 00007ff8`c7f42dd4 : 00000000`00000000 00000233`71a61480 00000000`00000008 00000233`71a61480 : d2d1!D2DDeviceContextBase::EndDraw+0x13b

000000ac`54afe990 00007ff8`c7f38cf3 : 00000000`00000000 00000233`71aaf3a0 00000000`c6fa3c00 00000000`00000008 : dwmcore!CD2DContext::PopTarget+0x94

000000ac`54afe9e0 00007ff8`c7f03a28 : 00000000`00000000 00000000`00000000 000000ac`54afeb40 000000ac`54afec30 : dwmcore!CDrawingContext::EndFrame+0x333

000000ac`54afea40 00007ff8`c7efb8f8 : 00000000`00010001 00000000`00010001 00000233`00010001 00000000`00010001 : dwmcore!CCachedVisualImage::RenderTargetBitmapInfo::Update+0x3cc

000000ac`54afebd0 00007ff8`c7efc05d : 000000ac`54afee30 00000233`717f9440 00000000`00000000 00000000`00000000 : dwmcore!CCachedVisualImage::EnsureRenderTargetBitmapInfo+0x1b4

000000ac`54afecb0 00007ff8`c7efbb7e : 00000233`717f9350 00000000`00000000 00000000`00000000 00000000`0000000...

idata · ‎02-22-2018

Hello Denisss

I am reviewing your case I am seeing that you have tried have tried to install the graphics drivers from Intel® which in your system will be the generic drivers, also I see the windows driver did not help to solve the problem, seems that we can try looking into Lenovo to assist on this case, I was doing research on the problem and I was able to spot on the following link the list of tested Lenovo systems for the Operating system (OS) that you are using

https://support.lenovo.com/cr/en/solutions/ht505322 https://support.lenovo.com/cr/en/solutions/ht505322

I was not able to find your system on the tested Lenovo devices for Windows® 10 fall creators, on the other hand, you can contact the manufacturer for them to replicate your situation.

Regards

Leonardo C.

DSuvo · ‎02-23-2018

Hello Leonardo,

Thank you for pointing to the list of possible migration issues found by Lenovo testing. However I have tried the Lenovo set of Windows 10 graphics drivers as well with the same results and I do not see similar cases in their reports.

Looking into the stack trace I do not see any vendor-specific components, but Microsoft DirectX and Intel driver calls only. Therefore I do not see how Lenovo can effectively help me with troubleshooting of this issue.

So I would greatly appreciate if you provide code analysis results based on the crash dump attached. I am ready to reproduce the issue with debug libraries if more precise information needed and the libraries provided to me.

Thank you!

idata · ‎02-26-2018

Hello Denisss

Thank you for your response

On the thread that you have made reference to on the original post (/thread/120734 https://communities.intel.com/thread/120734) the customer had graphics problems after the Operating System (OS) update, in that case, it was due to of incomparability with the component StarTech USB-HDMI that need it a driver updated, just to verify on your scenario are you using any hub on docking station? Besides the corruption on the screen that you provide in the picture are you having any error codes once the drivers are installed? Do you have the same display corruption with Microsoft basic driver?

Regards

Leonardo C.

DSuvo · ‎02-27-2018

Hello Leonardo,

No usb devices are connected, this is laptop screen. I have not seen any driver install errors and Microsoft driver works fine.

In the referenced thread the callstack in the crash dump pointed to the StarTech driver calls. In my case no obvious reason, only Microsoft and Intel libraries are involved.

Intel igd10umd64!OpenAdapter crashes trying to dereference null pointer

Looking at the source code may help understanding what object had been passed as null, and why this was not expected by the driver.

idata · ‎02-27-2018

Hello Denisss

Thank you for your response and for the information provided.

Allowed to investigate more on your specific scenario, we will be posting back when news becomes available.

Regards,

Leonardo C.

DSuvo · ‎02-28-2018

Leonardo_intel, thank you!

Looking forward for good news.

idata · ‎03-02-2018

Hello Denisss

Thank you for waiting, allowed me to share with you that we were able to perform a lab with the same graphics controller using the following hardware/software:

Lenovo x230 tablet laptop.
HD graphics 4000.
Windows® 10 (64 bit) fall creators update (clean installation).
Windows updates completed.
Graphics driver version:
- 10.18.0010.4252.
- 10.18.0010.4885.

With both driver versions, we did not have any display problem (see picture attach).

At this moment the best option would be contacting Lenovo* to see if they can replicate the issue with the exact same system you have in their lab.

Regards,

Leonardo C.

DSuvo · ‎03-03-2018

Hello Leonardo_intel, thank you for trying to help!

As there is no other option, I have run the Windows clean install and the issue gone away.

Best Regards,

-Denis.