Help with Vista crashes

[slorenc]

I'm hoping someone can help me. In the last few days my computer just started blue screening. I think it's a driver but can figure out which one. Can someone help me interpret the dump file? Thanks.

Microsoft ® Windows Debugger Version 6.9.0003.113 X86

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [f:\mini101008-10.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 Server 2008 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 6001.18063.x86fre.vistasp1_gdr.080425-1930

Kernel base = 0x81e3b000 PsLoadedModuleList = 0x81f52c70

Debug session time: Fri Oct 10 22:42:41.605 2008 (GMT-4)

System Uptime: 0 days 0:00:51.714

Loading Kernel Symbols

....................................................................................................

.................................................

Loading User Symbols

Loading unloaded module list

.

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffffff, 8, ffffffff, 0}

Probably caused by : Unknown_Image ( PAGE_NOT_ZERO_VISTA )

Followup: MachineOwner

---------

*** Memory manager detected 4 instance(s) of page corruption, target is likely to have memory corruption.

0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)

Invalid system memory was referenced. This cannot be protected by try-except,

it must be protected by a Probe. Typically the address is just plain bad or it

is pointing at freed memory.

Arguments:

Arg1: ffffffff, memory referenced.

Arg2: 00000008, value 0 = read operation, 1 = write operation.

Arg3: ffffffff, If non-zero, the instruction address which referenced the bad memory

address.

Arg4: 00000000, (reserved)

Debugging Details:

------------------

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81f72868

Unable to read MiSystemVaType memory at 81f52420

ffffffff

FAULTING_IP:

+ffffffffffffffff

ffffffff ?? ???

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 10

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: System

CURRENT_IRQL: 0

BAD_PAGES_DETECTED: 4

TRAP_FRAME: 8b7b3a70 -- (.trap 0xffffffff8b7b3a70)

ErrCode = 00000010

eax=ffffffff ebx=00000000 ecx=99b0d670 edx=00000000 esi=99b0d640 edi=85380b18

eip=ffffffff esp=8b7b3ae4 ebp=8b7b3afc iopl=0 nv up ei ng nz na pe nc

cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286

ffffffff ?? ???

Resetting default scope

LAST_CONTROL_TRANSFER: from 81e95bb4 to 81ee0155

STACK_TEXT:

8b7b3a58 81e95bb4 00000008 ffffffff 00000000 nt!MmAccessFault+0x10a

8b7b3a58 ffffffff 00000008 ffffffff 00000000 nt!KiTrap0E+0xdc

WARNING: Frame IP not in any known module. Following frames may be wrong.

8b7b3ae0 805a5211 99b0d670 0000ffff 87bb6c90 0xffffffff

8b7b3afc 805a53de 99b0d640 99b0d640 8b7b3b20 fltmgr!DoFreeContext+0x57

8b7b3b0c 805b569d 99b0d640 87bb6c68 99b0f12c fltmgr!DoReleaseContext+0x42

8b7b3b20 805c2195 87bb6c94 99b0d64c ffffffff fltmgr!FltpDeleteContextList+0x125

8b7b3b40 805c23b6 87bb6c68 99b0f0f8 00000000 fltmgr!CleanupStreamListCtrl+0x1b

8b7b3b54 82061cdc 87bb6c6c 807e6734 00000000 fltmgr!DeleteStreamListCtrlCallback+0x5a

8b7b3b94 8ab03d9b 99b0f0f8 99b0f008 99b0f0f8 nt!FsRtlTeardownPerStreamContexts+0x135

8b7b3bb0 8aaeee6c 00000705 99b0f030 99b0f008 Ntfs!NtfsDeleteScb+0x1f4

8b7b3bc8 8aa7515a 8832f2f0 99b0f0f8 00000000 Ntfs!NtfsRemoveScb+0xc0

8b7b3be4 8aaeec55 8832f2f0 99b0f008 00000000 Ntfs!NtfsPrepareFcbForRemoval+0x59

8b7b3c28 8aa76bde 8832f2f0 99b0f0f8 99b0f298 Ntfs!NtfsTeardownStructures+0x62

8b7b3c50 8aaf4b66 8832f2f0 99b0f0f8 99b0f298 Ntfs!NtfsDecrementCloseCounts+0xad

8b7b3cb0 8ab031d4 8832f2f0 99b0f0f8 99b0f008 Ntfs!NtfsCommonClose+0x4da

8b7b3d44 81e7341d 00000000 00000000 84556d78 Ntfs!NtfsFspClose+0x117

8b7b3d7c 82010b18 00000000 807e6160 00000000 nt!ExpWorkerThread+0xfd

8b7b3dc0 81e69a3e 81e73320 00000000 00000000 nt!PspSystemThreadStartup+0x9d

00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND: kb

SYMBOL_NAME: PAGE_NOT_ZERO_VISTA

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: PAGE_NOT_ZERO_VISTA

Followup: MachineOwner

---------

*** Memory manager detected 4 instance(s) of page corruption, target is likely to have memory corruption.