Iron Causing BSOD on Closing

[be4con]

I've had to reluctantly uninstall Iron because it has caused my system to become very unstable. I have found that if I have been browsing for a long time then when I close Iron it causes a BSOD.

Analysis of the crash dump each time implicates iron.exe as the cause of the problem.

Has anyone else had similar issues? If so how have they solved them?

Thanks

[Udy]

It can be,
1. Bad Drivers. When was the last time you updated them?
2. Malicious Software - viruses and such. When was the last time you scanned for them?
3. Norton or other malfunctioning antivirus.
4. Dying hardware.

[be4con]

Thanks for the reply.

I use Driver Genius Professional to keep my drivers up to date. I scan for them every couple of weeks.

I have a plethora of security on my system including Avast Professional, Adaware, Spybot SD and Spware Blaster. I scan for malware and viruses weekly. My system is malware free.

I don't have Norton - Avast is not malfunctioning as far as I am aware.

My PC has just been fully checked over at a store within the last 2 weeks and there are no malfunctioning components.

Iron is the problem as far as anyone can tell.

[Udy]

Thanks for the reply.

I use Driver Genius Professional to keep my drivers up to date. I scan for them every couple of weeks.

I have a plethora of security on my system including Avast Professional, Adaware, Spybot SD and Spware Blaster. I scan for malware and viruses weekly. My system is malware free.

I don't have Norton - Avast is not malfunctioning as far as I am aware.

My PC has just been fully checked over at a store within the last 2 weeks and there are no malfunctioning components.

Iron is the problem as far as anyone can tell.

Jeez, talk about being paranoid.
Microsoft security essentials + adblock, that is all you need at most.
Unless you surf shady websites or something...

So they ran a CPU stress test, GPU stress test, and checked for memory errors? Right? Or did they just rip you off?
Also, I don't know why you paid anyone to test your hardware, you can stress test and check memory yourself.

Are your Vista/7 updated? Make sure you grab the latest updates, it might fix your issues.

Also what about addons? Flash? Java? Adobe Reader? Whatever? Those might be the cause of your problems.
Try removing them and see if your problem goes away. Also make sure you have the latest versions.

[be4con]

Thanks for the reply.

Not paranoid, but once bitten twice shy.

I had a hardware fault which I couldn't diagnose myself. The guys at my local store who I know well diagnosed and cured the fault, replaced the faulty GPU and memory and stress tested the machine for me, yes. I didn't pay them to test it, I paid them to resolve an issue I couldn't resolve.

I'm running XP, it's up to date.

I don't use adobe, I use google docs. I have flash disabled, Java is up to date.

Since I uninstalled Iron no more BSOD.

[uibo]

Hello!

I am having the same problem.

I noticed it after upgrading iron to v8.0.555.0, radeon catalyst to 10.12 from 10.2 and updating my Realtek integrated audio drivers. I could revert back to another version of drivers but i had issues with them in an other app.

Orthos and ATI tool traytools stress tests show no errors.

windbg shows
BugCheck 1000008E, {c0000005, bf953e10, a902dc00, 0}

Probably caused by : win32k.sys ( win32k!GreGetGlyphIndicesW+af )

for the las 2 times. I also added an more detailed minidump analysis that has PROCESS_NAME: iron.exe in it.

be4con what kind of a gfx card do you have?

I have a Gigabyte HD4850 512MB

Pentium E2160
Biostart TP35-D2A7
2GB A-Data
Windows XP PRO 23-bit

[uibo]

It seems that I can't attach txt documents.

Code: Select all

Here's the content:


0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bf953e10, The address that the exception occurred at
Arg3: a902dc00, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP: 
win32k!GreGetGlyphIndicesW+af
bf953e10 8b4004          mov     eax,dword ptr [eax+4]

TRAP_FRAME:  a902dc00 -- (.trap 0xffffffffa902dc00)
ErrCode = 00000000
eax=00000000 ebx=00000100 ecx=000000b9 edx=e2d87404 esi=e1bf2000 edi=e2d87008
eip=bf953e10 esp=a902dc74 ebp=a902dc8c iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
win32k!GreGetGlyphIndicesW+0xaf:
bf953e10 8b4004          mov     eax,dword ptr [eax+4] ds:0023:00000004=????????
Resetting default scope

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  iron.exe

LAST_CONTROL_TRANSFER:  from bf94b49d to bf953e10

STACK_TEXT:  
a902dc8c bf94b49d e2a0b9c8 e1bf2200 e12d8d08 win32k!GreGetGlyphIndicesW+0xaf
a902dd28 bf94b519 4d010cf1 0012d8c0 00000100 win32k!NtGdiGetGlyphIndicesWInternal+0xf2
a902dd48 8054164c 4d010cf1 0012d8c0 00000100 win32k!NtGdiGetGlyphIndicesW+0x1b
a902dd48 7c90e514 4d010cf1 0012d8c0 00000100 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
4d010cf1 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!GreGetGlyphIndicesW+af
bf953e10 8b4004          mov     eax,dword ptr [eax+4]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!GreGetGlyphIndicesW+af

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4cc6d6a2

FAILURE_BUCKET_ID:  0x8E_win32k!GreGetGlyphIndicesW+af

BUCKET_ID:  0x8E_win32k!GreGetGlyphIndicesW+af

Followup: MachineOwner
---------