Hi Steve; welcome to the forums from a neighbor up the road in Orlando. Sorry you are having trouble. I looked at six of the dumps. In those six you have two error codes.
Error code D1, DRIVER_IRQL_NOT_LESS_OR_EQUAL. Usually caused by a device
driver.
Error code 7F, UNEXPECTED_KERNEL_MODE_TRAP. usually caused by Memory corruption, Hardware (memory in particular), Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device
drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack.
Notice that both of these error codes have device drivers in common.
Code:
Kernel base = 0xfffff800`0305f000 PsLoadedModuleList = 0xfffff800`0329ce50
Debug session time: Thu Sep 9 00:18:36.313 2010 (GMT-4)
System Uptime: 0 days 2:55:44.264
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffff7ffcb1a7907, 2, 8, fffff7ffcb1a7907}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
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: fffff7ffcb1a7907, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff7ffcb1a7907, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800033070e0
fffff7ffcb1a7907
CURRENT_IRQL: 2
FAULTING_IP:
+58d8952f00b8d858
fffff7ff`cb1a7907 ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff80000b9cbb0 -- (.trap 0xfffff80000b9cbb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000148000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff7ffcb1a7907 rsp=fffff80000b9cd40 rbp=0000000000000000
r8=fffffa8003c01c50 r9=0000000000000000 r10=fffff8000305f000
r11=fffffa8005c37c00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
fffff7ff`cb1a7907 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800030ceca9 to fffff800030cf740
FAILED_INSTRUCTION_ADDRESS:
+58d8952f00b8d858
fffff7ff`cb1a7907 ?? ???
STACK_TEXT:
fffff800`00b9ca68 fffff800`030ceca9 : 00000000`0000000a fffff7ff`cb1a7907 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff800`00b9ca70 fffff800`030cd920 : fffff800`00b9ce10 fffff800`03249e80 00000000`00000000 fffff800`030d5284 : nt!KiBugCheckDispatch+0x69
fffff800`00b9cbb0 fffff7ff`cb1a7907 : fffff800`00000000 fffff800`03257c01 fffff800`00b9d548 00000000`00000000 : nt!KiPageFault+0x260
fffff800`00b9cd40 fffff800`00000000 : fffff800`03257c01 fffff800`00b9d548 00000000`00000000 fffff800`00b9d540 : 0xfffff7ff`cb1a7907
fffff800`00b9cd48 fffff800`03257c01 : fffff800`00b9d548 00000000`00000000 fffff800`00b9d540 00000000`00000000 : 0xfffff800`00000000
fffff800`00b9cd50 fffff800`00b9d548 : 00000000`00000000 fffff800`00b9d540 00000000`00000000 fffff800`00b9d000 : nt!KiNode0+0x81
fffff800`00b9cd58 00000000`00000000 : fffff800`00b9d540 00000000`00000000 fffff800`00b9d000 fffff800`00b97000 : 0xfffff800`00b9d548
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiPageFault+260
fffff800`030cd920 440f20c0 mov rax,cr8
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiPageFault+260
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260
BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260
Followup: MachineOwner
---------
Kernel base = 0xfffff800`03008000 PsLoadedModuleList = 0xfffff800`03245e50
Debug session time: Thu Sep 9 00:24:37.361 2010 (GMT-4)
System Uptime: 0 days 0:05:04.311
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050031, 406f8, fffff80003040ec0}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000406f8
Arg4: fffff80003040ec0
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: wmpnetwk.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80003077ca9 to fffff80003078740
STACK_TEXT:
fffff880`009efc68 fffff800`03077ca9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000406f8 : nt!KeBugCheckEx
fffff880`009efc70 fffff800`03076172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009efdb0 fffff800`03040ec0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`02f1ceb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x58
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b2
fffff800`03076172 90 nop
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiDoubleFaultAbort+b2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2
BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2
Followup: MachineOwner
--------- The dumps do not point to a particular problem; but they do give us some clues on where to look.
To begin troubleshooting, I recommend that you uninstall AVG. AVG is known to cause problems on some Win 7 systems. Use this uninstall tool:
Info > Tool (32bit) - Tool (64 bit). If you have installed AVG Identity Protection, uninstall it with their removal tool: Info > Tool Download and install Microsoft Security Essentials in its place. An antivirus scanner is one of the possible causes listed in error code 7F.
Next please uninstall Zone Alarm. ZA is notorious for causing BSOD's on Win 7 systems. Use this removal tool:
http://download.zonealarm.com/bin/fr...cpes_clean.exe. Make sure Windows Firewall is turned on after you uninstall ZA.
You have a number of out of date drivers on your system. Generally speaking Win 7 does not like older third party drivers; they can and so cause conflicts, memory corruption and crashes. The ones in the red font are really obsolete. The following drivers need to be updated.
Quote:
Apfiltr.sys Tue Jun 16 18:09:26 2009
ArcSoftKsUFilter.sys Mon May 25 04:27:31 2009
btwaudio.sys Wed Jul 01 09:54:56 2009 )
btwavdt.sys Thu Jun 25 01:50:13 2009
btwl2cap.sys Fri Apr 03 20:28:45 2009
btwrchid btwrchid.sys Thu Jun 25 01:51:37 2009
iaStor.sys Thu Jun 04 21:53:40 2009
regi.sys Mon Apr 16 11:19:10 2007
rimssn64.sys Wed Jun 10 22:22:31 2009)
risdsn64 risdsn64.sys Thu Jun 11 23:49:37 2009
RTKVHD64.sys Thu Jul 02 05:42:36 2009
SFEP.sys Fri Aug 03 01:35:53 2007
yk62x64.sys Mon Feb 23 10:02:27 2009
I will help you with these drivers. The research will take a little time. I will start a new post with that information.