Three BSODs within the past few days

Hello! I have had three crashes within the past few days, and each has cited a different file as the cause. I'm not really sure what to do. I did not do anything new or different when this started--no drivers were updated, no new programs, nothing. I am fully up-to-date on my Windows and driver updates.

Steps I have tried:

• Ran memtest86+, no errors were found.
• Was running the latest stable release of my graphics driver (314.07), upgraded to the latest beta release (314.21) to try to fix--did not help.
• Ran sfc /scannow, it found no errors.

I'm not sure what else to do. Any help would be greatly appreciated!

Your errors seem to be gfx related, first step IMO would be to uninstall all gfx drivers run Drivers - Clean Left over Files after Uninstalling then reinstall new drivers

Get temp monitoring software if you dont already and run Video Card - Stress Test with Furmark whilst checking temps should give you an idea if your card is OK

Any more dumps after this and post back with new files :)

Can draw anything conclusive from that last dump but it is still complaing about nvidia drivers

Exactly same as before blames nVidia drivers

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff88047ec5000, 1, fffff88005215243, 5}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Could not read faulting driver name
Probably caused by : nvlddmkm.sys ( nvlddmkm+18b243 )
Followup: MachineOwner
---------
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: fffff88047ec5000, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff88005215243, 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: GetPointerFromAddress: unable to read from fffff80001ec3100
GetUlongFromAddress: unable to read from fffff80001ec31c0
 fffff88047ec5000 Nonpaged pool
FAULTING_IP: 
nvlddmkm+18b243
fffff880`05215243 890491          mov     dword ptr [rcx+rdx*4],eax
MM_INTERNAL_CODE:  5
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  dwm.exe
CURRENT_IRQL:  0
TRAP_FRAME:  fffff88002dabe60 -- (.trap 0xfffff88002dabe60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000003f3a01 rbx=0000000000000000 rcx=fffff88007800000
rdx=00000000101b1400 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88005215243 rsp=fffff88002dabff0 rbp=fffff88002dabff0
 r8=fffffa8007860368  r9=00000000406c5000 r10=0000000000000012
r11=fffff88002dac060 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac po nc
nvlddmkm+0x18b243:
fffff880`05215243 890491          mov     dword ptr [rcx+rdx*4],eax ds:fffff880`47ec5000=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80001d07673 to fffff80001c8ac40
STACK_TEXT:  
fffff880`02dabcf8 fffff800`01d07673 : 00000000`00000050 fffff880`47ec5000 00000000`00000001 fffff880`02dabe60 : nt!KeBugCheckEx
fffff880`02dabd00 fffff800`01c88d6e : 00000000`00000001 fffff880`47ec5000 fffffa80`070ca900 fffffa80`07860000 : nt! ?? ::FNODOBFM::`string'+0x43801
fffff880`02dabe60 fffff880`05215243 : fffff880`02dac050 fffff880`05291661 fffff880`02dac630 fffffa80`07860000 : nt!KiPageFault+0x16e
fffff880`02dabff0 fffff880`02dac050 : fffff880`05291661 fffff880`02dac630 fffffa80`07860000 fffffa80`07860368 : nvlddmkm+0x18b243
fffff880`02dabff8 fffff880`05291661 : fffff880`02dac630 fffffa80`07860000 fffffa80`07860368 00000000`406c5000 : 0xfffff880`02dac050
fffff880`02dac000 fffff880`02dac630 : fffffa80`07860000 fffffa80`07860368 00000000`406c5000 fffff880`003f3a01 : nvlddmkm+0x207661
fffff880`02dac008 fffffa80`07860000 : fffffa80`07860368 00000000`406c5000 fffff880`003f3a01 fffff880`02dac060 : 0xfffff880`02dac630
fffff880`02dac010 fffffa80`07860368 : 00000000`406c5000 fffff880`003f3a01 fffff880`02dac060 00000000`00000000 : 0xfffffa80`07860000
fffff880`02dac018 00000000`406c5000 : fffff880`003f3a01 fffff880`02dac060 00000000`00000000 00000000`406c5000 : 0xfffffa80`07860368
fffff880`02dac020 fffff880`003f3a01 : fffff880`02dac060 00000000`00000000 00000000`406c5000 00000000`003f3a01 : 0x406c5000
fffff880`02dac028 fffff880`02dac060 : 00000000`00000000 00000000`406c5000 00000000`003f3a01 00000000`00000040 : 0xfffff880`003f3a01
fffff880`02dac030 00000000`00000000 : 00000000`406c5000 00000000`003f3a01 00000000`00000040 fffff880`02dac0a0 : 0xfffff880`02dac060
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nvlddmkm+18b243
fffff880`05215243 890491          mov     dword ptr [rcx+rdx*4],eax
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  nvlddmkm+18b243
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME:  nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  51427b3c
FAILURE_BUCKET_ID:  X64_0x50_nvlddmkm+18b243
BUCKET_ID:  X64_0x50_nvlddmkm+18b243
Followup: MachineOwner
---------
0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0508a000 fffff880`05b35000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Mar 15 01:37:00 2013 (51427B3C)
    CheckSum:         00A8D47C
    ImageSize:        00AAB000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

You could try roling back to an older driver that worked for you 306.97 is a good one, avoid the one dated dec12/jan13

Do you have another machine you can try the vid card in or another card to try in this machine or onboard gfx you can use for testing ?

Did you try rolling back the gfx driver ? i only suggested onboard gfx as a test not a permanent solution

One dump wont load other blames memory/driver problem, did you let memtest run for multiple passes ?
You could also do a check on HDD Hard Drive Diagnostic Procedure using something like SeaTools | Seagate

Another option would be to enable driver verifier to try to flush out any faulting driver
Using Driver Verifier to identify issues with Drivers