Re: NIS2012 crashing with changes in firewall

Nicksecur · ‎04-22-2012

i forgot the mention that i came on this threat searching on the systems in the eventviewer.

The faulting module is exactly the same as with the older builds of NSIS2012:

Faulting module name: SYMHTML.DLL, version: 6.5.0.23, time stamp: 0x4ee5934c
Exception code: 0xc0000005

rh · ‎06-18-2008

Well, I was feeling so alone and bummed out because I couldn't get the crash but then...

after adding more custom rules this morning (I think I was at 130-140), I was about to give up. Then I remembered I forgot to turn off the advanced option "automatic program control". After doing that I clicked on the configure link to open the list of controlled programs and got the crash. Presumably the offending code is not encountered until automatic program control is actually turned off. Now I feel better, in a very sick and twisted way!

I can certainly understand the frustration here as this seems to nearly kill all of NIS and leave you with little or no control and no idea if you're even still being protected. I was able to browse web sites but accessing the Notron controls from the browser resulted in the attached dialog.

Problem signature:
Problem Event Name:   APPCRASH
Application Name:   ccSvcHst.exe
Application Version:   11.2.1.4
Application Timestamp:   4f14f6a9
Fault Module Name:   SYMHTML.DLL
Fault Module Version:   6.5.0.23
Fault Module Timestamp:   4ee5934c
Exception Code:   c0000005
Exception Offset:   0012911d
OS Version:   6.1.7600.2.0.0.768.3
Locale ID:   1033
Additional Information 1:   0a9e
Additional Information 2:   0a9e372d3b4ad19135b953a78882e789
Additional Information 3:   0a9e
Additional Information 4:   0a9e372d3b4ad19135b953a78882e789

From the event log:

Faulting application name: ccSvcHst.exe, version: 11.2.1.4, time stamp: 0x4f14f6a9
Faulting module name: SYMHTML.DLL, version: 6.5.0.23, time stamp: 0x4ee5934c
Exception code: 0xc0000005
Fault offset: 0x0012911d
Faulting process id: 0x5b0
Faulting application start time: 0x01cd20a59415b5d3
Faulting application path: C:\Program Files (x86)\Norton Internet Security\Engine\19.6.2.10\ccSvcHst.exe
Faulting module path: C:\Program Files (x86)\Norton Internet Security\Engine\19.6.2.10\SYMHTML.DLL
Report Id: 28b38665-8c99-11e1-b4ba-000c29640921

P.S. Hey Tony, I'm looking for a job if you guys need any help!

gwm · ‎01-16-2012

Welcome to the support site!!! Have you enjoyed "Further Assistance?

Nicksecur · ‎04-22-2012

Yes, i did. No installation errors found

rh · ‎06-18-2008

138...

...a rather odd limit. YMMV. After I got over 100, I painstakingly added one at a time, going back to the Settings dialog, clicking on Program Control and making sure the list reappeared. After adding #139 and clicking OK. Clicking on Program Control hung and eventually crashed. Rebooted, get back to the Settings dialog, click on Program Control, still hangs.

rh · ‎06-18-2008

19.7.0.9 (2012) - no difference, but none was really expected.

At least the gadget goes grey after the crash. Letting you know that your level of protection is in sort of a grey area

AstroMax · ‎09-17-2008

As Symantec is not able to fix this BUG after SEVERAL MONTHS, how can we trust ALL their software?????????????

jmason · ‎11-18-2011

You can't and you don't.

I believe the real issue here is not the trustworthiness of the software. We all understand bugs almost always exist. And with all kinds of computer system the software is installed in, the problems will eventually come out. The real issue here is the product or customer support of Symantec/Norton, if the support exists anyway. Do you call some guy over the phone who only knows how to tell you to keep reintalling the software "support?"

Some of you have - again - been faithfully reporting your problems in this thread. I guess you are doing so thinking that you can help the company resolve the problems sooner. That's what I did exactly several months ago. Effectively, you have only been piling up more dirt about Symantec/Norton products here. The fact that this thread continues to grow only proves that our problems still exist, despite their being reported in various ways by so many individuals over time in this official company forum.

It is likely that our feedbacks and complaints about their products are not being treated as seriously as we had hoped. From the looks of things, it seems our cases are being treated like those of some backwater hick town folks. Meaning, they will still promote and sell NIS 2013 or more newer versions however long this thread becomes. And the people who created our problems will still get compensated for their handy work.

This is why in the earlier message (#176) I pointed out that we should started posting links to this thread in other Internet media to let more people know how Symantec/Norton treats its customers who have serious problems with its products, and why they should have second thoughts about joining our bandwagon should they be tempted by false advertisements.