AOCLBF 1.8.4 by WinD - Dynamic clocks adjusting Completely AUTOfanspeed

[dishwara]

don't able to remember, coz it was more than 3 months ago.

[wind]

try this one... http://www.mediafire.com/?1qa45cb1182bjve
what about stability?

[RedLine888]

it downclocks each gpu by 10 MHz every second

[wind]

RedLine888
post your settings (screenshot preferred)

[RedLine888]

client settings or gpu settings?

[wind]

[FRanz33]

Wind. Great to see you are still around. the GUI is running very well. I Get the same error as well. Even More so on my big rigs with a couple 6970s or 5870s. the more miners the more often i see the error. I had the reconnect set to 15 sec. Some times when the connection gets bad it was enough to crash my systems. Increased the page file to 4 to 8gb increased ram and increased the reconnect window to 60 sec and it occurs less but still every 3 days or so. Tried 1.82b too and it was same thing. Also if you could add a NO OSD on start up so its completely stealth that would rock. And an Option to increase the Power Tune to 20% in the overclock window would help on the 6 and 7 series coming out. Its a bother when you have a headless unit and they are aren't X-fired together. Thank you so Much! Happy Holidays!

[disclaimer201]

Would love to see a solution to the array error.

[wind]

Well... trying to fix this error...
Give you on testing a new one http://www.mediafire.com/?8kak78yeq11t8a0
Waiting for your test results....
forget to say you should test on phoenix only-poclbm is without changes yet

[FRanz33]

Thank you! Testing right now. 1.82b2 with Phoenix 1.72 phatk2 2x5870 930/300. Leaving Office...now...

[Zarovsky]

Yes, with the same feature disabled downclock GPU power drops to 10 per second, working on 1.8, if a bug flies we are talking about a miner still continues.

[disclaimer201]

I get a trojan win 32 generic alert when I want to open the new aoclbf1.82b file. Now I'm scared. Is that normal?

[wind]

I get a trojan win 32 generic alert when I want to open the new aoclbf1.82b file. Now I'm scared. Is that normal?

Source code is attached! You can yourself compile it.

[farfiman]

tried this version to solve the script error that pops up.

The speeds of the hashing on gpu 2 and 3  were very low and not stable
and the whole system got stuck eventually ( not sure if it is related)
couldnt run it long enough to see if script error went away

running on win7 64

putting the old version back solved the problems ( script problem still there of course)

[wind]

putting the old version back solved the problems ( script problem still there of course)

What vesrsion is that?

[FRanz33]

I also ran the the beta. still got the array error. fiddled around with some stuff and i think the memory leak and the array error are two different problems. I was thinking the leak was coming from auto restarting so i i went from 60 to 90 seconds timer on all my single card miners 60 to 3 min on my double cards and 5 min on my 3 card miners. still got the array error but much much less memory usage. I mine at bitcoinpool.com and the had a power outage and a few miners got hit with the array error then another time for no reason all of them got the error. Only time i can produce the error myself is when swapping cards and not starting with a fresh copy of the GUI. For an example trade a 5870 for a 6970 and boot the system up. When the GUI starts it gives the error. If it helps beta 2 did resist the error longer than beta 1 and 1.81 but after i got the first array error i reverted back to 1.81. Thank you for staying with this. Any chance of being able to save the hide OSD command? kinda annoying to hit hide osd every time it starts up. esp with array bug and having to restart every few days.

[farfiman]

putting the old version back solved the problems ( script problem still there of course)

What vesrsion is that?

1.82b2

went back to 1.81

[wind]

FRanz33
farfiman
thanx for testing. i'm now working on optimizing the code . it'll be faster when disabling OSD and may be array and memory problem will be solved..i hope..
in plans is smth kinda sheduler to change aggression-useful for machines a user works on
 

Any chance of being able to save the hide OSD command? kinda annoying to hit hide osd every time it starts up. esp with array bug and having to restart every few days.

will be done

[BigBobo]

so how about those 7970 optimizations? 

[wind]

BigBobo
it seems to work with 7970. Unfortunately i am unable to test it.

2All
Catch aoclbf 1.82b3 by WinD
Another try to fix an array error