Ok, did a few system starts;
Twice with Commodo Def+ disabled, Avast Behaviour Shield on and Sandbox on ... crashed both times.
Twice with Commodo Def+ off and Sandbox off, Avast as above ... fine
Twice with Commodo Def+ enabled, Sandbox disabled, Avast as above ... fine.
There was a third crash but I can't remember the setting of that particular one
You are right, that is probably the conflict. I heard/read about it before but forgot as I never had this problem running the two programmes side by side. What has changed since the last update? Also, Defense+ does not automatically switch off Commodo's Sandbox.
More to the point, what is the solution in your informed opinion? What to run and what not ... .
Thanks and regards
On Sat 16/03/2013 15:55:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031613-25662-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0xA (0x10, 0x2, 0x0, 0xFFFFF80003C9FEE9)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 16/03/2013 15:55:32 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x87752)
Bugcheck code: 0xA (0x10, 0x2, 0x0, 0xFFFFF80003C9FEE9)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sat 16/03/2013 15:50:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031613-25599-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x19 (0x3, 0xFFFFF80003E0DF00, 0xFFFFF80003E0DF00, 0xFFFFFA8005246198)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.