BSOD, Windbg information included, contains two errors?

Ok, so ever since I put this machine together I have been getting the sysdata.xml error report with random restarts. I have literally been working on this problem all day now. Lately it has not been happening as much, but i d/l the battlefield 2 demo, and the second I join an online game my computer restarts. Most of the time I dont get the blue screen of death, but after reading some forums I checked the drivers through some run command to force the BSOD to get some minidumps. I know its not the ram (thanks to memtest86), and its not overheating (41c). At first it kept happening with a certain windows update, then sometimes my tivo transfers would do it.
Anyways, here are the reports below. The first report was when I forced the BWOD, the second is when I played battlefield. They contain two seperate errors, one seems to be a driver problem (perhaps my Geforce 6600 gt, although I reinstalled clean drivers on it with no luck) or a mobo/cpu problem. Thanks for your help.

FIRST DUMP FOR FORCED BSOD


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


Loading Dump File [C:\WINDOWS\Minidump\Mini051206-12.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Fri May 12 13:37:06.750 2006 (GMT-7)
System Uptime: 0 days 0:00:49.500
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.........................................................................................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {8fa8ebf8, 2, 0, 804db548}

Probably caused by : ntoskrnl.exe ( nt!RtlLargeIntegerAdd+0 )

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

0: kd> !Analyze -v=20
*******************************************************************************
* *
* 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: 8fa8ebf8, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804db548, address which referenced memory

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


READ_ADDRESS: 8fa8ebf8

CURRENT_IRQL: 2

FAULTING_IP:
nt!RtlLargeIntegerAdd+0
804db548 8b06 mov eax,[esi]

CUSTOMER_CRASH_COUNT: 12

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 00000000 to 804db548

STACK_TEXT:
f5af4cc4 00000000 00000000 00000000 ba460755 nt!RtlLargeIntegerAdd


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!RtlLargeIntegerAdd+0
804db548 8b06 mov eax,[esi]

FAULTING_SOURCE_CODE:


FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!RtlLargeIntegerAdd+0

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42250f77

FAILURE_BUCKET_ID: 0xA_nt!RtlLargeIntegerAdd+0

BUCKET_ID: 0xA_nt!RtlLargeIntegerAdd+0

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





THIS DUMP WAS TRYING TO PLAY BATTLEFIELD 2



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


Loading Dump File [C:\WINDOWS\Minidump\Mini051206-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Fri May 12 08:22:35.093 2006 (GMT-7)
System Uptime: 0 days 0:05:34.854
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
....................................................................................................................
Loading User Symbols
Loading unloaded module list
..........
*** WARNING: Unable to verify timestamp for hal.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, f7aca050, b2000000, 1040080f}

Probably caused by : memory_corruption ( nt!MiRemoveUnusedSegments+52f )

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

1: kd> !analyze -v=20
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 00000000
Arg2: f7aca050
Arg3: b2000000
Arg4: 1040080f

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

NOTE: This is a hardware error. This error was reported by the CPU
via Interrupt 18. This analysis will provide more information about
the specific error. Please contact the manufacturer for additional
information about this error and troubleshooting assistance.

This error is documented in the following publication:

- IA-32 Intel(r) Architecture Software Developer's Manual
Volume 3: System Programming Guide

Bit Mask:

MA Model Specific MCA
O ID Other Information Error Code Error Code
VV SDP ___________|____________ _______|_______ _______|______
AEUECRC| | | |
LRCNVVC| | | |
^^^^^^^| | | |
6 5 4 3 2 1
3210987654321098765432109876543210987654321098765432109876543210
----------------------------------------------------------------
1011001000000000000000000000000000010000010000000000100000001111


VAL - MCi_STATUS register is valid
Indicates that the information contained within the IA32_MCi_STATUS
register is valid. When this flag is set, the processor follows the
rules given for the OVER flag in the IA32_MCi_STATUS register when
overwriting previously valid entries. The processor sets the VAL
flag and software is responsible for clearing it.

UC - Error Uncorrected
Indicates that the processor did not or was not able to correct the
error condition. When clear, this flag indicates that the processor
was able to correct the error condition.

EN - Error Enabled
Indicates that the error was enabled by the associated EEj bit of the
IA32_MCi_CTL register.

PCC - Processor Context Corrupt
Indicates that the state of the processor might have been corrupted
by the error condition detected and that reliable restarting of the
processor may not be possible.

BUSCONNERR - Bus and Interconnect Error BUS{LL}_{PP}_{RRRR}_{II}_{T}_err
These errors match the format 0000 1PPT RRRR IILL



Concatenated Error Code:
--------------------------
_VAL_UC_EN_PCC_BUSCONNERR_F

This error code can be reported back to the manufacturer.
They may be able to provide additional information based upon
this error. All questions regarding STOP 0x9C should be
directed to the hardware manufacturer.

BUGCHECK_STR: 0x9C_IA32_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 80702bff to 805371aa

STACK_TEXT:
f7aca028 80702bff 0000009c 00000000 f7aca050 nt!MiRemoveUnusedSegments+0x52f
f7aca154 806fdc52 f7ac6d70 00000000 00000000 hal!KeRevertToUserAffinityThread+0x5
00000000 00000000 00000000 00000000 00000000 hal!HalpWriteCmosTime+0xce


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiRemoveUnusedSegments+52f
805371aa 5d pop ebp

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!MiRemoveUnusedSegments+52f

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 42250f77

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x9C_IA32_GenuineIntel_nt!MiRemoveUnusedSegments+52f

BUCKET_ID: 0x9C_IA32_GenuineIntel_nt!MiRemoveUnusedSegments+52f

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



Thanks for your help!

 

You overclocking?

 

nope.

 

My guess is that because of the infrequency in which it happens, its probably a driver problem. How do I find out which driver it is however?