PSU is fine so its just unlucky. Although, are you using two PCI-E cables from DIFFERENT strands of cables?

I received the replacement mini blade this morning and have replaced the faulty blade in my cube and it's all up and running now with no more x's but for some strange reason I cannot seem to get it functioning properly in High Clock mode!

Every time I try and switch to overclocked mode the cube starts loosing it's hashrate and efficiency till it functions no more and I'm left with all x's at which point I have to restart the machine to get it hashing again only in low clock mode, can anyone suggest what might be going wrong here?

That seems to have done the trick however the x's have moved

ASIC_01-16: O O O O O O O O O O O O O O O O
ASIC_17-32: O O O O O O O O O O O O O O O O
ASIC_33-48: x x x x x x x x O O O O O O O O
ASIC_49-64: O O O O O O O O O O O O O O O O
ASIC_65-80: O O O O O O O O O O O O O O O O
ASIC_81-96: O O O O O O O O O O O O O O O O

So I re-arranged the mini blades once again and the x's moved again, so I must have a faulty mini blade now which is rather annoying!

ASIC_01-16: x x x x x x x x O O O O O O O O
ASIC_17-32: O O O O O O O O O O O O O O O O
ASIC_33-48: O O O O O O O O O O O O O O O O
ASIC_49-64: O O O O O O O O O O O O O O O O
ASIC_65-80: O O O O O O O O O O O O O O O O
ASIC_81-96: O O O O O O O O O O O O O O O O

Nope router is deffo not 192.168.1.254

I'm guna try a factory reset and will let you know if that works!

Your router isn't 192.168.1.254 is it?  That was an issue I had when initially setting mine up.

Other than that, you might have to do a factory reset... strange though that you could connect with the old cube but not with the new boards. 

Initially when I received the cube, without any fiddling I had 8 x's, see my previous posts, then after the first time I opened it and tightened the screws I went down to 1 x, now I've opened it a further few times, not over tightened the screws but just made sure they weren't loose and I re-arranged the blades and am now back to 8 x's, plus the x's are always in the same row, so the problem must be the board, I have spoken to the seller and he is awaiting word back from the supplier, hopefully gets sorted soon!

Thanks for the advice, I got allot of support from this thread.


Deffo wasn't a power issue, 500W is more than capable of running one cube efficiently but thanks for the reply!


On low I have my cube running at 95% efficiency but only hashing at around 29000MHS



From the advice I received from the other thread, I opened the cube and found it not to be aligned correctly in it's structure, once I managed to get the board and blades out of it, I checked all the screws and tightened them as a few of them were loose, after I put the cube back together I only had 1 x but still wasn't able to run the cube efficiently in high clock mode, efficiency went down to 10% or less and it was only hashing at 01085MHS or thereabouts.

So once again I reopened the cube and checked the screws again, put it back together and was back to square 1 with 8 x's, I tried a final time to reopened and this time rearrange the blades to determine whether there was a problem with the actual board or the blades, turn's out the problem is with the board itself, as even after rearranging the blades the same 8 x's show up in the same row!

I have been on to the seller and he is awaiting a response from the supplier, so I'm hoping this will be sorted soon.

Thank you all for your help and advice.

That's what I've been doing all along... Sorry if that was unclear.  A new VM for each cube just sounds like it would eat up waaay too much RAM.
Also, it's -gp or --getwork-port, not --gp.



Here's an example.

proxy1.bat: proxy2.bat: Then in your cube config page, set the ports to 8332,8331


The various difficulty settings are simply a way to control the bandwidth used by limiting the number of shares submitted.  Lower difficulty shares means a more accurate hashrate reported by the pool, vs higher difficulty shares means less bandwidth but higher variance.

Evening All,

I'm after some advise on how I can get my cube to successfully mine on two separate pools, as in the primary/backup function, so if one looses connectivity or times out for any reason, it switches to the other pool.

I am currently mining on Slush's pool and another pool using a windows 7 64bit laptop as a proxy machine and am using mining_proxy.exe in order to do so, if I want to mine on the other pool I just open up the command prompt, navigate to the mining proxy directory and execute the following command
mining_proxy.exe -o (host) -p (port)

My cube is setup with the standard settings with the ports being 8332, 8332, pool address being the IP address of my proxy machine and the username and password of my pool worker credentials.

I have tried to use cgminer and bfg miner on numerous occasions but have been unsuccessful in making them work for me.

Yesterday I downloaded the latest cgminer 3.90 but after entering my pool address:port and leaving the username and password blank and hitting enter, the program would encounter a problem and shutdown, I tried again but this time I populated the username and password fields but I encountered the same problem.

bfg miner seems to get me to a page where I can start tinkering with some settings but always says that no devices were found, once I've managed to get it connected to a pool I think and it said something along the lines of "pool is hiding blocks", or something along those lines.

So now, as proxy miner seems to be the only one working for me, is their any way for me to set it up to achieve my purpose?

Also what does diff 64, 128 and 256 mean? The other pool that I am on offers me various different ports to choose from with the options of diff 64, 128 or 256.

Thanks in advance for your time and help.

working overclocking can not be guaranteed.
Thats why there is a guaranteed speed.

So the 8x stay always in the same position if you change the plug-in position from the miniblades?

ASIC_01-16: O O O O O O O O O O O O O O O O
ASIC_17-32: O O O O O O O O O O O O O O O O
ASIC_33-48: O O O O O O O O O O O O O O O O
ASIC_49-64: O O O O O O O O O O O O O O O O
ASIC_65-80: O O O O O O O O O O O O O O O O
ASIC_81-96: O O O O O O O O O O O O O O O O
if you have x's then you have a problem

see
https://bitcointalk.org/index.php?topic=352658.0

more than likely mot enough power id be using atleast a 700w psu for these

Four of my five cubes do the same thing. They run perfect on low so I don't really care but I know it is not a power issue as I'm using HX1050's.

I've been told that sometimes the heatsink screws on the mini-blades come loose during shipping, and that checking them all for tightness is recommended before hashing.  If you haven't already, you might check that.

I don't know how tight "tight as can be" is, but I'm wondering if you may have damaged the board/chips by overtightening the screws?  You went from 0 bad chips to 1 bad chip to 8 bad chips.

I'd try rearraging the modules, but I don't think it would make much difference.

Contact whoever you purchased the Cube from and let them know you have a bad board.  You might get a replacement blade for free like this guy:

Right I unscrewed the device, pulled all the cards out, screwed a few of the loose heatsink screws in tighter and put the unit back together.

Now I can get the cube to hash at 31693MHS with an efficiency of 96.58% in low clock speed, if I switch the clock to high both the hash rate and efficiency start dropping, I also noticed one X today which wasn't there yesterday after I put the device back together:

ASIC_01-16: O O O O O O O O O O O O O O O O
ASIC_17-32: O O O O O O O O O O O O O O O O
ASIC_33-48: O O O O O O O O O O O O O O O O
ASIC_49-64: O O O O O O x O O O O O O O O O
ASIC_65-80: O O O O O O O O O O O O O O O O
ASIC_81-96: O O O O O O O O O O O O O O O O

Can anyone shed any light on why my hash rate and efficiency might be dropping when I try to run the device in an overclocked state?

Dude, try what I recommended, I know it might sound silly but I have a Super Hub 2 aswell and it took me a while to figure out how to even see the cubes on my network, you basically ain't seeing them as they ain't on the same subnet!

Well I cant evan see the cubes on the network now? Virgin Media gave me a free fucking upgrade and broke both my cubes during the process... well fuck.

I tried just buying another router to plug in and still cant see the miners in the config.

Does anyone know how to factory reset the cubes? I pressed the button but it doesn't indicated its been reset.

I'm guessing you would need to do something similar to what I had to do in configuring the router manually as 192.168.1.1

From a quick Google search it appears the IP for the Virgin Hub is 192.168.0.x or 192.168.100.x which will need to be changed to 192.168.1.x

Did you pull the cards out and make sure all the heatsinks were tight? In Blades, low efficiency is usually due to chips overheating from poor heatsink contact, and these Cubes are notorious for loose screws upon delivery.