Intel Driver crash when restoring or minimizing window (ig4icd64.dll) #31423

New Issue

CodeManX · 2012-05-12T00:41:23+02:00

CodeManX commented

2012-05-12 00:41:23 +02:00

%%%Windows 7, 64bit
Intel Core i5 / Intel HD 3000 graphics driver v8.15.10.2622 and .2696

blender.exe / ig4icd64.dll crashes very often when i try to bring up the window from taskbar or minimize it

It seems to happen more often if the window is/was maximized or mousewheel was used in edit-mode right before. But it happens less if the splashscreen is opened.

To reproduce this, just click fast on the taskbar icon for a while. Sometimes crashes instantly, sometimes after a dozen clicks.

Might relate to other bug reports, as this seems to occur when OpenGL was re-initiated. Is there anything one can do about? In other reports the answer was Intel needs to fix their drivers... (I downgraded my driver from latest but no difference)

Stack trace:

ig4icd64.dll!0000000006a2acaa()

[Unten angegebene Rahmen sind möglicherweise nicht korrekt und/oder fehlen, keine Symbole geladen für ig4icd64.dll]	
ig4icd64.dll!0000000006a2c57b() 	
ig4icd64.dll!0000000006a04113() 	
ig4icd64.dll!0000000006269727() 	
ig4icd64.dll!000000000626b855() 	
blender.exe!0000000140018691() 	
blender.exe!0000000140018a7f() 	
blender.exe!0000000140018e3c() 	
blender.exe!00000001400043b0() 	
blender.exe!00000001400012e1() 	
blender.exe!000000014125d443() 	
kernel32.dll!00000000774d652d() 	
ntdll.dll!0000000077bcc521()

Auto values:

	ESI	00000000	
	RBX	0000000000000000	
	RSP	000000000022F9C0	
	ECX	00000113	
	R14	00000000003C37A0	
	R10	000000000752CF80

Assambly code line:

0000000006A2ACAA mov esi,dword ptr [rbx+14h]
(esi and rbx are 0)%%%

%%%Windows 7, 64bit Intel Core i5 / Intel HD 3000 graphics driver v8.15.10.2622 and .2696 blender.exe / ig4icd64.dll crashes very often when i try to bring up the window from taskbar or minimize it It seems to happen more often if the window is/was maximized or mousewheel was used in edit-mode right before. But it happens less if the splashscreen is opened. To reproduce this, just click fast on the taskbar icon for a while. Sometimes crashes instantly, sometimes after a dozen clicks. Might relate to other bug reports, as this seems to occur when OpenGL was re-initiated. Is there anything one can do about? In other reports the answer was Intel needs to fix their drivers... (I downgraded my driver from latest but no difference) Stack trace: > ig4icd64.dll!0000000006a2acaa() [Unten angegebene Rahmen sind möglicherweise nicht korrekt und/oder fehlen, keine Symbole geladen für ig4icd64.dll] ig4icd64.dll!0000000006a2c57b() ig4icd64.dll!0000000006a04113() ig4icd64.dll!0000000006269727() ig4icd64.dll!000000000626b855() blender.exe!0000000140018691() blender.exe!0000000140018a7f() blender.exe!0000000140018e3c() blender.exe!00000001400043b0() blender.exe!00000001400012e1() blender.exe!000000014125d443() kernel32.dll!00000000774d652d() ntdll.dll!0000000077bcc521() Auto values: ESI 00000000 RBX 0000000000000000 RSP 000000000022F9C0 ECX 00000113 R14 00000000003C37A0 R10 000000000752CF80 Assambly code line: 0000000006A2ACAA mov esi,dword ptr [rbx+14h] (esi and rbx are 0)%%%

CodeManX commented

2012-05-12 00:41:23 +02:00

Changed status to: 'Open'

Sergey Sharybin commented

2012-05-15 18:06:01 +02:00

%%%There's no much we can do here -- Intel's drivers are well-known for assorted crappiness about opengl.
Probably it's possible to figure out which exactly ogl command combination triggers crash, but even with having access to buggy software it's really difficult. Without having access to buggy hardware it's nearly impossible.

The only workaround would be to download opengl32.dll from http://download.blender.org/ftp/incoming/softwaregl/ and put it near blender.exe. It'll switch blender to fully software mode which will mean it wouldn't be affected by drivers bugs, but it'll be also really slow.

Also probably changing Window Draw Method in User Preferences -> System.

We have already report about non-working HD 3000 there http://projects.blender.org/tracker/index.php?func=detail&aid=28364&group_id=9&atid=231
Probably this might help somehow.%%%

%%%There's no much we can do here -- Intel's drivers are well-known for assorted crappiness about opengl. Probably it's possible to figure out which exactly ogl command combination triggers crash, but even with having access to buggy software it's really difficult. Without having access to buggy hardware it's nearly impossible. The only workaround would be to download opengl32.dll from http://download.blender.org/ftp/incoming/softwaregl/ and put it near blender.exe. It'll switch blender to fully software mode which will mean it wouldn't be affected by drivers bugs, but it'll be also really slow. Also probably changing Window Draw Method in User Preferences -> System. We have already report about non-working HD 3000 there http://projects.blender.org/tracker/index.php?func=detail&aid=28364&group_id=9&atid=231 Probably this might help somehow.%%%

Sergey Sharybin commented

2012-05-15 18:06:01 +02:00

Changed status from 'Open' to: 'Archived'

Sergey Sharybin closed this issue

2012-05-15 18:06:01 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Intel Driver crash when restoring or minimizing window (ig4icd64.dll) #31423