Please help me read dump files

My computer has been experiencing BSOD lately through out this month. I have attached some files with the dumps. Please help me figure out what was the cause of the BSODs. Thank you very much in advance.

monsteranh said:

My computer has been experiencing BSOD lately through out this month. I have attached some files with the dumps. Please help me figure out what was the cause of the BSODs. Thank you very much in advance.

Your video driver, re-install using this method.

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper


Or Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.

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\Seven Forums\053111-26754-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02c1d000 PsLoadedModuleList = 0xfffff800`02e62650
Debug session time: Tue May 31 22:09:52.090 2011 (GMT-4)
System Uptime: 0 days 21:16:40.932
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {20, 2, 0, fffff8800f411ec9}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1deec9 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000020, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800f411ec9, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ecc100
 0000000000000020 

CURRENT_IRQL:  2

FAULTING_IP: 
nvlddmkm+1deec9
fffff880`0f411ec9 ff5720          call    qword ptr [rdi+20h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff80004272760 -- (.trap 0xfffff80004272760)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000012 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800f411ec9 rsp=fffff800042728f0 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=000000000000000a
r11=fffff80004272a20 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nvlddmkm+0x1deec9:
fffff880`0f411ec9 ff5720          call    qword ptr [rdi+20h] ds:3600:00000000`00000020=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c9c2a9 to fffff80002c9cd00

STACK_TEXT:  
fffff800`04272618 fffff800`02c9c2a9 : 00000000`0000000a 00000000`00000020 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`04272620 fffff800`02c9af20 : fffffa80`05957000 00000000`00000000 fffffa80`059df000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`04272760 fffff880`0f411ec9 : fffffa80`07961000 00000000`00000000 00000000`00002080 00000000`00000000 : nt!KiPageFault+0x260
fffff800`042728f0 fffffa80`07961000 : 00000000`00000000 00000000`00002080 00000000`00000000 00000000`00000000 : nvlddmkm+0x1deec9
fffff800`042728f8 00000000`00000000 : 00000000`00002080 00000000`00000000 00000000`00000000 fffff880`0f74cbd1 : 0xfffffa80`07961000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+1deec9
fffff880`0f411ec9 ff5720          call    qword ptr [rdi+20h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nvlddmkm+1deec9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d64bb6c

FAILURE_BUCKET_ID:  X64_0xD1_nvlddmkm+1deec9

BUCKET_ID:  X64_0xD1_nvlddmkm+1deec9

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

thank for the reply. I used Phyxion to do a complete wipe and then reinstalled the video driver from their website. It seemed to be working fine but then the BSOD came back. Here are the 2 new dump files.