ADMIN UPDATE:

32-bit versions of Internet Explorer were crashing after Intrusion Prevention System (IPS) 20150220.001 definition package was applied to their Norton Products. We have released a fix for this issue through our LiveUpdate servers. See the Security Response Blog Article for more information.

Running NIS on Windows 7 Pro 64-bit with IE11 (latest updated). Sometime this evening, IE11 started crashing. In fact, it crashed an already-open browsing session, and now trying to start it up just instantly causes a "Internet Explorer Has Stopped Working" error.

Tried resetting IE11 settings to default. No change. Tried running IE11 in no-addons mode. No change. The error is shown as the following:

Source

Internet Explorer Summary

Stopped working Date

‎20/‎02/‎2015 11:09 PM Status

Report sent Description

Faulting Application Path: C:\Program Files (x86)\Internet Explorer\iexplore.exe Problem signature

Problem Event Name: BEX

Application Name: IEXPLORE.EXE

Application Version: 11.0.9600.17631

Application Timestamp: 54b31a70

Fault Module Name: IPSEng32.dll

Fault Module Version: 14.2.1.9

Fault Module Timestamp: 54c8223b

Exception Offset: 000c61e2

Exception Code: c0000417

Exception Data: 00000000

OS Version: 6.1.7601.2.1.0.256.48

Locale ID: 4105

Additional Information 1: 4f07

Additional Information 2: 4f072c04aa91eb87d88d7dd565652530

Additional Information 3: a15b

Additional Information 4: a15b24e56acca2f6a7c59c85b7f20aea Extra information about the problem

Bucket ID: 204937294

Now, IPSEng32.dll is a Norton file. So I uninstalled NIS. Bingo - IE11 started working like normal. Re-downloaded and re-installed NIS. At the outset (said last updated 20 hours ago) IE11 worked fine. Then it auto-updated and applied a patch... and instantly IE11 stopped working again. Ergo, something Norton did is breaking my IE11. Doesn't seem to have affected another computer I have running IE10.

Any ideas?

EDIT: The other IE10 PC had been asleep and hadn't updated NIS yet. It is also now crashing in exactly the same manner as this one... and since that PC is almost entirely unrelated to this one in terms of software being used, this is going to be a bigger problem than just me.