EI 7 Crashes with Event ID 1000

[dtweten]

I have a machine that has an application that relies on IE pretty heavily and not every time but often enough to be an issue the app will crash when they try to print from it. They have had this issue happen in IE as well, but it happens more in the app because this is where it happens the most. Originally the issue was with the same event id but it surrounded .net. After adding and removing .net and the app the error no longer surrounds .net. Any ideas on this issue?





Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 4/28/2010
Time: 11:32:36 AM
User: N/A
Computer: NLOBGYNBO1
Description:
Faulting application gmtgc.exe, version 1.0.0.0, faulting module mshtml.dll, version 7.0.6000.16981, fault address 0x00095050.
For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 67 6d 74 ure gmt
0018: 67 63 2e 65 78 65 20 31 gc.exe 1
0020: 2e 30 2e 30 2e 30 20 69 .0.0.0 i
0028: 6e 20 6d 73 68 74 6d 6c n mshtml
0030: 2e 64 6c 6c 20 37 2e 30 .dll 7.0
0038: 2e 36 30 30 30 2e 31 36 .6000.16
0040: 39 38 31 20 61 74 20 6f 981 at o
0048: 66 66 73 65 74 20 30 30 ffset 00
0050: 30 39 35 30 35 30 0d 0a 095050..

 

[rclarke250]

Have you checked this out?

http://support.microsoft.com/kb/917425

 

[dtweten]

Nope, i did not. But the security patch on the machine is newer than the notfix that you can download from the KB article. I am just going to try uninstalling IE7 and reinstalling it. I havent done that yet. Anyother sugjestions or insight?

 

[teqmod]

First thing I would start looking at is the gmtgc.exe app that is given credit for crashing IE. What is this app? Is it something you meant to have running with IE?

 

[dtweten]

gmtgc.exe is an application that uses IE as its core structure. I have not found a solution to this issue and the support for the gmtgc.exe application is of no use. I have just ended up re imaging all the machines that had this issue. Not even sure what caused it at this point in time. I have limited time to devote to this issue.