Bluescreen probleme bei NIS 2011

Hallo, 

seit Installation von NIS 2011 habe ich Bluescreens.

System: win7 prof. 32 bit / intel atom z550 2gb ram /  ssd 256gb 

 

bitte lösen Sie das problem ASAP.

 

mfg

m. ernst 

 

hier die minidumps:

 

Spoiler (Zum Lesen markieren)
On Sun 14.08.2011 22:09:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081511-19999-01.dmp
This was probably caused by the following module: srtsp.sys (SRTSP+0x38FDD)
Bugcheck code: 0xC5 (0x8320004, 0x2, 0x0, 0xFFFFFFFF82D3C7FF)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\System32\Drivers\NIS\1206000.01D\SRTSP.SYS
product: AutoProtect
company: Symantec Corporation
description: Symantec AutoProtect
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: srtsp.sys (Symantec AutoProtect, Symantec Corporation).

On Sun 14.08.2011 22:09:20 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: srtsp.sys (SRTSP+0x38FDD)
Bugcheck code: 0xC5 (0x8320004, 0x2, 0x0, 0xFFFFFFFF82D3C7FF)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\System32\Drivers\NIS\1206000.01D\SRTSP.SYS
product: AutoProtect
company: Symantec Corporation
description: Symantec AutoProtect
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: srtsp.sys (Symantec AutoProtect, Symantec Corporation).

[weshalb der eine BSOD doppelt aufgeführt wurde (vom program WhoCrashed), weiß ich nicht)

On Mon 18.07.2011 22:18:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071911-81962-01.dmp
This was probably caused by the following module: navex15.sys (NAVEX15+0x3C826)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFFB5072826, 0xFFFFFFFFAE67A2B8, 0xFFFFFFFFAE679E90)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\Definitions\VirusDefs\20110813.002\NAVEX15.SYS
product: Symantec Antivirus Engine
company: Symantec Corporation
description: AV Engine
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: navex15.sys (AV Engine, Symantec Corporation).

 -------------- 
On Sun 14.08.2011 22:09:20 GMT your computer crashedcrash dump file: C:\Windows\Minidump\081511-19999-01.dmpThis was probably caused by the following module: srtsp.sys (SRTSP+0x38FDD)Bugcheck code: 0xC5 (0x8320004, 0x2, 0x0, 0xFFFFFFFF82D3C7FF)Error: DRIVER_CORRUPTED_EXPOOLfile path: C:\Windows\System32\Drivers\NIS\1206000.01D\SRTSP.SYSproduct: AutoProtectcompany: Symantec Corporationdescription: Symantec AutoProtectBug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: srtsp.sys (Symantec AutoProtect, Symantec Corporation).On Sun 14.08.2011 22:09:20 GMT your computer crashedcrash dump file: C:\Windows\memory.dmpThis was probably caused by the following module: srtsp.sys (SRTSP+0x38FDD)Bugcheck code: 0xC5 (0x8320004, 0x2, 0x0, 0xFFFFFFFF82D3C7FF)Error: DRIVER_CORRUPTED_EXPOOLfile path: C:\Windows\System32\Drivers\NIS\1206000.01D\SRTSP.SYSproduct: AutoProtectcompany: Symantec Corporationdescription: Symantec AutoProtectBug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: srtsp.sys (Symantec AutoProtect, Symantec Corporation).[weshalb der eine BSOD doppelt aufgeführt wurde (vom program WhoCrashed), weiß ich nicht)On Mon 18.07.2011 22:18:29 GMT your computer crashedcrash dump file: C:\Windows\Minidump\071911-81962-01.dmpThis was probably caused by the following module: navex15.sys (NAVEX15+0x3C826)Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFFB5072826, 0xFFFFFFFFAE67A2B8, 0xFFFFFFFFAE679E90)Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_Mfile path: C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\Definitions\VirusDefs\20110813.002\NAVEX15.SYSproduct: Symantec Antivirus Enginecompany: Symantec Corporationdescription: AV EngineBug check description: This indicates that a system thread generated an exception which the error handler did not catch.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: navex15.sys (AV Engine, Symantec Corporation). --------------