Posts by Seraphim401

1) Message boards : Number crunching : All Milkyway@Home 1.02 tasks ending in computation error on HD6950. (Message 61316) Posted 3 Mar 2014 by Seraphim401 Post: Didn't know mod fit WUs gave less credit/hr, I wonder why they do that? Partial answer to my own question lol, I noticed when the MW v1.02 WUs are running, power draw at the wall goes up a lot on my HD 5850. Just now total power draw went from ~267w running MW sep. mod. fit to ~291w running MW v1.02! (think I'll start a new thread about that). Yeah I noticed that to.I hope they lay off the aggression a bit. There is no need for the gpu to be running at 99% for a WU. Just my humble opinion.
2) Message boards : Number crunching : All Milkyway@Home 1.02 tasks ending in computation error on HD6950. (Message 61156) Posted 19 Feb 2014 by Seraphim401 Post: Thank you for this thread. I was also having problems with my 2 5870's. Downgraded to 13.1 did the trick. I would also like to say how disappointed I am with lack of interest from the devs on this issue. Not one reply from them concerning this. Pathetic!
3) Message boards : Number crunching : Computational Error? (Message 59122) Posted 26 Jun 2013 by Seraphim401 Post: Thanks mikey,but it seems that the settings i'm using now did the trick. I'm keeping your settings in mind incase the madness returns :) Thank you.
4) Message boards : Number crunching : Computational Error? (Message 59108) Posted 25 Jun 2013 by Seraphim401 Post: <cc_config> <options> <use_all_gpus>1</use_all_gpus> <exclude_gpu> <url>http://milkyway.cs.rpi.edu/milkyway/</url> <device_num>1</device_num> <type>ATI</type> <app><name>milkyway_separation__modified_fit_1.22_windows_x86_64__opencl_amd_ati.exe</name></app> <app><name>milkyway_separation_1.02_windows_x86_64__opencl_amd_ati.exe</name></app> </exclude_gpu> </options> </cc_config> I'm using this setting in my cc_config.xml. So far so good. Will report if the errors still persists.
5) Message boards : Number crunching : Computational Error? (Message 59101) Posted 25 Jun 2013 by Seraphim401 Post: host 521265 Right now you have like 40% of your tasks working (HD7970) and 60% error tasks (HD5770). The error task logs are showing for separation: Found 2 CL devices Device 'Juniper' (Advanced Micro Devices, Inc.:0x1002) (CL_DEVICE_TYPE_GPU) Driver version: 1124.2 (VM) Version: OpenCL 1.2 AMD-APP (1124.2) Compute capability: 0.0 Max compute units: 10 Clock frequency: 500 Mhz Global mem size: 1073741824 Local mem size: 32768 Max const buf size: 65536 Double extension: (none) Device doesn't support double precision Failed to calculate likelihood and for separation modified fit: Found 2 CL devices Device 'Juniper' (Advanced Micro Devices, Inc.:0x1002) (CL_DEVICE_TYPE_GPU) Board: ATI Radeon HD 5700 Series Driver version: 1124.2 (VM) Version: OpenCL 1.2 AMD-APP (1124.2) Compute capability: 0.0 Max compute units: 10 Clock frequency: 500 Mhz Global mem size: 1073741824 Local mem size: 32768 Max const buf size: 65536 Double extension: (none) Device doesn't support double precision Failed to calculate likelihood That is weird. The device it detects as a Juniper is the 7970! I downclocked the 7970 to 500 Mhz and left the 5770 at stock (850 Mhz). So how do I disable the 5770 for this project only. The other projects I have running have no problem with the 5770. Thanks for your help.
6) Message boards : Number crunching : Computational Error? (Message 59085) Posted 24 Jun 2013 by Seraphim401 Post: Hey there, It looks to me like one of you GPUs doesn't support Double Precision. We require that GPUs have double precision support for Milkyway@home apps. Sometimes this is an issue with a driver not supporting it even though the card does because for some silly reason it is deemed optional to implement it in the OpenCL standards. I recommend you ensure all drivers are up to date because there may be a new driver that does support double precision. Sorry for the long response time, Jake W Thanks for the response. It looks like I spoke to soon,now all WU are failing. Milkyway never uses the 5770. Did a project reset and it looks like the WU are not failing anymore. What I don't understand is the fact that the WU's always used to fail at the end of the calculations. This was particularly annoying when doing the N-body calculation since it would use the cpu for hours only to give an error at the end.
7) Message boards : Number crunching : Computational Error? (Message 59083) Posted 24 Jun 2013 by Seraphim401 Post: The program does this automatically. It only uses the 7970. Thanks though :)
8) Message boards : Number crunching : Computational Error? (Message 59057) Posted 23 Jun 2013 by Seraphim401 Post: Just to clarify, it's the milkyway_seperation_1.02_windows_x86_64_opencl_amd_ati that was, and still is, causing the Computational Error on my machine. Yes that work unit always errors out on me,but only on my x64 rig with an HD 5770 and HD 7970. My 2 two HD 5870's in running on a x86 have no such problems.