Vista - BSOD and minidump points to ntfs.sys

I have quite a new computer and recently i installed a version on windows Vista Business. I get the BSOD regularly showing such errors as BAD_POOL_CALLER
PAGE_FAULT_IN_NON_PAGED_AREA
tdx.sys stop 0x0000007E

As stated in another forum I downloaded the windows debugger and searched the minidump file setting the symbols location to the one stated in the microsoft website. Here is the dump file. I looked through sevaral of these and most of these seems to point to ntfs.sys

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

Loading Dump File [C:\Windows\Minidump\Mini010108-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*Symbol information
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16575.x86fre.vista_gdr.071009-1548
Kernel base = 0x81800000 PsLoadedModuleList = 0x81911e10
Debug session time: Tue Jan 1 10:35:58.593 2008 (GMT+5)
System Uptime: 0 days 9:01:26.467
Loading Kernel Symbols
.................................................................................................................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1904ab, 87ecbb10, 87ecb80c, 818e7fc5}

Probably caused by : Ntfs.sys ( Ntfs!NtOfsFreeReadContext+29 )
Followup: MachineOwner
---------
0: 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: 001904ab
Arg2: 87ecbb10
Arg3: 87ecb80c
Arg4: 818e7fc5
Debugging Details:
------------------


EXCEPTION_RECORD: 87ecbb10 -- (.exr 0xffffffff87ecbb10)
ExceptionAddress: 818e7fc5 (nt!ExFreePoolWithTag+0x0000045b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 4b46664a
Attempt to read from address 4b46664a
CONTEXT: 87ecb80c -- (.cxr 0xffffffff87ecb80c)
eax=00000000 ebx=818e7b69 ecx=b22d3c4c edx=00000000 esi=4b466650 edi=4b466650
eip=818e7fc5 esp=87ecbbd8 ebp=87ecbc34 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!ExFreePoolWithTag+0x45b:
818e7fc5 0fb74ffa movzx ecx,word ptr [edi-6] ds:0023:4b46664a=????
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: STRING_DEREFERENCE
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
READ_ADDRESS: GetPointerFromAddress: unable to read from 819315ac
Unable to read MiSystemVaType memory at 819117e0
4b46664a
BUGCHECK_STR: 0x24
LAST_CONTROL_TRANSFER: from 8756dbe9 to 818e7fc5
STACK_TEXT:
87ecbc34 8756dbe9 4b466650 00000000 b23dac18 nt!ExFreePoolWithTag+0x45b
87ecbc4c 8759e95e b22d3b88 87ecbd14 83db6508 Ntfs!NtOfsFreeReadContext+0x29
87ecbc64 87597fc7 b23dac18 87ecbd14 876bef1f Ntfs!NtfsDeleteCcb+0x33
87ecbcb0 8757d126 83db6508 b23dad08 b23dac18 Ntfs!NtfsCommonClose+0x4bf
87ecbd44 81878fa0 00000000 00000000 83285ad0 Ntfs!NtfsFspClose+0x117
87ecbd7c 81a254e0 00000000 87ec0680 00000000 nt!ExpWorkerThread+0xfd
87ecbdc0 8189159e 81878ea3 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

FOLLOWUP_IP:
Ntfs!NtOfsFreeReadContext+29
8756dbe9 8b4730 mov eax,dword ptr [edi+30h]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: Ntfs!NtOfsFreeReadContext+29
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4549aceb
STACK_COMMAND: .cxr 0xffffffff87ecb80c ; kb
FAILURE_BUCKET_ID: 0x24_Ntfs!NtOfsFreeReadContext+29
BUCKET_ID: 0x24_Ntfs!NtOfsFreeReadContext+29
Followup: MachineOwner
---------
0: kd> .exr 0xffffffff87ecbb10
ExceptionAddress: 818e7fc5 (nt!ExFreePoolWithTag+0x0000045b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 4b46664a
Attempt to read from address 4b46664a
0: kd> .cxr 0xffffffff87ecb80c
eax=00000000 ebx=818e7b69 ecx=b22d3c4c edx=00000000 esi=4b466650 edi=4b466650
eip=818e7fc5 esp=87ecbbd8 ebp=87ecbc34 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!ExFreePoolWithTag+0x45b:
818e7fc5 0fb74ffa movzx ecx,word ptr [edi-6] ds:0023:4b46664a=????

And theres another point. I am almost certain that i get the BSOD when i acces one file named $WINDOWS.~LS in one of my partitions. Other than that i also get the BSOD randomly. I tried defragmenting the hard disk but that ddnt fix it. I also tried the seatools analysis software on my seagate hard disk and ddnt show up any errors. I would greatly appreciate if someone could help me out with this. My pc is

Core 2 Duo E4400
2 GB Kingston DDR667 PC5300 memory
ExpertVision Nvidia Geforce 8600GT
onboard LAN and Sound
ASUS P5B motherboard
Benq DVD RW drive
LG Combo drive
Hauppauge WinTV TV card

Thats about all of it THANKS.