BSOD: Memory_Management or NFTS.sys

I built this computer at the end of December 2009. It worked great for a while but recently I have been getting BSOD Crashes. They were very intermittent at first but have become frequent. I have yet to identify a cause as it seems to happen at random. Please help me analyze these dumps and identify my problem. Thank you in advance for your help.

Steps I have taken thus far:

1. Removed Overclock / Reset BIOS to Defaults (OC was 3.4GHz = 400MHz * 8.5)
2. Repair Windows via Upgrade from DVD
3. Ran System File Checker - No Integrity Issues
4. Ran Check Disk with Repairs
5. Scanned for a Virus with Microsoft Security Essentials
6. Ran CCleaner to Fix Registry

System Specs Below.

Besides what you have alredy done it would be a good idea to run memtest86+ overnight and also do a disk drive diagnostic test from the manufacturer of the disk drive.

Code:

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


Loading Dump File [C:\Users\Nickle\AppData\Local\Temp\Rar$DI00.225\022310-38204-01.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 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03013000 PsLoadedModuleList = 0xfffff800`03250e50
Debug session time: Tue Feb 23 08:43:39.599 2010 (GMT-5)
System Uptime: 0 days 8:23:23.097
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa80026f3e50, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa80026f3e50
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  MOM.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800030f726e to fffff80003084f00

STACK_TEXT:  
fffff880`0aab2ea8 fffff800`030f726e : 00000000`0000001a 00000000`00041790 fffffa80`026f3e50 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0aab2eb0 fffff800`030b85d9 : 00000000`00000000 000007fe`fbc7bfff 00000000`00000000 fffff800`03057c8a : nt! ?? ::FNODOBFM::`string'+0x339d6
fffff880`0aab3070 fffff800`03058080 : ffffffff`ffffffff fffff880`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`0aab3190 fffff800`033677af : fffff8a0`0a2c4060 fffff880`0aab34a0 00000000`00000000 fffffa80`070e2060 : nt!MmCleanProcessAddressSpace+0x228
fffff880`0aab31e0 fffff800`03341b3d : 00000000`40010004 00000000`00000001 000007ff`fff04000 00000000`00000000 : nt!PspExitThread+0x47f
fffff880`0aab32b0 fffff800`03061a43 : fffff900`c20f9010 fffff960`001c4bad 00000000`00000000 fffff900`c0606cf0 : nt!PsExitSpecialApc+0x1d
fffff880`0aab32e0 fffff800`03061e80 : 00000000`00000000 fffff880`0aab3360 fffff800`03342710 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`0aab3360 fffff800`030841f7 : 00000000`00000008 00000000`1b7c4160 00000000`1bf3e201 00000000`1bf3df60 : nt!KiInitiateUserApc+0x70
fffff880`0aab34a0 00000000`7716fdd6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`1bf3e730 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7716fdd6


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+339d6
fffff800`030f726e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+339d6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339d6

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339d6

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

BHowell said:

I built this computer at the end of December 2009. It worked great for a while but recently I have been getting BSOD Crashes. They were very intermittent at first but have become frequent. I have yet to identify a cause as it seems to happen at random. Please help me analyze these dumps and identify my problem. Thank you in advance for your help.


Steps I have taken thus far:

1. Removed Overclock / Reset BIOS to Defaults (OC was 3.4GHz = 400MHz * 8.5)
2. Repair Windows via Upgrade from DVD
3. Ran System File Checker - No Integrity Issues
4. Ran Check Disk with Repairs
5. Scanned for a Virus with Microsoft Security Essentials
6. Ran CCleaner to Fix Registry

System Specs Below.

Hello Welcome to SF,

I guess the NTFS.sys is related to your HDD. Go to your Manufactures website and download the Diagnostic Tool and run it. Follow the Link for more info HD Diagnostic

Found that your RAID driver is out-dated which might casue BSOD. Update you RAID Driver.

Code:

 
jraid.sys    Tue Nov 04 07:50:09 2008

Hope this helps,
Captain