Posts by Confusius

1) Message boards : News : maximum time limit elapsed bug (Message 49954) Posted 6 Jul 2011 by Confusius Post: Update: Running more than one hour, no errors (Computer WKS01)
2) Message boards : News : maximum time limit elapsed bug (Message 49949) Posted 6 Jul 2011 by Confusius Post: unfortunatly the arkain app seems to be the same as the stock app delivered by MW. No difference in atleast one byte. But i gave it a try though with the app_info.xml provided in the .zip archive. Result: 4 WUs in a row without an error!
3) Message boards : News : maximum time limit elapsed bug (Message 49896) Posted 5 Jul 2011 by Confusius Post: Maybe there is a debug Version with a verbosed log that can be provided? I would gladly participate in systematicaly testing against this bug.
4) Message boards : News : maximum time limit elapsed bug (Message 49895) Posted 5 Jul 2011 by Confusius Post: Unstability caused from to much heat could that be?? Maybe in some cases, but shure not mine. My 6950 is running at stock settings. I avoided overclocking my card right from the beginning.
5) Message boards : News : maximum time limit elapsed bug (Message 49880) Posted 4 Jul 2011 by Confusius Post: Since i remembered that last year the "optimized apps" have been running quiet well, i gave them a try. At least they ran without error (0.23 from P3DNow), but of course validation has failed.
6) Message boards : News : maximum time limit elapsed bug (Message 49844) Posted 3 Jul 2011 by Confusius Post: using Vista 64 and Catalyst 11.6. I also leave 1 core free from BOINC by going in to the BOINC manager under 'Advanced' \ 'Preferences' and set the 'On multiprocessor system, use at most' to 75%. Catalyst Version was 11.6 till this noon, then downgraded to 11.5. Changed nothing. The last 4 WUs differ in the time limit. Suddenly they are aborted at 1:09, 1:22, 1:09 and 1:13. DonÂ´t know what changed. [/img]
7) Message boards : News : maximum time limit elapsed bug (Message 49839) Posted 3 Jul 2011 by Confusius Post: me too, most of my WUs end up with the error. Got an 6950 too. posted the problem at first at http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=2496
8) Message boards : Number crunching : Massive "exceeded elapsed time limit" errors (Message 49834) Posted 3 Jul 2011 by Confusius Post: thanks for the advice, but changing the DCF did not change anything. Still got the problem.
9) Message boards : Number crunching : Massive "exceeded elapsed time limit" errors (Message 49833) Posted 3 Jul 2011 by Confusius Post: I gave it a try and installed the Boinc beta client, but this did not change anything. As far as i can see the calculations run fine till 1:05 (about 60%), then the error shows up. But neverless the calculation does continue until 100% is reached (progress bar continues as usual), while (sometimes) a new calculation thread gets startet before the last one has finished (Progress 100%). Like mentioned before, this only happens with milkyway projects. All others run smoothly like they should.
10) Message boards : Number crunching : Massive "exceeded elapsed time limit" errors (Message 49829) Posted 3 Jul 2011 by Confusius Post: I have unhidden the machine.
11) Message boards : Number crunching : Massive "exceeded elapsed time limit" errors (Message 49816) Posted 3 Jul 2011 by Confusius Post: Hi, after months of not beeing able to participate, due to missing hardware, i finally got my new 6950. I updated to the latest boinc client, started milkyway and was amazed: error following error. Every MW WU i got since start yesterday afternoon fails: "exceeded elapsed time limit". Other Projects run perfect. Drivers, Boinc and MW App are up to date, no app_config is used. So here the Question: am i the only one wasting GPU Time or is it a common problem? thnx in advance AndrÃ©
12) Message boards : Number crunching : v0.23 performance drop? (Message 39760) Posted 16 May 2010 by Confusius Post: I've got an Core i7 920 System and noticed the same behaviour a while ago while trying to overclock my 5850. As far as i found out, the GPU Usage and therfore the performance drops dramatically if all Cores are at 100%. GPU usage never exceeded 82%. The solution was to configure Boinc to only use 90% of the Processors on Multicore Systems. This freed one Core and raised the Milkyway GPU usage to 99%.