Windows 7: BSOD - Lenovo T500

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\061911-26379-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;srv*e:\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 Personal
Built by: 7600.16792.x86fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0x82a4c000 PsLoadedModuleList = 0x82b94810
Debug session time: Sun Jun 19 22:23:44.499 2011 (GMT-4)
System Uptime: 0 days 0:06:16.324
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
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
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000006, 82a8a7b3, 947c0a00, 0}

*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
Probably caused by : kl1.sys ( kl1+1cc272 )

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

0: 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: c0000006, The exception code that was not handled
Arg2: 82a8a7b3, The address that the exception occurred at
Arg3: 947c0a00, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

FAULTING_IP: 
nt!memcpy+33
82a8a7b3 f3a5            rep movs dword ptr es:[edi],dword ptr [esi]

TRAP_FRAME:  947c0a00 -- (.trap 0xffffffff947c0a00)
ErrCode = 00000000
eax=12616380 ebx=003c6380 ecx=000898e0 edx=00000000 esi=123f0000 edi=b1ba0000
eip=82a8a7b3 esp=947c0a74 ebp=947c0a7c iopl=0         nv up ei pl nz ac pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010216
nt!memcpy+0x33:
82a8a7b3 f3a5            rep movs dword ptr es:[edi],dword ptr [esi]
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  avp.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 893d7272 to 82a8a7b3

STACK_TEXT:  
947c0a7c 893d7272 b1a00000 12250000 003c6380 nt!memcpy+0x33
WARNING: Stack unwind information not available. Following frames may be wrong.
947c0ae8 893db032 885c18f8 82a70a89 002c002a kl1+0x1cc272
947c0b10 893dac0b 85438928 85438928 800520e8 kl1+0x1d0032
947c0b28 8920d65e 885c18f8 85bc228c 800520e8 kl1+0x1cfc0b
947c0b78 82a8848c 85bf1bf0 885d9188 885d9188 kl1+0x265e
947c0b90 82c8a3be 853d8f80 885d9188 885d91f8 nt!IofCallDriver+0x63
947c0bb0 82ca71af 85bf1bf0 853d8f80 00000000 nt!IopSynchronousServiceTail+0x1f8
947c0c4c 82ca998a 85bf1bf0 885d9188 00000000 nt!IopXxxControlFile+0x6aa
947c0c80 8de331d0 0000180c 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
947c0d04 82a8f41a 0000180c 00000000 00000000 klif+0x2e1d0
947c0d04 773c6344 0000180c 00000000 00000000 nt!KiFastCallEntry+0x12a
07f6f198 00000000 00000000 00000000 00000000 0x773c6344


STACK_COMMAND:  kb

FOLLOWUP_IP: 
kl1+1cc272
893d7272 ??              ???

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  kl1+1cc272

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: kl1

IMAGE_NAME:  kl1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c0f9617

FAILURE_BUCKET_ID:  0x8E_kl1+1cc272

BUCKET_ID:  0x8E_kl1+1cc272

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