Quick and final BSOD analyze plz for me!

BSOD came and I think my memory has something to do with It. If this is a memory crash let me know! Help is very appreciated, I'll give reps!

WIGILOCO said:

BSOD came and I think my memory has something to do with It. If this is a memory crash let me know! Help is very appreciated, I'll give reps!

This one was probably caused by VSSVC.exe which is the volume shadow service used in backup.

I would run a system file check
type cmd in search>right click and run as admin>sfc /scannow

Code:

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


Loading Dump File [C:\Users\K\Desktop\021110-31309-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a13000 PsLoadedModuleList = 0xfffff800`02c50e50
Debug session time: Thu Feb 11 12:54:26.180 2010 (GMT-5)
System Uptime: 0 days 0:04:31.475
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff880077f24b8, fffff880077f1d10, fffff80002a8d0c4}

Probably caused by : Ntfs.sys ( Ntfs!NtfsAcquireExclusiveFcb+73 )

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

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff880077f24b8
Arg3: fffff880077f1d10
Arg4: fffff80002a8d0c4

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


EXCEPTION_RECORD:  fffff880077f24b8 -- (.exr 0xfffff880077f24b8)
ExceptionAddress: fffff80002a8d0c4 (nt!ExAcquireResourceExclusiveLite+0x0000000000000054)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880077f1d10 -- (.cxr 0xfffff880077f1d10)
rax=0000000000000001 rbx=bffffa8006e0b8f0 rcx=bffffa8006e0b8f0
rdx=fffff8a007dbe501 rsi=0000000000000000 rdi=fffff88002f63180
rip=fffff80002a8d0c4 rsp=fffff880077f26f0 rbp=0000000000000001
 r8=0000000000000000  r9=0000000000000001 r10=fffff880077f2840
r11=0000000000000000 r12=0000000000000000 r13=00000000c00000d8
r14=fffffa800417c6d0 r15=0000000000010001
iopl=0         nv up di pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010046
nt!ExAcquireResourceExclusiveLite+0x54:
fffff800`02a8d0c4 f0480fba696000  lock bts qword ptr [rcx+60h],0 ds:002b:bffffa80`06e0b950=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  VSSVC.exe

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbb0e0
 ffffffffffffffff 

FOLLOWUP_IP: 
Ntfs!NtfsAcquireExclusiveFcb+73
fffff880`0122c5d3 84c0            test    al,al

FAULTING_IP: 
nt!ExAcquireResourceExclusiveLite+54
fffff800`02a8d0c4 f0480fba696000  lock bts qword ptr [rcx+60h],0

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff8800122c5d3 to fffff80002a8d0c4

STACK_TEXT:  
fffff880`077f26f0 fffff880`0122c5d3 : 00000000`c00000d8 fffff8a0`07dbe5b0 fffffa80`0403a2d0 00000000`00000702 : nt!ExAcquireResourceExclusiveLite+0x54
fffff880`077f2760 fffff880`012988a8 : 00000000`00000000 fffff880`077f2a80 00000000`00000001 fffffa80`0403a2d0 : Ntfs!NtfsAcquireExclusiveFcb+0x73
fffff880`077f27b0 fffff880`012e9bbd : fffffa80`0403a2d0 fffffa80`049ad180 00000000`00000001 0000000f`ffffff00 : Ntfs!NtfsFlushVolume+0x188
fffff880`077f28e0 fffff880`012ea5f0 : fffffa80`0403a2d0 fffffa80`04042600 fffffa80`05e8a590 00000000`00000000 : Ntfs!NtfsCommonFlushBuffers+0x459
fffff880`077f29c0 fffff880`010ec23f : fffffa80`040429a0 fffffa80`04042600 fffffa80`0403a2d0 fffff880`077f29e8 : Ntfs!NtfsFsdFlushBuffers+0x104
fffff880`077f2a30 fffff880`010ea6df : fffffa80`0493f8e0 00000000`00000000 fffffa80`0493f800 fffffa80`04042600 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`077f2ac0 fffff800`02d98929 : 00000000`00000002 fffffa80`05e8a590 00000000`00000000 fffffa80`04042600 : fltmgr!FltpDispatch+0xcf
fffff880`077f2b20 fffff800`02d268ad : fffffa80`04042600 fffffa80`0417c6d0 fffffa80`05e8a590 00000000`000007ff : nt!IopSynchronousServiceTail+0xf9
fffff880`077f2b90 fffff800`02a84153 : fffffa80`0417c6d0 00000000`ff452270 fffffa80`0493f8e0 fffffa80`05e8a590 : nt!NtFlushBuffersFile+0x171
fffff880`077f2c20 00000000`77a9036a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02d0f478 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a9036a


SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  Ntfs!NtfsAcquireExclusiveFcb+73

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc14f

STACK_COMMAND:  .cxr 0xfffff880077f1d10 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsAcquireExclusiveFcb+73

BUCKET_ID:  X64_0x24_Ntfs!NtfsAcquireExclusiveFcb+73

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

Ok I will do that. I'll tell the results. Can bad memory or some memory fail cause this kind of BSOD too?

It didn't find any errors. If this continues with my memory back to 1333MHz, should I repair install win 7? Is it bad?

WIGILOCO said:

Ok I will do that. I'll tell the results. Can bad memory or some memory fail cause this kind of BSOD too?

That one dmp had zero reference to memory. If you have others I can narrow it. If you are concerned ren memtestx86 it will tell you for sure

Ken

Now running prime95 and I will check what comes. My memory isn't failing now I have that sense. But here is 2 earlier BSOD's if you could analyze them please =)

WIGILOCO said:

Now running prime95 and I will check what comes. My memory isn't failing now I have that sense. But here is 2 earlier BSOD's if you could analyze them please =)

Both were bugcheck D1 caused by device driver

What device driver was it can you get It from there?