Norton Internet Security 2013 multiple crashes and incompatibility with Windows 8

Ever since, I have updated to NIS 2013 everything was fine out of the box. However, whenever I open the UI something strange always seems to happen. Some of the symptoms :

a. Clicking scans does not start any scans   -    Instead after like 4 - 10 minutes later, an error message is displayed : "Internal program error"

b. Doing a trust scan caused NIS 2013 to crash upon completion of the scan (After I scrolled down to view what are the programs with low trust) with the following error report in Windows error reporting :

 

Faulting application name: ccSvcHst.exe, version: 12.2.0.8, time stamp: 0x5075eeaf
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000001
Faulting process ID: 0xf98
Faulting application start time: 0x01cdbfd407ec96c4
Faulting application path: C:\Program Files (x86)\Norton Internet Security\Engine\20.2.0.19\ccSvcHst.exe
Faulting module path: unknown
Report ID: a6854dbf-2bed-11e2-be86-4061864cd2e1
Faulting package full name:
Faulting package-relative application ID:

 

c. Randomly but not occasionally, NIS 2013 crashes with no reasons. Only " ... not responding, click to terminate" OR "symantec service framework has stopped working"

 

Error reports:

 

Faulting application name: ccSvcHst.exe, version: 12.2.0.8, time stamp: 0x5075eeaf
Faulting module name: ntdll.dll, version: 6.2.9200.16420, time stamp: 0x505aaa82
Exception code: 0xc000000d
Fault offset: 0x000b0dbd
Faulting process ID: 0x1060
Faulting application start time: 0x01cdbfc475092f74
Faulting application path: C:\Program Files (x86)\Norton Internet Security\Engine\20.2.0.19\ccSvcHst.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report ID: 692aa6bf-2bc5-11e2-be84-4061864cd2e1
Faulting package full name:
Faulting package-relative application ID:

 

Faulting application name: ccSvcHst.exe, version: 12.2.0.8, time stamp: 0x5075eeaf
Faulting module name: ntdll.dll, version: 6.2.9200.16420, time stamp: 0x505aaa82
Exception code: 0xc000000d
Fault offset: 0x000b0dbd
Faulting process ID: 0x1060
Faulting application start time: 0x01cdbfc475092f74
Faulting application path: C:\Program Files (x86)\Norton Internet Security\Engine\20.2.0.19\ccSvcHst.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report ID: 69f15896-2bc5-11e2-be84-4061864cd2e1
Faulting package full name:
Faulting package-relative application ID:

 

Fault bucket , type 0
Event Name: BEX
Response: Not available
Cab Id: 0

Problem signature:
P1: ccSvcHst.exe
P2: 12.2.0.8
P3: 5075eeaf
P4: ntdll.dll
P5: 6.2.9200.16420
P6: 505aaa82
P7: 000b0dbd
P8: c000000d
P9: 00000000
P10:

Attached files:
C:\Users\Userdpm\AppData\Local\Temp\WERE61D.tmp.appcompat.txt
C:\Users\Userdpm\AppData\Local\Temp\WERE67C.tmp.WERInternalMetadata.xml
C:\Users\Userdpm\AppData\Local\Temp\WERE67D.tmp.hdmp
C:\Users\Userdpm\AppData\Local\Temp\WERE95B.tmp.dmp

 

 

 

What I have done :

 

1. Suspecting that this could be a virus, I have done the following measures:

- Scanned with malwarebytes in safe mode

- Scanned with Norton Virus removal tool in safe mode

- Scanned with Kaspersky virus removal tool in safe mode

 

Returned clean results.

 

2. Uninstalled using Norton Removal Tool, restarted and ccleaned it and restarted again. Then redownloaded the entire NIS2013 installer. Problem still persisted

 

3. Disabled performance monitoring. Problem still persisted.

 

4. For the meantime, I have exausted all methods. I have uninstalled NIS 2013 completely and switched on Windows Defender.

 

System specs:

 

Windows 8 Professional X64

AMD Phenom II X 4 955 BE

8GB RAM

Geforce GTX 550 Ti

 

 

Question is, how can something like a security suite be so easily terminated or crashed? It makes me wonder if NIS2013 is really going to be my choice of front line defense. I have been a faithful member of Norton for over 2 years, and these incidents are reminding me of the pre 2009 era where Norton was seriously unstable. 

 

Let me know what I can do further. Maybe I can access some of the dump files stored somewhere that could provide Symantec's engineers with useful information that can help improve their software.