Display driver failure?

Message boards : Number crunching : Display driver failure?
Message board moderation

To post messages, you must log in.

AuthorMessage
John

Send message
Joined: 2 Oct 00
Posts: 16
Credit: 17,094,836
RAC: 5
United States
Message 1597701 - Posted: 6 Nov 2014, 15:49:00 UTC

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.
ID: 1597701 · Report as offensive
John

Send message
Joined: 2 Oct 00
Posts: 16
Credit: 17,094,836
RAC: 5
United States
Message 1597705 - Posted: 6 Nov 2014, 15:55:57 UTC - in response to Message 1597701.  

Here is the report on my system
http://setiathome.berkeley.edu/show_host_detail.php?hostid=6322303
ID: 1597705 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1597710 - Posted: 6 Nov 2014, 16:24:03 UTC - in response to Message 1597705.  

Are you having the problem with both Apps or just the (opencl_ati_cat132) App?
ID: 1597710 · Report as offensive
John

Send message
Joined: 2 Oct 00
Posts: 16
Credit: 17,094,836
RAC: 5
United States
Message 1597715 - Posted: 6 Nov 2014, 16:53:41 UTC - in response to Message 1597710.  

Just the ati system.
ID: 1597715 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1597720 - Posted: 6 Nov 2014, 17:02:02 UTC - in response to Message 1597715.  

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?
ID: 1597720 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 5 Jul 99
Posts: 4654
Credit: 47,537,079
RAC: 4
United Kingdom
Message 1597756 - Posted: 6 Nov 2014, 18:20:01 UTC - in response to Message 1597701.  
Last modified: 6 Nov 2014, 18:21:03 UTC

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
ID: 1597756 · Report as offensive
John

Send message
Joined: 2 Oct 00
Posts: 16
Credit: 17,094,836
RAC: 5
United States
Message 1597768 - Posted: 6 Nov 2014, 18:54:35 UTC - in response to Message 1597756.  

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


How would I do that delete then reinstall the application?
ID: 1597768 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 5 Jul 99
Posts: 4654
Credit: 47,537,079
RAC: 4
United Kingdom
Message 1597777 - Posted: 6 Nov 2014, 19:15:58 UTC - in response to Message 1597768.  
Last modified: 6 Nov 2014, 19:27:51 UTC

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


How would I do that delete then reinstall the application?

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
MB_clFFTplan_Capeverde_16_r1831.bin
MB_clFFTplan_Capeverde_32_r1831.bin
MB_clFFTplan_Capeverde_64_r1831.bin
MB_clFFTplan_Capeverde_128_r1831.bin
MB_clFFTplan_Capeverde_256_r1831.bin
MB_clFFTplan_Capeverde_512_r1831.bin
etc all the way up to:
MB_clFFTplan_Capeverde_524288_r1831.bin

MultiBeam_Kernels_r1831.cl_Capeverde.bin_V7
MultiBeam_Kernels_r1831.clHD5_Capeverde.bin_V7

r1831_IntelRCoreTMi72600KCPU340GHz.wisdom

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
Priority of worker thread raised successfully
Priority of process adjusted successfully, below normal priority class used
OpenCL platform detected: Advanced Micro Devices, Inc.
BOINC assigns device 0
Info: BOINC provided device ID used

Build features: SETI7 Non-graphics OpenCL USE_OPENCL_HD5xxx OCL_ZERO_COPY OCL_CHIRP3 FFTW AMD specific USE_SSE x86
CPUID: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3
OpenCL-kernels filename : MultiBeam_Kernels_r1831.cl
INFO: can't open binary kernel file: C:\ProgramData\BOINC/projects/setiathome.berkeley.edu\MultiBeam_Kernels_r1831.clHD5_Capeverde.bin_V7, continue with recompile...
INFO: binary kernel file created
WARNING: can't open binary kernel file for oclFFT plan: C:\ProgramData\BOINC/projects/setiathome.berkeley.edu\MB_clFFTplan_Capeverde_524288_r1831.bin, continue with recompile...
WARNING: can't open binary kernel file for oclFFT plan: C:\ProgramData\BOINC/projects/setiathome.berkeley.edu\MB_clFFTplan_Capeverde_8_r1831.bin, continue with recompile...
WARNING: can't open binary kernel file for oclFFT plan: C:\ProgramData\BOINC/projects/setiathome.berkeley.edu\MB_clFFTplan_Capeverde_16_r1831.bin, continue with recompile...
WARNING: can't open binary kernel file for oclFFT plan: C:\ProgramData\BOINC/projects/setiathome.berkeley.edu\MB_clFFTplan_Capeverde_32_r1831.bin, continue with recompile...
WARNING: can't open binary kernel file for oclFFT plan: C:\ProgramData\BOINC/projects/setiathome.berkeley.edu\MB_clFFTplan_Capeverde_64_r1831.bin, continue with recompile...
WARNING: can't open binary kernel file for oclFFT plan: C:\ProgramData\BOINC/projects/setiathome.berkeley.edu\MB_clFFTplan_Capeverde_128_r1831.bin, continue with recompile...
WARNING: can't open binary kernel file for oclFFT plan: C:\ProgramData\BOINC/projects/setiathome.berkeley.edu\MB_clFFTplan_Capeverde_256_r1831.bin, continue with recompile...
WARNING: can't open binary kernel file for oclFFT plan: C:\ProgramData\BOINC/projects/setiathome.berkeley.edu\MB_clFFTplan_Capeverde_512_r1831.bin, continue with recompile...
WARNING: can't open binary kernel file for oclFFT plan: C:\ProgramData\BOINC/projects/setiathome.berkeley.edu\MB_clFFTplan_Capeverde_1024_r1831.bin, continue with recompile...
WARNING: can't open binary kernel file for oclFFT plan: C:\ProgramData\BOINC/projects/setiathome.berkeley.edu\MB_clFFTplan_Capeverde_2048_r1831.bin, continue with recompile...
WARNING: can't open binary kernel file for oclFFT plan: C:\ProgramData\BOINC/projects/setiathome.berkeley.edu\MB_clFFTplan_Capeverde_4096_r1831.bin, continue with recompile...
WARNING: can't open binary kernel file for oclFFT plan: C:\ProgramData\BOINC/projects/setiathome.berkeley.edu\MB_clFFTplan_Capeverde_8192_r1831.bin, continue with recompile...
WARNING: can't open binary kernel file for oclFFT plan: C:\ProgramData\BOINC/projects/setiathome.berkeley.edu\MB_clFFTplan_Capeverde_16384_r1831.bin, continue with recompile...
WARNING: can't open binary kernel file for oclFFT plan: C:\ProgramData\BOINC/projects/setiathome.berkeley.edu\MB_clFFTplan_Capeverde_32768_r1831.bin, continue with recompile...
WARNING: can't open binary kernel file for oclFFT plan: C:\ProgramData\BOINC/projects/setiathome.berkeley.edu\MB_clFFTplan_Capeverde_65536_r1831.bin, continue with recompile...
WARNING: can't open binary kernel file for oclFFT plan: C:\ProgramData\BOINC/projects/setiathome.berkeley.edu\MB_clFFTplan_Capeverde_131072_r1831.bin, continue with recompile...
ar=1.111341 NumCfft=133605 NumGauss= 425303298 NumPulse= 25401855487 NumTriplet= 5743942828032


You don't need to delete any apps at present.

Claggy
ID: 1597777 · Report as offensive
John

Send message
Joined: 2 Oct 00
Posts: 16
Credit: 17,094,836
RAC: 5
United States
Message 1598586 - Posted: 8 Nov 2014, 17:47:29 UTC - in response to Message 1597777.  

Thanks this seems to have worked.
ID: 1598586 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 5 Jul 99
Posts: 4654
Credit: 47,537,079
RAC: 4
United Kingdom
Message 1598591 - Posted: 8 Nov 2014, 18:03:25 UTC - in response to Message 1598586.  

Thanks this seems to have worked.

Brilliant.

Claggy
ID: 1598591 · Report as offensive

Message boards : Number crunching : Display driver failure?


 
©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.