Need info on memory debug

I did a memory debug and I found out what seems to be crashing my system but I dunno what it is maybe you can help
Heres the info on the dump


Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini051406-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Sun May 14 11:23:41.031 2006 (GMT-5)
System Uptime: 0 days 0:04:03.560
Loading Kernel Symbols
...................................................................................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, b10a2ae5, b1cb4b0c, 0}

*** WARNING: Unable to verify timestamp for khips.sys
*** ERROR: Module load completed but symbols could not be loaded for khips.sys
Unable to load image \??\C:\Program Files\ewido anti-malware\guard.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for guard.sys
*** ERROR: Module load completed but symbols could not be loaded for guard.sys
Probably caused by : khips.sys ( khips+1bbc )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: b10a2ae5, The address that the exception occurred at
Arg3: b1cb4b0c, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
+ffffffffb10a2ae5
b10a2ae5 ?? ???

TRAP_FRAME: b1cb4b0c -- (.trap ffffffffb1cb4b0c)
Unable to read trap frame at b1cb4b0c

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from b10a3f2c to b10a2ae5

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
b1cb4b7c b10a3f2c 00390004 00390000 00390000 0xb10a2ae5
b1cb4b90 b1bd8bbc ffffffff 00390000 00390004 0xb10a3f2c
b1cb4bf8 805c6612 00000330 00000178 00000000 khips+0x1bbc
b1cb4c1c 805c713c 00000001 00000007 8231b020 nt!PspExitProcess+0x5e
b1cb4cc8 805c73d0 00000000 8231b020 00000000 nt!PspExitThread+0x5ae
b1cb4ce8 805c75ab 8231b020 00000000 b1cb4d64 nt!PspTerminateThreadByPointer+0x52
b1cb4d14 f7cda683 00000000 00000000 b1cb4d64 nt!NtTerminateProcess+0x105
b1cb4d54 8053c808 ffffffff 00000000 0007fee4 guard+0x683
b1cb4d54 7c90eb94 ffffffff 00000000 0007fee4 nt!KiFastCallEntry+0xf8
0007fee4 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
khips+1bbc
b1bd8bbc ?? ???

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 2

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: khips+1bbc

MODULE_NAME: khips

IMAGE_NAME: khips.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 43a1f5df

FAILURE_BUCKET_ID: 0x8E_khips+1bbc

BUCKET_ID: 0x8E_khips+1bbc

Followup: MachineOwner

 

Got Kerio firewall? Looks like its malfunctioning, crashing you.

 

Yeah, been happening since ive installed it coincidentally, ill uninstall it and thanks