BSOD/probably HDD corrupt [DUMP DATA]

Hello.

When doing something with a lot of HDD operations, sometimes i get BSOD. Also sometimes, Windows Media player closes with errors when playing video files from the HDD. As i understand, problem is with file system. Chkdsk didn't help, so is the hard drive corrupt and will its replacement solve the problem? Here is my memory dump:

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 806ed134, The address that the exception occurred at
Arg3: f89a0b84, Exception Record Address
Arg4: f89a0880, Context Record Address

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


ERROR_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>

FAULTING_IP:
hal!ExAcquireFastMutex+c
806ed134 ff09 dec dword ptr [ecx]

EXCEPTION_PARAMETER1: f89a0b84

CONTEXT: f89a0880 -- (.cxr fffffffff89a0880)
eax=00000000 ebx=00000000 ecx=00000080 edx=f89a0c9c esi=81ceac00 edi=e24b75e8
eip=806ed134 esp=f89a0c4c ebp=f89a0cc8 iopl=0 nv up ei ng nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297
hal!ExAcquireFastMutex+0xc:
806ed134 ff09 dec dword ptr [ecx] ds:0023:00000080=????????
Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from f83aa398 to 806ed134

STACK_TEXT:
f89a0c48 f83aa398 81b90920 823253d0 81ceac00 hal!ExAcquireFastMutex+0xc
f89a0cc8 804e3d77 8230e020 81b90910 82325d10 Ntfs!NtfsFsdClose+0xa4
f89a0cd8 f8429459 f89a0d28 804e3d77 8230fc10 nt!IopfCallDriver+0x31
f89a0ce0 804e3d77 8230fc10 81b90910 81b90910 sr!SrPassThrough+0x31
f89a0cf0 8056afec 81ceabe8 00000000 00000000 nt!IopfCallDriver+0x31
f89a0d28 80563ff6 00ceac00 81ceabe8 00000000 nt!IopDeleteFile+0x132
f89a0d44 804e3c55 81ceac00 00000000 806ed03c nt!ObpRemoveObjectRoutine+0xdf
f89a0d68 804f736e 8055f1b8 81bf4728 806ed070 nt!ObfDereferenceObject+0x5f
f89a0d8c 8050087f e27b11d8 00000000 823c1020 nt!MiSegmentDelete+0xdd
f89a0dac 8057dfed 00000000 00000000 00000000 nt!MiDereferenceSegmentThread+0x9e
f89a0ddc 804fa477 805007e9 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


FOLLOWUP_IP:
Ntfs!NtfsFsdClose+a4
f83aa398 8b45dc mov eax,[ebp-0x24]

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: Ntfs!NtfsFsdClose+a4

MODULE_NAME: Ntfs

IMAGE_NAME: Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107eea

STACK_COMMAND: .cxr fffffffff89a0880 ; kb

BUCKET_ID: 0x7E_Ntfs!NtfsFsdClose+a4

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

 

possible pool corruption or freed memory. ill post later tonight how to use special pool and possibly verifier to identify the bad guy. In the mean time, it would be great to know your OS stats, or run the tool in my sig to get the other info.