x0a xc9 bsods on a newly built pc

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

STOP 0x000000C9: DRIVER_VERIFIER_IOMANAGER_VIOLATION
Usual causes: Driver verifier

- Test your RAM. your dump files states an indication of possible memory corruption
RAM - Test with Memtest86+
Run for at least 8 passes. Pay attention to #3 on that link

- Also, run these two commands from the elevated command prompt:
chkdsk /r /f
SFC /scannow

- One of the DirectX driver was caught on the BSOD dump files. Try to update directx
dxgmms1.sys - Driver Reference Table

Code:

Image path: \SystemRoot\System32\drivers\dxgmms1.sys
    Image name: dxgmms1.sys
    Timestamp:        Wed Jan 26 11:22:12 2011 (4D3FA174)

- Looks like Driver Verifier was enabled on your PC, and caught IOMap64.sys causing I/O error.
This also pops up several times in your dump files
IOMap64.sys - Driver Reference Table
Consider Updating that driver first:
ASUSTeK Computer Inc. -Support- Drivers and Download

Code:

Image path: \??\C:\Windows\system32\drivers\IOMap64.sys
    Image name: IOMap64.sys
    Timestamp:        Fri Feb 05 08:55:34 2010 (4B6B7A96)

- Until we need it again for further testing, disable driver verifier to reduce your PC Load
Driver Verifier - Enable and Disable


BSOD ANALYSIS

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa8018e4f010, 2, 1, fffff80002d43b07}

Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+87 )

Followup: MachineOwner
---------
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.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa8018e1b010, 2, 1, fffff80002d81b07}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::DestroyOneAllocation+153 )

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

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {226, fffff880047d5734, fffff98013e5eee0, 0}

Unable to load image \??\C:\Windows\system32\drivers\IOMap64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for IOMap64.sys
*** ERROR: Module load completed but symbols could not be loaded for IOMap64.sys
Probably caused by : IOMap64.sys ( IOMap64+1734 )

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

have you tried to move it to different slots?
if the RAM chip's at fault, replace the RAM.
if the slot's bad, it's motherboard's fault.

RAM - Test with Memtest86+ - on point #3 is to determine whether the RAM chip or the motherboard slot is at fault. do so accordingly

cheers