Ati3duag.dll / memory error

[Mkkl]

My pc keeps freezin and booting when i play games like COD4/5 and when i use a program like memtest86 ( even before i get an error )

here is my minidump file.
hope someone can help me

system:
Windows XP Pro SP3
Core 2 Duo E8400 3 Ghz
Radeon Sapphire HD4850
Samsung 640 GB HDD
4(2x2) Gb Kingston memory
MSI Neo3 FR

I already update all the drivers, re installed windows 3 times, and now Í am only running things like MSN iTunes and it still keeps booting.
And put 2 new mem sticks in it.

Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini121408-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: I:\Symbols
Executable search path is: 
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Dec 14 19:04:40.640 2008 (GMT+1)
System Uptime: 0 days 0:11:01.334
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
............................................................
Loading User Symbols
Loading unloaded module list
.........................
Unable to load image ati3duag.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ati3duag.dll
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {e634785c, 1, bf1b2f11, 1}


Could not read faulting driver name
Probably caused by : ati3duag.dll ( ati3duag!r200ProcEyeRoute+a1 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: e634785c, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: bf1b2f11, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 00000001, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS:  e634785c 

FAULTING_IP: 
ati3duag!r200ProcEyeRoute+a1
bf1b2f11 89543904        mov     dword ptr [ecx+edi+4],edx

MM_INTERNAL_CODE:  1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  CoDWaW.exe

LAST_CONTROL_TRANSFER:  from 00000000 to bf1b2f11

STACK_TEXT:  
9f862918 00000000 e14215d0 e2d73010 bf264303 ati3duag!r200ProcEyeRoute+0xa1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ati3duag!r200ProcEyeRoute+a1
bf1b2f11 89543904        mov     dword ptr [ecx+edi+4],edx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  ati3duag!r200ProcEyeRoute+a1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ati3duag

IMAGE_NAME:  ati3duag.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4844b372

FAILURE_BUCKET_ID:  0x50_ati3duag!r200ProcEyeRoute+a1

BUCKET_ID:  0x50_ati3duag!r200ProcEyeRoute+a1

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

0: kd> lmvm ati3duag
start    end        module name
bf18f000 bf4e5940   ati3duag M (pdb symbols)          I:\Symbols\dll\ati3duag.pdb
    Loaded symbol image file: ati3duag.dll
    Image path: ati3duag.dll
    Image name: ati3duag.dll
    Timestamp:        Tue Jun 03 04:58:58 2008 (4844B372)
    CheckSum:         003628BB
    ImageSize:        00356940
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[gbhall]

Using safe mode, try each memory stick singly. It is very odd to get an immediate fault on memtest86. Are you using the latest version ? Are you running it from a completely separate boot to Windows? e.g. from floppy, or bootable CD of any description.

Run hardware tests on your hard drive, starting with chkdsk /f and going on to manufacturers test set.

Can you take out the video card and run either onboard video or a loan video card?

pPlease give some history - has the PC run fine before, for how long, what did you do last before the fault began?

 

[Aerendyl]

Try with different RAM stick. Take the RAM to your friend and try it there.

 

[Mkkl]

About the history,
i put it together myself about 4 months ago, no problems and no different hardware or anything in it since then.
I didn't have the problem before i got COD 4 but i don't know if i would have had it in the begin because i didn't play games like COD 4 when it was just finished.

And i don't have another video card but i will try to get another one.

@ Black Knight, i tried using different sticks in my computer if you mean different like new, not another brand or something like that.

 

[gbhall]

On the face of it, the running of COD 4 (whatever that is, sorry ), has damaged either your video card or motherboard. Heat would do that, and running games at high refresh-rates causes heating....if you find yourself having to replace the video card, look to the cooling as well.

 

[Mkkl]

COD 4 is Call Of Duty 4, i hope you know wat call of duty is