Hi HelpMehPlz. Sorry you are having problems. You don't need to "bump". We are all volunteers here; we try not to let anyone fall through the cracks. I will look at your dumps and edit this thread.
Your three dumps have different error codes and the first two reference memory. The third points to a bad check sum.
Error code A, IRQL_NOT_LESS_OR_EQUAL - usual causes are Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility.
Error code 1E, KMODE_EXCEPTION_NOT_HANDLED - usual causes are Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.
Error code - 221, Status_IMAGE_CHECKSUM_MISMATCH - Device driver, System DLL corruption, Faulty hardware in I/O path (a disk error, faulty RAM, or a corrupted page file), BIOS.
These are hardware/hardware related errors. Notice in the usual causes that memory is listed in two of the error codes and device driver in in all three.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Windows_NT6_BSOD_jcgriff2.zip\Windows_NT6_BSOD_jcgriff2\090510-34164-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a14000 PsLoadedModuleList = 0xfffff800`02c51e50
Debug session time: Sun Sep 5 11:59:44.414 2010 (GMT-4)
System Uptime: 0 days 16:34:18.240
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffffffffffffd20, 2, 0, fffff80002a53dba}
Probably caused by : ntkrnlmp.exe ( nt!KeQueryValuesProcess+a0 )
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: fffffffffffffd20, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002a53dba, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbc0e0
fffffffffffffd20
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeQueryValuesProcess+a0
fffff800`02a53dba 488b8120fdffff mov rax,qword ptr [rcx-2E0h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: Wow.exe
TRAP_FRAME: fffff880084ab470 -- (.trap 0xfffff880084ab470)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000001659 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a53dba rsp=fffff880084ab600 rbp=0000000000000000
r8=000000000000d5ab r9=fffffa8003a36300 r10=fffffa8003a362a0
r11=fffffa800665d370 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po cy
nt!KeQueryValuesProcess+0xa0:
fffff800`02a53dba 488b8120fdffff mov rax,qword ptr [rcx-2E0h] ds:ffffffff`fffffd20=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a83ca9 to fffff80002a84740
STACK_TEXT:
fffff880`084ab328 fffff800`02a83ca9 : 00000000`0000000a ffffffff`fffffd20 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`084ab330 fffff800`02a82920 : fffff880`084ab680 fffff880`084ab680 00000000`0000048b fffffa80`06604b30 : nt!KiBugCheckDispatch+0x69
fffff880`084ab470 fffff800`02a53dba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000801 : nt!KiPageFault+0x260
fffff880`084ab600 fffff800`02d1c5e8 : fffffa80`0665d360 00000000`00000000 fffff880`084abca0 00000000`00000002 : nt!KeQueryValuesProcess+0xa0
fffff880`084ab630 fffff800`02d1b7da : 00000000`00000000 00000000`00013f70 00000000`002d7680 00000000`002d6fc0 : nt!ExpCopyProcessInfo+0x1f8
fffff880`084ab6f0 fffff800`02d82116 : 00000000`002c3810 00000000`00014400 fffff880`084ab880 00000000`00000000 : nt!ExpGetProcessInformation+0x14b
fffff880`084ab840 fffff800`02d831e5 : 00000000`002c3810 00000000`00008000 00000000`00000005 00000000`039fec2c : nt!ExpQuerySystemInformation+0xf14
fffff880`084abbe0 fffff800`02a83993 : ffffffff`ffffffff 00000000`0008e310 00000000`0008e308 00000000`00008000 : nt!NtQuerySystemInformation+0x4d
fffff880`084abc20 00000000`777700ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e208 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777700ba
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KeQueryValuesProcess+a0
fffff800`02a53dba 488b8120fdffff mov rax,qword ptr [rcx-2E0h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KeQueryValuesProcess+a0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0xA_nt!KeQueryValuesProcess+a0
BUCKET_ID: X64_0xA_nt!KeQueryValuesProcess+a0
Followup: MachineOwner
---------
Kernel base = 0xfffff800`02a08000 PsLoadedModuleList = 0xfffff800`02c45e50
Debug session time: Sun Sep 5 13:52:58.750 2010 (GMT-4)
System Uptime: 0 days 1:34:27.576
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
FAULTING_IP:
+5e6a952f019fdf0c
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: System
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff88002f8b2c8 -- (.exr 0xfffff88002f8b2c8)
ExceptionAddress: fffff80002a85167 (nt!KiInsertTimerTable+0x0000000000000157)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff88002f8b370 -- (.trap 0xfffff88002f8b370)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000040e76080 rbx=0000000000000000 rcx=fffff88002f63180
rdx=fffffa8006889c20 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a85167 rsp=fffff88002f8b500 rbp=0000000000000000
r8=52c15ca9e457a736 r9=00000000000000e7 r10=fffff88002f63180
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!KiInsertTimerTable+0x157:
fffff800`02a85167 410fb74002 movzx eax,word ptr [r8+2] ds:52c15ca9`e457a738=????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a7046e to fffff80002a78710
STACK_TEXT:
fffff880`02f8a3b8 fffff800`02a7046e : fffffa80`04be7010 00000000`00000001 fffff880`02f8ab30 fffff800`02aa5668 : nt!KeBugCheck
fffff880`02f8a3c0 fffff800`02a9e40d : fffff800`02c86b7c fffff800`02bc0e84 fffff800`02a08000 fffff880`02f8b2c8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f8a3f0 fffff800`02aa5a90 : fffff800`02bc7b14 fffff880`02f8a468 fffff880`02f8b2c8 fffff800`02a08000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f8a420 fffff800`02ab29ef : fffff880`02f8b2c8 fffff880`02f8ab30 fffff880`00000000 fffff800`02a08000 : nt!RtlDispatchException+0x410
fffff880`02f8ab00 fffff800`02a77d82 : fffff880`02f8b2c8 fffffa80`06889c20 fffff880`02f8b370 52c15ca9`e457a736 : nt!KiDispatchException+0x16f
fffff880`02f8b190 fffff800`02a7668a : fffffa80`051b3010 fffff880`051bc095 00000000`00000000 fffff880`051b83f1 : nt!KiExceptionDispatch+0xc2
fffff880`02f8b370 fffff800`02a85167 : 00000000`00000000 00000000`0000000f 00000000`00000000 ffffdc37`aeb87e8e : nt!KiGeneralProtectionFault+0x10a
fffff880`02f8b500 fffff800`02a8227a : 00000000`01201600 fffffa80`04de9b60 fffffa80`052d9b60 00000000`00000000 : nt!KiInsertTimerTable+0x157
fffff880`02f8b560 fffff800`02a83d7d : fffffa80`06889c20 fffffa80`063501b0 fffffa80`063501b0 00000000`00000102 : nt!KiTimerWaitTest+0x15a
fffff880`02f8b5e0 fffff800`02a844be : 0000000d`32239976 fffff880`02f8bc58 00000000`00058b27 fffff880`02f65a68 : nt!KiProcessExpiredTimerList+0x6d
fffff880`02f8bc30 fffff800`02a83cb7 : 00000013`509e5fc8 00000013`00058b27 00000013`509e5f7b 00000000`00000027 : nt!KiTimerExpiration+0x1be
fffff880`02f8bcd0 fffff800`02a80eea : fffff880`02f63180 fffff880`02f6dfc0 00000000`00000000 fffff880`050c5588 : nt!KiRetireDpcList+0x277
fffff880`02f8bd80 00000000`00000000 : fffff880`02f8c000 fffff880`02f86000 fffff880`02f8bd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`02a7046e 90 nop
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
Followup: MachineOwner
---------
Kernel base = 0xfffff800`02a4a000 PsLoadedModuleList = 0xfffff800`02c87e50
Debug session time: Sat Sep 4 11:40:01.611 2010 (GMT-4)
System Uptime: 0 days 0:00:20.063
Loading Kernel Symbols
..............................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C0000221, {fffff8a0001c9ac0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5ff )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Unknown bugcheck code (c0000221)
Unknown bugcheck description
Arguments:
Arg1: fffff8a0001c9ac0
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0xc0000221
ERROR_CODE: (NTSTATUS) 0xc0000221 - {Bad Image Checksum} The image %hs is possibly corrupt. The header checksum does not match the computed checksum.
EXCEPTION_CODE: (NTSTATUS) 0xc0000221 - {Bad Image Checksum} The image %hs is possibly corrupt. The header checksum does not match the computed checksum.
EXCEPTION_PARAMETER1: fffff8a0001c9ac0
EXCEPTION_PARAMETER2: 0000000000000000
EXCEPTION_PARAMETER3: 0000000000000000
EXCEPTION_PARAMETER4: 0
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002d0809f to fffff80002aba740
STACK_TEXT:
fffff880`009a91e8 fffff800`02d0809f : 00000000`0000004c 00000000`c0000221 fffff880`009a9288 fffffa80`04214ba0 : nt!KeBugCheckEx
fffff880`009a91f0 fffff800`02b04ec4 : 7ff00000`00000000 00000000`00000000 00000000`00000000 fffff700`01080000 : nt!ExpSystemErrorHandler2+0x5ff
fffff880`009a9420 fffff800`02eea961 : 00000000`c0000221 00000000`00000001 00000000`00000001 00000000`00200000 : nt!ExpSystemErrorHandler+0xd4
fffff880`009a9460 fffff800`02eead66 : fffffa80`c0000221 00000000`00000001 fffffa80`00000001 00000000`00200000 : nt!ExpRaiseHardError+0xe1
fffff880`009a9790 fffff800`02eec216 : fffff8a0`c0000221 00000000`00000001 00000000`00000001 fffff880`009a9988 : nt!ExRaiseHardError+0x1d6
fffff880`009a9890 fffff800`02eff41f : 00000000`c0000221 00000000`08000000 fffff800`02f85828 ffffffff`80000078 : nt!NtRaiseHardError+0x1e4
fffff880`009a9930 fffff800`02eff779 : 00000000`002a0028 00000000`00000000 00000000`00000001 fffff800`02fb5bc0 : nt!PspLocateSystemDll+0xbf
fffff880`009a9a00 fffff800`02fe8b3d : fffff800`00812860 00000000`00000002 00000000`00000000 fffff800`02c34e80 : nt!PsLocateSystemDlls+0x69
fffff880`009a9a40 fffff800`02febcec : 00000000`00000000 00000000`00000010 ffffffff`80000028 fffff800`00812860 : nt!IoInitSystem+0x85d
fffff880`009a9b40 fffff800`02f3c8c9 : d5a0f01f`5915ba5e fffffa80`036e3040 00000000`00000080 fffffa80`03669b30 : nt!Phase1InitializationDiscard+0x129c
fffff880`009a9d10 fffff800`02d5ec06 : c1f76729`83e07ef7 00000000`00000080 a3c51bc1`7675dfe3 fffff800`02a98c19 : nt!Phase1Initialization+0x9
fffff880`009a9d40 fffff800`02a98c26 : fffff800`02c34e80 fffffa80`036e3040 fffff800`02c42c40 138067c2`e1084ab9 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a93f0 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExpSystemErrorHandler2+5ff
fffff800`02d0809f cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!ExpSystemErrorHandler2+5ff
FOLLOWUP_NAME: MachineOwner
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0xc0000221_nt!ExpSystemErrorHandler2+5ff
BUCKET_ID: X64_0xc0000221_nt!ExpSystemErrorHandler2+5ff
Followup: MachineOwner
---------
This will be a process of elimination since the dumps do not point to specific causes. Begin by uninstalling AVG using this tool, Info > Tool (32bit) - Tool (64 bit). If you have AVG Identity protection installed, uninstall it using this tool, Info > Tool. AVG is a known cause of BSOD's on some Win 7 systems.
Next uninstall Norton/Symantec. One of the Symantec drivers was indicated in your most recent dump. Norton is another know cause of BSOD's on some win 7 systems. Use this removal tool, Info > Tool.
Download and install Microsoft Security Essentials and make sure Windows Firewall is turned on. Neither of these will cause crashes. Reboot your system and see how it runs.
I find the following out of date driver on your system.
ahcix64s.sys Tue Mar 17 02:38:19 2009 - AMD AHCI Compatible RAID Controller AMD Support Search. Windows 7 tends to be finicky about RAID arrays. One of your dumps indicated this driver and your third dumps indicated a checksum problem. If you cannot find an update for this driver, let me know and I will get one of our hardware experts involved. I am not an expert with RAID.
Post back and let us know your progress and upload any new BSOD's.