Shintaro
Well-known member
Hi,
This might be useful:
I have a HP Envy M6 with 2 GPU's (Intel 4000 and ATI Radeon 7670M) until recently had a few problems with them (see the embeded crash sample, at least 1 per day).
In CCC (Catalyst Control Center) I started ensuring that I set which application could use the Intel graphics (Power Saving) and which could use the Radeon(High Performance) (See the attached pic). This seems to have settled things down.
What annoys me about HP is that I was not able to disable the Intel video card in the BIOS.......unless someone else know something.
Anyway a question, does anybody know if there exists a similar application for Nvidia? Specifically with the GTX 760 EVGA?
This might be useful:
I have a HP Envy M6 with 2 GPU's (Intel 4000 and ATI Radeon 7670M) until recently had a few problems with them (see the embeded crash sample, at least 1 per day).
In CCC (Catalyst Control Center) I started ensuring that I set which application could use the Intel graphics (Power Saving) and which could use the Radeon(High Performance) (See the attached pic). This seems to have settled things down.
What annoys me about HP is that I was not able to disable the Intel video card in the BIOS.......unless someone else know something.
Anyway a question, does anybody know if there exists a similar application for Nvidia? Specifically with the GTX 760 EVGA?
Code:
VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for a real bugcheck.)
Arguments:
Arg1: ffffe000022ab010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80001e2928c, 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:
atikmpag+928c
fffff800`01e2928c ?? ???
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
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
STACK_TEXT:
ffffd000`2333ea20 fffff800`019a1b70 : 00000000`00000002 ffffe000`022ab010 00000000`80000000 ffffe000`0201b8f0 : watchdog!WdDbgReportRecreate+0x10c
ffffd000`2333ea70 fffff800`019a1235 : ffffc000`00000000 ffffc000`0666ce70 00000000`00000002 ffffe000`0b304bf0 : dxgkrnl!TdrUpdateDbgReport+0xc0
ffffd000`2333eac0 fffff800`01995f1b : ffffc000`20c53d33 ffffe000`0b304540 ffffd000`2333eb20 00000000`00000001 : dxgkrnl!TdrCollectDbgInfoStage2+0x1d9
ffffd000`2333eaf0 fffff800`019a1901 : ffffe000`0b300100 ffffffff`fffe7960 ffffe000`0b301000 ffffffff`fffe7960 : dxgkrnl!DXGADAPTER::Reset+0x407
ffffd000`2333eb60 fffff800`01a8ac4a : fffff800`01a709e0 ffffe000`0b301000 fffff801`13887000 00000000`00000000 : dxgkrnl!TdrResetFromTimeout+0x15
ffffd000`2333eb90 fffff800`01a70a6d : ffffe000`0b301000 00000000`00000080 ffffe000`00288500 ffffe000`00288500 : dxgmms1!VidSchiRecoverFromTDR+0x1a
ffffd000`2333ebc0 fffff801`139142e4 : ffffd000`201dd340 ffffe000`00288500 ffffd000`2333ec90 fffff801`139d807d : dxgmms1!VidSchiWorkerThread+0x8d
ffffd000`2333ec00 fffff801`139db2c6 : ffffd000`201d1180 ffffe000`00288500 ffffd000`201dd340 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`2333ec60 00000000`00000000 : ffffd000`2333f000 ffffd000`23339000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
atikmpag+928c
fffff800`01e2928c ?? ???
SYMBOL_NAME: atikmpag+928c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 505810d8
FAILURE_BUCKET_ID: 0x117_IMAGE_atikmpag.sys
BUCKET_ID: 0x117_IMAGE_atikmpag.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x117_image_atikmpag.sys
FAILURE_ID_HASH: {157488ff-1bd3-8412-e0eb-3da867eede83}