I have a windows 7 64 bit system with an amh 6800hd radion card I am running the seti program. I get a repeated display driver failure. any suggestions I have downloaded the betas and the newest driver from amd.

Not an AMD user but sounds like a driver issue. What driver are you using? Hopefully one of the others will come by and give advice.

From another thread, there is this. Take a look and see if you can use it. Catalyst 14.9

http://support.amd.com/en-us/download/desktop?os=Windows+7+-+64

... I am running the seti program...

You are Not "running the seti program" and you never did (from this account):
http://setiathome.berkeley.edu/hosts_user.php?sort=rpc_time&rev=0&show_all=1&userid=10061048

And "amh 6800hd radion card" do not exist on the market

What exist are AMD Radeon HD 6850 / 6870
http://www.amd.com/en-gb/products/graphics/desktop/6000/6850
http://www.amd.com/en-gb/products/graphics/desktop/6000/6870

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

Sorry when I posted this question I was having no luck accessing my original. I have been running this seti program since 2000. The problem has been hapening for about 3 months. I have tried to use the new drivers as well as the betas. Dell has even replace the graphics car

---

I am trying 14.9.2 right now but neither of the other updates have worked.

---

as of right now driver 14.9.2 beta does not work. I hate to think this will end my time on the seti application.

---

Hi John, could you please read this information from my posts regarding my win 8.1 laptop:

"I have resolved the stalled wu issue on my AMD laptop. My solution was to add a registry value called TdrDelay and adjust it from the default of 2 to a value of 8. I would still suggest that you make certain that your drivers are current as a start to resolve this issue.

The following is just some information that I found after reading from many sources.

Snips from the various Microsoft web pages:

.. snip...

Symptom
Your PC may temporarily hang or become unresponsive, and you receive the following error message:
Display driver stopped responding and has recovered

Resolution
To resolve this issue, follow the steps in the methods starting with method 1 and then proceeding with method 2 if that solution does not resolve the issue.
Method 1: Increase the GPU (Graphics Processing Unit) processing time by adjusting the Timeout Detection and Recovery registry value
Timeout Detection and Recovery is a Windows feature that can detect when video adapter hardware or a driver on your PC has taken longer than expected to complete an operation. When this happens, Windows attempts to recover and reset the graphics hardware. If the GPU is unable to recover and reset the graphics hardware in the time permitted (2 seconds), your system may become unresponsive, and display the error “Display driver stopped responding and has recovered.”

Giving the Timeout Detection and Recovery feature more time to complete this operation by adjusting the registry value, may resolve this issue.

..snip...

Limiting Repetitive GPU Hangs and Recoveries

Beginning with Windows Vista with Service Pack 1 (SP1) and Windows Server 2008, the user experience has been improved in situations where the GPU hangs frequently and rapidly. Repetitive GPU hangs indicate that the graphics hardware has not recovered successfully. In these situations, the end user must shut down and restart the operating system to fully reset the graphics hardware. If the operating system detects that six or more GPU hangs and subsequent recoveries occur within 1 minute, the operating system bug-checks the computer on the next GPU hang.

..snip...

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up the registry in Windows 7, see Back up the registry


TDR Registry Keys

You can use the following TDR-related registry keys for testing or debugging purposes only. That is, they should not be manipulated by any applications outside targeted testing or debugging.

TdrDelay

Specifies the number of seconds that the GPU can delay the preempt request from the GPU scheduler. This is effectively the timeout threshold. The default value is 2 seconds.


KeyPath : HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\GraphicsDrivers
KeyValue : TdrDelay
ValueType : REG_DWORD
ValueData : Number of seconds to delay. 2 seconds is the default value.

I would postulate that when we add a massive workload to gpu it takes longer than normal to report and the os sees this as a fault - thus we need to give it more time to report.

On a further information note - in my research I saw that this fault was not isolated to AMD APU's, I saw NVIDIA and AMD stand alone cards involved in the issue.

If this helps even 1 person I will be very happy."

2nd bit of information:

"Hi HAL9000, could you please post some details on your solution. It will help not just I but others that run across this thread. I thank you in advance.

Robert


Here is the whole MS write up on the options for the video Timeout Detection & Recovery.
http://msdn.microsoft.com/en-us/library/windows/hardware/ff569918%28v=vs.85%29.aspx

I set TdrLevel to 0. Which basically just turns the whole thing off.

When I would VNC into my HTPC dwm.exe was fluctuating in memory use up to 300-400MB and back down to its normal amount. The graph on the performance tab looked like a sawtooth. Then after a few minutes I would get the display driver has stopped & been recovered message.

far_raf
Send message
Joined: 26 Apr 00
Posts: 92
Credit: 7,289,781
RAC: 37,827
Canada

Message 1512718 - Posted: 6 May 2014, 5:18:01 UTC
Last modified: 6 May 2014, 5:19:00 UTC

Hal9000, I took your advise and set TdrLevel to 0. And wanted to post so I can change title."

Just to be clear, it is not boinc that is the problem, it is an OS level problem. Look for the thread called in Number crunching : solution with reason for "display driver has stopped responding the system has recovered"
--------------------------------------------------------

The other thing to note is that you should not run boinc gpu apps in the background if you are using your gpu for things like videos. I hope this helps you mretome and jason.

The same info in very short:
http://setiathome.berkeley.edu/forum_thread.php?id=74843&postid=1553166#1553166

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

I have tried as you suggested and Microsoft suggested I set it to 8 and I have set it to 0 and still get the display driver has failed.

---

So finally - what did you set and to what value

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

I set TdrLevel to 0 as well as I tried the microsoft fixit which set it to 8

---

It's not TdrLevel but TdrDelay.
So if you set TdrLevel, you used the wrong key.

---

 
http://msdn.microsoft.com/en-us/library/windows/hardware/ff569918%28v=vs.85%29.aspx

"ValueData : TdrLevelOff (0) - Detection disabled"

TdrLevel can be set to 0 to Disable 'Timeout Detection and Recovery (TDR)' altogether

***

TdrLevel have to not exist in Registry or be set to 3 (default) to enable usage of TdrDelay

***

So use either (not both):

TdrLevel=0
or
TdrDelay=8

***

If you set TdrLevel=0 "and still get the display driver has failed" something is wrong (e.g. TdrLevel was not set in the proper place in the Registry or is not REG_DWORD)

Did you reboot? (I think these values are not used until reboot)

 

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

Also, the key thing from the jumble above:

KeyPath : HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\GraphicsDrivers
KeyValue : TdrDelay
ValueType : DWORD (32bit) value
ValueData : Number of seconds to delay. 2 seconds is the default value.

Make sure to set the Base value to Decimal when entering numbers above 9, as else your value of 10 or more is more than the value you'd want.

---

Ok I tried the delay at 8 decimal and 0. 0 lasted the longest but I am still getting failures.

---

So you try TdrDelay=0 ?? - for me the result of this will be 'unknown'

Either:
- driver will fail very often
- Windows will ignore the value as 'stupid'

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

From what I was reading the options given were to set tdrdelay to 8 for more time or 0 to turn it off and quit the detection. So you say turn it up to what 30?

---

From what I was reading the options given were to set tdrdelay to 8 for more time or 0 to turn it off and quit the detection.

Where did you read such thing?
Copy/Paste the "reading" and/or give the link.
(in Microsoft article you'll not see this)

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

I am sorry I have read to many of these articles and tried everything I have seen even the microsoft fix it which set it to 8. The only thing I can find is the trdelay in my registry. Its not working at 8 or 2 or 0 I even set it higher and still had a failure so what do you suggest? Get a new card? Drop seti and all the years worth of my time?

---

The only thing I can find is the trdelay in my registry

As already noted - NONE of these values exist in the Registry, even TdrDelay do not exist until you create it. (manually or running a .reg file)

And it's TdrDelay - not trdelay nor tdrdelay
(I'm not sure cASe mattERs but it's best to Copy/Paste it from Microsoft article: TdrDelay TdrLevel)

... so what do you suggest?

Reboot after any change to these values? (so they take effect)

Read files in <BOINC_Data>\projects\setiathome.berkeley.edu\docs\ for available switches "to reduce GUI lags or to prevent driver restarts"
e.g. "If you experience screen lags reduce unroll factor and ffa_block_fetch value."

Ask in Number Crunching for what and how to do (e.g. which switches to use and where to put them)

When asking specify which computer you talk about ("DELL" means nothing - give link or ID#)
Give link to this thread;
Stress that you aim for low lag and no driver restarts (else most people tend to think you want highest performance)


e.g. for low lag I use:
-cpu_lock -unroll 2

in:
ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt


***

And about this computer:
http://setiathome.berkeley.edu/show_host_detail.php?hostid=5156032

"NVIDIA GeForce 9400 GT (1024MB) driver: 340.52"

Read:
"@Pre-FERMI nVidia GPU users: Important warning"
http://setiathome.berkeley.edu/forum_thread.php?id=75633

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)