paul w

Hi,
Does anyone know why i get this fault with ie.

Thanks in advance.
Paul

IEXPLORE caused a general protection fault
in module USER.EXE at 0003:00006c50.
Registers:
EAX=00000000 CS=17c7 EIP=00006c50 EFLGS=00000202
EBX=006443d0 SS=3ba7 ESP=0000b4e2 EBP=0000b4e4
ECX=bff53ce6 DS=16cf ESI=0002b562 FS=336f
EDX=00010000 ES=3347 EDI=00000000 GS=0000
Bytes at CS:EIP:
1f c9 ca 0c 00 66 58 5b 66 50 e8 59 fb 55 8b ec
Stack dump:
b4fe1a17 462f07df 1a170092 3ba7b562 00000001 00003ba7 3ba70000 6d2ab51c b56217c7 00013ba7 16cf0000 00005800 00000000 33470002 b5580000 17bf1a8f

ChrisB

Can you reproduce the fault?

What version of Windows and IE?

Chris.

paul w

Hi Chris,

Just happens now and then while on the net,no set pattern or anything. ie6 with win 98.

Cheers Paul

scoobyrob

uninstall ie 6 and go back to 5.5, it runs better under 98. or try reinstalling 6.

rob

paul w

It did it with ie 5 as well and makes no difference after format and new install.

Cheers rob

ChrisB

I'd suspect a hardware issue then. Maybe a flakey memory stick.

kimera

re
Q: What does this mean?
A: Its foooked

kimera

RE:
----------------------------------------------------------------
I'd suspect a hardware issue then. Maybe a flakey memory stick.
----------------------------------------------------------------

Isnt that a new lolly from cadburys

scoobyrob

ok, it does sound like a hardware fault, i would replace the memory first because that is a memory addressing error.


rob

MarkO

Spot the people here who aren't developers, and who know f-all about computers. It's not a memory addressing error, it's simply an unhandled exception.

That's a standard GPF, probably caused by an unchecked buffer or a buffer overrun, as a result of the buffoons who coded Internet Explorer.

I wouldn't worry about it. Sh*t happens, and IE crashes. It's no big deal.

Gordo

mine does it all the time since I put IE6 on Windows 98. ah well, saved me from the growler spotting some grot on the screen by crashing as she came up the stairs (it was like it was trying to help out!).

G

MarkO

Check out Microsoft's MSDN article Q276393 which goes through a whole host of possible explanations for this sort of problem (none of which involve hardware faults or replacing memory ).