Recurring BSOD

Tater, it sounds like maybe the RAM is incompatible or incompatible with the motherboard. Try running Prime95 following these instructions. https://www.sevenforums.com/tutorials...t-prime95.html. The blended test will test both your CPU and RAM. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post your results.

Error code 1E, KMODE_EXCEPTION_NOT_HANDLED. Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.

Code:

Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03254000 PsLoadedModuleList = 0xfffff800`03491e50
Debug session time: Thu Oct 28 22:52:10.346 2010 (GMT-4)
System Uptime: 0 days 0:37:48.188
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff800032caaa6, 0, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt!SwapContext_PatchXRstor+c0 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800032caaa6, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!SwapContext_PatchXRstor+c0
fffff800`032caaa6 c3              ret

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034fc0e0
 ffffffffffffffff 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff80000b9cb38 -- (.exr 0xfffff80000b9cb38)
ExceptionAddress: fffff800032caaa6 (nt!SwapContext_PatchXRstor+0x00000000000000c0)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff80000b9cbe0 -- (.trap 0xfffff80000b9cbe0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000003
rdx=0000000000187000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032caaa6 rsp=fffff80000b9cd78 rbp=0000000000000002
 r8=fffffa80018c20c8  r9=0000000000000000 r10=fffffffffffffffe
r11=fffff8000343ee80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!SwapContext_PatchXRstor+0xc0:
fffff800`032caaa6 c3              ret
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032fea39 to fffff800032c4740

STACK_TEXT:  
fffff800`00b9c368 fffff800`032fea39 : 00000000`0000001e ffffffff`c0000005 fffff800`032caaa6 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c370 fffff800`032c3d82 : fffff800`00b9cb38 fffff800`0343ee80 fffff800`00b9cbe0 fffff800`0344cc40 : nt!KiDispatchException+0x1b9
fffff800`00b9ca00 fffff800`032c268a : fffffa80`02673f20 000b0000`00000000 00000000`00000002 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`00b9cbe0 fffff800`032caaa6 : ff16f800`032ccf9d fffff800`0343ee80 fffff800`0344cc40 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9cd78 ff16f800`032ccf9d : fffff800`0343ee80 fffff800`0344cc40 00000000`00000000 fffff880`03e0f480 : nt!SwapContext_PatchXRstor+0xc0
fffff800`00b9cd80 fffff800`0343ee80 : fffff800`0344cc40 00000000`00000000 fffff880`03e0f480 fffff800`00812730 : 0xff16f800`032ccf9d
fffff800`00b9cd88 fffff800`0344cc40 : 00000000`00000000 fffff880`03e0f480 fffff800`00812730 00000000`00000000 : nt!KiInitialPCR+0x180
fffff800`00b9cd90 00000000`00000000 : fffff880`03e0f480 fffff800`00812730 00000000`00000000 fffff800`00b9d000 : nt!KiInitialThread


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!SwapContext_PatchXRstor+c0
fffff800`032caaa6 c3              ret

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!SwapContext_PatchXRstor+c0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1E_nt!SwapContext_PatchXRstor+c0

BUCKET_ID:  X64_0x1E_nt!SwapContext_PatchXRstor+c0

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

The dump does not tell us anything except memory corruption. Let's track down the RAM problem. After you run Prime 95, I will get the hardware guys to take a look.

OK, good job. I will ask for help from the hardware Guru's.

Can you restart the machine and tell me what revision of BIOS you are using?

Here are the steps to take to update your BIOS:

CD Method (Blank CD and CD Rewritable Drive Required)
Download the following .iso file: Attachment 112502 <<NF68_P33.iso
Use a CD Burning software to burn the .iso image onto a blank CD (Windows 7 software, Nero, MagicIso, etc)
Restart machine, and set the CD Drive as the primary boot device
The BIOS flash process will begin, Press "Y" to program BIOS
After flash remove the CD, power off PC Completely
Turn on the PC and load defaults in BIOS

Also, after that, download and execute this file:

My apologies for the direct download link, but it is the only way I can find to link you to the proper driver set, released in March this year from EVGA for that board and Windows 7 x64 operating system.

<<<DIRECT DOWNLOAD LINK>>>
http://us.download.nvidia.com/Window...ional_whql.exe