New build: IE crashes on certain pages

[sempur]

I just build a new computer, Asus P5E-VM HDMI and E6750. Installed XP+SP2 and the newest drivers. Used Automatic Updates to update windows, except for IE7. Zonealarm and NOD32 is also installed.

Problem is that IE crashes on certain pages with message that says 'Instruction at xxxxxx tried to access memory at yyyyyyyyy. Memory could not be read'

It happens when I visit picasa.google.com or www.google.com/talk.

It also happens when I visit google.com, make a search for either picasa or gtalk and then visit the site.

BUT if I visit adobe.com and then picasa.google.com it works.

I tried to alter security settings in IE to high, so all scripts are disabled, and then the sites work. When restoring security settings it crashes.

I have installed Firefox, which works perfect so far, but I would like to get this problem fixed. It looks to be some javascript thing that causes this, but how can I fix it ?

I don't know if it could be some of the drivers causing this, so one thing to try, would be a new clean install of XP + SP2 + LAN-driver, to see if the error is still there, but I would prefer to avoid that if possible at all.

So, has anybody experienced a crash like this ?

 

[AnnonUSA]

Add this key to your registry - should solve the problem.


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_PROTECT_DECOMPRESSION_FILTER_FROM_ABORT_KB942367]
"*"=dword:00000001

 

[Harvey]

Have you installed all critical updates to Windows? There was a recent update that caused IE to crash, followed a few days later by a patch for that problem.

 

[cubby1223]

That error message is almost always from a 3rd party toolbar or another IE add-on.

Also, if you haven't done so already, grab the newest version of Java from http://www.java.com and the newest version of flash from http://www.adobe.com - if that's your problem, then great you've fixed it, but if not, at least you have them updated anyways.

 

[sempur]

Thank you. You just saved me at least 10 hours of testing and installing.

Of course it was one of the windows updates that caused the problem, but installing KB946627 seems to have solved the problem. The KB946627 does the same as AnnonUSA suggested.

So, on a sidenote, how do you keep track of problems with windows update. I did a lot of searching, but 'IE crash javascript' returns too many hits.

Anyway, I'm happy now