HELP!! - Can anyone help me read this minidump?

My system hangs or gives a BSOD or simply shuts down by itself every without any regularity of pattern I can figure out. The only thing I know is that when the SATAII disk is disconnected it doesn't happen.
My system is:
Gigabyte mobo: AN8 Ultra
AMD 3000 venice core
1 GB memory (Kingston CL 3)
Radeon 300X video card.
SATAII WD hard drive (200GB)

So far I have:
- Ran memtest, and diagnostics tools from here to the other side of the moon, on my memory sticks, hard disk, video card, and processor.
- Replaced the hard disk
- Tested the system on linux - it creashed too!
- Had a technition test each piece of hardware and give it a clean bill of health (including the PSU)
- Upgraded my BIOS to include the erratum 109 correction of AMD
- Lost my temper on several occations!
- And last attempt was to change the timing of the memory from auto to SPD in the BIOS - whatever that means.

Nothing seems to help.

Can anyone see from this minidump deciphered log if the problem is in the memory timings? Is it possible that my mobo is the problem?

Help!
I am close to giving up!






the minidump analysis:
--------------------------------------------------------------------------




C:\WINDOWS\Minidump>"E:\Program Files\Debugging Tools for Windows\kd.exe" -y srv
*c:\symbols*http://msdl.microsoft.com/download/symbols -i c:\windows\i386 -z "C:
\WINDOWS\Minidump\Mini010306-03.dmp"

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


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

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is: c:\windows\i386
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Tue Jan 3 18:35:43.828 2006 (GMT+2)
System Uptime: 0 days 4:52:52.413
Loading Kernel Symbols
................................................................................
.......................................
Loading unloaded module list
.................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1902fe, b82f757c, b82f7278, f73c1883}

Unable to load image avg7rsw.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for avg7rsw.sys
*** ERROR: Module load completed but symbols could not be loaded for avg7rsw.sys

Probably caused by : Ntfs.sys ( Ntfs!NtfsCreateScb+54 )

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

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

NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 001902fe
Arg2: b82f757c
Arg3: b82f7278
Arg4: f73c1883

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


EXCEPTION_RECORD: b82f757c -- (.exr ffffffffb82f757c)
ExceptionAddress: f73c1883 (Ntfs!NtfsCreateScb+0x00000054)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 0000003c
Attempt to read from address 0000003c

CONTEXT: b82f7278 -- (.cxr ffffffffb82f7278)
eax=000000a0 ebx=ffffffc0 ecx=8556e930 edx=f73b7358 esi=e41bec58 edi=00000000
eip=f73c1883 esp=b82f7644 ebp=b82f76c8 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
Ntfs!NtfsCreateScb+0x54:
f73c1883 3b437c cmp eax,[ebx+0x7c] ds:0023:0000003c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

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

READ_ADDRESS: 0000003c

BUGCHECK_STR: 0x24

LAST_CONTROL_TRANSFER: from f73c6a7c to f73c1883

STACK_TEXT:
b82f76c8 f73c6a7c b82f7848 e41bec58 000000a0 Ntfs!NtfsCreateScb+0x54
b82f7824 f73c2f72 b82f7848 8547f2b0 b82f7978 Ntfs!NtfsCommonCreate+0xfd3
b82f79d0 f7449f70 8547f2b0 b82f7c00 85b73020 Ntfs!NtfsNetworkOpenCreate+0x8a
b82f79f0 f7b3895a 8547f2b0 b82f7c00 85e15718 sr!SrFastIoQueryOpen+0x40
WARNING: Stack unwind information not available. Following frames may be wrong.
b82f7af4 805b365e 86761980 00000000 85540b90 avg7rsw+0x95a
b82f7b7c 805afb3f 00000000 b82f7bbc 00000040 nt!ObpLookupObjectName+0x56a
b82f7bd0 8056b0cf 00000000 00000000 b82f7c01 nt!ObOpenObjectByName+0xeb
b82f7d54 8053c808 0e85fa10 0e85f9e8 0e85fa3c nt!NtQueryAttributesFile+0xf1
b82f7d54 7c90eb94 0e85fa10 0e85f9e8 0e85fa3c nt!KiFastCallEntry+0xf8
0e85fa3c 00000000 00000000 00000000 00000000 0x7c90eb94


FOLLOWUP_IP:
Ntfs!NtfsCreateScb+54
f73c1883 3b437c cmp eax,[ebx+0x7c]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: Ntfs!NtfsCreateScb+54

MODULE_NAME: Ntfs

IMAGE_NAME: Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107eea

STACK_COMMAND: .cxr ffffffffb82f7278 ; kb

FAILURE_BUCKET_ID: 0x24_Ntfs!NtfsCreateScb+54

BUCKET_ID: 0x24_Ntfs!NtfsCreateScb+54

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

kd>

Gigabyte does not make the AN8 board - Abit does.

Your mobo does NOT support SATA2.

Sorry - it is an ABIT mobo - my mistake

Anyhow the computer does work for a while, and the HD is accessible with the SATA connection, only after a while it reboots or freezes or throw a BSOD.

Is it possible that the HD works with SATAII and the mobo works with SATA I?
Can that be the cause of my problems?