- Joined
- Apr 20, 2008
- Messages
- 243 (0.04/day)
System Name | Silverstorm |
---|---|
Processor | Intel Core i5 2500k |
Motherboard | Gigabyte GA-P67A-D3-B3 (Rev. 2.0) |
Memory | 2x4GB Kingston HyperX PC3-12800 1600MHz CL9-9-9-27 |
Video Card(s) | Gigabyte GeForce GTX 760 2GB |
Storage | 250GB Samsung 840 EVO SSD, 1TB WD Caviar Green, 2x500GB Seagate Barracuda, 2TB WD Elements (ext) |
Display(s) | Samsung S24B300 + HP w2207h |
Case | Fractal Design Define R4 Black Pearl |
Audio Device(s) | 7.1 CH HD Audio (Onboard) |
Power Supply | OCZ StealthXStream 800W |
Software | Microsoft Windows 10 Pro 64bit |
Greetings TPU,
A dear friend of mine have had a longrunning problem now. I've tried a lot of different solutions, but nothing seems to fix the problem.
We've tried formatting his computer with a different OS and much more; he also have the newest drivers for his graphics card and everything else.
His hardware is as follows:
CPU: Intel Core 2 Quad Q6600
MOBO: DFI Lanparty LT X48-T2R
RAM: 2x2GB DDR2 (Can't remember the brand)
GPU: 2xATi HD3870 in CrossFire (512mb each)
I've also dugged out his crash dump file, so if anyone would like to have a look at it, here goes:
I know it's a display problem, and I'm pretty sure it probably one of his cards that have some sort of problem. Any suggestions before I tell him to get a new card?
Thanks,
Valen
P.S. There is no Overclocking of any kind on the system.
P.P.S. This almost only happens when playing World of Warcraft. I've recently updated his drivers to the newest available, which seemed to make the problem worse.
A dear friend of mine have had a longrunning problem now. I've tried a lot of different solutions, but nothing seems to fix the problem.
We've tried formatting his computer with a different OS and much more; he also have the newest drivers for his graphics card and everything else.
His hardware is as follows:
CPU: Intel Core 2 Quad Q6600
MOBO: DFI Lanparty LT X48-T2R
RAM: 2x2GB DDR2 (Can't remember the brand)
GPU: 2xATi HD3870 in CrossFire (512mb each)
I've also dugged out his crash dump file, so if anyone would like to have a look at it, here goes:
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80067a04e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004945c80, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
atikmpag+6c80
fffff880`04945c80 4883ec28 sub rsp,28h
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`076119c8 fffff880`05334ef8 : 00000000`00000116 fffffa80`067a04e0 fffff880`04945c80 00000000`00000000 : nt!KeBugCheckEx
fffff880`076119d0 fffff880`05334c02 : fffff880`04945c80 fffffa80`067a04e0 fffffa80`05c69c00 fffffa80`06088010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`07611a10 fffff880`0520ff07 : fffffa80`067a04e0 00000000`00000000 fffffa80`05c69c00 fffffa80`06088010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`07611a40 fffff880`05239b75 : 00000000`ffffffff 00000000`000bab72 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`07611b20 fffff880`052382bb : 00000000`00000102 00000000`00000005 00000000`000bab72 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`07611b50 fffff880`0520b2c6 : ffffffff`ff676980 fffffa80`06088010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`07611bf0 fffff880`05237e7a : 00000000`00000000 fffffa80`04ca9d50 00000000`00000080 fffffa80`06088010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`07611d00 fffff800`02f32a86 : 00000000`fffffc32 fffffa80`05c71b60 fffffa80`03ccf040 fffffa80`05c71b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`07611d40 fffff800`02c6bb06 : fffff880`02f63180 fffffa80`05c71b60 fffff880`02f6dfc0 00000000`000cabb3 : nt!PspSystemThreadStartup+0x5a
fffff880`07611d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
atikmpag+6c80
fffff880`04945c80 4883ec28 sub rsp,28h
SYMBOL_NAME: atikmpag+6c80
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c33d53e
FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys
BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys
Followup: MachineOwner
I know it's a display problem, and I'm pretty sure it probably one of his cards that have some sort of problem. Any suggestions before I tell him to get a new card?
Thanks,
Valen
P.S. There is no Overclocking of any kind on the system.
P.P.S. This almost only happens when playing World of Warcraft. I've recently updated his drivers to the newest available, which seemed to make the problem worse.