Topic: Problem with Guiminer (Read 23897 times)

I'll buy. Bank ransfer is ok for you?

i had that too it was one of the extra miners in the miners folder, i just deleted the questionable one, works fine.

I'm using the 2010-8-24 version and was using pocibm with it untill I switched to ufasoft

It's a false positive based on the chance that it's a payload in a Trojan Horse.

My antivirus program reports that there is a virus in that file when I download it (TR/Monitor.A.1).

get GUIMiner v2011-07-01 (the older one) still works good with opencl like Schwede65 said at the top of this page

Yes, that's what I would want, too. I want to use guiminer and at the moment it works only with the phoenix-miner but that has only half the hashrate.

Let me rephrase my wish. Can somebody please write a new poclbm kernel that works with the gui? Much appreciated.

Well I was able to update Phonex but it's not as good a poclbm. And I can't get Poclbm working properly.

one last time for the handycapped

Guiminer is just a graphical inter face to other miners

up date it yourself
replace the cgminer ... phonex ... what ever to the latest versions

IT HAS NOTHING TO DO WITH THE GUI

cgminer runs fine in windows, and if you tweak the config file you don't even have to open a command prompt. Just double-click cgminer.exe and it will auto-load the config and start mining.

Can't someone please update Guiminer for 2012? It's a super beloved mining program and I don't see myself switching to cgminer or linux anytime ever.

I have been having this problem also.  My miners work for a while then stop. 

I don't know why this is the first time I saw this thread.  I am trying to switch to cgminer but I can't get that to work at all.  It will detect my cards but not much more.

I'm curious what is considered "high stales" my 6870's are getting 0.14% - 0.16% stales, and the 6950's are ~0.19% on phoenix for the last 27,000 shares. When i ran poclbm i honestly think it was about the same % of stales, i never paid much attention to it to be honest.

A lot of them perhaps got tired of waiting and moved to cgminer instead. 

I'm really surprised at how little chatter this thread has. You would think a TON of people would have this problem.

My settings for cgminer and phoenix aren't perfect, but for some reason to reach the same mh/s that was getting from OpenCL my wattage increase is like 20% from normal. 

its because 11.12+ uses sdk 2.6 which is terrible. just dont install the sdk and use the one from 11.1 or whatever one you prefer to use (sdk 2.1)

i get 50Mh/s less using Catalyst 12.1 and 11.12 - using 11.11 is best for me and ive been using GUIMiner v2011-07-01 with no problems, stopping and starting works fine.

Is the Radeon Catalyst 12.1 driver package a possible source of the problem?
Haven't been receiving shares for two days, upgraded to catalyst 12.1 64 bit around that time.

Is anyone experiencing problems without having recently upgraded?

Edit: Ah... Nvm, poclbm bug.  

so far as i can see:

guiminer-20110824.exe seems to be the poclbm-broken-one

guiminer-20110701.exe is poclbm-o.k. and does his good mining-job 

I run a really old version of guiminer (newer versions are less efficient) and all 10 of my 4gpu rigs are doing fine with opencl on deepbit.

It must be an issue with newer versions (within the past few months or so)

"Actually many probably still are doing work since the problem only presents when the worker is switched off and then back on. I think many will be coming here as workers are powercycled and don't come back up proberly and find the fix right away so there will sort of be a rolling amount of downtime that doesn't affect the difficulty rate too much"

I agree with the above statement   -- if you powercycle your pc --- i was unable to restart guiminer and had to switch to cgminer --
I have another 4 pc with multi gpu  and guminer which have not being power cycled working correctly --- I would expect the same problem if I was to power cycle those pc's

Same too me. Use cgminer. At least that's what the BTC Guild operator suggested.

Actually many probably still are doing work since the problem only presents when the worker is switched off and then back on. I think many will be coming here as workers are powercycled and don't come back up proberly and find the fix right away so there will sort of be a rolling amount of downtime that doesn't affect the difficulty rate too much

Does GUIminer automatically pull the latest version of polcbm? Or will we have to redownload guiminer whenever the patch is out for Windows?

Also, I'm curious as to how much the difficulty has fallen because of this. We'll see just how many users are using polcbm. My guess is...a lot. And judging by the small amount of responses here on the forum, most of them probably haven't even realized that they're not actually doing work lately, since the computer by all outside measures (power draw, heat created) looks as though it is still working.

I was pretty sure it had to do with the difficulty rise. 

Please see https://bitcointalksearch.org/topic/m.732081

I don't have problems at all running 24/7 in last 2 months but I haven't updated my miner in 2 months either.

Check out the fix here:
https://github.com/m0mchil/poclbm/commit/3c4bf83c9fe8602c687afcd82d556cf58af4fbba

Win7 users don't have a lot of choices. Switching to CGMiner is easy enough. Hopefully Guiminer will be fixed soon.

Strange thing though, if you stayed connected before the diff change it still works. Thats some funky magikx right there o_0

I've only had one report on BTC Guild, but the pool hash rate definitely reflects that its affecting a large number of users.  I'm eagerly awaiting someone making a post after discovering the cause of this problem and why it only seems to be hurting poclbm based miners.

watching this thread, only because the detailed explanation will be very interesting, like one of those "mystery diagnosis" TV shows 
 
"On the morning of.... bitcoin miners across the world stopped working all at once, and nobody knew why....   It took the dedicated work of one man to piece this mystery together, and solve the case of this strange phenomenon.  This is his story."

watching

i'm also having problems with GUI miner with all rigs!!!

I can second that, we at bitlc.net have seen reports of users having issues as well.

Do we have any fix for this atm slush? suggested action? switch miner?

Its only Guiminer with open Cl
Guiminer with phoenix-miner working!

Some people reported me issues with GUI miner on my pool, but I don't have an idea why it is doing that failure. I didn't modified pool software and also only guiminer is having issues. I think it is something strange in gui miner...

Agreed.. I have one machine still running GUIminer from yesterday and it's still hashing away well. The one I stopped and started again today doesn't work with the standard poclbm core..

I don't really know python, but after having a look through the source code and following it through to the point at which the error occurs it seems to be a problem with submitting a found result... But it does appear to keep hashing even though it doesn't seem able to send them. Which is why the computers still seem to be busy despite the pools showing 0 shares.

If that was the case, anybody who had an existing miner running (those who haven't re-turned it on recently) wouldn't have the problem.

I'm wondering if it has to do with the dificulty rise, thats all I can tell has changed

Also something that is odd, this issue has not affected any of my nvidia based miners.

So am I; I didn't even check the post's date, got here by the error as I just changed flags and though it was something related to that..

2012-02-04 16:01:28: Listener for "SECONDARY": pit.deepbit.net:8332 04/02/2012 16:01:28, Unexpected error:


Accounts in deepbit are showing as active even though i shut down most of them minutes ago..

Software upgrades on pools??

Does anyone know how to setup the backup pool on this.

1 more person experiencing this problem. WTF is going on? I don't conceptually understand how it could suddenly break? Seems like the source of failure is the software rather than any individual pool? But how? Without an update, how did everything break?

I used this and it seems it bumped up 10 hash per gpu
VECTORS BFI_INT FASTLOOP=FALSE WORKSIZE=64 AGGRESSION=7

dont know!
I use phoenix the first time

Thanks, that works better, how can I setup a backup pool with that that.  With open cl  I used -f. 

vectors worksize=128 aggression=11

What setting are you using on phoenix.  Mine are running slow on phoenix. 

Yup with GUIminer i tried 5 differents pools getting the same error
switch to phoenix and its working..

Doing a bit more digging..

The full and actual error is:

api2.bitcoin.cz:8332 04/02/2012 18:36:59, Unexpected error:
Traceback (most recent call last):
  File "HttpTransport.pyo", line 50, in loop
  File "Transport.pyo", line 88, in send
TypeError: 'NoneType' object is unsubscriptable

Hi,

I switch to Phoenix miner and it start to send shares!!
With Open CL miner i have the same problem.

I can confirm that stopping and starting DOES have that effect...

Switched to other mining program on that machine

I'll give it a try on the slowest miner and see what happens

Once you disconnect and reconnect it will happen.

I tried Deepbit, Slush, GPUMax and Goat's pool getting the below message, some pool get connected but I dont see any share accepted
Is something wrong with the bitcoin network ?

2012-02-04 09:55:03: Listener for "slush2": api2.bitcoin.cz:8332 04/02/2012 09:55:03, No more backup pools left. Using primary and starting over.
2012-02-04 09:55:05: Listener for "slush1": api2.bitcoin.cz:8332 04/02/2012 09:55:05, Problems communicating with bitcoin RPC 0 2
2012-02-04 09:55:06: Listener for "slush4": api2.bitcoin.cz:8332 04/02/2012 09:55:06, Problems communicating with bitcoin RPC 0 2
2012-02-04 09:55:07: Listener for "slush3": api2.bitcoin.cz:8332 04/02/2012 09:55:07, Problems communicating with bitcoin RPC 1 2
2012-02-04 09:55:09: Listener for "slush2": api2.bitcoin.cz:8332 04/02/2012 09:55:09, Problems communicating with bitcoin RPC 0 2
2012-02-04 09:55:11: Listener for "slush3": api2.bitcoin.cz:8332 04/02/2012 09:55:11, Unexpected error:
2012-02-04 09:55:12: Listener for "slush4": api2.bitcoin.cz:8332 04/02/2012 09:55:12, Problems communicating with bitcoin RPC 1 2
2012-02-04 09:55:15: Listener for "slush1": api2.bitcoin.cz:8332 04/02/2012 09:55:15, Problems communicating with bitcoin RPC 1 2
2012-02-04 09:55:15: Listener for "slush2": api2.bitcoin.cz:8332 04/02/2012 09:55:15, Problems communicating with bitcoin RPC 1 2
2012-02-04 09:55:16: Listener for "slush3": api2.bitcoin.cz:8332 04/02/2012 09:55:16, Problems communicating with bitcoin RPC 0 2
2012-02-04 09:55:17: Listener for "slush2": api2.bitcoin.cz:8332 04/02/2012 09:55:17, Unexpected error:
2012-02-04 09:55:22: Listener for "slush4": api2.bitcoin.cz:8332 04/02/2012 09:55:22, Problems communicating with bitcoin RPC 2 2
2012-02-04 09:55:22: Listener for "slush3": api2.bitcoin.cz:8332 04/02/2012 09:55:22, Problems communicating with bitcoin RPC 1 2
2012-02-04 09:55:28: Listener for "slush4": api2.bitcoin.cz:8332 04/02/2012 09:55:28, Problems communicating with bitcoin RPC 3 2
2012-02-04 09:55:28: Listener for "slush4": api2.bitcoin.cz:8332 04/02/2012 09:55:28, No more backup pools left. Using primary and starting over.
2012-02-04 09:55:28: Listener for "slush1": api2.bitcoin.cz:8332 04/02/2012 09:55:28, Unexpected error:
2012-02-04 09:55:32: Listener for "slush1": api2.bitcoin.cz:8332 04/02/2012 09:55:32, Unexpected error:
2012-02-04 09:55:34: Listener for "slush4": api2.bitcoin.cz:8332 04/02/2012 09:55:34, Problems communicating with bitcoin RPC 0 2
2012-02-04 09:55:34: Listener for "slush1": api2.bitcoin.cz:8332 04/02/2012 09:55:34, Unexpected error:
2012-02-04 09:55:35: Listener for "slush2": api2.bitcoin.cz:8332 04/02/2012 09:55:35, Unexpected error:
2012-02-04 09:55:38: Listener for "slush3": api2.bitcoin.cz:8332 04/02/2012 09:55:38, Unexpected error:
2012-02-04 09:55:39: Listener for "slush4": api2.bitcoin.cz:8332 04/02/2012 09:55:39, Unexpected error:
2012-02-04 09:55:44: Listener for "slush4": api2.bitcoin.cz:8332 04/02/2012 09:55:44, Problems communicating with bitcoin RPC 0 2
2012-02-04 09:55:44: Listener for "slush2": api2.bitcoin.cz:8332 04/02/2012 09:55:44, Unexpected error:
2012-02-04 09:55:47: Listener for "slush2": api2.bitcoin.cz:8332 04/02/2012 09:55:47, Unexpected error:
2012-02-04 09:55:51: Listener for "slush4": api2.bitcoin.cz:8332 04/02/2012 09:55:51, Unexpected error:
2012-02-04 09:55:52: Listener for "slush3": api2.bitcoin.cz:8332 04/02/2012 09:55:52, Unexpected error:
2012-02-04 09:55:53: Listener for "slush4": api2.bitcoin.cz:8332 04/02/2012 09:55:53, Unexpected error:

2012-02-04 09:56:59: Listener for "hash4": goat1.zapto.org:8337 04/02/2012 09:56:59, Problems communicating with bitcoin RPC 1 2
2012-02-04 09:57:00: Listener for "hash1": goat1.zapto.org:8337 04/02/2012 09:57:00, Problems communicating with bitcoin RPC 2 2
2012-02-04 09:57:00: Listener for "hash2": goat1.zapto.org:8337 04/02/2012 09:57:00, Problems communicating with bitcoin RPC 1 2
2012-02-04 09:57:02: Listener for "hash3": goat1.zapto.org:8337 04/02/2012 09:57:02, Problems communicating with bitcoin RPC 2 2
2012-02-04 09:57:05: Listener for "hash4": goat1.zapto.org:8337 04/02/2012 09:57:05, Problems communicating with bitcoin RPC 2 2
2012-02-04 09:57:06: Listener for "hash2": goat1.zapto.org:8337 04/02/2012 09:57:06, Problems communicating with bitcoin RPC 2 2
2012-02-04 09:57:06: Listener for "hash1": goat1.zapto.org:8337 04/02/2012 09:57:06, Problems communicating with bitcoin RPC 3 2
2012-02-04 09:57:06: Listener for "hash1": goat1.zapto.org:8337 04/02/2012 09:57:06, No more backup pools left. Using primary and starting over.
2012-02-04 09:57:08: Listener for "hash3": goat1.zapto.org:8337 04/02/2012 09:57:08, Problems communicating with bitcoin RPC 3 2
2012-02-04 09:57:08: Listener for "hash3": goat1.zapto.org:8337 04/02/2012 09:57:08, No more backup pools left. Using primary and starting over.
2012-02-04 09:57:11: Listener for "hash4": goat1.zapto.org:8337 04/02/2012 09:57:11, Problems communicating with bitcoin RPC 3 2
2012-02-04 09:57:11: Listener for "hash4": goat1.zapto.org:8337 04/02/2012 09:57:11, No more backup pools left. Using primary and starting over.
2012-02-04 09:57:12: Listener for "hash2": goat1.zapto.org:8337 04/02/2012 09:57:12, Problems communicating with bitcoin RPC 3 2
2012-02-04 09:57:12: Listener for "hash2": goat1.zapto.org:8337 04/02/2012 09:57:12, No more backup pools left. Using primary and starting over.
2012-02-04 09:57:12: Listener for "hash1": goat1.zapto.org:8337 04/02/2012 09:57:12, Problems communicating with bitcoin RPC 0 2
2012-02-04 09:57:14: Listener for "hash3": goat1.zapto.org:8337 04/02/2012 09:57:14, Problems communicating with bitcoin RPC 0 2
2012-02-04 09:57:18: Listener for "hash4": goat1.zapto.org:8337 04/02/2012 09:57:18, Problems communicating with bitcoin RPC 0 2
2012-02-04 09:57:18: Listener for "hash2": goat1.zapto.org:8337 04/02/2012 09:57:18, Problems communicating with bitcoin RPC 0 2
2012-02-04 09:57:18: Listener for "hash1": goat1.zapto.org:8337 04/02/2012 09:57:18, Problems communicating with bitcoin RPC 1 2
2012-02-04 09:57:19: Listener for "hash1": goat1.zapto.org:8337 04/02/2012 09:57:19, Unexpected error:
2012-02-04 09:57:20: Listener for "hash3": goat1.zapto.org:8337 04/02/2012 09:57:20, Problems communicating with bitcoin RPC 1 2
2012-02-04 09:57:24: Listener for "hash4": goat1.zapto.org:8337 04/02/2012 09:57:24, Problems communicating with bitcoin RPC 1 2

2012-02-04 09:57:32: Listener for "1DB": pit.deepbit.net:8332 04/02/2012 09:57:32, Unexpected error:
2012-02-04 09:57:32: Listener for "2DB": pit.deepbit.net:8332 04/02/2012 09:57:32, Unexpected error:
2012-02-04 09:57:32: Listener for "4DB": pit.deepbit.net:8332 04/02/2012 09:57:32, Unexpected error:
2012-02-04 09:57:33: Listener for "3DB": pit.deepbit.net:8332 04/02/2012 09:57:33, Unexpected error:
2012-02-04 09:57:37: Listener for "1DB": pit.deepbit.net:8332 04/02/2012 09:57:37, Problems communicating with bitcoin RPC 0 2
2012-02-04 09:57:39: Listener for "2DB": pit.deepbit.net:8332 04/02/2012 09:57:39, Unexpected error:
2012-02-04 09:57:40: Listener for "3DB": pit.deepbit.net:8332 04/02/2012 09:57:40, Unexpected error:
2012-02-04 09:57:40: Listener for "1DB": pit.deepbit.net:8332 04/02/2012 09:57:40, Unexpected error:
2012-02-04 09:57:41: Listener for "4DB": pit.deepbit.net:8332 04/02/2012 09:57:41, Unexpected error:
2012-02-04 09:57:41: Listener for "1DB": pit.deepbit.net:8332 04/02/2012 09:57:41, Unexpected error:


2012-02-04 09:58:48: Listener for "gpumax2": gpumax.com:8332 04/02/2012 09:58:48, Problems communicating with bitcoin RPC 0 2
2012-02-04 09:58:49: Listener for "gpumax3": gpumax.com:8332 04/02/2012 09:58:49, Problems communicating with bitcoin RPC 3 2
2012-02-04 09:58:49: Listener for "gpumax3": gpumax.com:8332 04/02/2012 09:58:49, No more backup pools left. Using primary and starting over.
2012-02-04 09:58:54: Listener for "gpumax2": gpumax.com:8332 04/02/2012 09:58:54, Problems communicating with bitcoin RPC 1 2
2012-02-04 09:58:55: Listener for "gpumax4": gpumax.com:8332 04/02/2012 09:58:55, Problems communicating with bitcoin RPC 0 2
2012-02-04 09:58:58: Listener for "gpumax1": gpumax.com:8332 04/02/2012 09:58:58, Unexpected error:
2012-02-04 09:58:58: Listener for "gpumax3": gpumax.com:8332 04/02/2012 09:58:58, Problems communicating with bitcoin RPC 0 2
2012-02-04 09:58:58: Listener for "gpumax1": gpumax.com:8332 04/02/2012 09:58:58, Unexpected error:
2012-02-04 09:59:00: Listener for "gpumax2": gpumax.com:8332 04/02/2012 09:59:00, Problems communicating with bitcoin RPC 2 2
2012-02-04 09:59:01: Listener for "gpumax4": gpumax.com:8332 04/02/2012 09:59:01, Problems communicating with bitcoin RPC 1 2
2012-02-04 09:59:04: Listener for "gpumax3": gpumax.com:8332 04/02/2012 09:59:04, Problems communicating with bitcoin RPC 1 2
2012-02-04 09:59:06: Listener for "gpumax2": gpumax.com:8332 04/02/2012 09:59:06, Problems communicating with bitcoin RPC 3 2
2012-02-04 09:59:06: Listener for "gpumax2": gpumax.com:8332 04/02/2012 09:59:06, No more backup pools left. Using primary and starting over.
2012-02-04 09:59:06: Listener for "gpumax1": gpumax.com:8332 04/02/2012 09:59:06, Unexpected error:
2012-02-04 09:59:10: Listener for "gpumax3": gpumax.com:8332 04/02/2012 09:59:10, Problems communicating with bitcoin RPC 2 2
2012-02-04 09:59:11: Listener for "gpumax4": gpumax.com:8332 04/02/2012 09:59:11, Problems communicating with bitcoin RPC 2 2
2012-02-04 09:59:12: Listener for "gpumax2": gpumax.com:8332 04/02/2012 09:59:12, Problems communicating with bitcoin RPC 0 2
2012-02-04 09:59:16: Listener for "gpumax3": gpumax.com:8332 04/02/2012 09:59:16, Problems communicating with bitcoin RPC 3 2
2012-02-04 09:59:16: Listener for "gpumax3": gpumax.com:8332 04/02/2012 09:59:16, No more backup pools left. Using primary and starting over.
2012-02-04 09:59:17: Listener for "gpumax4": gpumax.com:8332 04/02/2012 09:59:17, Problems communicating with bitcoin RPC 3 2
2012-02-04 09:59:17: Listener for "gpumax4": gpumax.com:8332 04/02/2012 09:59:17, No more backup pools left. Using primary and starting over.
2012-02-04 09:59:18: Listener for "gpumax2": gpumax.com:8332 04/02/2012 09:59:18, Problems communicating with bitcoin RPC 1 2
2012-02-04 09:59:20: Listener for "gpumax1": gpumax.com:8332 04/02/2012 09:59:20, Unexpected error:
2012-02-04 09:59:22: Listener for "gpumax3": gpumax.com:8332 04/02/2012 09:59:22, Problems communicating with bitcoin RPC 0 2
2012-02-04 09:59:23: Listener for "gpumax4": gpumax.com:8332 04/02/2012 09:59:23, Problems communicating with bitcoin RPC 0 2

Mine all seem ok... am on slush's pool

same here tried a few different pools all getting unexpect error

Is anyone having a problem with their GUI Miner.  I keep on getting unexpected error on all my rigs.