Tony, since you rolled back the BIOS, lets see if you get any more crashes. Error code A is a hardware error. Usual causes are Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility. Because BIOS is a possibility. We need to see what rolling it back did.
The dumps are nearly identical and do not tell much. Both dumps reference memory.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {ffffffffffffffd0, 2, 1, fffff80002c976e0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
Followup: MachineOwner
---------
4: 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: ffffffffffffffd0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002c976e0, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec30e0
ffffffffffffffd0
CURRENT_IRQL: 2
FAULTING_IP:
nt!ObfReferenceObject+20
fffff800`02c976e0 f0480fc11f lock xadd qword ptr [rdi],rbx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff88003387a50 -- (.trap 0xfffff88003387a50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c976e0 rsp=fffff88003387be0 rbp=0000000000000001
r8=0000000000000002 r9=0000000000000000 r10=fffff80002c1b000
r11=0000000000007532 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!ObfReferenceObject+0x20:
fffff800`02c976e0 f0480fc11f lock xadd qword ptr [rdi],rbx ds:3428:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c8aca9 to fffff80002c8b740
STACK_TEXT:
fffff880`03387908 fffff800`02c8aca9 : 00000000`0000000a ffffffff`ffffffd0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`03387910 fffff800`02c89920 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`03387a50 fffff800`02c976e0 : fffffa80`000000cb 00000000`00000030 00000000`00000030 00000000`0000000b : nt!KiPageFault+0x260
fffff880`03387be0 fffff800`02d75afc : fffffa80`04ab3428 fffffa80`04ab3428 00000000`00000001 00000000`00000000 : nt!ObfReferenceObject+0x20
fffff880`03387c10 fffff800`02ef4daf : fffffa80`04ab3428 00000000`00000001 00000000`00000000 00000000`00007533 : nt!IopDisassociateThreadIrp+0x9c
fffff880`03387c40 fffff800`02f70a2b : 00000000`00000000 ffffffff`fffe7960 00000000`00000000 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x1e7aa
fffff880`03387c70 fffff800`02f7472d : 00000000`00000000 fffff800`02f2fc00 fffffa80`04ab3000 00000000`00000000 : nt!PspExitThread+0x58b
fffff880`03387d30 fffff800`02c69c26 : fffff880`009b1180 00000000`00000080 fffffa80`04ab3040 00000000`00000000 : nt!PspTerminateThreadByPointer+0x4d
fffff880`03387d80 00000000`00000000 : fffff880`03388000 fffff880`03382000 fffff880`033879c0 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiPageFault+260
fffff800`02c89920 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_0xA_nt!KiPageFault+260
BUCKET_ID: X64_0xA_nt!KiPageFault+260
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {ffffffffffffffd0, 2, 1, fffff80002c866e0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
Followup: MachineOwner
---------
4: 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: ffffffffffffffd0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002c866e0, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb20e0
ffffffffffffffd0
CURRENT_IRQL: 2
FAULTING_IP:
nt!ObfReferenceObject+20
fffff800`02c866e0 f0480fc11f lock xadd qword ptr [rdi],rbx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff88009667a50 -- (.trap 0xfffff88009667a50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c866e0 rsp=fffff88009667be0 rbp=0000000000000001
r8=0000000000000002 r9=0000000000000000 r10=fffff80002c0a000
r11=0000000000007532 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!ObfReferenceObject+0x20:
fffff800`02c866e0 f0480fc11f lock xadd qword ptr [rdi],rbx ds:3f48:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c79ca9 to fffff80002c7a740
STACK_TEXT:
fffff880`09667908 fffff800`02c79ca9 : 00000000`0000000a ffffffff`ffffffd0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`09667910 fffff800`02c78920 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`09667a50 fffff800`02c866e0 : fffffa80`0000009d 00000000`00000030 00000000`00000030 00000000`0000000b : nt!KiPageFault+0x260
fffff880`09667be0 fffff800`02d64afc : fffffa80`051c3f48 fffffa80`051c3f48 00000000`00000001 00000000`00000000 : nt!ObfReferenceObject+0x20
fffff880`09667c10 fffff800`02ee3daf : fffffa80`051c3f48 00000000`00000001 00000000`00000000 00000000`00007533 : nt!IopDisassociateThreadIrp+0x9c
fffff880`09667c40 fffff800`02f5fa2b : 00000000`00000000 ffffffff`fffe7960 00000000`00000000 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x1e7aa
fffff880`09667c70 fffff800`02f6372d : 00000000`00000000 fffff800`02f1ec00 fffffa80`051c3b00 00000000`00000000 : nt!PspExitThread+0x58b
fffff880`09667d30 fffff800`02c58c26 : fffff800`02df4e80 00000000`00000080 fffffa80`051c3b60 00000000`00000000 : nt!PspTerminateThreadByPointer+0x4d
fffff880`09667d80 00000000`00000000 : fffff880`09668000 fffff880`09662000 fffff880`096679c0 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiPageFault+260
fffff800`02c78920 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_0xA_nt!KiPageFault+260
BUCKET_ID: X64_0xA_nt!KiPageFault+260
Followup: MachineOwner
---------
I do find some older drivers.
Acceler.sys Fri Jun 26 16:56:34 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.sys Thu Jun 25 01:51:37 2009
CtClsFlt.sys Mon Jun 15 01:06:41 2009
rimspe64.sys Wed Jul 01 19:54:49 2009
risdpe64.sys Wed Jul 01 05:31:57 2009
rixdpe64.sys Sat Jul 04 06:27:00 2009
I can't say these drivers are causing the problem; but Win 7 generally does not like out of date drivers. See if you can update these drivers. If you need help, please post.