These each had a different cause but I suspect that they are all related. They were allo probably caused by your Kaspersky. I would uninstall it and repplace it with Microsoft Security essentials.
I wou,d also run a system file check
(type cmd in search>right click and run as admin>sfc /scannow)
Let us know if you need help
Ken
Code:
050510-18610-01.dmp 5/5/2010 10:55:43 AM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 0x037423d8 0x00000002 0x00000001 0x8c1abaff tdx.sys tdx.sys+1aff 32-bit C:\Users\K\Desktop\Minidump\050510-18610-01.dmp 4 15 7600
050410-18891-01.dmp 5/4/2010 6:27:07 PM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 0x28854365 0x00000002 0x00000000 0x92e6efea kl1.sys kl1.sys+46fea 32-bit C:\Users\K\Desktop\Minidump\050410-18891-01.dmp 4 15 7600
042910-20373-01.dmp 4/29/2010 1:24:41 PM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 0x000003a2 0x00000002 0x00000001 0x82e2471e halmacpi.dll halmacpi.dll+371e 32-bit C:\Users\K\Desktop\Minidump\042910-20373-01.dmp 4 15 7600
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Minidump\042910-20373-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 (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a11000 PsLoadedModuleList = 0x82b59810
Debug session time: Thu Apr 29 01:23:14.919 2010 (GMT-4)
System Uptime: 0 days 2:56:30.714
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {3a2, 2, 1, 82e2471e}
*** WARNING: Unable to verify timestamp for kl1.sys
*** ERROR: Module load completed but symbols could not be loaded for kl1.sys
Probably caused by : tdx.sys ( tdx!DbgTdxReferenceTransportAddress+19 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 000003a2, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 82e2471e, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82b79718
Unable to read MiSystemVaType memory at 82b59160
000003a2
CURRENT_IRQL: 2
FAULTING_IP:
hal!KeAcquireSpinLockRaiseToSynch+e
82e2471e f00fba2900 lock bts dword ptr [ecx],0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: b1c2fbd4 -- (.trap 0xffffffffb1c2fbd4)
ErrCode = 00000002
eax=00000002 ebx=85c2a328 ecx=000003a2 edx=00000002 esi=0000020a edi=000003a2
eip=82e2471e esp=b1c2fc48 ebp=b1c2fc58 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
hal!KeAcquireSpinLockRaiseToSynch+0xe:
82e2471e f00fba2900 lock bts dword ptr [ecx],0 ds:0023:000003a2=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 82e2471e to 82a577eb
STACK_TEXT:
b1c2fbd4 82e2471e badb0d00 00000002 00000000 nt!KiTrap0E+0x2cf
b1c2fc44 8bbd0adb 85c2a330 0000020a 85c2a328 hal!KeAcquireSpinLockRaiseToSynch+0xe
b1c2fc58 8bbd6039 0000020a 8bbde0ea 000005b7 tdx!DbgTdxReferenceTransportAddress+0x19
b1c2fcdc 8bbdb317 00c2a328 85754c58 85754cec tdx!TdxConnectConnection+0x67
b1c2fcf8 82a4d4bc 8651c568 85754c58 85bbbe68 tdx!TdxTdiDispatchInternalDeviceControl+0x149
b1c2fd10 91243b8a 00000000 85ad0d78 91244318 nt!IofCallDriver+0x63
WARNING: Stack unwind information not available. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 kl1+0x3bb8a
STACK_COMMAND: kb
FOLLOWUP_IP:
tdx!DbgTdxReferenceTransportAddress+19
8bbd0adb 8ad8 mov bl,al
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: tdx!DbgTdxReferenceTransportAddress+19
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: tdx
IMAGE_NAME: tdx.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf4a
FAILURE_BUCKET_ID: 0xA_tdx!DbgTdxReferenceTransportAddress+19
BUCKET_ID: 0xA_tdx!DbgTdxReferenceTransportAddress+19
Followup: MachineOwner
---------
Quote