BSOD, help plzz

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86

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


Loading Dump File [C:\Users\Josh\Desktop\Mini020811-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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18488.amd64fre.vistasp1_gdr.100608-0458
Machine Name:
Kernel base = 0xfffff800`02464000 PsLoadedModuleList = 0xfffff800`02629db0
Debug session time: Tue Feb  8 17:25:15.924 2011 (UTC + 0:00)
System Uptime: 0 days 0:01:49.968
Loading Kernel Symbols
..........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa81069129d0, 1, fffffa6000c7083b, 5}


Could not read faulting driver name
Probably caused by : fileinfo.sys ( fileinfo!FIPreCreateCallback+1d1 )

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

*******************************************************************************
*                                                                             *
*                        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: fffffa81069129d0, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffffa6000c7083b, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS:  fffffa81069129d0 

FAULTING_IP: 
fltmgr!FltGetInstanceContext+4b
fffffa60`00c7083b f00fc14150      lock xadd dword ptr [rcx+50h],eax

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffffa6007348490 -- (.trap 0xfffffa6007348490)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffffa8106912980
rdx=fffffa60073486a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa6000c7083b rsp=fffffa6007348620 rbp=fffffa80040528b0
 r8=fffffa60073487c0  r9=0000000000000002 r10=fffffa800ca9a010
r11=0000000000000011 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
fltmgr!FltGetInstanceContext+0x4b:
fffffa60`00c7083b f00fc14150      lock xadd dword ptr [rcx+50h],eax ds:744e:fffffa81`069129d0=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800024c74e2 to fffff800024b93d0

STACK_TEXT:  


STACK_COMMAND:  kb

FOLLOWUP_IP: 
fileinfo!FIPreCreateCallback+1d1
fffffa60`00cb5929 41bd01000000    mov     r13d,1

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  fileinfo!FIPreCreateCallback+1d1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: fileinfo

IMAGE_NAME:  fileinfo.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  47919323

FAILURE_BUCKET_ID:  X64_0x50_fileinfo!FIPreCreateCallback+1d1

BUCKET_ID:  X64_0x50_fileinfo!FIPreCreateCallback+1d1

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