BleepingComputer.com: Bsod Memory Corruption?

I just built this brand new PC, Q6600 2.4, 4GB Ram and I'm getting BSOD telling me that i have a memory corruption, I hope it isn't, Could anybody confirm this?

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8050a7b2, The address that the exception occurred at
Arg3: ba523ca4, Exception Record Address
Arg4: ba5239a0, Context Record Address

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!MiSegmentDelete+14
8050a7b2 8b07 mov eax,dword ptr [edi]

EXCEPTION_RECORD: ba523ca4 -- (.exr 0xffffffffba523ca4)
ExceptionAddress: 8050a7b2 (nt!MiSegmentDelete+0x00000014)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000002
Attempt to read from address 00000002

CONTEXT: ba5239a0 -- (.cxr 0xffffffffba5239a0)
eax=00000000 ebx=806e6a4c ecx=00000000 edx=00000000 esi=8ac43008 edi=00000002
eip=8050a7b2 esp=ba523d6c ebp=ba523d8c iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nt!MiSegmentDelete+0x14:
8050a7b2 8b07 mov eax,dword ptr [edi] ds:0023:00000002=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

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

READ_ADDRESS: 00000002

BUGCHECK_STR: 0x7E

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from 8050c0c9 to 8050a7b2

STACK_TEXT:
ba523d8c 8050c0c9 00000002 00000000 8aea9da8 nt!MiSegmentDelete+0x14
ba523dac 805cff64 00000000 00000000 00000000 nt!MiDereferenceSegmentThread+0xa7
ba523ddc 805460de 8050c022 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


FOLLOWUP_IP:
nt!MiSegmentDelete+14
8050a7b2 8b07 mov eax,dword ptr [edi]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiSegmentDelete+14

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a

STACK_COMMAND: .cxr 0xffffffffba5239a0 ; kb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x7E_nt!MiSegmentDelete+14

BUCKET_ID: 0x7E_nt!MiSegmentDelete+14

Followup: MachineOwner

My computer use to get the BSOD because I had a defective stick of ram. The best thing to do is run memtest http://memtest86.com/ . Burn the .ISO image to a cd, and restart your computer. Make sure your computer is set to boot off the cd drive before the hard drive. The program should automatically start running, and you should let it go for at least 2 hours, but I usually just let it sit over night. It will tell you if it found any errors.

You can also take each individual stick of ram out at a time, to find which is the bad one. I doubt that all of them would be bad.

The last time i used Memtest it came with no errors but then i found 1 of my sticks was corrupt, I might try the take 1 out method