Seeking BSOD Assistance

Welcome to SF!

First, I suggest a memory test. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and run at least 5 passes.

If it checks out with no errors, follow these directions for enabling Driver Verifier. Please upload any new dmps that are generated. Using Driver Verifier to identify issues with Drivers

Code:

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


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_050510-84646-01.zip\050510-84646-01.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: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c51000 PsLoadedModuleList = 0xfffff800`02e8ee50
Debug session time: Wed May  5 11:52:23.474 2010 (GMT-4)
System Uptime: 1 days 23:45:22.300
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {7, 1b8080, 1eba3f, 0}

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

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000007, A driver has unlocked a page more times than it locked it
Arg2: 00000000001b8080, page frame number
Arg3: 00000000001eba3f, current share count
Arg4: 0000000000000000, 0

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


BUGCHECK_STR:  0x4E_7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  OUTLOOK.EXE

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d23949 to fffff80002cc1600

STACK_TEXT:  
fffff880`07787348 fffff800`02d23949 : 00000000`0000004e 00000000`00000007 00000000`001b8080 00000000`001eba3f : nt!KeBugCheckEx
fffff880`07787350 fffff800`02d23bdd : fffff8a0`048be000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x16dc6
fffff880`07787390 fffff800`02d3f5c9 : 00000000`00000000 fffffa80`000006c0 00000000`00000000 fffffa80`00687c11 : nt! ?? ::FNODOBFM::`string'+0x17075
fffff880`077873c0 fffff800`02cad834 : fffff8a0`04400000 fffff8a0`0de66800 fffffa80`08ba26c0 fffffa80`0760b6f0 : nt! ?? ::FNODOBFM::`string'+0x3fb3a
fffff880`07787600 fffff800`02cad3da : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`10457600 : nt!MmFlushSection+0x1f4
fffff880`077876c0 fffff880`012f1642 : fffffa80`0c86d5c8 fffff880`00000000 fffffa80`00000000 fffffa80`085f6bb0 : nt!CcFlushCache+0x88a
fffff880`077877c0 fffff880`012f26ba : fffff8a0`0411b140 fffff8a0`0411b140 fffff8a0`0411b140 fffffa80`10457670 : Ntfs!NtfsFlushUserStream+0x92
fffff880`07787840 fffff880`012f188e : fffffa80`10457670 fffff8a0`0411b140 00000000`00000000 00000000`00100000 : Ntfs!NtfsPerformOptimisticFlush+0x7a
fffff880`077878a0 fffff880`012f25f0 : fffffa80`10457670 fffffa80`07ba6c10 fffffa80`08da0f20 00000000`00000000 : Ntfs!NtfsCommonFlushBuffers+0x12a
fffff880`07787980 fffff880`0107023f : fffffa80`07ba6fb0 fffffa80`07ba6c10 fffffa80`10457670 fffff880`077879a8 : Ntfs!NtfsFsdFlushBuffers+0x104
fffff880`077879f0 fffff880`0106e6df : fffffa80`07f75760 00000000`00000000 fffffa80`07f75700 fffffa80`07ba6c10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`07787a80 fffff800`02fd8c49 : 00000000`00000002 fffffa80`08da0f20 00000000`00000000 fffffa80`07ba6c10 : fltmgr!FltpDispatch+0xcf
fffff880`07787ae0 fffff800`02f651c1 : fffffa80`07ba6c10 fffffa80`0c70d8e0 fffffa80`08da0f20 fffff880`009e9180 : nt!IopSynchronousServiceTail+0xf9
fffff880`07787b50 fffff800`02cc0853 : fffffa80`0c70d8e0 00000000`7ef56000 fffffa80`07f75760 fffffa80`08da0f20 : nt!NtFlushBuffersFile+0x171
fffff880`07787be0 00000000`76db036a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0383e728 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76db036a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+16dc6
fffff800`02d23949 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+16dc6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0x4E_7_nt!_??_::FNODOBFM::_string_+16dc6

BUCKET_ID:  X64_0x4E_7_nt!_??_::FNODOBFM::_string_+16dc6

Followup: MachineOwner

Hmm... it doesn't look like Verifier is enabled. Make sure you followed these directions exactly: Using Driver Verifier to identify issues with Drivers

You should update these old drivers:

Code:

fffff880`011b7000 fffff880`011c2d00   PxHlpa64 PxHlpa64.sys Wed Mar 12 21:58:17 2008 (47D88A39)
fffff880`03d8d000 fffff880`03da1000   rimmpx64 rimmpx64.sys Sun Mar 18 23:09:34 2007 (45FDFEEE)
fffff880`05600000 fffff880`05607c00   RimSerial_AMD64 RimSerial_AMD64.sys Mon Nov 24 12:01:01 2008 (492ADDCD)
fffff880`03da1000 fffff880`03db8000   rimspx64 rimspx64.sys Thu Jul 26 07:33:52 2007 (46A886A0)
fffff880`0428b000 fffff880`042e2000   rixdpx64 rixdpx64.sys Fri Jul 27 06:45:50 2007 (46A9CCDE)
fffff880`06d10000 fffff880`06d1b000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)