BSOD (RSOD) playing WoW, Multiple Crashes.

Frontear, welcome to Seven Forums, I will try to help if I can. You have dump files dating back to 5/2014, all with the same problem. They stopped in June this year and started again this month. What happened during those months where there were no dump files?

Your description od what you are seeing are classic signs of a Video driver problem or a video card going out. What you are experiencing is a classic video TDR error. That means your drivers are crashing but not recoverind in the time given by the OS so Windows assumes it is a video failure. TDR means Time delay and Recovery.

Code:

Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa800e61e200, fffff8800fdc2828, ffffffffc000009a, 4}
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+921828 )
Followup: MachineOwner

Code:

 nvlddmkm
start             end                 module name
fffff880`0f66a000 fffff880`1034a000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Nov 12 14:51:31 2014 (5463C853)
    CheckSum:         00CA4D59
    ImageSize:        00CE0000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please try to update your video driver using the method described here NVIDIA Drivers - Avoid Problems

Same thing

Code:

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800a363100, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fb87828, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

Code:

nvlddmkm
start             end                 module name
fffff880`0f265000 fffff880`0ff46000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Nov 20 17:01:23 2014 (546E72C3)
    CheckSum:         00C9D354
    ImageSize:        00CE1000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Try uninstalling just like you did last time, then follow this Drivers - Clean Left over Files after Uninstalling Just be sure to only select Nvidia Display and PhysX, nothing else. Then follow the first tutorial in installing drivers and select only the Display Driver and PhysX.

Please use a utility and log the temps for your CPU and GPU or keep an eye on it and tell me what they are during your game.

two things.
1. the reason I asked about logging temps or at least a utility that will tell us the high and low is because I found this in you event log

Code:

Event[1]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2014-01-15T17:20:06.715
  Event ID: 89
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Bart-PC
  Description: 
ACPI thermal zone ACPI\ThermalZone\TZ01 has been enumerated.             
_PSV = 379K             
_TC1 = 1             
_TC2 = 5             
_TSP = 1000ms             
_AC0 = 0K             
_AC1 = 0K             
_AC2 = 0K             
_AC3 = 0K             
_AC4 = 0K             
_AC5 = 0K             
_AC6 = 0K             
_AC7 = 0K             
_AC8 = 0K             
_AC9 = 0K             
_CRT = 379K             
_HOT = 0K             
_PSL - see event data.

2. Would you please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.