• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Card problem: Possible Solution or Faulty?

R0B75

R0B75

R0B75

Soldato
Joined
15 Aug 2003
Posts
5,872
Location
Kirk Langley
Installed a Radeon HD 6870 yesterday ran a 3d Mark once and played 10 minutes of the Crysis demo. All appeared well.

I mainly use my PC for video editing and have had zero problems doing this with the onboard HD3000 graphics. When encoding a video with the new card my PC froze and then blue screened, this happened twice after getting the following message "display driver stopped responding and has recovered"

I then stripped the drivers (Catalyst 11.5) and installed 11.4. Same problem.

I then removed the card and reverted back to onboard graphics, problems went away. This was without stripping out the drivers, just physically removed the card.

Now this could be a faulty card, or it could be a setting issue (something the new card can do that the onboard can't, and cause it to crash??) but I can't think what might cause it, but it can't be a driver problem because both are using the same driver, right??

I've done some searching and cannot find an answer for toffee so I turn to OcUK for salvation :D

Any ideas on this one?
 
Is anything overclocked? might be that the extra power draw/heat output from the new card is tipping something over the edge.
 
Last edited:
Agree with mmj on this it seems as though something is pushing it over the top power/heat
or bad overclock
I myself don't think its a driver issue
I think you should test the card with some programs like furmark/occt and look for problems like overheating/artifacts there.
 
I'm thinking the same but I would think its being given enough power. 700w OCZ PSU, both connectors plugged into the card. Motherboard (Asus M4A78LT-M) has latest bios also.

I'll try some more benchmarking programs.
 
Just ran Furmark and it came back with the below. Not entirely sure which is the best way to push the card using this tool as I've not used it before. Which settings should I change?

Score: 1924 points (32 FPS)

Submitted by R0B75 on May 21 2011, 6:44 pm

Bench duration: 60 seconds
Resolution: 1920 x 1080
MSAA samples: 0
Window mode: fullscreen

Primary renderer: ATI Radeon HD 6870
Device ID: 0x1002 - 0x6738
GPU clock: 299 MHz
Memory clock: 300 MHz
Graphics drivers: Catalyst 11.4 - 8.841-110405a-116954C-ATI (4-5-2011)
GPU temperatures (start/end):38°C / 75°C
Number of GPUs: 1

CPU: AMD Phenom(tm) II X4 840 Processor
CPU speed: 3214 MHz
Operating system: Windows 7 64-bit build 7601 [Service Pack 1]
 
I would run a stabillity test at your native resolution,
Ive just noticed that your gpu clock says 299mhz and your memory clock says 300mhz
shouldn't that be 900mhz and 4200mhz minimum
 
Yeah, I noticed that, which is why I'm trying OCCT but it thinks my directx version is out of date and disables the GPU test. Checked DxDiag and its v11. :confused:
 
Is this problem with Adobe Photoshop? I have heard of this with the 11.3 and 11.4 drivers (possibly 11.5 too?), although don't use adobe myself.

You might try an earlier driver.
 
Last edited:
No, it happens with windows movie maker. As I said though, never a problem until I tried with the new card.

Completely stripped off/cleaned the drivers and re-installed 11.5. OCCT still won't let me run GPU tests :/
 
Ran Furmark and OCCT CPU tests at the same time and nothing happened. Anyone know any games that have built-in benchmarks, preferably ones you can loop?

Stress.jpg
 
Last edited:
Try another CPU tester like Prime95, I never reckoned much to OCCT.

What is your CPU temp under load? with the GPU running at 80-90C that's a lot of extra heat inside your case it could be overheating your CPU.

The best test imo would be to run Prime95 and then loop something like 3dmark while it's running, that way both CPU and GPU are fully loaded.
 
Last edited:
CPU topped out at 51c with both CPU and GPU at full load for 10 minutes.

I wouldn't say that was particularly high. My case has good air flow. Tomorrow I'll try using a different editing program.
 
Here's the info from the latest blue screen mini dump. This time Windows was Idle!


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\052211-29640-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`0301e000 PsLoadedModuleList = 0xfffff800`03263650
Debug session time: Sun May 22 00:02:02.111 2011 (UTC + 1:00)
System Uptime: 0 days 4:14:17.927
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8008315010, fffff88006c2f45c, 0, 2}

*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+745c )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8008315010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88006c2f45c, 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+745c
fffff880`06c2f45c 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`03cd79c8 fffff880`06cd5000 : 00000000`00000116 fffffa80`08315010 fffff880`06c2f45c 00000000`00000000 : nt!KeBugCheckEx
fffff880`03cd79d0 fffff880`06cd4d0a : fffff880`06c2f45c fffffa80`08315010 fffffa80`081bb600 fffffa80`08b69010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03cd7a10 fffff880`07b47f07 : fffffa80`08315010 00000000`00000000 fffffa80`081bb600 fffffa80`08b69010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`03cd7a40 fffff880`07b71b75 : 00000000`ffffffff 00000000`000eebc1 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03cd7b20 fffff880`07b702bb : 00000000`00000102 00000000`00000002 00000000`000eebc1 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`03cd7b50 fffff880`07b432c6 : ffffffff`ff676980 fffffa80`08b69010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`03cd7bf0 fffff880`07b6fe7a : 00000000`00000000 fffffa80`0741d3c0 00000000`00000080 fffffa80`08b69010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`03cd7d00 fffff800`0333a32e : 00000000`fffffc32 fffffa80`08b5c060 fffffa80`06a05b30 fffffa80`08b5c060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`03cd7d40 fffff800`0308f666 : fffff800`03210e80 fffffa80`08b5c060 fffff800`0321ecc0 fffff880`0122e384 : nt!PspSystemThreadStartup+0x5a
fffff880`03cd7d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+745c
fffff880`06c2f45c 4883ec28 sub rsp,28h

SYMBOL_NAME: atikmpag+745c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4dae3558

FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

Followup: MachineOwner
---------
Click to expand...
 
Seams like it could well be a driver issue after all,
here's what i suggest you do,
Make sure your using the lastest driver sweeper from here http://phyxion.net/Driver-Sweeper/Driver-Sweeper/ making sure you choose version 3.0.0
Drivesweeper all drivers & in Safe Mode
Unistall all drivers that aren't used in DriveSweeper (CCC Profiler Updates, MSI AfterBurner, anything related to ATI that use's it's drivers.)
After you do this, the first thing you need to do is go into Device Manager and Unistall your ATI Drivers
Once your done, restart the PC and then try installing the latest drivers.
Also
try to disable AMD External Events Utility : right click "my computer" "manage" "services". Stop the service first then disable it.

If you still get the bsod after doing the above then search google for atikmpag.sys and see if you can find the exact same issue you have with this error.
 
I've done everything you have mentioned aside from disabling AMD External Events Utility.

I even updated DirectX so that I can now run the GPU tests in OCCT. PC hasn't Blue screened today or frozen and I was able to encode a video in AVS Video Editor.

Going to run some more stress tests and try editing more videos but I feel I'm getting somewhere now.
 
You must log in or register to reply here.
Back
Top Bottom