obviously if the card is still dripping oil when you rma the card, that's obvious the warranty will be voided... 
However, cleaning the card with acetone should remove any trace of oil

You are being too nice. Suck it primeGPU .. am I glad not to have put coins into trashbin. Talk is cheap, no updates till now to prove your point.

So now, perhaps you can speed it up with madMax's code.. Congrats.

fpga

[And again:] ... and we are not able to speed-up ours any further. Which is not the case.

But again, it will be only temporary so there is at least one pool running at all.

In the long run i don't want to be bothered with DOS attacks or manage firewall settings all day long.
I think there should be multiple pools running and then the miner could be auto-switching in case one goes down.
And yeah solo mining of course.

Server is now crashing consistenly. Some bug in bitcoin function ConnectSocketDirectly is causing the issue.

This is just too much, i've been baby sitting this thing for over 48h straight now.

FINAL UPDATE: The pool will close. All balances will be PAID once they are mature. I WILL release a solo miner.

Need to sleep now...

Alright guys, pool works again, this time properly fixed.

All the issues were cause by the ancient ulimit -n of 1024. Basically the server ran out of file descriptors and this caused the blockchain to go corrupt.
This is also why the DOS was so effective and why it crashed again once we hit >100 workers.

I set the ulimit -n now to 102400, more than enough 

Can please someone give link to catalyst 14.3?

Getting the following before the program closes:

C:\Users\Ivan\Desktop\madPrimeMiner-v1.0-rc0-T10-w32>xpmclient
madPrimeMiner-v1.0-T10
ClientName = 'IVANLABRIE'  ClientID = 951955625  InstanceID = 2300866414
Address = 'AT4iEgpfXBDqth1k8tQU5Bb57z9mchwgY9'
Found 2 devices
Using device 0 as GPU 0
Using device 1 as GPU 1
N=11 SIZE=4096 STRIPES=420 WIDTH=20 PCOUNT=40960 TARGET=10
GPU 0: has 32 CUs
GPU 0: hash primorial = 30030 (14 bits)
GPU 0: sieve primorial = 435656388001 (58 bits)
GPU 0: sieve size = 5505 (7 bits)
GPU 0: max bits used 341/352
N=11 SIZE=4096 STRIPES=420 WIDTH=20 PCOUNT=40960 TARGET=10
GPU 1: has 32 CUs
GPU 1: hash primorial = 30030 (14 bits)
GPU 1: sieve primorial = 435656388001 (58 bits)
GPU 1: sieve size = 550556388001 (7 bits)
GPU 1: max bits used 341/352
Connecting to frontend: 54.187.143.168:6666 ...
Connecting to bitcoin: 54.187.143.168:60000 ...
Connecting to signals: 54.187.143.168:60001 ...
Work received: height=529682 diff=10.890427 latency=1071ms
error: ProbablePrimeChainTestFast 0/3
error: ProbablePrimeChainTestFast 0/3
er
C:\Users\Ivan\Desktop\madPrimeMiner-v1.0-rc0-T10-w32>



i7 3820
2x4gb samsung 1600mhz cl11 ram
2 x msi gaming r9 280x cards
win 8 64
cat 14.4

Yeah they change based on pool luck. They are calculated based on the blocks vs. shares found in the last 24h. Once the pool has more hashpower the share values should stabilize.
11-ch is the same as 10 because they are too rare to make an exception.

Don't know. You can try, but it might be slower, so compare your results with other miners.

In this case juve4v has the same error and he uses 14.4 ... i'm looking for the bug right now.