Display driver has stopped responding Radeon HD6870

Status
Not open for further replies.

areamike

Distinguished
Dec 5, 2011
66
0
18,640
Hello All,

Here are my specs:
MOBO: MSI 970A-G45
CPU: AMD Phenom II X4 955BE
RAM: Corsair Vengeance 2x4GB PC12800
VIDEO: XFX Radeon HD 6870
HDD w/OS and games and other progams: OCZ 120GB SOLID 3 SERIES SATA III HD
HDD: with programs less used: WD 500GB Green HDD
DVDRW: Sony DVDRW 24x
Ultra LSP 650W PSU
OS: Windows7 x64 w/SP1

I am getting an error more often than I like. The ONLY time it happens is when joining a server in Battlefield 3 or once I am in a server when it switches maps. It does not happen always. Only occasionally.

"Display Driver has stopped responding and has recovered" -> Pretty common error after searching the web for over a week now.

What I have tried:
1. Drivers from 11.0 to 12.3 (uninstalling and reinstalling properly in safe mode using driver sweeper etc.)
2. Disabled antivirus (avast)
3. Under clocked video card
4. Overclocked video card
5. Overclocked CPU
6. RMA'd video card for replacement
7. Tried different PSU (BFG 550w)
8. Reinstalled OS fresh with drivers etc.
9. New motherboard
10. Memtested both sticks of RAM overnight (passed)
11. Tried with only one stick of RAM at a time(same error occasionally)
12. Stood on my head and tried to drink a glass of water
13. Kicked my dog(just kidding)

Temperatures are as follows:
GPU Idle: 39C
GPU Under load : 70C

CPU Idle: 38C
CPU Under load : 51C


I do not overclock and never have. I only over and under clocked recently to see if that would help the problem. It did not.

I have read countless threads and countless articles with others having this same issue. Some have had success with a different PSU, Some have had success with new RAM. Some have had success with replacing the Video Card. I have tried all I can think of and at this point I am out of ideas. I don't usually ask for advice or help since I have been building PC's for almost 20 years now, but I am at my wit's end.

Any magic tricks out there?

 
It only happens in BF3? Maybe try uninstalling BF3 and reinstalling. That may have been covered in your reformat and OS install but just a thought. Seems like it should be happening with other applications too if its a hardware or driver issue. Also, I didn't check out your motherboard but is there another PCIe x16 slot you could try?
 
scout_03 - I tried with one stick at a time during memtest and with both. I also tried with one stick during BF3 gaming. No matter what, I get the error whether I have one stick in or not and memt4est passed all tests with single sticks at a time and with both sticks.

stickg1 - I do have another PCI-e slot. I actually thought about trying that as it is the only thing I can think of to try at this point. I'll give it a shot right now.

EDIT: One thing I just noticed si that I don't seem to get the error as often if I switch to windowed mode in BF3 when joining or switching maps. If in FULL screen, it happens more often.
 
MOBO Manual says this:

1 PCIe 2.0x16 slots (PCI_E2 supports up to x16 speed, PCI_E4 supports up to x4 speed)

There's nothing else that says whether one or both slots run at slower speeds when occupied or not.

I placed the card in the second PCIe slot last night and ran a few rounds of BF3 with no problems. However, since the error is not consistent, I can't say for sure that the problem is resolved yet.

BF3 has been reinstalled already once before. I guess I can do it again. Just stinks that it takes a while to do so.
 


Yes, I have an older PCIe card, but it is not powerful enough to run BF3.


@suat - I'll give the link a try.

Also, I moved the card to the other PCIe slot and did not get the error while playing, however, I did get something different where the video locked up and graphics went crazy then booted me out of the middle of a match. Something that never happened with the video card in the upper PCIe slot.
 
After applying the fix in the link suat gave, I ran BF3 last night for over 3 hours and never once got the error. Whether it is fixed or not, we shall see. I'll keep an eye on it. If it does not give me the error for a week, then I will consider it probably fixed.

I'm also running the 12.3 drivers after a driversweep in safe mode and reinstalling.
 
I'm back.

Still getting the error, even after the above MS fix was applied.


I've tried drivers all the way back to 11.7.
I've reformatted HDD and installed OS
Reinstalled the game
Moved video card to other slot.
Updated MOBO bios
RMA'd video card
Swapped out PSU
MEM tested RAM
Swapped 6 pin power connectors on GPU
Unhooked all USB devices
Unhooked DVDrom and SATA backup drive

At this point I'm at a loss.

 


So you have tried a different video card and no luck? Might be a motherboard issue.
 
My FPS are high. When running Fraps, I see anywhere from 40-90FPS.

I have a guy I can get another MOBO from and try but that will be about a week or so.

One thing I have noticed lately. When I join a certain sever, I get the error more.

EDIT:!!!!
I just noticed something. In between maps in BF3 or when loading maps, FRAPS shows my FPS THROUGH THE ROOF. Like 170 FPS+

Is that normal?
 


Yeh that's not out of the norm because it's not displaying high demanding graphics. Do the direct x updates suggested.
 
I have often suggested here increasing core/memory idle clock speeds in case one is experiencing TDR issue. It seems nobody is interested in doing it.

Here is the procedure doing it if anyone is interested:

Open Catalyst Control Center (new version since October 2011. Older versions have a different procedure.).

Make sure Enable Graphics Overdrive is unchecked in Overdrive section.

Click Presets.

Click Add preset.

Give a name to the preset (such as Speedy and note it) and save.

Now go to %USERPROFILE%\AppData\Local\ATI\ACE\Profiles\ (AppData folder is hidden. Select Show all files and folders in Folder Options.).

In Profiles folder, you will see a file called Speedy.xml. This file you have just created.

Open Speedy.xml with notepad.

In this file there is a line

name="CoreClockTarget....."
<Property name="Want_0" value="xxx00" /> (xxx00 is your idle-state core clock. Make it 40000)

and another line

name="MemoryClockTarget....."
<Property name="Want_0" value="yyy00" /> (yyy00 is your idle-state memory clock. Make it 90000)

Change only the Want_0 values. These are the idle-state clocks.

Save the file with the changes you have made.

Now go back to Catalyst Control Center.

Select the Preset called Speedy and then put a checkmark in the box next to Enable Graphics OverDrive.

Click Apply at the bottom of the Catalyst Control Center window.

Now you can see the new increased idle-state core/memory clock speeds.

Now try to give your card a good TDR if you can.

If your issue is resolved, then you may back off little by little on idle core/memory clock speeds until you find your system's lowest values, just to save energy and help GreenPeace act. If it is not resolved, good luck.
 


Tried it and the installer came back and said my installation is up to date.

I'm going to try what you suggested with the core and memory clocks, even though I have already tried under and over clocking the video card.


 
suat:

Those lines you mention are not there. Here is my Speedy.xml

<Profile>
<Caste name="Graphics">
<Groups />
<Adapter name="PCI_VEN_1002&amp;DEV_6738&amp;SUBSYS_31071682&amp;REV_00_4&amp;39319B62&amp;0&amp;0010A" />
</Caste>
<Caste name="Fuel">
<Groups />
<Adapter name="FuelAdapterUDID" />
</Caste>
<Caste name="Platform">
<Groups />
<Adapter name="PlatformAdapterUDID">
<Aspect name="AMDOverDrive">
<Feature name="AMDOverDriveEnableAOD">
<Property name="AMDOverDriveEnableAOD_Control" value="False" />
</Feature>
<Feature name="AMDOverDriveEnableCOD">
<Property name="AMDOverDriveEnableCOD_Control" value="False" />
</Feature>
<Feature name="AMDOverDriveEnableGOD">
<Property name="AMDOverDriveEnableGOD_Control" value="False" />
</Feature>
</Aspect>
</Adapter>
</Caste>
</Profile>
 
I can't edit my above post.

I had to delete then re-add the Speedy preset a couple times and now those lines are showing up. I made the changes you suggest and now my idle speeds are 400/900
 
Now do what you did previously to get TDR error to show up "Display driver stopped responding..."

By the way, this is not overclocking. You are not above your card's speed limit. This is not under-clocking, either, because you are not underclocking your max set speeds. This is just increasing idle clocks.
 


Yes, I realized this was idle speeds you were referring to and not actual overclocking once I followed your instructions.

I'll give it a try later on. Have to get some work done first today.

I'll keep ya'll posted.
 
Getting similar issues myself with a 6950.
Some people are suggesting that if you have a Realtek onboard sound, then make sure all the drivers on that are fully up to date, and if that doesn't work try disabling.
I'm downloading the latest drivers now in an attempt to fix mine.
 



Interesting. I do have Realtak onboard sound. One more thing I noticed. Right before the error happens while a match is loading the sound sort of blips out and loops.

Pretty sure I have updated drivers for the sound, but I'll check. Also disabling the sound would be a good way to see if it is somehow causing the problem or not, so, I'll try that too.
 
Status
Not open for further replies.

Latest posts