Self-built machine. Worked fine for over a year. Added another ram module (6G-8G) and the problems began. Blue Screen Memory Dump at random times. Sometimes I'm in a Firefox, sometimes I'm playing a game, sometimes I'm on AIM...nothing is consistent as FAR as what the Operating SYSTEM is doing.
DRAM Modules have been RMA'd, problem persists. Many MemTests have been done. DIMM slots check out fine (moved modules about and observed behavior). BIOS has been reflashed and left on Safest Settings.

System is:
MoBo: Gigabyte (EP45T-UD3LR v1.0 BIOS: F5a[Award])
GPU: Galaxy (Nvidia GeForce 9600GT: 256Bit, 512MB DDR3, PCI-E 2.0x16)
Mem: A-Data (AD31333002GMU 2Gigs(x3) 667Mhz
Proc: Intel Core2 Duo (E8400 [Wolfdale] 775LGA 3Ghz)
OS: Windows 7 Pro

WhoCrashed Log (Some Reports may be irrelevant):
On Fri 5/7/2010 14:09:55 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x128 (0xFFFFF80002FCD504, 0x2, 0xFFFFFA8006DB18E0, 0xFFFFFA8006DB18E0)
Error: Unknown
Dump file: C:\Windows\Minidump\050710-36239-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Thu 5/6/2010 09:35:29 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88003AB84CC, 0xFFFFF88008C55E60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\050610-49764-01.dmp



On Thu 4/1/2010 05:06:47 your computer crashed
This was likely caused by the following module: nvlddmkm.sys
Bugcheck code: 0xA (0xFFFFF80802F0CD00, 0x2, 0x0, 0xFFFFF80002CC86F5)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\040110-33025-01.dmp
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 196.21
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 196.21



On Wed 3/31/2010 20:48:36 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFFFFF6807F3BB7C0, 0x0, 0xFFFFF80002CA2AE2, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\033110-48641-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Mon 2/15/2010 19:06:14 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFC (0xFFFFF88008A3F780, 0x800000019EBB2963, 0xFFFFF880065C8440, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
Dump file: C:\Windows\Minidump\021510-49421-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Thu 2/11/2010 14:14:17 your computer crashed
This was likely caused by the following module: dxgmms1.sys
Bugcheck code: 0x19 (0x22, 0xFF00000000000000, 0x0, 0x0)
Error: BAD_POOL_HEADER
Dump file: C:\Windows\Minidump\021110-59670-01.dmp
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DIRECTX Graphics MMS
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Tue 2/2/2010 21:37:49 your computer crashed
This was likely caused by the following module: atwpkt264.sys
Bugcheck code: 0x11B (0xFFFFFA8005391780, 0xFFFFF8800942B390, 0x0, 0x0)
Error: DRIVER_RETURNED_HOLDING_CANCEL_LOCK
Dump file: C:\Windows\Minidump\020210-46425-01.dmp
file path: C:\Windows\system32\drivers\atwpkt264.sys
product: ATW Protocol Driver
company: America Online
description: ATW Protocol Driver



On Sat 1/30/2010 19:24:37 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x58, 0x2, 0x0, 0xFFFFF80002D77A10)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\013010-42900-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Fri 1/1/2010 22:08:14 your computer crashed
This was likely caused by the following module: bthaudiohf.sys
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88003920430, 0xFFFFF88008FD57D8, 0xFFFFF88008FD5030)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\010110-32963-01.dmp
file path: C:\Windows\system32\drivers\bthaudiohf.sys
product: Bluetooth Hands-free Audio Device Driver
company: CSR, plc
description: Bluetooth Hands-free Audio Device Driver



On Wed 12/30/2009 19:47:25 your computer crashed
This was likely caused by the following module: atwpkt264.sys
Bugcheck code: 0x11B (0xFFFFFA8007287AE0, 0xFFFFF880079BA390, 0x0, 0x0)
Error: DRIVER_RETURNED_HOLDING_CANCEL_LOCK
Dump file: C:\Windows\Minidump\123009-42229-01.dmp
file path: C:\Windows\system32\drivers\atwpkt264.sys
product: ATW Protocol Driver
company: America Online
description: ATW Protocol Driver



On Tue 12/29/2009 21:52:13 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x58, 0x2, 0x0, 0xFFFFF80002D7BA10)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\122909-39561-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Wed 11/25/2009 14:24:38 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x403, 0xFFFFF68000077658, 0xE240000086A67867, 0xFFFFF60000077658)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\112509-32417-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Tue 11/24/2009 19:54:28 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x48, 0x2, 0x1, 0xFFFFF80002D7FABF)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\112409-37643-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Tue 11/24/2009 14:01:18 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002F78AE1, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\112409-35225-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Mon 11/23/2009 12:18:25 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x403, 0xFFFFF68000054A70, 0xFD5000006C882867, 0xFFFFF60000054A70)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\112309-40123-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Mon 11/23/2009 07:39:34 your computer crashed
This was likely caused by the following module: atwpkt264.sys
Bugcheck code: 0x11B (0xFFFFFA80092EC610, 0xFFFFF880071D7390, 0x0, 0x0)
Error: DRIVER_RETURNED_HOLDING_CANCEL_LOCK
Dump file: C:\Windows\Minidump\112309-27206-01.dmp
file path: C:\Windows\system32\drivers\atwpkt264.sys
product: ATW Protocol Driver
company: America Online
description: ATW Protocol Driver



On SUN 11/22/2009 03:42:12 your computer crashed
This was likely caused by the following module: asyncmac.sys
Bugcheck code: 0x50 (0xFFFFF8800A29392C, 0x0, 0xFFFFF88001862CCE, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\112109-16504-01.dmp
file path: C:\Windows\system32\drivers\asyncmac.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: MS Remote Access serial network driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Sat 11/21/2009 07:44:32 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002AC6105, 0xFFFFF8800744CE60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\112109-17877-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Sat 11/21/2009 02:21:20 your computer crashed
This was likely caused by the following module: tcpip.sys
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\112009-19203-01.dmp
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Sun 11/1/2009 14:39:13 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFFA7FFFFFFFD0, 0x2, 0x1, 0xFFFFF80002A91AE3)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\110109-33228-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.Swap in a another power supply of equal or greater wattage.

Good luck!Power Supply?! Really?! I haven't recorded any voltage fluctuations throughout all this and I'm only pulling down about 350-400 watts out of the 750 that's in there. Memtest is returning errors again...
At this point I think I'm going to contact A-Data and politely inform them that their product sucks for all intents and purposes. This will be the third bad module I've replaced...