Set an intensity

1. no

2. because the dyn interval timing means something when only 1 thread is running otherwise they overlap ... if you want high throughput increase the interval

3. it shouldn't...

I bet you're loading *2* configuration files...

Your log shows 3 GPU's but you are only setting some of the settings for 2 of them ...
"intensity" : "8,8",

When It acts up it does this

Proof of work result false booo
block info
BFL waited (time proper varies a little) Line seems to appear when no nonce is found so not if it says rejected.
Pushing work to staged thread
sucessfully rolled work
Repeat

How many repeats depends. If the work was from the previous block would it come in about 5 second submissions? I think no but only because I assume it would try to submit more then one every 5 seconds to the pool to get credit for stales. What I see will repeat until it stops rolling work (at 120 seconds and 5 seconds per work unit that should leave me with 24 possible work units to get rejected before it runs out of work). The pool is disabled at 13 work units or so being rejected. If the units are truely stales that I am submitting would it count expected stales into the pools rejected work in a row? My thought is not as likely. Maybe it is but somewhere in the 70 or so seconds between LP notice and pool change because of excessive rejects I should submit some work from the current pools LP that my single has been working on. If what I am thinking is accurate I am asking for help from the wrong place and really should ask at EclipseMC thread about it. If I am wrong in my thinking I am sure someone will point out what I am missing.

PS: Did anyone else asking for help on this thread get a PM from lukeJR?

Come to the dark side ... we have cookies

We are all on the dark side ... cookies optional.

I am running 11.9 and SDK 2.5 (Windows 7) for my 5870's. Going from 2.7.0 to 2.7.5, I had to change mem from 170 to 300 and set work size to 256 to get the same hash rate.

At 970/300 -w 256 I get 445.6 MH per 5870. Fan is at 75% and temp is 69 to 74 depending on how hot it is outside.

I use SDK 2.5 because I also have one 6970 in that rig. I did not have to raise memory or change work size for the 6970 in that rig to maintain the same hash rate as before (960/170 - 430.3 MH)

Yes, I know it has the CPU bug, but I use affinity to only use one core. I have tried other driver versions but loose hash rate and have worse stability.

Any news on a Mac Binary?

Haha sounds fair. I can't stand not having the latest version of any piece of software, so Im always updating everything.