Please analyze my win7 x64 minidump file for me

[geepondy]

Please analyze my win7 x64 minidump file for me(updated

I had gone a long time between BSODs until this occurred a couple of days ago. If somebody could analyze it for me, it would be greatly appreciated.

 

[usasma]

Not much info in the single memory dump file. Please zip up and upload the entire contents of the C:\Windows\Minidump folder. Often we need all of the minidumps to establish a pattern.

The only significant mention is that these drivers are older and should be updated:

LMouFilt.Sys Fri Feb 29 05:08:31 2008
LHidFilt.Sys Fri Feb 29 05:08:27 2008

Summary of the BSOD:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Dec 22 21:09:40.314 2009 (GMT-5)
System Uptime: 6 days 1:26:54.296
BugCheck 7A, {fffff6fc400394d8, ffffffffc000000e, 93096be0, fffff8800729b000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+34cde )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System

 

[geepondy]

Ok, I've had two more crashes since original post. Here are all three mini dump files. Thanks for any assistance.

 

[zigzag3143]

Ok, I've had two more crashes since original post. Here are all three mini dump files. Thanks for any assistance.

Hi Geepondy

Usual causes: Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack

Lets start with the memory. download memtestx86 and run it for 5 passes.

For corrupt paging file. go to the system control panel and uncheck paging file. reboot. check page file and it will rebuild.

For file system corruption
run a system file check
type cmd in search>right clICk and run as admin>SFC /SCANNOW

fOR hd
RUN CHKDSK /r

DMPS

021310-44725-01.dmp    2/13/2010 9:03:50 PM    KERNEL_DATA_INPAGE_ERROR    0x0000007a    fffff6fb`80008000    ffffffff`c000000e    00000000`a7576880    fffff700`01000000    ntoskrnl.exe    ntoskrnl.exe+71f00        x64    
122209-34304-01.dmp    12/22/2009 9:11:52 PM    KERNEL_DATA_INPAGE_ERROR    0x0000007a    fffff6fc`400394d8    ffffffff`c000000e    00000000`93096be0    fffff880`0729b000    ntoskrnl.exe    ntoskrnl.exe+71f00        x64    
013110-47798-01.dmp    1/31/2010 1:36:32 PM    KERNEL_DATA_INPAGE_ERROR    0x0000007a    fffff6fc`40007320    ffffffff`c00000c0    00000000`22ce1860    fffff880`00e64f90    volmgr.sys    volmgr.sys+ff90        x64

Analysis

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


Loading Dump File [C:\Users\K\Desktop\New folder\021310-44725-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`02a0f000 PsLoadedModuleList = 0xfffff800`02c4ce50
Debug session time: Sat Feb 13 21:01:37.338 2010 (GMT-5)
System Uptime: 6 days 5:11:26.352
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fb80008000, ffffffffc000000e, a7576880, fffff70001000000}

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

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

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

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fb80008000, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 00000000a7576880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff70001000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000000e

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88003386f70 -- (.trap 0xfffff88003386f70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff70001080068 rbx=0000000000000000 rcx=0000000000000009
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d8e9da rsp=fffff88003387100 rbp=0000000000000009
 r8=fffff70001000000  r9=0000000000000000 r10=8000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!MiInsertVadCharges+0x10a:
fffff800`02d8e9da 490fa308        bt      qword ptr [r8],rcx ds:ffff:fffff700`01000000=b8c1ea229f5b3127
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002af4438 to fffff80002a80f00

STACK_TEXT:  
fffff880`03386c58 fffff800`02af4438 : 00000000`0000007a fffff6fb`80008000 ffffffff`c000000e 00000000`a7576880 : nt!KeBugCheckEx
fffff880`03386c60 fffff800`02a72d8b : fffffa80`076bf7c0 fffff880`03386dd0 fffffa80`03b596a8 fffff880`033873b0 : nt! ?? ::FNODOBFM::`string'+0x34cde
fffff880`03386d40 fffff800`02a9c09b : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : nt!MiIssueHardFault+0x28b
fffff880`03386e10 fffff800`02a7efee : 00000000`00000000 00000000`0145f000 00000000`00000000 fffff800`02a9caf5 : nt!MmAccessFault+0x14bb
fffff880`03386f70 fffff800`02d8e9da : fffff800`02c0ea00 fffff880`02fd3180 00000000`0000000f 00000000`000000ad : nt!KiPageFault+0x16e
fffff880`03387100 fffff800`02d804c3 : ffffffff`00000000 ffffffff`ffffffff 00000000`00000004 00000000`000007ff : nt!MiInsertVadCharges+0x10a
fffff880`03387190 fffff800`02a80153 : ffffffff`ffffffff fffff880`03387ad8 00000000`00000080 fffff880`03387ac8 : nt!NtAllocateVirtualMemory+0x773
fffff880`03387340 fffff800`02a7c6f0 : fffff800`02d47800 ffffffff`ffffffff 00000000`00000000 86200001`12cbe025 : nt!KiSystemServiceCopyEnd+0x13
fffff880`03387548 fffff800`02d47800 : ffffffff`ffffffff 00000000`00000000 86200001`12cbe025 80000001`12cbe121 : nt!KiServiceLinkage
fffff880`03387550 fffff800`02a80153 : fffffa80`03a8b700 00000000`00005a4d 00000000`ff630000 00000000`00000000 : nt!NtSetInformationProcess+0x383
fffff880`033878a0 fffff800`02a7c6f0 : fffff800`02d4abce 00000000`00000000 00000000`ff6300e8 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`03387a38 fffff800`02d4abce : 00000000`00000000 00000000`ff6300e8 00000000`00000000 fffff800`02d77034 : nt!KiServiceLinkage
fffff880`03387a40 fffff800`02d493b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00001000 : nt!RtlCreateUserStack+0x122
fffff880`03387b30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspAllocateThread+0x29e


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+34cde
fffff800`02af4438 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+34cde

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34cde

BUCKET_ID:  X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34cde

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

3: kd> lmvm nt
start             end                 module name
fffff800`02a0f000 fffff800`02fec000   nt         (pdb symbols)          d:\symbols\ntkrnlmp.pdb\F8E2A8B5C9B74BF4A6E4A48F180099942\ntkrnlmp.pdb
    Loaded symbol image file: ntkrnlmp.exe
    Mapped memory image file: d:\symbols\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
    Image path: ntkrnlmp.exe
    Image name: ntkrnlmp.exe
    Timestamp:        Mon Jul 13 19:40:48 2009 (4A5BC600)
    CheckSum:         0054B487
    ImageSize:        005DD000
    File version:     6.1.7600.16385
    Product version:  6.1.7600.16385
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     ntkrnlmp.exe
    OriginalFilename: ntkrnlmp.exe
    ProductVersion:   6.1.7600.16385
    FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
    FileDescription:  NT Kernel & System
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

 

[panorama]

Please, be kind to analyze my dump files. Thank you in advance.