Hello,
How are the temps? Install HWMonitor and post a screenshot of the program at idle and under load.
Has the fan and vents been cleaned lately?
Try the steps below to completely uninstall the graphics driver:
-Download Driver Sweeper here and install it. Don't run the program yet
- First, Uninstall the NVidia driver/software from Control Panel > Uninstall a program and restart
-Now run Driver Fusion, select Nvidia Display and then select Delete
-After complete restart the PC then install correct Graphics driver from the MSI Support Site.
The dump files that is in the report is 0x116 Video TDR Failure. This can usually be caused by faulty drivers, Overheating, or faulty hardware
One of your earlier dumps files also indicate a problem with the XBOX USB Controller I would suggest updating the driver or remove teh device for testing.
MotioninJoy simulate Xbox 360 controller(virtual Xinput device) | MotioninJoy
How are the temps? Install HWMonitor and post a screenshot of the program at idle and under load.
Has the fan and vents been cleaned lately?
Try the steps below to completely uninstall the graphics driver:
-Download Driver Sweeper here and install it. Don't run the program yet
- First, Uninstall the NVidia driver/software from Control Panel > Uninstall a program and restart
-Now run Driver Fusion, select Nvidia Display and then select Delete
-After complete restart the PC then install correct Graphics driver from the MSI Support Site.
The dump files that is in the report is 0x116 Video TDR Failure. This can usually be caused by faulty drivers, Overheating, or faulty hardware
Code:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`03415000 PsLoadedModuleList = 0xfffff800`03659670
Debug session time: Fri Mar 29 02:59:50.991 2013 (UTC - 4:00)
System Uptime: 0 days 4:51:44.025
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa800cbae4a0, fffff880063fc918, ffffffffc000009a, 4}
*** 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+992918 )
Followup: MachineOwner
---------
7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800cbae4a0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880063fc918, 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.
Debugging Details:
------------------
FAULTING_IP:
nvlddmkm+992918
fffff880`063fc918 4055 push rbp
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0MotioninJoy simulate Xbox 360 controller(virtual Xinput device) | MotioninJoy
Code:
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`0304e000 PsLoadedModuleList = 0xfffff800`03292670
Debug session time: Fri Dec 7 04:13:40.378 2012 (UTC - 4:00)
System Uptime: 0 days 3:39:18.268
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
....................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10D, {5, 0, 1202, fffffa8010415010}
*** WARNING: Unable to verify timestamp for MijXfilt.sys
*** ERROR: Module load completed but symbols could not be loaded for MijXfilt.sys
Probably caused by : MijXfilt.sys ( MijXfilt+363a )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this bug check.
Arguments:
Arg1: 0000000000000005, A framework object handle of the incorrect type was passed to
a framework object method.
Arg2: 0000000000000000, The handle value passed in.
Arg3: 0000000000001202, Reserved.
Arg4: fffffa8010415010, Reserved.
Debugging Details:
------------------
BUGCHECK_STR: 0x10D_5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: DS3_Tool.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff88000f2ab46 to fffff800030ccfc0
STACK_TEXT:
fffff880`0f1f36a8 fffff880`00f2ab46 : 00000000`0000010d 00000000`00000005 00000000`00000000 00000000`00001202 : nt!KeBugCheckEx
fffff880`0f1f36b0 fffff880`0a95f63a : fffffa80`100c3460 fffffa80`100c3560 00000000`00000004 00000000`00000001 : Wdf01000!imp_WdfUsbTargetDeviceSendControlTransferSynchronously+0x8a
fffff880`0f1f39d0 fffffa80`100c3460 : fffffa80`100c3560 00000000`00000004 00000000`00000001 fffff880`0f1f3b00 : MijXfilt+0x363a
fffff880`0f1f39d8 fffffa80`100c3560 : 00000000`00000004 00000000`00000001 fffff880`0f1f3b00 fffff880`0f1f3a50 : 0xfffffa80`100c3460
fffff880`0f1f39e0 00000000`00000004 : 00000000`00000001 fffff880`0f1f3b00 fffff880`0f1f3a50 fffff880`0f1f3a18 : 0xfffffa80`100c3560
fffff880`0f1f39e8 00000000`00000001 : fffff880`0f1f3b00 fffff880`0f1f3a50 fffff880`0f1f3a18 00000000`00000000 : 0x4
fffff880`0f1f39f0 fffff880`0f1f3b00 : fffff880`0f1f3a50 fffff880`0f1f3a18 00000000`00000000 fffffa80`10477040 : 0x1
fffff880`0f1f39f8 fffff880`0f1f3a50 : fffff880`0f1f3a18 00000000`00000000 fffffa80`10477040 00000000`00000040 : 0xfffff880`0f1f3b00
fffff880`0f1f3a00 fffff880`0f1f3a18 : 00000000`00000000 fffffa80`10477040 00000000`00000040 fffffa80`0fa92360 : 0xfffff880`0f1f3a50
fffff880`0f1f3a08 00000000`00000000 : fffffa80`10477040 00000000`00000040 fffffa80`0fa92360 fffffa80`09a642a0 : 0xfffff880`0f1f3a18
STACK_COMMAND: kb
FOLLOWUP_IP:
MijXfilt+363a
fffff880`0a95f63a ?? ???
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: MijXfilt+363a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: MijXfilt
IMAGE_NAME: MijXfilt.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4fade6a0
FAILURE_BUCKET_ID: X64_0x10D_5_MijXfilt+363a
BUCKET_ID: X64_0x10D_5_MijXfilt+363a
Followup: MachineOwner
