Welcome to Seven Forums.
Always a good Idea to install new drivers from the
Asus Motherboard website, also to update the UEFI BIOS(1101).
When you get a crash on a new build it's a good idea to take a close look at the hardware and it's settings in BIOS.
Can you
download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place. Then post the screen shot in your next post, use this tutorial to do it.
How to Post a Screenshot in Seven Forums
With this information we can make better suggestions to find the cause of the crashes.
It is good that the RAM passed memtest86+ on another system, at least we know that the individual RAM cards are good.
You need to test it on your new build, if/when it is stable enough.
For now, take out two of your RAM cards, this will leave you with 2X4GB RAM. Check your motherboard manual for the correct RAM slots to use with two RAM cards, eight RAM slots is a lot to choose from.
Two RAM cards need to go in Dimm B1 and Dimm D1.
Your system may still not run stable with this amount of RAM.
Go to your UEFI and tell us what the first four RAM timings are set to, and the RAM frequency.
Also, what the DRAM and CPU IMC (Integrated Memory Controller) voltages are set at.
You may need to take out two of your graphics cards, try running it with one card until we can get it stable.
Did you check/update the Vertex 3 SSD firmware?
You have had 19 crashes today.
Your time setting must be off they are all dated 29 Jan 2012.
The last four crashes.
None of these are Driver Verifier caused, meaning the Driver Verifier is not set to run.
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
Cause:
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.
The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.
Code:
*******************************************************************************
* *
* 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: 0000000000004b02, 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: fffff8000348694f, address which referenced memory
Debugging Details:
------------------
PROCESS_NAME: audiodg.exe
IMAGE_NAME: usbaudio.sys
STOP 0x000000D3: DRIVER_PORTION_MUST_BE_NONPAGED
Usual causes: Device driver
This indicates that the system attempted to access pageable memory at a process IRQL that was too high.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_PORTION_MUST_BE_NONPAGED (d3)
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
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 marking code or data as pageable when it should be
marked nonpaged.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff88007bcba25, memory referenced
Arg2: 0000000000000000, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff800036bdfe2, address which referenced memory
Debugging Details:
------------------
PROCESS_NAME: dwm.exe
IMAGE_NAME: hardware
Desktop Window Manager (dwm.exe) is the compositing window manager that gives you all those pretty effects in Windows.
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory
Cause:
This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8000369894f, Address of the instruction which caused the bugcheck
Arg3: fffff8801009d980, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
PROCESS_NAME: audiodg.exe
IMAGE_NAME: usbaudio.sys
3b again.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800036e794f, Address of the instruction which caused the bugcheck
Arg3: fffff880105d5a10, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
PROCESS_NAME: audiodg.exe
IMAGE_NAME: usbaudio.sys
From your System Events Log:
A lot of these.
Code:
Event[20]:
Log Name: System
Source: Microsoft-Windows-WHEA-Logger
Date: 2012-01-28T16:56:11.696
Event ID: 19
Task: N/A
Level: Warning
Opcode: Info
Keyword: N/A
User: S-1-5-19
User Name: NT AUTHORITY\LOCAL SERVICE
Computer: Neo
Description:
[COLOR="red"]A corrected hardware error has occurred.[/COLOR]
[COLOR="Red"]Reported by component: Processor Core[/COLOR]
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor ID: 8
The details view of this entry contains further information.
Event[107]:
Log Name: System
Source: Microsoft-Windows-WHEA-Logger
Date: 2012-01-28T16:53:27.164
Event ID: 19
Task: N/A
Level: Warning
Opcode: Info
Keyword: N/A
User: S-1-5-19
User Name: NT AUTHORITY\LOCAL SERVICE
Computer: Neo
Description:
[COLOR="red"]A corrected hardware error has occurred.[/COLOR]
[COLOR="red"]Reported by component: Processor Core[/COLOR]
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor ID: 9
The details view of this entry contains further information.
Event[250]:
Log Name: System
Source: Microsoft-Windows-WHEA-Logger
Date: 2012-01-28T16:46:04.156
Event ID: 19
Task: N/A
Level: Warning
Opcode: Info
Keyword: N/A
User: S-1-5-19
User Name: NT AUTHORITY\LOCAL SERVICE
Computer: Neo
Description:
A corrected hardware error has occurred.
Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor ID: 9
The details view of this entry contains further information.
This is indicating a CPU issue, could be motherboard also.
I would get Driver Verifier running first to see if it identifies any bad drivers.
)
