Quote from: Caterpie69 on March 30, 2014, 01:30:33 AM

Quote from: binaryclock on March 30, 2014, 01:26:50 AM

Quote from: Caterpie69 on March 30, 2014, 01:15:16 AM

Quote from: Caterpie69 on March 30, 2014, 12:56:47 AM

Quote from: cryptodave on March 30, 2014, 12:54:56 AM

Quote from: Caterpie69 on March 30, 2014, 12:48:06 AM

Quote from: BtcBrothers on March 29, 2014, 11:56:16 PM

Quote from: Caterpie69 on March 29, 2014, 11:51:59 PM

My miner is going fine, then all of a sudden it just stops accepting shares. It keeps telling me new blocks are detected, that's it. Once I restart my miner, all is well again for 10 or so minutes. What's the issue? Anyone know? I'm on the official pool.

I too am mining on the official pool. I have not had any issues. Are you using vertminer? screenshot?

I just restarted my miner now. I'll post a pic when it happens again. Yes, I'm using vertminer. Here is my setup

setx GPUMAXALLOCPERCENT 100
setx GPUUSESYNCOBJECTS 1

Vertminer.exe --scrypt-vert -o stratum+tcp://h2o.imine.at:8787 -u USER -p PASS -w 64 -I 12 -g 1 --thread-concurrency 8192 --gpu-fan 55 --temp-overheat 90

EDIT - I have 2x radeon 5870. Older cards, so my TC is low.

just REM or delete the setx parameters in your *.bat file.

Alrighty, I'll see how it goes. XD

It's hanging again, here is my miner. I get shares every few seconds and then all of a sudden this happens.

The vardiff at that pool is set too high. 512? You shouldn't be higher than 256. With 512 vardiff and your hash rate, you can't submit shares fast enough before the next block is found. I bet the person even has multiple machines all on the same worker, which is really bad.

Seems there are a few kinks to iron out here for now. I will go back to mining LTC and come back to H2O soon.

You would not have had any issues if you created multiple workers for your rig/rigs.

I have lowered the pool vardiff to 256. That should cover you guys that are using a single worker which you should NOT be doing in the first place

But smooth sailing, cheers