Bitcoin Forum
December 02, 2024, 11:34:32 AM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Perpetual Connecting  (Read 1877 times)
Kohta (OP)
Member
**
Offline Offline

Activity: 63
Merit: 10



View Profile
February 10, 2012, 05:28:32 PM
 #1

System Information
Intel Core i7-2600K 4.5ghz @ 1.35v
GIGABYTE GA P67A UD5
G.SKILL Ripjaws X Series 16GB DDR3 2133
Sapphire Radeon HD 6870 @ 950mhz
[Crossfire]
Sapphire Radeon HD 6870 @ 950mhz
Sapphire Radeon HD 6870 @ 950mhz
Corsair AX 1200w Professional Series
Noctua NH-D14
Corsair Force 120GB SSD
Antec 1200v2
Windows 7 Ultimate x64
CCC 12.1 CAP 3
AMD APP SDK 2.3(2.1)



GUIMiner 2011-8-24
Using Phoenix flags: -k phatk2 VECTORS BFI_INT AGGRESSION=11 worksize=128 FASTLOOP=false
~300 MH/s per GPU
CPU affinity:
Core 1 - GPU 1
Core 3 - GPU 2
Core 5 - GPU 3

So the problem i'm having is the GPU load will just drop and the miner will perpetually read "Connecting..." this is happening 4-5 times a day on any of the 3 GPU's or sometimes more than one, at first i thought it was an Overclock issue, so i set them all back to  stock but it persisted, so i pushed to voltage a bit higher (1.180v) @ 950mhz which is more voltage than it really needs, i tested and overclocked them all individually for several hours. So i'm ruling out instability.

I don't have any tools to check the PSU but i have my doubts it's that, i had 2xGTX 580's peaked out for several days on it, and 2x5970's awhile back, this little bit is nothing it can't handle.

Iv'e tried reinstalling the drivers, wiping the OS, pretty much everything time consuming. I'm at a loss, not sure where to go from here, i have a test bench with a 850W Corsair PSU with 3 of the same cards, same Miner/flags (with no crossfire bridge) and it isn't giving me this problem at all.

The only thing i didn't try was taking the crossfire bridge off, because i occasionally use it for gaming, but i don't game to much anymore. What does it sound like to you?
malevolent
can into space
Legendary
*
Offline Offline

Activity: 3472
Merit: 1725



View Profile
February 10, 2012, 07:01:52 PM
 #2

Try different mining software.

Signature space available for rent.
bangra
Newbie
*
Offline Offline

Activity: 43
Merit: 0



View Profile
February 11, 2012, 03:31:33 AM
 #3

Change to Phoenix 2.0 and drop guiminer and see how it goes, had similar issues with pheonix 1.x when the cards would crash due to the overclock they ran, also what temp do the cards run at and do you have somthing like afterburner controlling fan speed?
Kohta (OP)
Member
**
Offline Offline

Activity: 63
Merit: 10



View Profile
February 12, 2012, 03:48:07 PM
Last edit: February 12, 2012, 04:33:01 PM by Kohta
 #4

Change to Phoenix 2.0 and drop guiminer and see how it goes, had similar issues with pheonix 1.x when the cards would crash due to the overclock they ran, also what temp do the cards run at and do you have somthing like afterburner controlling fan speed?

They run anywhere from 72~83C @75% inside the case, i can't keep the side panel off or anything right now i have a baby that thinks it's funny to try to stick her hand inside of it, the test bench is around the same temps slightly cooler but i have a box fan blowing on it.

EDIT: I spent almost an hour trying to edit the Phoenix 2 conf. in windows and it just spouts error this error that, this is why i stick to GUIMiner, because there aren't any guides out there for people who don't know what they're doing when it comes to programming, it was mainly not allowing me to connect to deepbit- and deepbit's pool doesn't have a formatted log-in example for me to use for phoenix, plus it's not reading the GPU Threads.
bangra
Newbie
*
Offline Offline

Activity: 43
Merit: 0



View Profile
February 15, 2012, 11:49:23 AM
 #5

Try this in your pheonix.cfg
Code:
[general]
verbose = True
autodetect = +cl -cpu # The rightmost parameter takes precedence. This enables all OpenCL devices, except those that are CPUs.
backend = http://<yourdeepbitworkername>:<yourdeepbitworkerpassword>@pit.deepbit.net:8332 # URL format is exactly as it was in Phoenix 1

[web]
password = <your_password> # Set an RPC password to keep people from messing with your miners.

# If you want to configure miners yourself, edit and uncomment this section:
[cl:0:0] # Or whatever ID you want to configure.
autoconfigure = False # Do you still want autoconfiguration?
#disabled = False # Do you want to disable the miner?
bfi_int = True    # Any other kernel options...
vectors = True # can go into this section.
worksize = 256
aggression = 10
kernel = phatk2
[cl:0:1] # Or whatever ID you want to configure.
autoconfigure = False # Do you still want autoconfiguration?
#disabled = False # Do you want to disable the miner?
bfi_int = True    # Any other kernel options...
vectors = True # can go into this section.
worksize = 256
aggression = 10
kernel = phatk2
[cl:0:2] # Or whatever ID you want to configure.
autoconfigure = False # Do you still want autoconfiguration?
#disabled = False # Do you want to disable the miner?
bfi_int = True    # Any other kernel options...
vectors = True # can go into this section.
worksize = 256
aggression = 10
kernel = phatk2
Change the relevant bits for your worker on deepbit, see what it comes back with
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!