Re-installing IE6 (without all the patches) seemed to have fixed the problem so far... I think I'll install the patches one by one over the weekend, and avoid the anti-S2Ki patch.

 

Here's the culprit:
Cumulative Security Update for Internet Explorer 6 Service Pack 1 (KB918899)

 

I swear, some day they are going to release a not-so-well-tested patch that's going to destroy everyone's machine. There is no way they can regression test the whole code-base each week. It's only a matter of time before someone says "this patch should have no effect on anything else" and pow, 100 million unhappy customers.

 

I was having the same problem after running the latest windows update. I uninstalled KB918899 and everything is fine now.

 

glad that I found this. I had the same problem but didn't want to post anything cause I thought it was just my computer lol. I had a feeling that it had to be something with recent updates cause everything work great til I did my routine update. Thanks to this thread it's confirmed lol. Now I can final start using s2ki again at home instead of at work .

Mike

 

Click This! --> <-- Click This!

 

Stop it, Ian!

 

I have the same thing at work and we just updated the system so I can log on at work then it goes nuts and I have to close it. So no more browsing at work. NSX Prime is fine with no problems, its just s2ki for that matter. No other sites. Ohh well.

 

I'm another that has the problem. Only IE doesn't quite crash... I notice the computer is bogged down and then manually kill the process.

Anyway, it's rather strange it only happens on this site. Do we know of any other sites that use the same software? If so, does the same issue happen there?

 

That's a different problem. IE's CPU utilization will spike to 100% and remain there till it's killed. And it's still happening to me, so the solution mentioned above won't work. It happens when you do certain things you're not supposed to do, like hit ctrl-F to do a search, hit certain mouse buttons, or read a post.

I'm not sure what's causing it exactly though. Do you have a Logitech Mouse, and use the Setpoint driver by any chance? I've noticed that on several occasions, for me, this occurs when I use one of my mouse's custom buttons.

Yup, only happens with S2Ki.com...