Hello,
Looked at your Dump files. Seems like nVidia is the cause for the System to crash. Here is a small information about the Error
http://forums.amd.com/game/messageview.cfm?catid=260&threadid=104677&enterthread=yThis is the best advice for one of my colleague H2SO4
If playing with video driver versions hasn't helped, make sure the box is not overheating. Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU. Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference. If so, it might be as simple as dust buildup and subsequently inadequate cooling.
Do a complete nVidia Driver Cleanup: Follow this article
http://captaindebugger.wordpress.com/nvidia-driver-cleanup-guide/Try this free video stress test:
http://www.ozone3d.net/benchmarks/fur/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
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit
Try this free stress test:
http://www.mersenne.org/freesoft/Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.
Bugcheck:Code:
VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for real bugcheck).
Arguments:
Arg1: fffffa8004961420, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880101bdcf8, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
nvlddmkm+119cf8
fffff880`101bdcf8 ?? ???
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_TIMEOUT
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
BUGCHECK_STR: 0x117
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`061e15f0 fffff880`044af4ef : fffffa80`04961420 fffff880`044fbc80 fffffa80`04961420 fffff880`0447d843 : watchdog!WdDbgReportRecreate+0xa3
fffff880`061e1b10 fffff880`044b01b4 : fffff8a0`10aa7e60 fffff8a0`10aa7e60 00000000`00000080 fffffa80`04961420 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`061e1b60 fffff880`044846b3 : 00000000`00000001 fffffa80`0808f000 00000000`00000000 fffff880`00000083 : dxgkrnl!TdrCollectDbgInfoStage2+0x220
fffff880`061e1b90 fffff880`044b0d07 : fffffa80`08095658 ffffffff`fffe7960 fffffa80`04961420 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0xef
fffff880`061e1c40 fffff880`0457fec1 : fffffa80`03e5eac0 00000000`00000080 00000000`00000000 fffffa80`08095010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`061e1cc0 fffff800`03317c06 : 00000000`fffffc32 fffffa80`07d0ea10 fffffa80`03cd4040 fffffa80`07d0ea10 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`061e1d00 fffff800`03051c26 : fffff800`031ede80 fffffa80`07d0ea10 fffffa80`046366b0 fffff880`01467a90 : nt!PspSystemThreadStartup+0x5a
fffff880`061e1d40 00000000`00000000 : fffff880`061e2000 fffff880`061dc000 fffff880`08578b20 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+119cf8
fffff880`101bdcf8 ?? ???
SYMBOL_NAME: nvlddmkm+119cf8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c37918e
FAILURE_BUCKET_ID: X64_0x117_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x117_IMAGE_nvlddmkm.sys
Followup: MachineOwner
Hope this helps,
Captain
............................................................................................Regards,
Captain MVP
It is considered
courteous to post a reply if you have been able to resolve your problem, or received an answer to your question.