topic Re: Intel display driver stopped responding and has recovered. in Graphics

Intel display driver stopped responding and has recovered.

RFedo — Sun, 09 Mar 2014 12:08:58 GMT

Hello,

I just bought FIFA 13 for my computer and when I try to play it, it freezes after every 10 seconds and says that Intel display driver has stopped working and has recovered. I can play it for max 2 min then my computer crashes. Can somebody help me with this, because I would really like to play FIFA.

Re: Intel display driver stopped responding and has recovered.

Kevin_M_Intel — Mon, 10 Mar 2014 14:51:57 GMT

Hi Ringo,

I am sorry you are having problems to play your game but let me help you that.

There are many steps we can do but at this point I am not sure about what is the graphics controller in your system so, can you post your dxdiag report and the graphics report here?

How to get it?

Dxdiag Report: Type dxdiag in Start Menu> open> Save> Copy/Paste here.

Graphics Report: Right click on desktop> Graphics Properties> Options> Drop Down Menu> Information Center> Save> Open .txt file created> Copy/Paste here.

Re: Intel display driver stopped responding and has recovered.

RFedo — Sat, 15 Mar 2014 14:46:47 GMT

Hey, here is the DxDiag report:

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

System Information

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

Time of this report: 3/15/2014, 16:41:54

Machine name: RINGO-PC

Operating System: Windows 7 Professional 64-bit (6.1, Build 7600) (7600.win7_gdr.130318-1532)

Language: Estonian (Regional Setting: Estonian)

System Manufacturer: Hewlett-Packard

System Model: HP Pro 3130 Microtower PC

BIOS: 03/18/11 21:07:57 Ver: 6.16

Processor: Intel(R) Core(TM) i3 CPU 550 @ 3.20GHz (4 CPUs), ~3.2GHz

Memory: 2048MB RAM

Available OS Memory: 1784MB RAM

Page File: 2289MB used, 2167MB available

Windows Dir: C:\Windows

DirectX Version: DirectX 11

DX Setup Parameters: Not found

User DPI Setting: Using System DPI

System DPI Setting: 96 DPI (100 percent)

DWM DPI Scaling: Disabled

DxDiag Version: 6.01.7600.16385 32bit Unicode

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

DxDiag Notes

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

Display Tab 1: No problems found.

Sound Tab 1: No problems found.

Sound Tab 2: No problems found.

Input Tab: No problems found.

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

DirectX Debug Levels

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

Direct3D: 0/4 (retail)

DirectDraw: 0/4 (retail)

DirectInput: 0/5 (retail)

DirectMusic: 0/5 (retail)

DirectPlay: 0/9 (retail)

DirectSound: 0/5 (retail)

DirectShow: 0/6 (retail)

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

Display Devices

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

Card name: Intel(R) HD Graphics

Manufacturer: Intel Corporation

Chip type: Intel(R) HD Graphics (Core i3)

DAC type: Internal

Device Key: Enum\PCI\VEN_8086&DEV_0042&SUBSYS_2A9C103C&REV_18

Display Memory: 763 MB

Dedicated Memory: 128 MB

Shared Memory: 635 MB

Current Mode: 1280 x 1024 (32 bit) (60Hz)

Monitor Name: Generic PnP Monitor

Monitor Model: L1954

Monitor Id: GSM4B64

Native Mode: 1280 x 1024(p) (60.020Hz)

Output Type: HD15

Driver Name: igdumd64.dll,igd10umd64.dll,igdumdx32,igd10umd32

Driver File Version: 8.15.0010.2119 (English)

Driver Version: 8.15.10.2119

DDI Version: 10

Driver Model: WDDM 1.1

Driver Attributes: Final Retail

Driver Date/Size: 4/21/2010 18:18:40, 6534144 bytes

WHQL Logo'd: Yes

WHQL Date Stamp:

Device Identifier: {D7B78E66-4302-11CF-CB7B-960AB8C2C535}

Vendor ID: 0x8086

Device ID: 0x0042

SubSys ID: 0x2A9C103C

Revision ID: 0x0018

Driver Strong Name: oem2.inf:Intel.Mfg.NTamd64:iILKD0:8.15.10.2119:pci\ven_8086&dev_0042&subsys_2a9c103c

Rank Of Driver: 00E60001

Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_B ModeWMV9_C ModeVC1_B ModeVC1_C

Deinterlace Caps: {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVert...

Re: Intel display driver stopped responding and has recovered.

Kevin_M_Intel — Tue, 18 Mar 2014 18:42:34 GMT

Hi ringo,

Thanks for the information.

I would like you to update the drivers for your graphics controller. Here you have the latest one:

https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=22521 https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=22521

If you get a notification message during the installation, it indicates that your computer manufacturer does not allow the installation of generic Intel video drives. You are required to install drivers from your computer manufacturer.

You may try to force the installation of Intel generic drivers by performing manual procedure, see here for instructions:

http://support.intel.com/support/graphics/sb/CS-022355.htm http://support.intel.com/support/graphics/sb/CS-022355.htm

Here is the zip version of the video driver:

https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=22521 https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=22521

Re: Intel display driver stopped responding and has recovered.

RFedo — Wed, 19 Mar 2014 07:26:33 GMT

I cant seem to install it automatically, but if i try to install it manually it says that the latest drivers are already installed, i followed the steps that were given.

Re: Intel display driver stopped responding and has recovered.

Kevin_M_Intel — Fri, 21 Mar 2014 16:35:50 GMT

I am sorry you are still having problems. At this point, since your system seems not to accept our generic driver I recommend you contacting HP for them to provide the drivers designed specifically for your unit.

Here you have their support information:

http://www8.hp.com/us/en/drivers.html http://www8.hp.com/us/en/drivers.html

Re: Intel display driver stopped responding and has recovered.

DDimi5 — Tue, 25 Mar 2014 23:14:44 GMT

Hello i have the same problem with Acer aspire one D270 Netbook.

It happens every time im watchin youtube, while changing videos automaticly (in mix or playlist)

I updated my bios, video drivers and the chipset drivers.

Here is the dxdiag i hope kevin can help me

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

System Information

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

Time of this report: 3/26/2014, 00:46:20

Machine name: MIGLENA-PC

Operating System: Windows 7 Ultimate 32-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130828-1532)

Language: Bulgarian (Regional Setting: Bulgarian)

System Manufacturer: Acer

System Model: AOD270

BIOS: InsydeH2O Version CCB.03.61.31V1.10

Processor: Intel(R) Atom(TM) CPU N2600 @ 1.60GHz (4 CPUs), ~1.6GHz

Memory: 2048MB RAM

Available OS Memory: 2036MB RAM

Page File: 1081MB used, 2991MB available

Windows Dir: C:\Windows

DirectX Version: DirectX 11

DX Setup Parameters: Not found

User DPI Setting: Using System DPI

System DPI Setting: 96 DPI (100 percent)

DWM DPI Scaling: Disabled

DxDiag Version: 6.01.7601.17514 32bit Unicode

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

DxDiag Notes

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

Display Tab 1: No problems found.

Sound Tab 1: No problems found.

Input Tab: No problems found.

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

DirectX Debug Levels

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

Direct3D: 0/4 (retail)

DirectDraw: 0/4 (retail)

DirectInput: 0/5 (retail)

DirectMusic: 0/5 (retail)

DirectPlay: 0/9 (retail)

DirectSound: 0/5 (retail)

DirectShow: 0/6 (retail)

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

Display Devices

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

Card name: Intel(R) Graphics Media Accelerator 3600 Series

Manufacturer: Intel Corporation

Chip type: Intel(R) GMA 3600 Series (Atom N2600)

DAC type: Internal

Device Key: Enum\PCI\VEN_8086&DEV_0BE1&SUBSYS_061F1025&REV_09

Display Memory: 762 MB

Dedicated Memory: 0 MB

Shared Memory: 762 MB

Current Mode: 1024 x 600 (32 bit) (60Hz)

Monitor Name: Digital Flat Panel (640x480 60Hz)

Monitor Model: unknown

Monitor Id: MS_0001

Native Mode: 1024 x 600(p) (60.041Hz)

Output Type: Internal

Driver Name: igdumd32.dll

Driver File Version: 8.14.0008.1096 (English)

Driver Version: 8.14.8.1096

DDI Version: 9Ex

Driver Model: WDDM 1.1

Driver Attributes: Final Retail

Driver Date/Size: 11/4/2013 15:48:16, 1100800 bytes

WHQL Logo'd: n/a

WHQL Date Stamp: n/a

Device Identifier: {D7B78E66-48A1-11CF-DD77-1726A8C2C535}

Vendor ID: 0x8086

Device ID: 0x0BE1

SubSys ID: 0x061F1025

Revision ID: 0x0009

Driver Strong Name: oem5.inf:Intel.Mfg:iCNT0:8.14.8.1096:pci\ven_8086&dev_0be1

Rank Of Driver: 00E62001

Video Accel: ModeMPEG2_A ModeMPEG2_C

Deinterlace Caps: {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,X8R8G8B8) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,X8R8G8B8) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,X8R8G8B8) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,X8R8G8B8) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,X8R8G8B8) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,X8R8G8B8) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,X8R8G8B8) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,X8R8G8B8) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,X8R8G8B8) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,X8R8G8B8) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,X8R8G8B8) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,X8R8G8B8) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,X8R8G8B8) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,X8R8G8B8) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,X8R8G8B8) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,X8R8G8B8) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,X8R8G8B8) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,X8R8G8B8) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,X8R8G8B8) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S34...

Re: Intel display driver stopped responding and has recovered.

Kevin_M_Intel — Wed, 26 Mar 2014 15:57:04 GMT

Hi Logical,

I recommend you updating the BIOS and the Management Engine driver provided by the Computer Manufacture. You can also try reinstalling the driver in your system. Here is the latest driver we have:

https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=3468&DwnldID=23473 https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=3468&DwnldID=23473

Re: Intel display driver stopped responding and has recovered.

LD2 — Thu, 03 Apr 2014 01:22:48 GMT

My computer is having the same issue, I am hoping you can tell me what I need to do to fix it.

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

System Information

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

Time of this report: 4/2/2014, 11:19:59

Machine name: POGS-PC

Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130828-1532)

Language: English (Regional Setting: English)

System Manufacturer: Hewlett-Packard

System Model: Compaq Presario A900 Notebook PC

BIOS: Default System BIOS

Processor: Intel(R) Pentium(R) Dual CPU T2390 @ 1.86GHz (2 CPUs), ~1.9GHz

Memory: 3072MB RAM

Available OS Memory: 3062MB RAM

Page File: 1997MB used, 4125MB available

Windows Dir: C:\Windows

DirectX Version: DirectX 11

DX Setup Parameters: Not found

User DPI Setting: Using System DPI

System DPI Setting: 96 DPI (100 percent)

DWM DPI Scaling: Disabled

DxDiag Version: 6.01.7601.17514 32bit Unicode

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

DxDiag Notes

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

Display Tab 1: No problems found.

Sound Tab 1: No problems found.

Input Tab: No problems found.

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

DirectX Debug Levels

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

Direct3D: 0/4 (retail)

DirectDraw: 0/4 (retail)

DirectInput: 0/5 (retail)

DirectMusic: 0/5 (retail)

DirectPlay: 0/9 (retail)

DirectSound: 0/5 (retail)

DirectShow: 0/6 (retail)

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

Display Devices

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

Card name: Mobile Intel(R) 965 Express Chipset Family

Manufacturer: Intel Corporation

Chip type: Mobile Intel(R) 965 Express Chipset Family

DAC type: Internal

Device Key: Enum\PCI\VEN_8086&DEV_2A02&SUBSYS_30D9103C&REV_03

Display Memory: 358 MB

Dedicated Memory: 0 MB

Shared Memory: 358 MB

Current Mode: 1440 x 900 (32 bit) (60Hz)

Monitor Name: Generic PnP Monitor

Monitor Model: unknown

Monitor Id: AUO6287

Native Mode: 1440 x 900(p) (59.996Hz)

Output Type: Internal

Driver Name: igdumd64.dll,igd10umd64.dll,igdumdx32,igd10umd32

Driver File Version: 8.14.0010.1930 (English)

Driver Version: 8.15.10.1930

DDI Version: 10

Driver Model: WDDM 1.1

Driver Attributes: Final Retail

Driver Date/Size: 9/23/2009 19:22:58, 5472256 bytes

WHQL Logo'd: Yes

WHQL Date Stamp:

Device Identifier: {D7B78E66-6942-11CF-0674-D310A2C2C535}

Vendor ID: 0x8086

Device ID: 0x2A02

SubSys ID: 0x30D9103C

Revision ID: 0x0003

Driver Strong Name: oem4.inf:Intel.Mfg.NTamd64:i965GM0:8.15.10.1930:pci\ven_8086&dev_2a02

Rank Of Driver: 00EC2001

Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_B ModeVC1_B

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProc...

Re: Intel display driver stopped responding and has recovered.

MFalk1 — Mon, 14 Apr 2014 11:22:58 GMT

I tried to look into the igddim32.sys. I tried to figure out, why I cannot disable the HotPlug, so, if the driver really reads the HotPlug_DVO_SDVO, HotPlug_CRT and INF_VBT_Override_EnableFeature registry entries. I found these things:

10047D90 55 PUSH EBP

10047D91 8BEC MOV EBP,ESP

10047D93 83EC 10 SUB ESP,10

10047D96 E8 F5670100 CALL igddim32.1005E590

10047D9B 8945 F4 MOV DWORD PTR SS:[EBP-C],EAX

10047D9E C745 FC 00000000 MOV DWORD PTR SS:[EBP-4],0

10047DA5 C645 FB 00 MOV BYTE PTR SS:[EBP-5],0

10047DA9 C645 F3 00 MOV BYTE PTR SS:[EBP-D],0

10047DAD 837D F4 00 CMP DWORD PTR SS:[EBP-C],0

10047DB1 74 29 JE SHORT igddim32.10047DDC

10047DB3 8D45 FC LEA EAX,DWORD PTR SS:[EBP-4]

10047DB6 50 PUSH EAX

10047DB7 6A 04 PUSH 4

10047DB9 68 0CC51210 PUSH igddim32.1012C50C ; UNICODE "INF_VBT_Override_EnableFeature"

10047DBE 8B4D F4 MOV ECX,DWORD PTR SS:[EBP-C]

10047DC1 51 PUSH ECX

10047DC2 8B55 F4 MOV EDX,DWORD PTR SS:[EBP-C]

10047DC5 8B42 04 MOV EAX,DWORD PTR DS:[EDX+4]

10047DC8 FFD0 CALL EAX

10047DCA 0FB6C8 MOVZX ECX,AL

10047DCD 83F9 01 CMP ECX,1

10047DD0 75 0A JNZ SHORT igddim32.10047DDC

10047DD2 837D FC 00 CMP DWORD PTR SS:[EBP-4],0

10047DD6 76 04 JBE SHORT igddim32.10047DDC

10047DD8 C645 F3 01 MOV BYTE PTR SS:[EBP-D],1

10047DDC 0FB655 F3 MOVZX EDX,BYTE PTR SS:[EBP-D]

10047DE0 85D2 TEST EDX,EDX

10047DE2 0F84 4B020000 JE igddim32.10048033

... Lots of things ...

10047FA0 8D45 FC LEA EAX,DWORD PTR SS:[EBP-4]

10047FA3 50 PUSH EAX

10047FA4 6A 04 PUSH 4

10047FA6 68 10C71210 PUSH igddim32.1012C710 ; UNICODE "HotPlug_DVO_SDVO"

10047FAB 8B4D F4 MOV ECX,DWORD PTR SS:[EBP-C]

10047FAE 51 PUSH ECX

10047FAF 8B55 F4 MOV EDX,DWORD PTR SS:[EBP-C]

10047FB2 8B42 04 MOV EAX,DWORD PTR DS:[EDX+4]

10047FB5 FFD0 CALL EAX

10047FB7 0FB6C8 MOVZX ECX,AL

10047FBA 83F9 01 CMP ECX,1

10047FBD 75 26 JNZ SHORT igddim32.10047FE5

10047FBF 837D FC 02 CMP DWORD PTR SS:[EBP-4],2

10047FC3 73 20 JNB SHORT igddim32.10047FE5

10047FC5 8A55 FC MOV DL,BYTE PTR SS:[EBP-4]

10047FC8 80E2 01 AND DL,1

10047FCB C0E2 03 SHL DL,3

10047FCE 8B45 08 MOV EAX,DWORD PTR SS:[EBP+8]

10047FD1 8A88 80000000 MOV CL,BYTE PTR DS:[EAX+80]

10047FD7 80E1 F7 AND CL,0F7

10047FDA 0ACA OR CL,DL

10047FDC 8B55 08 MOV EDX,DWORD PTR SS:[EBP+8]

10047FDF 888A 80000000 MOV BYTE PTR DS:[EDX+80],CL

10047FE5 8D45 FC LEA EAX,DWORD PTR SS:[EBP-4]

10047FE8 50 PUSH EAX

10047FE9 6A 04 PUSH 4

10047FEB 68 34C71210 PUSH igddim32.1012C734 ; UNICODE "HotPlug_CRT"

10047FF0 8B4D F4 MOV ECX,DWORD PTR SS:[EBP-C]

10047FF3 51 PUSH ECX

10047FF4 8B55 F4 MOV EDX,DWORD PTR SS:[EBP-C]

10047FF7 8B42 04 MOV EAX,DWORD PTR DS:[EDX+4]

10047FFA FFD0 CALL EAX

10047FFC 0FB6C8 MOVZX ECX,AL

10047FFF 83F9 01 CMP ECX,1

10048002 75 2F JNZ SHORT igddim32.10048033

10048004 837D FC 02 CMP DWORD PTR SS:[EBP-4],2

10048008 73 29 JNB SHORT igddim32.10048033

1004800A 66:0FB655 FC MOVZX DX,BYTE PTR SS:[EBP-4]

1004800F 66:83E2 01 AND DX,1

10048013 66:C1E2 0A SHL DX,0A

10048017 B8 FFFB0000 MOV EAX,0FBFF

1004801C 8B4D 08 MOV ECX,DWORD PTR SS:[EBP+8]

1004801F 66:2381 87000000 AND AX,WORD PTR DS:[ECX+87]

10048026 66:0BC2 OR AX,DX

10048029 8B55 08 MOV EDX,DWORD PTR SS:[EBP+8]

1004802C 66:8982 87000000 MOV WORD PTR DS:[EDX+87],AX

10048033 B0 01 MOV AL,1

10048035 8BE5 MOV ESP,EBP

10048037 5D POP EBP

10048038 C2 0400 RETN 4

I tried to make break point into this area, but OllyDbg never stopped. I would like to ask, if this area never executed, or, because this area executed at the initalisation of the Kernel Driver (igddim32.sys), and than the OllyDbg is not active yet?

I would like to ask an Intel Engineer to please respond to this entry.

Re: Intel display driver stopped responding and has recovered.

MFalk1 — Mon, 14 Apr 2014 11:50:38 GMT

Is it possible, that I was not able to set break point, because igddim32.sys runs as a 0 ring program, and OllyDbg runs as a 3 ring program? I am on the user level (3) in the OllyDbg and the igddim32.sys is in the system level (0) so I cannot see what happening there? Is it the reason?

Should I use Visual SoftIce instead of OllyDbg? Is it the problem?

Re: Intel display driver stopped responding and has recovered.

Kevin_M_Intel — Tue, 15 Apr 2014 16:24:04 GMT

Hi MTRAP,

I am sorry but this thread is related to a different issue. I recommend you posting your question related to development at the following link:

https://software.intel.com/ https://software.intel.com/

Re: Intel display driver stopped responding and has recovered.

DBitn — Thu, 17 Apr 2014 20:59:10 GMT

Guys could you point me where to complain about this Intel HD crash issue? I wrote to intel support about 3 weeks ago, and got only automatic reply kind of "we will look into the problem and reply to you shortly". But I still didn't get any replies. The problem is that when I play Half Life 2 episode Two, I have flying textures

The problem is semi persistent. Sometimes I have it sometimes I don't. It also happens that some textures become white or purple. And in this game scene also it constantly crashes in the train when you look up. The message in notification area says "Driver for windows 8 crashed and recovered... blah-blah-blah". But the game does not recover. And I have windows 7, not 8. Personally I think that this is a problem with Windows 7/8 driver. Because:

1. When I put NVidia card into my MB and play this game, I get no such problems.

2. When I play this game on linux with Intel HD, I have no such problems.

3. When I play this game on Windows XP with XPEmbedded driver, downloaded here https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=3656&DwnldID=22875&ProductFamily=Embedded+Components&ProductLine=Embedded+Graphics+Drivers&ProductProduct=Intel%C2%AE+HD+Graphics&keyword=14.56&DownloadType=Drivers+%28Embedded%2c+for+Developers%29&lang=eng Download Center . I have no such problems.

I have the latest driver 10.18.10.3496, Windows 7 64-bit, 4 gigs of memory. My CPU is Celeron G1820, Motherboard Asus H81M-E. The latest BIOS update.

This problem seems to less affect other games. But sometimes I have black squares in DosBox and in some console emulators. Which are fully 2D applications.

I tried clean installation of Windows 7, with clean drivers, without any additional software and updates. Also I tried it with latest updates for windows 7. No effects on the problem.

With previous driver the game used to freeze for 5 secs. Now it does not.

Re: Intel display driver stopped responding and has recovered.

Kevin_M_Intel — Fri, 18 Apr 2014 19:01:12 GMT

Hi dmit.bit,

I am sorry you had a bad experience before. Please open a new thread with this topic since it is about a different issue.

You can open one here:

/community/tech/graphics https://communities.intel.com/community/tech/graphics

Re: Intel display driver stopped responding and has recovered.

ASuth — Fri, 29 Aug 2014 10:06:30 GMT

Dear Kevin,

Myself also facing the same problem. Please suggest the way forward to resolve.. My PC every 1-3 min the display freezes for 5-10 sec or so and after a few times doing that it crashes, turn to black and then says: Intel display driver stopped responding and has recovered....as below....

I have provided My DxDiag report, plz provide your suggestion.

My DxDiag report:

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

System Information

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

Time of this report: 8/28/2014, 09:37:23

Machine name: C002686

Operating System: Windows 7 Professional 32-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130828-1532)

Language: English (Regional Setting: English)

System Manufacturer: Hewlett-Packard

System Model: HP Pro 3090 Microtower PC

BIOS: BIOS Date: 01/27/10 16:47:47 Ver: V1.01

Processor: Pentium(R) Dual-Core CPU E5500 @ 2.80GHz (2 CPUs), ~2.8GHz

Memory: 2048MB RAM

Available OS Memory: 1918MB RAM

Page File: 1142MB used, 2692MB available

Windows Dir: C:\Windows

DirectX Version: DirectX 11

DX Setup Parameters: Not found

User DPI Setting: Using System DPI

System DPI Setting: 96 DPI (100 percent)

DWM DPI Scaling: Disabled

DxDiag Version: 6.01.7601.17514 32bit Unicode

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

DxDiag Notes

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

Display Tab 1: No problems found.

Sound Tab 1: No problems found.

Input Tab: No problems found.

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

DirectX Debug Levels

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

Direct3D: 0/4 (retail)

DirectDraw: 0/4 (retail)

DirectInput: 0/5 (retail)

DirectMusic: 0/5 (retail)

DirectPlay: 0/9 (retail)

DirectSound: 0/5 (retail)

DirectShow: 0/6 (retail)

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

Display Devices

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

Card name: Intel(R) G45/G43 Express Chipset (Microsoft Corporation - WDDM 1.1)

Manufacturer: Intel Corporation

Chip type: Intel(R) 4 Series Express Chipset Family

DAC type: Internal

Device Key: Enum\PCI\VEN_8086&DEV_2E22&SUBSYS_1479103C&REV_03

Display Memory: 830 MB

Dedicated Memory: 128 MB

Shared Memory: 702 MB

Current Mode: 1366 x 768 (32 bit) (60Hz)

Monitor Name: Generic PnP Monitor

Monitor Model: V193HQL

Monitor Id: ACR0127

Native Mode: 1366 x 768(p) (59.790Hz)

Output Type: HD15

Driver Name: igdumd32.dll,igd10umd32.dll

Driver File Version: 8.15.0010.1749 (English)

Driver Version: 8.15.10.1749

DDI Version: 10

Driver Model: WDDM 1.1

Driver Attributes: Final Retail

Driver Date/Size: 7/14/2009 06:45:31, 3805184 bytes

WHQL Logo'd: Yes

WHQL Date Stamp:

Device Identifier: {D7B78E66-6D62-11CF-5975-7334A3C2C535}

Vendor ID: 0x8086

Device ID: 0x2E22

SubSys ID: 0x1479103C

Revision ID: 0x0003

Driver Strong Name: igdlh.inf:Intel.Mfg.NTx86...1:iEGL0:8.15.10.1749:pci\ven_8086&dev_2e22

Rank Of Driver: 00EC2001

Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_B ModeWMV9_C ModeVC1_B ModeVC1_C

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProc...

Re: Intel display driver stopped responding and has recovered.

Kevin_M_Intel — Wed, 03 Sep 2014 19:20:42 GMT

Hello just4ashok85,

Thanks for the information. I would recommend you updating the BIOS to the latest provided by the Computer Manufacture and update the graphics driver.

Here you have the download link:

https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=22165 https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=22165

Kevin M

Re: Intel display driver stopped responding and has recovered.

cxxc — Sun, 07 Jun 2015 02:47:37 GMT

I am having similar problem, when playing Half Life 2 and games on Source Engine (except for Garry's Mod)

Whenever I start new game in Half Life 2 Episode 2, it freezes and I get the following error:

Display Driver has stopped responding and has recovered.

Yes, sometimes I get the flying textures too.

Re: Intel display driver stopped responding and has recovered.

Kevin_M_Intel — Tue, 09 Jun 2015 14:09:24 GMT

Hello BloxxingBlocks,

The issue you are reporting is completely different than the one reported by the OP. Please create another thread and provide all the necessary information so we can check it out.

Kevin M