https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867849#M466 <PRE class="brush:bash;">10047FA0&nbsp;&nbsp; 8D45 FC&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LEA EAX,DWORD PTR SS:[EBP-4] 10047FA3&nbsp;&nbsp; 50&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PUSH EAX 10047FA4&nbsp;&nbsp; 6A 04&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PUSH 4 10047FA6&nbsp;&nbsp; 68 10C71210&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PUSH igddim32.1012C710&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ; UNICODE "HotPlug_DVO_SDVO" 10047FAB&nbsp;&nbsp; 8B4D F4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOV ECX,DWORD PTR SS:[EBP-C] 10047FAE&nbsp;&nbsp; 51&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PUSH ECX 10047FAF&nbsp;&nbsp; 8B55 F4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOV EDX,DWORD PTR SS:[EBP-C] 10047FB2&nbsp;&nbsp; 8B42 04&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOV EAX,DWORD PTR DS:[EDX+4] 10047FB5&nbsp;&nbsp; FFD0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CALL EAX </PRE> <P>This is only a registry query, (calling ntoskrnl.RtlQueryRegistryValues). It transfers all the necessary inputs, like handle for the opened key, etc.</P> <PRE class="brush:bash;">10047FB7&nbsp;&nbsp; 0FB6C8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOVZX ECX,AL 10047FBA&nbsp;&nbsp; 83F9 01&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CMP ECX,1 10047FBD&nbsp;&nbsp; 75 26&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; JNZ SHORT igddim32.10047FE5 </PRE> <P>The return value arrives in AL, and this tests if the query was successfull or not. If AL=1 then the query was succesfull, otherwise it jumps out to 10047fe5. If the query was successfull, the code continues at the next instruction.</P> <PRE class="brush:bash;">10047FBF&nbsp;&nbsp; 837D FC 02&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CMP DWORD PTR SS:[EBP-4],2 10047FC3&nbsp;&nbsp; 73 20&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; JNB SHORT igddim32.10047FE5 </PRE> <P>This code executes only if the query was successfull, for example if the value exists in the registry tree. SS:[EBP-4] containst the value of "HotPlug_DVO_SDVO". If the value is greater or equialent with 2 than jumps out. Practically the value can be 0 or 1 to remain here. 0 means the HotPlug is enabled, 1 means HotPlug is disabled</P> <PRE class="brush:bash;">10047FC5&nbsp;&nbsp; 8A55 FC&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOV DL,BYTE PTR SS:[EBP-4] 10047FC8&nbsp;&nbsp; 80E2 01&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AND DL,1 10047FCB&nbsp;&nbsp; C0E2 03&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SHL DL,3 </PRE> <P>This is taking the result (which can be 0 or 1, so practicaly one bit, on the 0. position of the byte) and shifts to left by 3, so the bit will go to the 3. position of the byte. (can be 8 or 0)</P> <PRE class="brush:bash;">10047FCE&nbsp;&nbsp; 8B45 08&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOV EAX,DWORD PTR SS:[EBP+8] 10047FD1&nbsp;&nbsp; 8A88 80000000&nbsp;&nbsp;&nbsp; MOV CL,BYTE PTR DS:[EAX+80] 10047FD7&nbsp;&nbsp; 80E1 F7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AND CL,0F7 </PRE> <P>This is taking the value of some local storage area, and "kills" the 3. bit of this local byte variable (because the new registry value will be stored&nbsp;at this freshly "killed" bit. (((SS:[EBP+8] is the addres of the local storage area, and DS:[EAX+80] is the local byte variable.)))</P> <PRE class="brush:bash;">10047FDA&nbsp;&nbsp; 0ACA&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OR CL,DL </PRE> <P>This is combining together the old data, which came from the local data area, and the new data which came from the registry, and it was shifted, and stored now in DL.</P> <PRE class="brush:bash;">10047FDC&nbsp;&nbsp; 8B55 08&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOV EDX,DWORD PTR SS:[EBP+8] 10047FDF&nbsp;&nbsp; 888A 80000000&nbsp;&nbsp;&nbsp; MOV BYTE PTR DS:[EDX+80],CL </PRE> <P>And this is atoring back the combined data to the local data area.</P> <P>So, practicly the code queried the registry value, and stored to one bit of a local byte variable of a local data area.</P> <P>This is totaly clear for me.</P> <P>But the problem this code, which I just discovered, and it seems, that this code is never called, so the stored bit will never be used any longer. The following whole procedure is ignored, never called, and this is the problem. I guess, that the driver was compiled with some conditional parameter, and the reference to (calling of)&nbsp;this procedure was not compiled to the code.</P> <PRE class="brush:bash;">10046050&nbsp;&nbsp; 55&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PUSH EBP 10046051&nbsp;&nbsp; 8BEC&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOV EBP,ESP 10046053&nbsp;&nbsp; 83EC 0C&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SUB ESP,0C 10046056&nbsp;&nbsp; C645 FF 00&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOV BYTE PTR SS:[EBP-1],0 1004605A&nbsp;&nbsp; E8 413F0000&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CALL igddim32.10049FA0 1004605F&nbsp;&nbsp; 8945 F8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOV DWORD PTR SS:[EBP-8],EAX 10046062&nbsp;&nbsp; E8 B9170200&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CALL igddim32.10067820 10046067&nbsp;&nbsp; 8945 F4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOV DWORD PTR SS:[EBP-C],EAX 1004606A&nbsp;&nbsp; 837D 0C 00&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CMP DWORD PTR SS:[EBP+C],0 1004606E&nbsp;&nbsp; 75 2E&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; JNZ SHORT igddim32.1004609E 10046070&nbsp;&nbsp; 837D F4 00&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CMP DWORD PTR SS:[EBP-C],0 10046074&nbsp;&nbsp; 74 11&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; JE SHORT igddim32.10046087 10046076&nbsp;&nbsp; 8B45 F4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOV EAX,DWORD PTR SS:[EBP-C] 10046079&nbsp;&nbsp; 0FB648 1F&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOVZX ECX,BYTE PTR DS:[EAX+1F] 1004607D&nbsp;&nbsp; 85C9&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TEST ECX,ECX 1004607F&nbsp;&nbsp; 74 06&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; JE SHORT igddim32.10046087 10046081&nbsp;&nbsp; C645 FF 00&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOV BYTE PTR SS:[EBP-1],0 10046085&nbsp;&nbsp; EB 15&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; JMP SHORT igddim32.1004609C 10046087&nbsp;&nbsp; 8B55 08&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOV EDX,DWORD PTR SS:[EBP+8] 1004608A&nbsp;&nbsp; 66:8B82 87000000 MOV AX,WORD PTR DS:[EDX+87] 10046091&nbsp;&nbsp; 66:C1E8 0A&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SHR AX,0A 10046095&nbsp;&nbsp; 66:83E0 01&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AND AX,1 10046099&nbsp;&nbsp; 8845 FF&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOV BYTE PTR SS:[EBP-1],AL 1004609C&nbsp;&nbsp; EB 72&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; JMP SHORT igddim32.10046110 1004609E&nbsp;&nbsp; 837D 0C 02&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CMP DWORD PTR SS:[EBP+C],2 100460A2&nbsp;&nbsp; 74 06&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; JE SHORT igddim32.100460AA 100460A4&nbsp;&nbsp; 837D 0C 03&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CMP DWORD PTR SS:[EBP+C],3 100460A8&nbsp;&nbsp; 75 14&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; JNZ SHORT igddim32.100460BE 100460AA&nbsp;&nbsp; 8B4D 08&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOV ECX,DWORD PTR SS:[EBP+8] 100460AD&nbsp;&nbsp; 8A91 80000000&nbsp;&nbsp;&nbsp; MOV DL,BYTE PTR DS:[ECX+80] 100460B3&nbsp;&nbsp; C0EA 03&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SHR DL,3 100460B6&nbsp;&nbsp; 80E2 01&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AND DL,1 100460B9&nbsp;&nbsp; 8855 FF&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOV BYTE PTR SS:[EBP-1],DL 100460BC&nbsp;&nbsp; EB 52&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; JMP SHORT igddim32.10046110 100460BE&nbsp;&nbsp; 837D 0C 06&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CMP DWORD PTR SS:[EBP+C],6 100460C2&nbsp;&nbsp; 75 4C&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; JNZ SHORT igddim32.10046110 100460C4&nbsp;&nbsp; 837D F4 00&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CMP DWORD PTR SS:[EBP-C],0 100460C8&nbsp;&nbsp; 74 11&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; JE SHORT igddim32.100460DB 100460CA&nbsp;&nbsp; 8B45 F4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOV EAX,DWORD PTR SS:[EBP-C] 100460CD&nbsp;&nbsp; 0FB648 20&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOVZX ECX,BYTE PTR DS:[EAX+20] 100460D1&nbsp;&nbsp; 85C9&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TEST ECX,ECX 100460D3&nbsp;&nbsp; 74 06&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; JE SHORT igddim32.100460DB 100460D5&nbsp;&nbsp; C645 FF 00&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOV BYTE PTR SS:[EBP-1],0 100460D9&nbsp;&nbsp; EB 35&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; JMP SHORT igddim32.10046110 100460DB&nbsp;&nbsp; 8B55 F8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOV EDX,DWORD PTR SS:[EBP-8] 100460DE&nbsp;&nbsp; 837A 10 04&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CMP DWORD PTR DS:[EDX+10],4 100460E2&nbsp;&nbsp; 1BC0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SBB EAX,EAX 100460E4&nbsp;&nbsp; 83C0 01&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ADD EAX,1 100460E7&nbsp;&nbsp; 74 27&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; JE SHORT igddim32.10046110 100460E9&nbsp;&nbsp; 8B4D 08&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOV ECX,DWORD PTR SS:[EBP+8] 100460EC&nbsp;&nbsp; 0FB791 24010000&nbsp; MOVZX EDX,WORD PTR DS:[ECX+124] 100460F3&nbsp;&nbsp; 81FA 84000000&nbsp;&nbsp;&nbsp; CMP EDX,84 100460F9&nbsp;&nbsp; 7C 15&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; JL SHORT igddim32.10046110 100460FB&nbsp;&nbsp; 8B45 08&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOV EAX,DWORD PTR SS:[EBP+8] 100460FE&nbsp;&nbsp; 66:8B88 87000000 MOV CX,WORD PTR DS:[EAX+87] 10046105&nbsp;&nbsp; 66:C1E9 0D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SHR CX,0D 10046109&nbsp;&nbsp; 66:83E1 01&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AND CX,1 1004610D&nbsp;&nbsp; 884D FF&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOV BYTE PTR SS:[EBP-1],CL 10046110&nbsp;&nbsp; 8A45 FF&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOV AL,BYTE PTR SS:[EBP-1] 10046113&nbsp;&nbsp; 8BE5&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOV ESP,EBP 10046115&nbsp;&nbsp; 5D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; POP EBP 10046116&nbsp;&nbsp; C2 0800&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; RETN 8 </PRE> <P>&nbsp;</P> Tue, 15 Apr 2014 08:44:38 GMT MFalk1 2014-04-15T08:44:38Z https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867816#M433 <P>Access violation reading location 0x00000510</P> <P>We`ve got this big problem in our game.</P> <P>Access violation happens only under Win7 + Intel graphics (GMA 3100, GMA 950) and works fine under WinXP or with non-Intel cards so it is definitely not a problem of our 3d engine. Affected both 8.15.10.1749 driver and the latest available 1930.</P> <P>Call stack right after crash:</P> <P>igdumd32.dll!01854ec5() <BR /> [Frames below may be incorrect and/or missing, no symbols loaded for igdumd32.dll] <BR /> igdumd32.dll!0186c20f() <BR /> igdumd32.dll!0189df4a() <BR /> igdumd32.dll!0189af4c() <BR /> igdumd32.dll!0189d2ea() <BR /> igdumd32.dll!018a0276() <BR /> igdumd32.dll!0196bd79() <BR /> igdumd32.dll!0187863a() <BR /> igdumd32.dll!01863b13() <BR /> d3d9.dll!CD3DDDIDX10::DrawIndexPrim() + 0x204 bytes <BR /> d3d9.dll!wmt_DRAW_CLIPPED_PRIM() + 0x1be bytes <BR /> d3d9.dll!wmt_PVFUNCS::ProcessIndexedPrimitive() + 0x11a bytes <BR /> d3d9.dll!CD3DDDIDX8::ProcessIndexedPrimitiveC() + 0x119 bytes <BR /> d3d9.dll!CD3DHal_DrawIndexedPrimitive() + 0xa4 bytes <BR /> d3d9.dll!CD3DBase::DrawIndexedPrimitive() + 0xc3 bytes <BR />&gt; lzView.exe!lzMesh::Dip(D3DXMATRIX * iTm=0x0abb9b18, int iFrame=0) Line 79 + 0x43 bytes C++</P> <P>Help to find any <STRONG>workaround</STRONG> as soon as possible. Our customers have Intel graphics, so we need to fix this in some way.</P> <P>I can make a bug <STRONG>repro</STRONG>, if it helps you dealing with this problem. Or if it is possible you may send to me igdumd32 pdb file, then I can provide more readable report.</P> <P>Eugene.</P> Wed, 09 Dec 2009 12:28:41 GMT https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867816#M433 oev_nsk 2009-12-09T12:28:41Z https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867817#M434 <P>As an additional note, I try to describe some logic behind this bug.</P> <P>We are drawing different object on the scene, using <STRONG>FFP</STRONG> setup. Just SetRenderStates, SetTextures and so on and finally DIPs.</P> <P>At the some beautiful moment (when tens of objects allready drawn), all crashes after calling DIP.</P> <P>But it is not the DIP problem by itself I guess. This is something what your dll do behind the scene: changing the shader or it`s constants or something. I think so, because if I alter statechanges before make that killing DIP, all works fine. My expirements shows, that if i.e. I will change D3DRS_SPECULARENABLE to TRUE before that dip nothing crashes.</P> <P>Also, when I change stages setup (i.e. switch off stage 1 by passing D3DTOP_DISABLE), an address in access violation changes too (it is equals to 0x000003f0).</P> <P></P> <P>Don`t know helps this or no, but I tell some more about the program.</P> <P>- There is a Reset() at the start of the game.</P> <P>- All works using FFP, no custom shading applied.</P> <P>- Compiled with DirectX 9c SDK (2004 aug and 2008 aug).</P> <P>- Works in windowed mode</P> <P>- ... anything you ask</P> Wed, 09 Dec 2009 17:39:42 GMT https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867817#M434 oev_nsk 2009-12-09T17:39:42Z https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867818#M435 <DIV style="margin:0px;"> <DIV id="quote_reply" style="width: 100%; margin-top: 5px;">Is it okay for intel to ignore this forum or to reply once in several weeks maybe?</DIV> <DIV style="width: 100%; margin-top: 5px;"><BR /></DIV> <DIV style="width: 100%; margin-top: 5px;">p.s. btw, there is even no Win7 OS variant in the problem submit (http://supportmail.intel.com/scripts-emf/prodspec.aspx).</DIV> </DIV> Wed, 16 Dec 2009 11:44:37 GMT https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867818#M435 oev_nsk 2009-12-16T11:44:37Z https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867819#M436 <DIV style="margin:0px;"> <DIV id="quote_reply" style="margin-top: 5px; width: 100%;"> <DIV style="margin-left:2px;margin-right:2px;">Quoting - <A href="https://community.intel.com/en-us/profile/456043">oev.nsk</A></DIV> <DIV style="background-color:#E5E5E5; padding:5px;border: 1px; border-style: inset;margin-left:2px;margin-right:2px;"><EM> <DIV style="margin:0px;"> <DIV id="quote_reply" style="margin-top: 5px; width: 100%;">Is it okay for intel to ignore this forum or to reply once in several weeks maybe?</DIV> <DIV style="margin-top: 5px; width: 100%;"><BR /></DIV> <DIV style="margin-top: 5px; width: 100%;">p.s. btw, there is even no Win7 OS variant in the problem submit (http://supportmail.intel.com/scripts-emf/prodspec.aspx).</DIV> </DIV> </EM></DIV> </DIV> </DIV> <BR />Hello oev.nsk<BR /><BR />I am the community manager and want tosend my apologiesfor the delay in answering this question. I have notified our forum moderator and he will get back to you soon. <BR /><BR />Regards Wed, 16 Dec 2009 17:30:06 GMT https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867819#M436 Arti_G_Intel 2009-12-16T17:30:06Z https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867820#M437 <P>Waiting for a qualified help.</P> <P>Thank you.</P> Wed, 16 Dec 2009 17:52:46 GMT https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867820#M437 oev_nsk 2009-12-16T17:52:46Z https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867821#M438 <DIV style="margin:0px;">Hi Eugene,<BR /><BR />Do you have a test case that you can provide us, so we can reproduce the crash within Intel?<BR /><BR />Have you been able to reproduce the failure on a later generation Intel graphics (GMA 4500 variant)?<BR /><BR />Thanks,<BR />-Ganesh</DIV> <BR /> Wed, 16 Dec 2009 18:21:11 GMT https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867821#M438 Doraisamy_G_Intel 2009-12-16T18:21:11Z https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867822#M439 <DIV style="margin:0px;"> <DIV id="quote_reply" style="width: 100%; margin-top: 5px;">Hi<BR /><BR />&gt;Do you have a test case that you can provide us, so we can reproduce the crash within Intel?<BR />Yes, I will send a link to you via a private message. <BR /><BR />&gt;Have you been able to reproduce the failure on a later generation Intel graphics (GMA 4500 variant)?<BR />We have no such configurations at this moment, so I just have no answer.<BR />But I can try to find GMA4500-based system later, if provided repro will not be enough to figure out the problem.</DIV> </DIV> Wed, 16 Dec 2009 19:10:09 GMT https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867822#M439 oev_nsk 2009-12-16T19:10:09Z https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867823#M440 <DIV style="margin: 0px; height: auto;"></DIV> Do you download the test and be able to reproduce bug now?<BR /> Thu, 17 Dec 2009 04:48:18 GMT https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867823#M440 oev_nsk 2009-12-17T04:48:18Z https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867824#M441 <DIV style="margin:0px;"> <DIV id="quote_reply" style="margin-top: 5px; width: 100%;"> <DIV style="margin-left:2px;margin-right:2px;">Quoting - <A href="https://community.intel.com/en-us/profile/456043">oev.nsk</A></DIV> <DIV style="background-color:#E5E5E5; padding:5px;border: 1px; border-style: inset;margin-left:2px;margin-right:2px;"><EM>Do you download the test and able to reproduce bug now?<BR /></EM></DIV> </DIV> </DIV> <BR />Just downloaded it from home. I didn't get a notice from the system about the private message.<BR /><BR />I will get back to you tomorrow after checking it out on Intel GMA. Thu, 17 Dec 2009 05:06:08 GMT https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867824#M441 Doraisamy_G_Intel 2009-12-17T05:06:08Z https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867825#M442 Any news?<BR /> Fri, 18 Dec 2009 09:02:00 GMT https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867825#M442 oev_nsk 2009-12-18T09:02:00Z https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867826#M443 <DIV style="margin:0px;"> <DIV id="quote_reply" style="margin-top: 5px; width: 100%;"> <DIV style="margin-left:2px;margin-right:2px;">Quoting - <A href="https://community.intel.com/en-us/profile/456043">oev.nsk</A></DIV> <DIV style="background-color:#E5E5E5; padding:5px;border: 1px; border-style: inset;margin-left:2px;margin-right:2px;"><EM>Any news?<BR /></EM></DIV> </DIV> </DIV> <BR />We are working on it. Setting up a system with Win7 32 bit. The older generation hardware machines are becoming rarer to find around here. Will keep you posted.<BR /> Fri, 18 Dec 2009 09:14:57 GMT https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867826#M443 Doraisamy_G_Intel 2009-12-18T09:14:57Z https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867827#M444 Thank you.<BR /> Fri, 18 Dec 2009 09:58:27 GMT https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867827#M444 oev_nsk 2009-12-18T09:58:27Z https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867828#M445 Eugene,<BR /><BR />I tried the test workload on a GMA X3000 and a GMA X4500. Both of them worked fine, with either driver version (8.15.10.1749 or 8.15.10.1930).<BR /><BR />Keep in mind the X3000 is a newer generation architecture than the GMA 3100 or 950. I haven't been able to get a hold of anything older than the X3000 yet. Have you had a chance to try out on anything newer?<BR /><BR />Cheers,<BR />-Ganesh Sat, 19 Dec 2009 02:19:10 GMT https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867828#M445 Doraisamy_G_Intel 2009-12-19T02:19:10Z https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867829#M446 <P>I found x3000, all works fine. But that was almost obvious, since x3000 is hardly improved and has totally different codepath in the driver I guess. The main problem is that too many casual customers haven`t recent hardware, so we need to deal with that outdated stuff too.</P> <P>Is it possible to get a pdb file for that dll? Then I can report more readable info about the place where all crashes.</P> <P>Will some kind of memory dump be helpful?</P> <P>Or maybe your company has something like "hardware archive" and it is possible to query older generation systems from it for several days?</P> Sat, 19 Dec 2009 10:11:19 GMT https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867829#M446 oev_nsk 2009-12-19T10:11:19Z https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867830#M447 <DIV style="margin:0px;"> <DIV id="quote_reply" style="width: 100%; margin-top: 5px;">Is anybody here?</DIV> </DIV> Tue, 05 Jan 2010 07:29:40 GMT https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867830#M447 oev_nsk 2010-01-05T07:29:40Z https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867831#M448 <DIV style="margin:0px;"> <DIV id="quote_reply" style="width: 100%; margin-top: 5px;"> <DIV style="margin-left:2px;margin-right:2px;">Quoting - <A href="https://community.intel.com/en-us/profile/456043">oev.nsk</A></DIV> <DIV style="background-color:#E5E5E5; padding:5px;border: 1px; border-style: inset;margin-left:2px;margin-right:2px;"><EM> <DIV style="margin:0px;"> <DIV id="quote_reply" style="width: 100%; margin-top: 5px;">Is anybody here?</DIV> </DIV> </EM></DIV> </DIV> </DIV> Hello oev.nsk<BR /><BR />Ganesh has been working on this issue but unfortunately this hardware has reached end of life so we have not been able to find an answer for you. <BR /><BR />Apologies for the inconvenience.<BR /><BR />Regards<BR />Arti<BR /> Thu, 07 Jan 2010 22:09:04 GMT https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867831#M448 Arti_G_Intel 2010-01-07T22:09:04Z https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867832#M449 <P>I've got a similar problem:</P> <P>Faulting application name:X.vshost.exe, version: 9.0.21022.8, time stamp: 0x47316898</P> <P>Faulting module name: igdumd32.dll, version: 8.15.10.1986, time stamp: 0x4aeb3b2c</P> <P>Exception code: 0xc0000409</P> <P>Fault offset: 0x00014fe6</P> <P>Faulting process id: 0xbdc</P> <P>Faulting application start time: 0x01cac63abe14226d</P> <P>Faulting application path: C:\Projects\X\Debug\X.vshost.exe</P> <P>Faulting module path: C:\Windows\system32\igdumd32.dll</P> <P>Report Id: 01ca9c3f-322e-11df-9568-00247edc9161</P> <P><BR />Basically, whenever I try to run my project in Visual Studio 2008 vshost.exe crashes and the above is in the event log.</P> <P><BR />My environment is:</P> <P>Windows 7 Professional</P> <P>Lenovo T400s</P> <P>Intel 4 Series Express Chipset - GMA 4500MD</P> <P><BR />I've tried various 8.15.10.x builds, but none of them helped.</P> <P><BR />I installed 7.15.10.1666 (the latest version 7 build that I could get) and I can run the project in Visual Studio 2008.</P> <P><BR />The problem now is that the screen will judder below the cursor!</P> <P><BR />This can be solved to some degree by reducing the resolution on the laptop screen, but not on my external monitor.</P> Thu, 18 Mar 2010 05:27:03 GMT https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867832#M449 drscrummaster 2010-03-18T05:27:03Z https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867833#M450 Problem is... they are not becoming rarer among many end-users! Tue, 30 Mar 2010 20:04:33 GMT https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867833#M450 c0ldf1re 2010-03-30T20:04:33Z https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867834#M451 Unfortunately, the driver for the platform you are using(GMA 3100or GMA 950)is no longer actively supported by Intel. Regretfully, it is not feasible to issue a driver patch at this time for this bug.However it is fixed in the later releases of our hardware. Thu, 15 Apr 2010 17:10:55 GMT https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867834#M451 Doraisamy_G_Intel 2010-04-15T17:10:55Z https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867835#M452 You have compiled the app under debug, with full D3D debug info, and the debug runtime turned all the way up?<BR /><BR />There is no extra debug output?<BR /><BR />You can capture and playback the frame with PIX? Fri, 21 May 2010 00:51:35 GMT https://community.intel.com/t5/Developing-Games-on-Intel/Driver-bug-AV-in-igdumd32-dll-DirectX-9-related/m-p/867835#M452 Philip_T_Intel1 2010-05-21T00:51:35Z