Win8 x86 Intel HD Graphics Driver BSOD, version 10.18.10.3345 (Win32_15338)

DStev4 · ‎01-06-2014

Hi, we occasionally ran into BSOD with the Intel HD Graphics driver, version 10.18.10.3345.

CPU: i3-3220

Chipset: B75M

OS: Win8 x86

Below is analysis log of kernel dump in WinDbg.

Symbol search path is: srv*E:\SymbolCache*E:\Symbols*\\rdsrv\symbols*http://msdl.microsoft.com/download/symbols http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows 8 Kernel Version 9200 MP (4 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 9200.16384.x86fre.win8_rtm.120725-1247

Machine Name:

Kernel base = 0x81270000 PsLoadedModuleList = 0x8145ade8

Debug session time: Tue Jan 7 10:21:31.540 2014 (UTC + 8:00)

System Uptime: 0 days 0:00:52.210

WARNING: Process directory table base CED4E480 doesn't match CR3 00185000

Loading Kernel Symbols

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

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

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

Loading User Symbols

PEB is paged out (Peb.Ldr = 7f24f00c). Type ".hh dbgerr001" for details

Loading unloaded module list

.........

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80fb9000, 0, 0}

*** ERROR: Symbol file could not be found. Defaulted to export symbols for igdkmd32.sys -

Probably caused by : igdkmd32.sys ( igdkmd32!hybDriverEntry+63977 )

Followup: MachineOwner

---------

0: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)

This means a trap occurred in kernel mode, and it's a trap of a kind

that the kernel isn't allowed to have/catch (bound trap) or that

is always instant death (double fault). The first number in the

bugcheck params is the number of the trap (8 = double fault, etc)

Consult an Intel x86 family manual to learn more about what these

traps are. Here is a *portion* of those codes:

If kv shows a taskGate

use .tss on the part before the colon, then kv.

Else if kv shows a trapframe

use .trap on that value

Else

.trap on the appropriate frame will show where the trap was taken

(on x86, this will be the ebp that goes with the procedure KiTrap)

Endif

kb will then show the corrected stack.

Arguments:

Arg1: 00000008, EXCEPTION_DOUBLE_FAULT

Arg2: 80fb9000

Arg3: 00000000

Arg4: 00000000

Debugging Details:

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

BUGCHECK_STR: 0x7f_8

TSS: 00000028 -- (.tss 0x28)

eax=b786d138 ebx=b786d500 ecx=000701ac edx=8822a000 esi=882a8234 edi=c0000001

eip=8dcc27e7 esp=b786cffc ebp=b786d120 iopl=0 nv up ei pl zr na pe nc

cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246

igdkmd32!hybDriverEntry+0x63977:

8dcc27e7 56 push esi

Resetting default scope

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 9

EXCEPTION_RECORD: 9295c2c0 -- (.exr 0xffffffff9295c2c0)

ExceptionAddress: 81345d51 (nt!KiInterruptMessageDispatch)

ExceptionCode: 02a00016

ExceptionFlags: 9295c2c4

NumberParameters: -1933483778

Parameter[0]: 00000000

Parameter[1]: 8d075020

Parameter[2]: 00000000

Parameter[3]: ffffffff

Parameter[4]: 85faf280

Parameter[5]: 813df400

Parameter[6]: 000000a2

Parameter[7]: 01000909

Parameter[8]: 00000000

Parameter[9]: 00000001

Parameter[10]: 00000000

Parameter[11]: 00000001

Parameter[12]: 00000000

Parameter[13]: 00000000

Parameter[14]: ffffffff

TRAP_FRAME: b786dbcc -- (.trap 0xffffffffb786dbcc)

ErrCode = 00000000

eax=006f0068 ebx=00000000 ecx=0000000e edx=aaa8ddec esi=aab33b8c edi=00000004

eip=8136bbcd esp=b786dc40 ebp=b786dc4c iopl=0 nv up ei pl nz na pe nc

cs=0008 ss=0010 ds=dc4c es=dccc fs=0010 gs=0004 efl=00000206

nt!memcmp+0x16:

8136bbcd 8b02 mov eax,dword ptr [edx] ds:dc4c:ddec=????????

Resetting default scope

LAST_CONTROL_TRANSFER: from 8dc5fb3c to 8dcc27e7

STACK_TEXT:

WARNING: Stack unwind information not available. Following frames may be wrong.

b786d120 8dc5fb3c 8822a000 000701ac b786d138 igdkmd32!hybDriverEntry+0x63977

b786d13c 8dd9047b 8822a000 000701ac b786d1f4 igdkmd32!hybDriverEntry+0xccc

b786d150 8de235a0 882a8234 b786d170 8ddd29ec igdkmd32!hybDriverEntry+0x13160b

b786d15c 8ddd29ec 882a8008 b786d1f4 8828e000 igdkmd32!hybDriverEntry+0x1c4730

b786d170 8dc4214a 8829c000 b786d1f4 8822f624 igdkmd32!hybDriverEntry+0x173b7c

b786d204 8dd094bf 8822a000 b786d94c 8822a000 igdkmd32+0x2c14a

b786dab4 8dd09add 8822a000 00000000 b786db18 igdkmd32!hybDriverEntry+0xaa64f

b786dac4 8dcbc40f 8822a000 b786db40 b786db74 igdkmd32!hybDriverEntry+0xaac6d

b786db18 8dc37cd3 8822a000 00000000 00000000 igdkmd32!hybDriverEntry+0x5d59f

b786db78 8cc1612a 8822a000 00000000 b786dc4c igdkmd32+0x21cd3

b786db8c 81345d63 9295c2c0 8d075020 00000000 dxgkrnl!DpiFdoMessageInterruptRoutine+0x2c

b786dba0 813df46d 9295c2c0 8d075020 b786dbcc nt!KiInterruptMessageDispatch+0x12

b786dba0 8136bbcd 9295c2c0 8d075020 b786dbcc nt!KiInterruptDispatch+0x6d

b786dc4c 8617dca0 aaa8dd90 aab33b30 0000006a nt!memcmp+0x16

b786dc90 8617e5cd 00000000 b786dccc 0000000c NETIO!MatchValues+0x151

b786dcf0 8617b76d a42fb938 b786e22c 8aba75f8 NETIO!IndexHashClassify+0x25c

b786df20 8228f757 0000002e b786e22c 8aba75f8 NETIO!KfdClassify+0x25d

b786e170 82298668 b786e22c 00000000 b786e1c7 tcpip!WfpAleClassify+0x50

b786e344 82299268 ab51ae28 0000002e 00000017 tcpip!WfpAlepAuthorizeReceive+0xd4f

b786e564 8228ea5d 00000017 00000011 88662d10 tcpip!WfpAleAuthorizeReceive+0x320

b786e65c 82294551 00000011 00000017 00006c07 tcpip!ProcessALEForTransportPacket+0x2d6

b786ea5c 822954bd 00000017 00006c07 00003dcc tcpip!WfpProcessInTransportStackIndication+0xb5e

b786ead8 822960b7 ab51ae28 00000017 00006c07 tcpip!InetInspectReceiveD...

Allan_J_Intel1 · ‎01-07-2014

I am sorry to hear that you had issues with the latest video drivers.

Does this problem occur with previous driver version 9.18.10.3257?

https://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Graphics&ProductLine=Laptop+graphics+drivers&ProductProduct=3rd+Generation+Intel%C2%AE+Core%E2%84%A2+Processors+with+Intel%C2%AE+HD+Graphics+2500&ProdId=3711&LineId=1101&FamilyId=39 https://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Graphics&ProductLine=Laptop+graphics+drivers&ProductProduct=3rd+Generation+Intel%C2%AE+Core%E2%84%A2+Processors+with+Intel%C2%AE+HD+Graphics+2500&ProdId=3711&LineId=1101&FamilyId=39

Does it continue with Original Equipment Manufacturer (OEM) drivers?

Allan.

DStev4 · ‎01-09-2014

Dear Allan, this BSOD happens very rare. It's hard to reproduce.