Message boards :
Number crunching :
Display driver failure?
Message board moderation
Author | Message |
---|---|
John Send message Joined: 2 Oct 00 Posts: 16 Credit: 17,094,836 RAC: 5 |
I have been having issues with a display driver failure happening on my system. I have tried updating the drivers for my graphics car but with no luck. My system is an xps 8300 with a amd radion 6800 series card. I posted in the help section here http://setiathome.berkeley.edu/forum_thread.php?id=75985 and was told to try and adjust a registry option TdrDelay which has not worked. I was told that maybe someone here could walk me through adjusting switches to get my system back up. I have been in the seti program since 2000 and would hat eot think a bug will knock me out. |
John Send message Joined: 2 Oct 00 Posts: 16 Credit: 17,094,836 RAC: 5 |
Here is the report on my system http://setiathome.berkeley.edu/show_host_detail.php?hostid=6322303 |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
Are you having the problem with both Apps or just the (opencl_ati_cat132) App? |
John Send message Joined: 2 Oct 00 Posts: 16 Credit: 17,094,836 RAC: 5 |
Just the ati system. |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
Just the ati system. Your machine has Two different ATI Apps listed. AstroPulse v7 v7.04 (opencl_ati_100) SETI@home v7 v7.03 (opencl_ati_cat132) Can you remember if they both give this problem? |
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
You could delete the compilations the app made when they first ran, and get the app to regenerate them under the current driver. the latest Stock AP v7 OpenCL apps regenerate the compilations every time there is a driver change, while the old Stock MB v7 OpenCL (r1831) apps only generate the compilations once, which might cause problems if they were generated with Cat 13.1/APP runtime 1084.4, doing the compilations on that driver/APP combination often caused driver restarts. Claggy |
John Send message Joined: 2 Oct 00 Posts: 16 Credit: 17,094,836 RAC: 5 |
You could delete the compilations the app made when they first ran, and get the app to regenerate them under the current driver. the latest Stock AP v7 OpenCL apps regenerate the compilations every time there is a driver change, How would I do that delete then reinstall the application? |
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
You could delete the compilations the app made when they first ran, and get the app to regenerate them under the current driver. the latest Stock AP v7 OpenCL apps regenerate the compilations every time there is a driver change, All you need to do is shut Boinc down (or Suspend GPU computation), Navigate to the Setiathome project directory, (Should be C:\ProgramData\BOINC\projects\setiathome.berkeley.edu) and delete the files that follow the following format, where instead of Capeverde your GPU will be named, and on the .wisdom your CPU will be named: MB_clFFTplan_Capeverde_8_r1831.bin Then either restart Boinc, or resume GPU computation, the files will be regenerated again when the app starts, For example: Running on device number: 0 You don't need to delete any apps at present. Claggy |
John Send message Joined: 2 Oct 00 Posts: 16 Credit: 17,094,836 RAC: 5 |
Thanks this seems to have worked. |
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
Thanks this seems to have worked. Brilliant. Claggy |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.