Question : Burn In Program - Fault Finding

Windows Vista Ultimate 64bit SP1
ASUS P5N-T Deluxe
PC2 8500 2GB Dual Channel Memory (4 x 2GB) [email protected]
Geforce 8800 GTX OC x 2 SLI

Fault - When we seam to put a bit of stress on the system it will just hang or blue screen.
           It does not give us any MiniDumps

I have run a couple of memory programs which show no issues.

I need a Graphics Card Memory Tester and a bit of software to check the motherboard out.

Any ideas?

Also could this be the bios settings for the memory?

Answer : Burn In Program - Fault Finding

Here is the first one. Bedtime now, will check back tomorrow

Chris B

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d89d6f46be, Reserved
Arg2: b3b7465eefec12ee, Reserved
Arg3: fffff80001ac212f, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
      0 : A generic data region
      1 : Modification of a function or .pdata
      2 : A processor IDT
      3 : A processor GDT
      4 : Type 1 process list corruption
      5 : Type 2 process list corruption
      6 : Debug routine modification
      7 : Critical MSR modification

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


BUGCHECK_STR:  0x109

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

BAD_PAGES_DETECTED: 2

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80001a55650

STACK_TEXT:  
fffffa60`01bd0698 00000000`00000000 : 00000000`00000109 a3a039d8`9d6f46be b3b7465e`efec12ee fffff800`01ac212f : nt!KeBugCheckEx


STACK_COMMAND:  kb

SYMBOL_NAME:  PAGE_NOT_ZERO_VISTA

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  PAGE_NOT_ZERO_VISTA

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

 *** Memory manager detected 2 instance(s) of page corruption, target is likely to have memory corruption.