- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am working on a Dell Optiplex 745 with Intel GMA 3000 (identifies as Q965). In Windows 7 Aero loads and works fine.
The system has a clean install of Windows 7 64-bit and no antivirus or any other additions to the system that would cause any issues. I did run a previous install with all Windows Updates installed -- same trouble with AppCrash.
The trouble is when launching any standard Windows game such as Solitaire.exe. When it launches it crashes with the following info:
Executable for Solitaire Game has stopped working
Problem signature:
Problem Event Name: APPCRASH
Application Name: solitaire.exe
Application Version: 6.1.7600.16385
Application Timestamp: 4a5bc9f9
Fault Module Name: igdumd64.dll
Fault Module Version: 8.15.10.1749
Fault Module Timestamp: 4a5bdf54
Exception Code: c0000005
Exception Offset: 0000000000070862
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional Information 1: cfa9
Additional Information 2: cfa960e6b4c4547a2e547d51c23416cb
Additional Information 3: 1681
Additional Information 4: 1681d76793b43ec02aadd13ff22676
Event Viewer Event 1000, Application Error
Driver installed is Intel(R) Q965/Q963 Express Chipset Family (Microsoft Corporation - WDDM 1.0)
I did remove the Microsoft Driver and installed the Intel Driver Package 76560 (win7_64_1512754) which is version 8.15.10.1930...Dec 2009 and identifies itself as WDDM 1.1.
The condition that produces AppCrash with faulting application igdumd64.dll is still present with the new drivers. The faulting module with the new drivers lists a version of igdumd64.dll that is 8.14.10.1930. NOTE: 8.14 would be older than the previous version but the suffix reflects that this is the newer installed file. I suspect this might be a typo on someone's part... perhaps that is also what's wrong with igdumd64.dll?
What can be done to determine the root cause of the application crash and fix it? I am willing to try or do anything requested as the system isn't going anywhere until this is resolved. Why could igdumd64.dll cause such a simple program as Solitaire to have an AppCrash?
I installed a very old PCI video card without any support for Aero interface and no drivers for Windows 7 or even Vista. It used SVGA drivers and while there were clear performance issues I had no AppCrashes.
I ran dxdiag and it did not show any errors in either 32-bit or 64-bit versions.
I have found many similar complaints and issues with Windows 7 and Intel GMA on sites that like to knock the GMA and solve all problems with a "discreet" graphics adapter. I am reluctant to do this as there is no expectation of high performance but I do expect to have basic function without AppCrashes.
Please let me know if there are other drivers, settings, or steps I can take to resolve the issue or gather more information that will be helpful to get Intel and Microsoft working on this issue to fix it.
- Tags:
- Intel® Gaming
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a Dell Studio Hybrid and I'm getting a crash in the same module when I try to play certain DVDs. Some play fine, others cause Windows Media Center or Windows Media Player to crash. Running Windows 7 Home Premium 64-bit. The DVDs I've found crash it, so far, are "Christmas Vacation" and "A Christmas Story."
The crash from Windows Media Center:
Faulting application name: ehShell.exe, version: 6.1.7600.16385, time stamp: 0x4a5bd053
Faulting module name: igdumd64.dll, version: 8.15.10.1912, time stamp: 0x4aaa8332
Exception code: 0x40000015
Fault offset: 0x00000000000b3288
Faulting process id: 0xb0c
Faulting application start time: 0x01ca80463f9998c1
Faulting application path: C:\Windows\ehome\ehShell.exe
Faulting module path: C:\Windows\system32\igdumd64.dll
Report Id: bfebb77f-ec39-11de-ab4d-00217014b0bd
I then tried the same disc in Windows Media Player and it, too, crashed - but this time it, for some reason, used igdumd32.dll.
Faulting application name: wmplayer.exe, version: 12.0.7600.16415, time stamp: 0x4a98ae4b
Faulting module name: igdumd32.dll, version: 8.15.10.1912, time stamp: 0x4aaa8220
Exception code: 0xc0000005
Fault offset: 0x00087b49
Faulting process id: 0x688
Faulting application start time: 0x01ca80437c0eb56a
Faulting application path: C:\Program Files (x86)\Windows Media Player\wmplayer.exe
Faulting module path: C:\Windows\system32\igdumd32.dll
Report Id: 269c4a02-ec37-11de-85d5-00217014b0bd
Since I'm using this for my main Media Center computer, it'd be nice to see if a fix can be had. If any additional information is needed, I'd be happy to provide it.
Has anyone had any luck by rolling back to an earlier version of the drivers maybe?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As we approach the one year anniversary, over 4900 reads of the topic and 0 ideas, suggestions, requests for more information, or offers to assist. The lack of response suggests nobody at Intel is concerned or motivated enough to help find a solution. Is there someone at Intel who can at least respond and explain?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
More than one year later, a new patched Windows 7 SP1 64bit, a newer Intel driver, but still the same problem and no explanation about what causes the problem and what resolves it.
Crashdump:
Problemsignatur:
Problemereignisname: APPCRASH
Anwendungsname: solitaire.exe
Anwendungsversion: 6.1.7600.16385
Anwendungszeitstempel: 4a5bc9f9
Fehlermodulname: igdumd64.dll
Fehlermodulversion: 8.14.10.1930
Fehlermodulzeitstempel: 4aba758c
Ausnahmecode: c0000005
Ausnahmeoffset: 0000000000070c62
Betriebsystemversion: 6.1.7601.2.1.0.768.3
Gebietsschema-ID: 1031
Zusatzinformation 1: cfa9
Zusatzinformation 2: cfa960e6b4c4547a2e547d51c23416cb
Zusatzinformation 3: d3b9
Zusatzinformation 4: d3b9a87ac727b849c019f7ad661c15c0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- I stumbled on a solution. I copied the games folder that was in the Program Files folder to the Program Files (x86) folder, then changed the compatibility to run in Windows 7. They are working now.

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page