[4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool

[Uliss]

Still didn't get any reward for that block. Thats suck.

18074   2013-05-17 14:52:13   2:34:44   22016288   1833   0.00000000   236621    25.25560000    confirmed

Don't worry!

and oh look, it fixed its self.
I don't want to sound annoyed, but it ALWAYS FIXES ITS SELF so STOP your pointless moaning!

Geez..

 

[1714496559]

1714496559

[1714496559]

1714496559

[1714496559]

1714496559

[1714496559]

1714496559

[MSO]

I have tried to install different drivers for the cards, and I have tried installing a previous version that supports both cards. Neither worked. It seems to be the combination of the new card and anything but the new driver that makes GUIMiner not start.

Now, when I am running only the new card, Phoenix and Stratum Proxy, it stopped working tonight, a few hours after I started it. I restarted the miner this morning and it worked again. I hope it's a one time occurance, but I doubt it. It didn't happen with Phoenix and BCPool. Any guesses?

This happened to me when I upgraded Catalyst from 3.1 to 3.4 using only a single card (7770).  Catalyst 3.4 fixed some display problems (flickering pixels) but slowed my miner around 20%.  I wanted to revert back to 3.1 so I uninstalled all AMD software (including the driver via device manager) and then installed Catalyst 3.1.  GUIMiner failed to start after this with no error message.

I can only speculate, but I believe that the OpenCL package is not removed when Catalyst is uninstalled. Software developers frequently leave support packages, such as OpenCL in place because they cannot determine if other software not written by them may be using the interface.

So when the older reinstalled Catalyst 3.1 attempts to use the newer OpenCL from Catalyst 3.4, its probably misusing a changed interface causing an error that GUIMiner doesn't know how to handle.

[oroboras]

Still didn't get any reward for that block. Thats suck.

18074   2013-05-17 14:52:13   2:34:44   22016288   1833   0.00000000   236621    25.25560000    confirmed

Don't worry!

and oh look, it fixed its self.
I don't want to sound annoyed, but it ALWAYS FIXES ITS SELF so STOP your pointless moaning!

Geez..

 

Well, that is the first time ever I have actually seen it not adjust the reward.
In that case, I retract my previous statement.

@LordTheron PM me your wallet address, and I'll gladly share my reward with you for that block, 50/50 (we do about the same hash rate)

[RayJay]

What is a normal rate for invalid blocks, we seam to have a lot of those lately on top of bad luck. I remember 2 yesterday and now two today.

[KNK]

I need to restart my miner. Does someone know when will this round end  ?

P.S. sorry for the spam, hope my post will trigger round end soon

[oroboras]

Current round duration:   2:47:07
Current shares CDF:   85.07 %

So not too long now, I guess.

EDIT: Unless I really don't get how the ratio works, which is highly likely.

[kanta]

The CDF% will go up more and more slowly as more time passes. We had an 11 hour block the other day, no one knows exactly how long a block will take, that's part of the luck that everyone talks about

[KNK]

no one knows exactly how long a block will take

I know, i was joking
As a keep watching it seems it will never end will go for a walk and will need to restart the miner later

[5120-01-518-6126]

What is a normal rate for invalid blocks, we seam to have a lot of those lately on top of bad luck. I remember 2 yesterday and now two today.

Invalid is just bad luck, too -- more machines hashing with increasing hash power = greater chance of "collision"

[crashoveride54902]

no one knows exactly how long a block will take

I know, i was joking
As a keep watching it seems it will never end will go for a walk and will need to restart the miner later

how long is it gona take to restart your miner? few shares off at the end shouldn't hurt, unless you have a very slow miner...and of course lets not forget the mysterious reward bug running around...maybe ya are better off to wait hehe

[LordTheron]

Still didn't get any reward for that block. Thats suck.

18074   2013-05-17 14:52:13   2:34:44   22016288   1833   0.00000000   236621    25.25560000    confirmed

Don't worry!

and oh look, it fixed its self.
I don't want to sound annoyed, but it ALWAYS FIXES ITS SELF so STOP your pointless moaning!

Geez..

 

Well, that is the first time ever I have actually seen it not adjust the reward.
In that case, I retract my previous statement.

@LordTheron PM me your wallet address, and I'll gladly share my reward with you for that block, 50/50 (we do about the same hash rate)

many thanks for that mate but I will be fine. Stopped mining here and will not come back until I know that the pool  is working as it should. No sign of slush  doesn't give me any confidence at all. It is disappointing that pool admin is not around for so long.

As you see not everything is fixing itself. here is another one..

18091   2013-05-18 23:10:26   2:23:58   18213818   2621   0.00000070   236826    25.03250000    confirmed

[MyOldGeForce]

I believe this is the workaround (pics and all in there to make it easy)

http://bitclockers.com/forums/index.php?topic=7.0

Then that isn't the problem. I measured the corresponding pins on the monitor when it was unplugged, I got about 80 ohms.

Now I have tried running only a 4870 and also only the 4850 that worked before. Now they don't. Driver: 13-1 legacy. I'm beginning to think something in Windows is corrupted. For speed reasons, we deactivated windows update when we installed this machine, and then forgot about it. Now I have re-activated it to see if that does the trick. It will take some time, so I'll try it tomorrow. It's 10:50PM here in Sweden.

Have you tried using one of the older full Catalyst Suite drivers that support the HD4xxx cards as opposed to the legacy drivers? (not available for Windows 8 ).  The legacy driver set doesn't support hardware accelerated OpenGL support, (no Minecraft  ) so perhaps OpenCL is compromised or removed too.

Yes I have. The legacy driver set for Windows 7 supports OpenCL, it even worked before I tried using two cards.

I have tried to install different drivers for the cards, and I have tried installing a previous version that supports both cards. Neither worked. It seems to be the combination of the new card and anything but the new driver that makes GUIMiner not start.

Now, when I am running only the new card, Phoenix and Stratum Proxy, it stopped working tonight, a few hours after I started it. I restarted the miner this morning and it worked again. I hope it's a one time occurance, but I doubt it. It didn't happen with Phoenix and BCPool. Any guesses?

This happened to me when I upgraded Catalyst from 3.1 to 3.4 using only a single card (7770).  Catalyst 3.4 fixed some display problems (flickering pixels) but slowed my miner around 20%.  I wanted to revert back to 3.1 so I uninstalled all AMD software (including the driver via device manager) and then installed Catalyst 3.1.  GUIMiner failed to start after this with no error message.

I can only speculate, but I believe that the OpenCL package is not removed when Catalyst is uninstalled. Software developers frequently leave support packages, such as OpenCL in place because they cannot determine if other software not written by them may be using the interface.

So when the older reinstalled Catalyst 3.1 attempts to use the newer OpenCL from Catalyst 3.4, its probably misusing a changed interface causing an error that GUIMiner doesn't know how to handle.

Thanks! Could Windows' system restore function help? I think I'll try that.

[autonomous42]

Try this tool: http://sites.amd.com/us/game/downloads/Pages/catalyst-uninstall-utility.aspx
I used it when downgrading from 13.1 to 12.8 to use vanitygen. It actually removes everything and gives you a clean slate. Just run it, reboot, and install again.

[MyOldGeForce]

Nope. I didn't have any restore point that was old enough. I'll try to search a bit on the web, otherwise I'll just have to reinstall it. And take a Ghost copy in case something happens again.

Edit: Thanks autonomous42, I'll try that first.

[MyOldGeForce]

The uninstall utility didn't do the trick.

With some configurations that doesn't work, I get an error message when starting Windows, that kdbsync.exe has stopped working. Could this be a clue? I searched it, and it seems to have something to do with the APP SDK. The only "solutions" I find is to remove or inhibit start of APP SDK. It's not like that's an option here...

[autonomous42]

There are other cleaning utilities you can try but AMD doesn't recommend them. You can't uninstall the SDK? Do you have time for a clean install of Windows? That will do the trick for sure. With the luck in the pool lately, I doubt you'll miss much.

[Lucko]

What is a normal rate for invalid blocks, we seam to have a lot of those lately on top of bad luck. I remember 2 yesterday and now two today.

Invalid is just bad luck, too -- more machines hashing with increasing hash power = greater chance of "collision"

Not such hi number... Thinking that 4 in 2 days is normal is stupid... Last time Slush was fixing things when we had 2 in 4 days or something like that...

[nottm28]

What is a normal rate for invalid blocks, we seam to have a lot of those lately on top of bad luck. I remember 2 yesterday and now two today.

Invalid is just bad luck, too -- more machines hashing with increasing hash power = greater chance of "collision"

Not such hi number... Thinking that 4 in 2 days is normal is stupid... Last time Slush was fixing things when we had 2 in 4 days or something like that...

Not quite 4 in 2 days

block=start_time,duration,hashes,luck,difficulty,confirmations
236729=2013-05-18 09:52:02,1:06:34,9169,0.61,11187257,invalid
236657=2013-05-17 20:34:35,2:27:43,9905,0.95,11187257,invalid
236442=2013-05-16 12:10:31,0:35:00,9526,0.84,11187257,invalid
236382=2013-05-16 01:59:30,0:25:24,9361,0.71,11187257,invalid

But unusually, I find myself tending to agree with Lucko for once - it does look a bit odd and we have had a problem before with bitcoind not having a fast enough connection to the outside world (so when we find a block we can report it the world as fast as is humanly (or computingly) possible).

But if we see this invalid rate drop off over the next few days then it probably was just bad luck.

[Lucko]

Not quite 4 in 2 days

Sorry my mistake. I thought that RayJay counted that correctly... But then again it is only 8 hours more...

EDIT: Also looking at this: Pool luck (1 day, 7 days, 30 days):   91%, 83%, 97%.
7 days is doping but this is not enough to say it is a problem, but 30 days is a good indicator. If it goes down too much. Now it is hard to say anything. It is still normal. But if we see it below 85% is a really big chance that pool is really malfunctioning. 90% would be start thinking that it is not only counting shares but also other things...

[nottm28]

Not quite 4 in 2 days

Sorry my mistake. I thought that RayJay counted that correctly... But then again it is only 8 hours more...

EDIT: Also looking at this: Pool luck (1 day, 7 days, 30 days):   91%, 83%, 97%.
7 days is doping but this is not enough to say it is a problem, but 30 days is a good indicator. If it goes down too much. Now it is hard to say anything. It is still normal. But if we see it below 85% is a really big chance that pool is really malfunctioning. 90% would be start thinking that it is not only counting shares but also other things...

I've been checking luck on other pools - most of the ones I look at are running with low luck and is not incomparable to ours. One exception stands out strongly - you'll never guess - BTCGuild - they are flying with luck atm. Bitminter's luck is even worse than ours... It'll change (I hope) - that's what luck does.