hardware or software

STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes: Device driver

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Low\Temporary Internet Files\Content.IE5\ZAB4MTBL\081510-13743-01[1]\081510-13743-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 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82a14000 PsLoadedModuleList = 0x82b5c810
Debug session time: Sat Aug 14 18:48:03.198 2010 (GMT-4)
System Uptime: 0 days 5:33:21.923
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {d884e982, 2, 0, 8de6052c}
Unable to load image \SystemRoot\system32\DRIVERS\kl1.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for kl1.sys
*** ERROR: Module load completed but symbols could not be loaded for kl1.sys
Probably caused by : kl1.sys ( kl1+3b52c )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: d884e982, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8de6052c, address which referenced memory
Debugging Details:
------------------
 
READ_ADDRESS: GetPointerFromAddress: unable to read from 82b7c718
Unable to read MiSystemVaType memory at 82b5c160
 d884e982 
CURRENT_IRQL:  2
FAULTING_IP: 
kl1+3b52c
8de6052c 393c18          cmp     dword ptr [eax+ebx],edi
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  avp.exe
TRAP_FRAME:  8a3e5680 -- (.trap 0xffffffff8a3e5680)
ErrCode = 00000000
eax=d884e95e ebx=00000024 ecx=d884e966 edx=85c49e00 esi=85c49df8 edi=84da3b28
eip=8de6052c esp=8a3e56f4 ebp=8a3e575c iopl=0         nv up ei ng nz ac po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010292
kl1+0x3b52c:
8de6052c 393c18          cmp     dword ptr [eax+ebx],edi ds:0023:d884e982=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from 8de6052c to 82a5a82b

As you already mentioned, the BSOd was caused by a driver associated with your AntiVirus. Please uninstall using the uninstall tool and replace with Microsoft Security Essentials, Malwarebyes and the Windows Firewall. This should resolve the problem
If applicable to your antivius this tool should be used
http://support.kaspersky.com/faq/?qid=208279463

Remember, the dump files are like a road map, but they stop just short of the final goal. If the BSOD continue, we can use both reports to get even closer to preventing the problem, but I think that the A/V uninstall will solve your problem