Topic: is my 5830 going to die? (Read 1002 times)
I got the same problem in 2 different PCs, with 2 different GPUs, in 2 different pools. Anyway the temp is about 70°C, but actually I think the problem is due to the miner I use: poclbm; I don't have the same problem when I use cgminer.
- check your temperatures (use gpu-z, msi afterbuner), and make sure it's below 90C
- run benchmarking programs to make sure your card is stable
Hello,
my ati 5830 very often doesn't mine at its full potential. I mine in two pools: slush and deepbit, actually I can't connect to the first one and I get this:
2013-04-17 15:22:47: Running command: poclbm.exe user.miner:[email protected]:8332 --device=0 --platform=0 --verbose -r1 -v -f10 -w128
2013-04-17 15:22:47: Listener for "slush" started
2013-04-17 15:22:48: Listener for "slush": api2.bitcoin.cz:8332 17/04/2013 15:22:48, checking for stratum...
2013-04-17 15:22:48: Listener for "slush": api2.bitcoin.cz:8332 17/04/2013 15:22:48, started OpenCL miner on platform 0, device 0 (Cypress)
2013-04-17 15:22:51: Listener for "slush": api2.bitcoin.cz:8332 17/04/2013 15:22:51, diverted to stratum on stratum.bitcoin.cz:3333
2013-04-17 15:22:56: Listener for "slush": api2.bitcoin.cz:8332 17/04/2013 15:22:56, timed out
2013-04-17 15:22:57: Listener for "slush": api2.bitcoin.cz:8332 17/04/2013 15:22:57, IO errors - 1, tolerance 2
2013-04-17 15:23:02: Listener for "slush": api2.bitcoin.cz:8332 17/04/2013 15:23:02, timed out
2013-04-17 15:23:03: Listener for "slush": api2.bitcoin.cz:8332 17/04/2013 15:23:03, IO errors - 2, tolerance 2
2013-04-17 15:23:08: Listener for "slush": api2.bitcoin.cz:8332 17/04/2013 15:23:08, timed out
2013-04-17 15:23:09: Listener for "slush": api2.bitcoin.cz:8332 17/04/2013 15:23:09, IO errors - 3, tolerance 2
2013-04-17 15:23:09: Listener for "slush": api2.bitcoin.cz:8332 17/04/2013 15:23:09, No more backup servers left. Using primary and starting over.
2013-04-17 15:23:14: Listener for "slush": api2.bitcoin.cz:8332 17/04/2013 15:23:14, timed out
2013-04-17 15:23:15: Listener for "slush": api2.bitcoin.cz:8332 17/04/2013 15:23:15, IO errors - 1, tolerance 2
2013-04-17 15:23:20: Listener for "slush": api2.bitcoin.cz:8332 17/04/2013 15:23:20, timed out
while I do connect to deepbit and for a while I mine at max (let's say 290Mhash/s) but suddenly I got 400Khash/s (kilo hash, wtf???).
2013-04-17 15:26:38: Running command: poclbm.exe user_miner:[email protected]:8332 --device=0 --platform=0 --verbose -r1 -v -f10 -w128
2013-04-17 15:26:38: Listener for "deepbit" started
2013-04-17 15:26:40: Listener for "deepbit": pit.deepbit.net:8332 17/04/2013 15:26:40, checking for stratum...
2013-04-17 15:26:40: Listener for "deepbit": pit.deepbit.net:8332 17/04/2013 15:26:40, started OpenCL miner on platform 0, device 0 (Cypress)
2013-04-17 15:26:44: Listener for "deepbit": pit.deepbit.net:8332 17/04/2013 15:26:44, using JSON-RPC (no stratum header)
2013-04-17 15:27:00: Listener for "deepbit": pit.deepbit.net:8332 17/04/2013 15:27:00, warning: job finished, 0:0:Cypress is idle
2013-04-17 15:27:18: Listener for "deepbit": pit.deepbit.net:8332 17/04/2013 15:27:18, warning: job finished, 0:0:Cypress is idle
2013-04-17 15:27:35: Listener for "deepbit": pit.deepbit.net:8332 17/04/2013 15:27:35, warning: job finished, 0:0:Cypress is idle
So, I read somewhere that probably the gpu is going to die, does anyone know/experience anything similar to me?
Thanks
my ati 5830 very often doesn't mine at its full potential. I mine in two pools: slush and deepbit, actually I can't connect to the first one and I get this:
2013-04-17 15:22:47: Running command: poclbm.exe user.miner:[email protected]:8332 --device=0 --platform=0 --verbose -r1 -v -f10 -w128
2013-04-17 15:22:47: Listener for "slush" started
2013-04-17 15:22:48: Listener for "slush": api2.bitcoin.cz:8332 17/04/2013 15:22:48, checking for stratum...
2013-04-17 15:22:48: Listener for "slush": api2.bitcoin.cz:8332 17/04/2013 15:22:48, started OpenCL miner on platform 0, device 0 (Cypress)
2013-04-17 15:22:51: Listener for "slush": api2.bitcoin.cz:8332 17/04/2013 15:22:51, diverted to stratum on stratum.bitcoin.cz:3333
2013-04-17 15:22:56: Listener for "slush": api2.bitcoin.cz:8332 17/04/2013 15:22:56, timed out
2013-04-17 15:22:57: Listener for "slush": api2.bitcoin.cz:8332 17/04/2013 15:22:57, IO errors - 1, tolerance 2
2013-04-17 15:23:02: Listener for "slush": api2.bitcoin.cz:8332 17/04/2013 15:23:02, timed out
2013-04-17 15:23:03: Listener for "slush": api2.bitcoin.cz:8332 17/04/2013 15:23:03, IO errors - 2, tolerance 2
2013-04-17 15:23:08: Listener for "slush": api2.bitcoin.cz:8332 17/04/2013 15:23:08, timed out
2013-04-17 15:23:09: Listener for "slush": api2.bitcoin.cz:8332 17/04/2013 15:23:09, IO errors - 3, tolerance 2
2013-04-17 15:23:09: Listener for "slush": api2.bitcoin.cz:8332 17/04/2013 15:23:09, No more backup servers left. Using primary and starting over.
2013-04-17 15:23:14: Listener for "slush": api2.bitcoin.cz:8332 17/04/2013 15:23:14, timed out
2013-04-17 15:23:15: Listener for "slush": api2.bitcoin.cz:8332 17/04/2013 15:23:15, IO errors - 1, tolerance 2
2013-04-17 15:23:20: Listener for "slush": api2.bitcoin.cz:8332 17/04/2013 15:23:20, timed out
while I do connect to deepbit and for a while I mine at max (let's say 290Mhash/s) but suddenly I got 400Khash/s (kilo hash, wtf???).
2013-04-17 15:26:38: Running command: poclbm.exe user_miner:[email protected]:8332 --device=0 --platform=0 --verbose -r1 -v -f10 -w128
2013-04-17 15:26:38: Listener for "deepbit" started
2013-04-17 15:26:40: Listener for "deepbit": pit.deepbit.net:8332 17/04/2013 15:26:40, checking for stratum...
2013-04-17 15:26:40: Listener for "deepbit": pit.deepbit.net:8332 17/04/2013 15:26:40, started OpenCL miner on platform 0, device 0 (Cypress)
2013-04-17 15:26:44: Listener for "deepbit": pit.deepbit.net:8332 17/04/2013 15:26:44, using JSON-RPC (no stratum header)
2013-04-17 15:27:00: Listener for "deepbit": pit.deepbit.net:8332 17/04/2013 15:27:00, warning: job finished, 0:0:Cypress is idle
2013-04-17 15:27:18: Listener for "deepbit": pit.deepbit.net:8332 17/04/2013 15:27:18, warning: job finished, 0:0:Cypress is idle
2013-04-17 15:27:35: Listener for "deepbit": pit.deepbit.net:8332 17/04/2013 15:27:35, warning: job finished, 0:0:Cypress is idle
So, I read somewhere that probably the gpu is going to die, does anyone know/experience anything similar to me?
Thanks
Jump to: