Norton 2011 and Application Crashes/Not Responding

Hi,

 

Ever since installing N.I.S. 2011, the following has been happening:

 

- I.E.8 has Stopped Responding and needs to Close most of the Tabs that are Open upon Opening I.E.8.

 

- Malwarebytes' Anti-Malware is Crashing so cannot Complete a Full Scan.

 

 

WINDOWS7.

 

 

 

Hi Floating_Red:

 

You will have to do a bit of troubleshooting.  I'm not seeing any of these problems on my home machine, Win 7, IE8, MBAM.  Is there any information of note in event viewer?

Hi, delphinium,

 

Yes, there are Errors in Event Viewer and it appears I.D.S. is causing the Error with I.E. with regard to the application Stop Responding. 

 

When Scanning with Malwarebytes', am not sure what part of Norton is causing Malwarebytes' to Crash.

 

Can Send you a P.M. if you wish with Screen Shots if that would be helpful; please let me know.

 

 

 

I'm not sure what kind of help I might be, even with screen shots.  Do the initials stand for Intrusion Detection System?

Was just in case you wanted some, some could be created.  Intrusion Detection System, yes. 

 

Thanks for replying; I welcome any more comments or suggestions, thanks.

 

 

Is it possible that that software is conflicting with Norton?  I am not familiar with it.  Is it a Windows app or is it a third party app.

Sorry, what software...?  Don't quite understand what you mean...

 

 

 

Hello Delph

 

Some call it Intrusion prevention system, so therefore IPS and others call it IDS. They both refer to the same intrusion prevention definitions and the same thing.

Just wish to confirm that the issue with I.E. is still happening; not sure about Malwarebytes' since I've stopped using it.

 

 

 

 


Floating_Red wrote:

Hi, delphinium,

 

Yes, there are Errors in Event Viewer and it appears I.D.S. is causing the Error with I.E. with regard to the application Stop Responding. 

 

When Scanning with Malwarebytes', am not sure what part of Norton is causing Malwarebytes' to Crash.

 

Can Send you a P.M. if you wish with Screen Shots if that would be helpful; please let me know.

 

 

 


What sorts of events are you seeing in Event Viewer that lead you to suspect IDS? Are there any events in the Norton Error Reporting section of your Security History?

 

Hi Reese

 

The Windows 'Problem Reports and Solutions' application is probably a quicker way to identify the module causing the fault in IE8 and Malwarebytes.

 

(Vista/Windows 7) 

Start > Problem Reports and Solutions > View problem history

 

I've only had one Norton-related IE8 crash; the majority of the other IE8 crashes in the Problem History are Adobe Flash related!

 

Here are the details:

 

APPCRASH IE8 ccIPC.jpg

 

Corresponding Norton Error Report:

 

Date & Time14/11/2010 22:00
RiskInfo
ActivityNorton Error Reporting Submission
StatusSubmitted
Error TypeApplication Failure
Error TimeSunday, 14 November 2010 8:28 PM
Error ID{887546DE-21F9-43BA-81F5-A44EBF20E20F}
Error Class0xD22E5CA1
Product NameNorton Internet Security
Product Version18.1.0.37
Process ID0x1EE8
Thread ID0x840
Process Nameiexplore
Process Version8.0.6001.18975
Process TimestampWednesday, 8 September 2010 4:27 AM
Module NameccIPC
Module Version10.0.1.8
Module TimestampFriday, 23 July 2010 5:01 AM
Module Offset0x182DE
Hash Code0xDAB0BA7B
Exception Code0xC0000005

 

Yes, there are many Errors in the "Norton Error Reporting"; in fact, there are multiple Errors multiple times a day, with the Process "iexplore", and many of them listing "IPSBHO" as the "Module Name".

 

 

 


Floating_Red wrote:

Yes, there are many Errors in the "Norton Error Reporting"; in fact, there are multiple Errors multiple times a day, with the Process "iexplore", and many of them listing "IPSBHO" as the "Module Name".

 

 


If you can right-click on one of the entries and copy it to your clipboard and then paste it into a response I can research it further...

 

This is the first time I've seen this one:

 

Category: Norton Error Reporting
Date & Time,Risk,Activity,Status,Error Type,Error Time,Error ID,Error Class,Product Name,Product Version,Process ID,Thread ID,Process Name,Process Version,Process Timestamp,Module Name,Module Version,Module Timestamp,Module Offset,Hash Code,Exception Code,Error File
29/11/2010 15:44,Info,Norton Error Reporting Submission,Submitted,Application Failure, November 27, 2010; 09:39,{97EE924E-6785-4362-A6CB-58FB178DF785},0xDF138C24,Norton Internet Security,18.1.0.37,0x14A4,0x1478,iexplore,8.0.7600.16671,08 September 2010 02:49,SymHTML,5.1.0.1,30 June 2010 09:11,0x2D880,0x753BAE43,0xC0000005,"C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\CmnClnt\ErrorInstances\DF138C24\97EE924E-6785-4362-A6CB-58FB178DF785.dat, C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\ErrorManagement\Queue\Incoming\SQ_{990A4451-09AF-4508-8AA7-F9E9D322589D}\iexplore.exe.5284.dmp, C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\ErrorManagement\Queue\Incoming\SQ_{990A4451-09AF-4508-8AA7-F9E9D322589D}\{E6A95E34-975D-4739-AF96-11DF8C6DDA5A}.etl, C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\ErrorManagement\Queue\Incoming\SQ_{990A4451-09AF-4508-8AA7-F9E9D322589D}\SQ_{44240B63-ED0F-4D12-9529-68C522F7C7EC}.plist"


 

Category: Norton Error Reporting
Date & Time,Risk,Activity,Status,Error Type,Error Time,Error ID,Error Class,Product Name,Product Version,Process ID,Thread ID,Process Name,Process Version,Process Timestamp,Module Name,Module Version,Module Timestamp,Module Offset,Hash Code,Exception Code,Error File
29/11/2010 15:44,Info,Norton Error Reporting Submission,Submitted,Application Failure,27 November, 2010; 09:31,{D0D7B58A-E75D-4129-87F1-8D6D43034440},0xB7E4BB96,Norton Internet Security,18.1.0.37,0x9BC,0xAB8,iexplore,8.0.7600.16671,08 September 2010 02:49,IPSBHO,9.2.0.97,16 May 2010 00:06,0x4BAB,0x27B64DE8,0xC0000005,"C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\CmnClnt\ErrorInstances\B7E4BB96\D0D7B58A-E75D-4129-87F1-8D6D43034440.dat, C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\ErrorManagement\Queue\Incoming\SQ_{25CEFA7D-0837-4DBA-BC47-072D531CF917}\iexplore.exe.2492.dmp, C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\ErrorManagement\Queue\Incoming\SQ_{25CEFA7D-0837-4DBA-BC47-072D531CF917}\{0E413C4B-32A6-46C2-9C90-019626E5A5D9}.etl, C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\ErrorManagement\Queue\Incoming\SQ_{25CEFA7D-0837-4DBA-BC47-072D531CF917}\SQ_{43B6EE16-93FC-4EFC-8CB4-9BFBF5829FB6}.plist"


 

elsewhere,

 

Thanks for providing the 887546de-21f9-43ba-81f5-a44ebf20e20f event id. I'm looking into it. This error was a crash. It's the only Norton crash that I see from this machine during the past month.

 

One of the three more recent errors from this machine should be fixed in the next update and the other two (which are the same) are being researched but probably will not be resolved in the next update.

 

 


Floating_Red wrote:

This is the first time I've seen this one:

 

Category: Norton Error Reporting
Date & Time,Risk,Activity,Status,Error Type,Error Time,Error ID,Error Class,Product Name,Product Version,Process ID,Thread ID,Process Name,Process Version,Process Timestamp,Module Name,Module Version,Module Timestamp,Module Offset,Hash Code,Exception Code,Error File
29/11/2010 15:44,Info,Norton Error Reporting Submission,Submitted,Application Failure, November 27, 2010; 09:39,{97EE924E-6785-4362-A6CB-58FB178DF785},0xDF138C24,Norton Internet Security,18.1.0.37,0x14A4,0x1478,iexplore,8.0.7600.16671,08 September 2010 02:49,SymHTML,5.1.0.1,30 June 2010 09:11,0x2D880,0x753BAE43,0xC0000005,"C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\CmnClnt\ErrorInstances\DF138C24\97EE924E-6785-4362-A6CB-58FB178DF785.dat, C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\ErrorManagement\Queue\Incoming\SQ_{990A4451-09AF-4508-8AA7-F9E9D322589D}\iexplore.exe.5284.dmp, C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\ErrorManagement\Queue\Incoming\SQ_{990A4451-09AF-4508-8AA7-F9E9D322589D}\{E6A95E34-975D-4739-AF96-11DF8C6DDA5A}.etl, C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\ErrorManagement\Queue\Incoming\SQ_{990A4451-09AF-4508-8AA7-F9E9D322589D}\SQ_{44240B63-ED0F-4D12-9529-68C522F7C7EC}.plist"

 


Yes, this looks like the first time that that this machine has encountered this problem. Attempts to reproduce this in-house have been unsuccessful. If you start seeing this some more we'd like to work with you on this...

 


reese_anschultz wrote:

 


Floating_Red wrote:

This is the first time I've seen this one:

 

Category: Norton Error Reporting
Date & Time,Risk,Activity,Status,Error Type,Error Time,Error ID,Error Class,Product Name,Product Version,Process ID,Thread ID,Process Name,Process Version,Process Timestamp,Module Name,Module Version,Module Timestamp,Module Offset,Hash Code,Exception Code,Error File
29/11/2010 15:44,Info,Norton Error Reporting Submission,Submitted,Application Failure, November 27, 2010; 09:39,{97EE924E-6785-4362-A6CB-58FB178DF785},0xDF138C24,Norton Internet Security,18.1.0.37,0x14A4,0x1478,iexplore,8.0.7600.16671,08 September 2010 02:49,SymHTML,5.1.0.1,30 June 2010 09:11,0x2D880,0x753BAE43,0xC0000005,"C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\CmnClnt\ErrorInstances\DF138C24\97EE924E-6785-4362-A6CB-58FB178DF785.dat, C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\ErrorManagement\Queue\Incoming\SQ_{990A4451-09AF-4508-8AA7-F9E9D322589D}\iexplore.exe.5284.dmp, C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\ErrorManagement\Queue\Incoming\SQ_{990A4451-09AF-4508-8AA7-F9E9D322589D}\{E6A95E34-975D-4739-AF96-11DF8C6DDA5A}.etl, C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\ErrorManagement\Queue\Incoming\SQ_{990A4451-09AF-4508-8AA7-F9E9D322589D}\SQ_{44240B63-ED0F-4D12-9529-68C522F7C7EC}.plist"

 


Yes, this looks like the first time that that this machine has encountered this problem. Attempts to reproduce this in-house have been unsuccessful. If you start seeing this some more we'd like to work with you on this...

 


Thanks, reese.  I'd be happy to work with the team just now, so please let me know if the team changes their mind on this.  Obviously there must be a reason why the team don't want to work on it just now, but please let me know if anything does change.

 

 

 


Floating_Red wrote:

Category: Norton Error Reporting
Date & Time,Risk,Activity,Status,Error Type,Error Time,Error ID,Error Class,Product Name,Product Version,Process ID,Thread ID,Process Name,Process Version,Process Timestamp,Module Name,Module Version,Module Timestamp,Module Offset,Hash Code,Exception Code,Error File
29/11/2010 15:44,Info,Norton Error Reporting Submission,Submitted,Application Failure,27 November, 2010; 09:31,{D0D7B58A-E75D-4129-87F1-8D6D43034440},0xB7E4BB96,Norton Internet Security,18.1.0.37,0x9BC,0xAB8,iexplore,8.0.7600.16671,08 September 2010 02:49,IPSBHO,9.2.0.97,16 May 2010 00:06,0x4BAB,0x27B64DE8,0xC0000005,"C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\CmnClnt\ErrorInstances\B7E4BB96\D0D7B58A-E75D-4129-87F1-8D6D43034440.dat, C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\ErrorManagement\Queue\Incoming\SQ_{25CEFA7D-0837-4DBA-BC47-072D531CF917}\iexplore.exe.2492.dmp, C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\ErrorManagement\Queue\Incoming\SQ_{25CEFA7D-0837-4DBA-BC47-072D531CF917}\{0E413C4B-32A6-46C2-9C90-019626E5A5D9}.etl, C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\ErrorManagement\Queue\Incoming\SQ_{25CEFA7D-0837-4DBA-BC47-072D531CF917}\SQ_{43B6EE16-93FC-4EFC-8CB4-9BFBF5829FB6}.plist"

 


Symantec is aware of this issue and believe that there is a fix. I'm looking into when it is expected to be deployed.

 

 


Floating_Red wrote:

reese_anschultz wrote:

 


Floating_Red wrote:

This is the first time I've seen this one:

 

Category: Norton Error Reporting
Date & Time,Risk,Activity,Status,Error Type,Error Time,Error ID,Error Class,Product Name,Product Version,Process ID,Thread ID,Process Name,Process Version,Process Timestamp,Module Name,Module Version,Module Timestamp,Module Offset,Hash Code,Exception Code,Error File
29/11/2010 15:44,Info,Norton Error Reporting Submission,Submitted,Application Failure, November 27, 2010; 09:39,{97EE924E-6785-4362-A6CB-58FB178DF785},0xDF138C24,Norton Internet Security,18.1.0.37,0x14A4,0x1478,iexplore,8.0.7600.16671,08 September 2010 02:49,SymHTML,5.1.0.1,30 June 2010 09:11,0x2D880,0x753BAE43,0xC0000005,"C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\CmnClnt\ErrorInstances\DF138C24\97EE924E-6785-4362-A6CB-58FB178DF785.dat, C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\ErrorManagement\Queue\Incoming\SQ_{990A4451-09AF-4508-8AA7-F9E9D322589D}\iexplore.exe.5284.dmp, C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\ErrorManagement\Queue\Incoming\SQ_{990A4451-09AF-4508-8AA7-F9E9D322589D}\{E6A95E34-975D-4739-AF96-11DF8C6DDA5A}.etl, C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\ErrorManagement\Queue\Incoming\SQ_{990A4451-09AF-4508-8AA7-F9E9D322589D}\SQ_{44240B63-ED0F-4D12-9529-68C522F7C7EC}.plist"

 


Yes, this looks like the first time that that this machine has encountered this problem. Attempts to reproduce this in-house have been unsuccessful. If you start seeing this some more we'd like to work with you on this...

 


Thanks, reese.  I'd be happy to work with the team just now, so please let me know if the team changes their mind on this.  Obviously there must be a reason why the team don't want to work on it just now, but please let me know if anything does change.

 

 


 

It's not a matter of being willing to work on it. In fact, the team is working on it but the information that we have received via the Norton Error Reporting isn't sufficient to understand the source of this problem. Nobody has been able to reproduce this on-demand, either in-house or externally, so we can't gather more information to help solve the problem.

 

As I said before, if you start seeing more instances of this with the same module name and module offset we can set up some instrumentation on your machine that should enable us to find the source of the issue.