HI Ghanner ^_^,
I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-
Code:
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffe001ca530010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff800e9e4d5c8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc00000b5, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000a, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
nvlddmkm+1575c8
fffff800`e9e4d5c8 48ff25c1e86800 jmp qword ptr [nvlddmkm+0x7e5e90 (fffff800`ea4dbe90)]
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
STACK_TEXT:
ffffd000`b32f57d8 fffff800`e9986fac : 00000000`00000116 ffffe001`ca530010 fffff800`e9e4d5c8 ffffffff`c00000b5 : nt!KeBugCheckEx
ffffd000`b32f57e0 fffff800`e99868d2 : fffff800`e9e4d5c8 ffffe001`ca530010 ffffd000`b32f58c9 00000000`0000008f : dxgkrnl!TdrBugcheckOnTimeout+0xec
ffffd000`b32f5820 fffff800`e9a32644 : ffffe001`ca530010 ffffd000`b32f58c9 00000000`00000000 ffffe001`cb48c748 : dxgkrnl!TdrIsRecoveryRequired+0x1de
ffffd000`b32f5850 fffff800`e9a653fa : 00000000`00000008 ffffd000`b32f5950 ffffe001`cc3e5c70 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x3e4
ffffd000`b32f5930 fffff800`e9a1eba8 : ffffe001`cc3e5c70 ffffe001`cc3e5c70 ffffd000`b32f5ac0 00000000`00000002 : dxgmms1!VidSchiCheckHwProgress+0x1868a
ffffd000`b32f59c0 fffff800`e9a59d4a : ffffe001`cb48c000 ffffe001`cb48c001 ffffe001`cc3e5c70 ffffe001`00000000 : dxgmms1!VidSchiScheduleCommandToRun+0x448
ffffd000`b32f5b70 fffff800`e9a59d1d : ffffe001`cb48c000 00000000`00000080 ffffe001`cb6be500 ffffe001`00000000 : dxgmms1!VidSchiRun_PriorityTable+0x2a
ffffd000`b32f5bc0 fffff803`848ee514 : ffffd000`b1c8d3c0 ffffe001`cb6be500 ffffd000`b32f5c90 fffff803`8496c07d : dxgmms1!VidSchiWorkerThread+0x8d
ffffd000`b32f5c00 fffff803`8496f2c6 : ffffd000`b1c81180 ffffe001`cb6be500 ffffd000`b1c8d3c0 ffffe001`cb41b4e8 : nt!PspSystemThreadStartup+0x58
ffffd000`b32f5c60 00000000`00000000 : ffffd000`b32f6000 ffffd000`b32f0000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+1575c8
fffff800`e9e4d5c8 48ff25c1e86800 jmp qword ptr [nvlddmkm+0x7e5e90 (fffff800`ea4dbe90)]
SYMBOL_NAME: nvlddmkm+1575c8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
[COLOR=#FF0000][U][B]FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys[/B][/U][/COLOR]
BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x116_image_nvlddmkm.sys
FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}
Followup: MachineOwner
---------
As we can see from the Dump file analysis, the NVIDIA Driver is causing the problem. I would suggest you to uninstall the currently installed NVIDIA Driver using the Display Driver Uninstaller from this **LINK** and then clean up the NVIDIA Drivers. Once the NVIDIA Drivers are removed, kindly install a driver version which was released few months ago and see if you are still having the problems or not.
If the problem is still not solved, I would suggest you to run the Furmark Benchmark and report back if you face any problems along with the temperatures.
FurMark Video Stress Test - free from here:
FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test (Looks like it's "BURN-IN test" now)
- Run the test until the GPU temperature maxes out - or until you start having problems
(whichever comes first).
NOTE: Set the alarm to go off at 90ºC. Then watch the system from that point on. If the system doesn't display a temperature, watch it constantly and turn it off at the first sign of video problems.
DO NOT leave it it unmonitored, it can
DAMAGE your video card!!!
If the temperature gets above
100ºC, quit the test - the video card is
overheating.
- Click "Quit" to exit[/quote]
What you are looking for:
- excessive heat from the GPU (report back with anything over 90ºC)
- problems with the video display (picture is distorted or jumbled, picture turns black, etc)
- problems reported by the program (I haven't seen this, but "just in case")
Let me know how it goes ^_^