Search content
Sort by
Showing 20 of 276 results by exahash
Re: SRBMiner Cryptonight AMD GPU Miner V1.7.0 - native algo switching
Ayone have problems with benchmarking ? (120 secont timeout),,, ??
...
Startup monitor detected that GPU's could not be initialised in 120 seconds!
Doing a forced restart...
Restarting miner...Uno momento
...
Startup monitor detected that GPU's could not be initialised in 120 seconds!
Doing a forced restart...
Restarting miner...Uno momento
Easy workaround, run:
SRBMiner-CN.exe --benchmarkalgos --maxstartuptime 9999
I just tested it and it looks like maxstartuptime caps out at 600. So you have to cut algos.txt to 10 algos or less.
Or just wait for the fix.
Re: SRBMiner Cryptonight AMD GPU Miner V1.7.0 - native algo switching
Ayone have problems with benchmarking ? (120 secont timeout),,, ??
[2018-11-13 20:52:40] Releasing GPU resources...
[2018-11-13 20:52:40] This can take a while, please be patient
[2018-11-13 20:52:41] Device BUS_ID[4] thread0 resources released
[2018-11-13 20:52:41] Device BUS_ID[4] thread1 resources released
[2018-11-13 20:52:41] Device BUS_ID[5] thread2 resources released
[2018-11-13 20:52:41] Device BUS_ID[5] thread3 resources released
[2018-11-13 20:52:41] Device BUS_ID[3] thread4 resources released
[2018-11-13 20:52:41] Device BUS_ID[3] thread5 resources released
[2018-11-13 20:52:41] Loading heavy kernel for DEVICE BUS_ID[4] ...
[2018-11-13 20:52:41] Loading heavy kernel for DEVICE BUS_ID[4] ...
[2018-11-13 20:52:42] Loading heavy kernel for DEVICE BUS_ID[5] ...
[2018-11-13 20:52:42] Loading heavy kernel for DEVICE BUS_ID[5] ...
[2018-11-13 20:52:42] Loading heavy kernel for DEVICE BUS_ID[3] ...
[2018-11-13 20:52:42] Loading heavy kernel for DEVICE BUS_ID[3] ...
[2018-11-13 20:52:42] ADL initialised successfully!
[2018-11-13 20:52:42] Benchmarking algo 'heavy', please wait
[2018-11-13 20:52:55] Speed: 3044.0 H/S
[2018-11-13 20:53:08] Speed: 3136.0 H/S
[2018-11-13 20:53:21] Speed: 3083.0 H/S
[2018-11-13 20:53:34] Speed: 3132.0 H/S
Startup monitor detected that GPU's could not be initialised in 120 seconds!
Doing a forced restart...
Restarting miner...Uno momento
[2018-11-13 20:52:40] Releasing GPU resources...
[2018-11-13 20:52:40] This can take a while, please be patient
[2018-11-13 20:52:41] Device BUS_ID[4] thread0 resources released
[2018-11-13 20:52:41] Device BUS_ID[4] thread1 resources released
[2018-11-13 20:52:41] Device BUS_ID[5] thread2 resources released
[2018-11-13 20:52:41] Device BUS_ID[5] thread3 resources released
[2018-11-13 20:52:41] Device BUS_ID[3] thread4 resources released
[2018-11-13 20:52:41] Device BUS_ID[3] thread5 resources released
[2018-11-13 20:52:41] Loading heavy kernel for DEVICE BUS_ID[4] ...
[2018-11-13 20:52:41] Loading heavy kernel for DEVICE BUS_ID[4] ...
[2018-11-13 20:52:42] Loading heavy kernel for DEVICE BUS_ID[5] ...
[2018-11-13 20:52:42] Loading heavy kernel for DEVICE BUS_ID[5] ...
[2018-11-13 20:52:42] Loading heavy kernel for DEVICE BUS_ID[3] ...
[2018-11-13 20:52:42] Loading heavy kernel for DEVICE BUS_ID[3] ...
[2018-11-13 20:52:42] ADL initialised successfully!
[2018-11-13 20:52:42] Benchmarking algo 'heavy', please wait
[2018-11-13 20:52:55] Speed: 3044.0 H/S
[2018-11-13 20:53:08] Speed: 3136.0 H/S
[2018-11-13 20:53:21] Speed: 3083.0 H/S
[2018-11-13 20:53:34] Speed: 3132.0 H/S
Startup monitor detected that GPU's could not be initialised in 120 seconds!
Doing a forced restart...
Restarting miner...Uno momento
Easy workaround, run:
SRBMiner-CN.exe --benchmarkalgos --maxstartuptime 9999
Re: [ANN][MULTI][VARDIFF] Pool|TradeMyBit - 0.5% Prop/Profit Swap/Auto-Exch
We 'normalize' the price per mhash to do exactly what you're asking, determine which algo is paying the most currently.. but I'll see about doing it in a different way since it seems to be confusing.
I was confused too and it took me a few minutes to figure out what you're doing. I think an FAQ entry on how you calculate it and what you mean by "BTC/day/scryptMhash" would be very helpful.
Till then, for everyone else who's confused:
merc82 said he's using an X11/scrypt factor of 2.9, so if I have a rig doing 1 Mh/s mining scrypt, he expects that same rig to do about 2.9 Mh/s mining X11.
Given an scrypt hashrate, to get an X11 hashrate, I'd multiply by 2.9. Whereas given an X11 hash rate, to get an scrypt hash rate, I'd divide it by 2.9. Looking at the "BTC/day/scryptMhash" value tells you if mining X11 using that same rig could be more profitable than mining scrypt.
If you're trying to figure out projected revenue using an X11 hash rate in Mh/s (from sphminer or cpuminer, doesn't matter), first divide your hash rate by 2.9, then multiply by the "BTC/day/scryptMhash" value.
Re: What's the most stupid comment you've heard about bitcoin?
2011: Bitcoin is dead (after June MtGox hack and November price bottom)
2012: Bitcoin is dead (after pirateat40 default and glbse closure)
2013: Bitcoin is dead (after April and December price drops)
2014: Bitcoin is dead (after MtGox bankruptcy, and probably many more times)
2012: Bitcoin is dead (after pirateat40 default and glbse closure)
2013: Bitcoin is dead (after April and December price drops)
2014: Bitcoin is dead (after MtGox bankruptcy, and probably many more times)
This is pretty insane...
This is insane for a different reason.
Can anyone think of why such an article is a bad idea in light of current events?
Anyone?
Anyone?
Bueller?
How about this... isolated data center in tiny country responsible for 15% of world's BTC identified to world's SIGINT organizations (China, NSA, GCHC, etc). Doesn't have to be that "the NSA is against bitcoin" - it only has to be a faction of one (possibly corrupt) organization with the ability to intercept and mangle communications and this guys in a world of hurt.
Mining installations greater than 1% of the network need to be secret.
So in a few months when we get another roller coaster, we'll all be singing https://www.youtube.com/watch?feature=player_detailpage&v=bOR38552MJA#t=21
Re: Alex jones calls Bitcoin a "Bubble" & "Globalist NWO" Creation
I've been wondering for a while whether or not we should come up with a formal response to the inevitable fire & brimstone evangelist argument that Bitcoin is the global currency of end times. Maybe it's not too late.
Of course, if we even argue against it, it could just fan the flames and lead more people taking the position that Bitcoin is some type of antichrist currency.
Of course, if we even argue against it, it could just fan the flames and lead more people taking the position that Bitcoin is some type of antichrist currency.
Refer them to Matthew 22:21 - http://en.wikipedia.org/wiki/Render_unto_Caesar and tell them Ceasar won't take USD.
12, I turn 13 in December.
Start young, be rich when old.
Start young, be rich when old.
Now I'm jealous.
Hello, today I received this email from BTC-TC
What am I able to do here?
Thank you in advance for any kind of help.
Quote
BTC-TC Emergency Notification
Hello,
BTC-TC has shutdown. We do not have a withdrawal address on file for your
account. Please reply to this email with your withdrawal address ASAP.
Account: hkckoo
Account balances will be zeroed out when the site servers are shutdown.
Thank you for using BTC-TC
Don't want to receive these emails? Most emails can be disabled in the
Account Settings, available here: https://btct.co/account?tab=tab2
The problem is.. it was sent from noreply email and I cant get in touch with the people behind the site? I appreciate this email I received and that they want to give the balance back, last time i sent to my account 13 BTC if I remeber correctly, so it is quite a lot of money right now. Hello,
BTC-TC has shutdown. We do not have a withdrawal address on file for your
account. Please reply to this email with your withdrawal address ASAP.
Account: hkckoo
Account balances will be zeroed out when the site servers are shutdown.
Thank you for using BTC-TC
Don't want to receive these emails? Most emails can be disabled in the
Account Settings, available here: https://btct.co/account?tab=tab2
What am I able to do here?
Thank you in advance for any kind of help.
Same thing happened to me. I don't keep up with this stuff and had no idea btc-tc was closing shop.
I emailed ceo@btct.co instead, then came to find this thread. We'll see what happens.
Has anyone had luck getting their avalon to mine at a getwork diff1 (non-stratum) pool?
My avalon gets the work and submits shares, but they all get rejected. I've been playing with it and searching almost all day. I can't be the only one who's tried this.
My avalon gets the work and submits shares, but they all get rejected. I've been playing with it and searching almost all day. I can't be the only one who's tried this.
Anyone here good at troubleshooting or reviving a possibly dead hashing card? I had the "red light" issue with a batch 3 unit and while I disconnected the power supply to replace it I found out my replacement power supply was missing a second EPS 12v connect (ie CPU connector) so I plugged in a power supply from a batch 2 unit. When I tried to start it up the typical giving up the ghost smoke came out of the the third card - not a lot of smoke but it was noticeable. The unit of course refused to power on. With the third module disconnected the unit powers up just fine. It even power up just fine with it's original PSU.
Could I have killed it trying to swap the power supply or was it most likely already dead (due to the red light warning) before I tried to mess with it?
If anyone had this happen to their batch 3 unit I'm wondering if you can tell me what the exact cause was. Was it blown capacitor(s)? I looked at the exposed side of the board and no obvious burn marks or dead caps are visible. The smoke appeared to have come from the top of the backplane near where the power connector is, but from underneath.
Could I have killed it trying to swap the power supply or was it most likely already dead (due to the red light warning) before I tried to mess with it?
If anyone had this happen to their batch 3 unit I'm wondering if you can tell me what the exact cause was. Was it blown capacitor(s)? I looked at the exposed side of the board and no obvious burn marks or dead caps are visible. The smoke appeared to have come from the top of the backplane near where the power connector is, but from underneath.
I doubt you killed it swapping the psu, more likely it was already dead and finally burnt when you turned it back on. I found my damaged b3 units off with only the red lights on, and when I turned each back on got the smoke and some sparks. A few pages back I posted pics and people told me what the parts were. I don't know if mine were burnt at first because I didn't open them up, just toggled the psu power switch. I was able to find the burnt components and simply segregated the affected workers by bending the pins so they wouldn't plug into the bus (the top board that the cables plug into).
If you can't see anything burnt on the face of the module, try unplugging the module from the bus and looking for signs of damage on the underside of the bus or around the edge of the module where it meets the heatsink. The smoke had to come from somewhere and usually leaves residue that's fairly easy to spot. If the bus itself is damaged you'll probably have to get it repaired, not just bend some pins.
Today I experienced smoke as well.
After inspection I noticed 2 burnouts on 1 module.
Other 3 modules are already working again...
SO - with this problematic one - any ideas how to make it work again?
Is there any way to make this module work without the burnout part/area?
How to fix this? Is it enough to get burnout parts replaced? (are they anything special or should I get them anywhere?)... Or are the nearby chips damaged too? Any recepie from anyone who went thru this before? Experience and ideas welcome!
After inspection I noticed 2 burnouts on 1 module.
Other 3 modules are already working again...
SO - with this problematic one - any ideas how to make it work again?
Is there any way to make this module work without the burnout part/area?
How to fix this? Is it enough to get burnout parts replaced? (are they anything special or should I get them anywhere?)... Or are the nearby chips damaged too? Any recepie from anyone who went thru this before? Experience and ideas welcome!
Looks similar to the burnt components I ran into a couple weeks ago (back a few pages in this thread). I decided to bend the pins where the bus plugs into the module, since I don't have soldering skills and finding the components and someone to do the work would be more time and effort than one worker is worth. The rest of the workers on my module seem to work just fine.
Now I'm wondering if unplugging the affected miner from the bus would work. Might be tough to do, but it would let me use the other seven miners on that module without having to try and repair the broken one.
I've done this. It works.Just remove the screws and peel/pull it off (the thermal paste will stick a bit). Depending on which one it is, you may have to remove the backplane board to access all the screws.
Bogart (and anyone else who has tried) how did you do it and did it let you use the remaining 7 of the workers or only 6 on the module?
In my b3, I found that the module is one big pcb, and the bus pcb is stiff enough that even if I try to unplug only the damaged worker, a bunch more get unplugged too. Since the workers are all together on the module board, there is no peeling them off the heatsink one at a time.
One of my damaged workers occurs at the end of a module, so I bent the pins on the bus for that worker and managed to get the rest plugged in. cgminer seems to prefer if I tell it there are 30 workers instead of 31, so I'm concluding that workers really come in pairs (4 sets of 2 on a module). If that's not the case, then I'd guess that the adjacent worker is not plugged into the bus well enough.
My next problem is that my other damaged worker (the first one I posted) is closer to the middle of a module, so I don't think this will work - I'll end up with at least half the workers on the module unplugged from the bus.
So... does anyone have a solution that doesn't involve soldering? I thought about disconnecting the power wires from the connector for that module, but I don't know which ones to pull.
Is there a tool that is able to brute force the private key, given a full Bitcoin address? I know it's nearly impossible, but want to try just for fun.
Yes, there is. But it was developed by the NSA and is not available to the public.
If you'd like to try to develop your own such tool, go ahead, just be aware that jack-booted thugs will show up at your door and "disappear you" if you are successful.
Thanks for the info. What PSU do you use and how much do you spend on hydro?
My Avalon came preset since I bought it used. It uses --avalon-fan 65 --avalon-cutoff 60. At 350mhz temp 2 & 3 stay at 50.
Is it a b3? If so, do you have very cool ambient air temp, a/c, or some special cooling? Temp2 is the one to watch, and if its really *at* 50 (not "in the 50's") I'd say you should check your pool to see if the reported hashrate is close to what your avalon reports. It might be idling to keep the temp that low.
If it's a b1 or b2, never mind, 50c is on the higher side. If you don't mind the noise, you could turn the fans up with --avalon-fan 100.
Guys, my batch3 3 module unit has two 12V EPS connectors on PDU. Do I have to connect them both?
Thanks
Thanks
Mine do too, and yes, I did connect them all: 3 x 8-pin pci-e, 2 x 8-pin EPS 12v, 1 x 24pin mobo
All the higher wattage PSU's I've seen come with two eps 12v connectors anyway (one 8pin and one 2x4pin).
Just my luck... another burnt part, in a different unit. Unlike my other one there were no unusual symptoms beforehand. Same settings as the last unit.
Now I'm wondering if unplugging the affected miner from the bus would work. Might be tough to do, but it would let me use the other seven miners on that module without having to try and repair the broken one.
I suspect you might just be overclocking way too aggressively.Now I'm wondering if unplugging the affected miner from the bus would work. Might be tough to do, but it would let me use the other seven miners on that module without having to try and repair the broken one.
I have mine (Batch 1) overlcocked to 350 (constant) and I don't let it pass from 45C. The fans are set to 40%-100% with them running mostly at about 2000 to 2400 RPM~. Note: That is because I am using dust filters on the intake. So if I take them off the fan RPM would go even lower....but the unit become dirty on the inside and needs to be cleaned out.
I let avalon-auto do the overclocking. 350 is where this one was staying, for days and days. Fans are at 100%, it's a batch 3 and the temp always hovered in the mid 60's.
Perhaps the recommendations being adhered to were by a very good batch 3 that could take thermals that high?
Yours seems to be suffering...if a third module goes out then I think we can probably say that not all Avalon Batch 3's should be allowed to go that high in temps. Especially when Avalon usually has a very poor thermal interface with the metal heatsink.
Oh and I also have a heavy duty laptop cooler beneath my Avalon Batch 1 to cool the bottom aluminum plate.
http://www.amazon.com/gp/product/B004G603E2/ref=oh_details_o03_s02_i00?ie=UTF8&psc=1
You might be right about the recommended temp being too high. I'm torn between keeping my two unaffected units on avalon-auto up to 350Mhz and 70c (to squeeze out every last satoshi while I can), and lowering the target temp to prolong their lives.
Just my luck... another burnt part, in a different unit. Unlike my other one there were no unusual symptoms beforehand. Same settings as the last unit.
Now I'm wondering if unplugging the affected miner from the bus would work. Might be tough to do, but it would let me use the other seven miners on that module without having to try and repair the broken one.
I suspect you might just be overclocking way too aggressively.Now I'm wondering if unplugging the affected miner from the bus would work. Might be tough to do, but it would let me use the other seven miners on that module without having to try and repair the broken one.
I have mine (Batch 1) overlcocked to 350 (constant) and I don't let it pass from 45C. The fans are set to 40%-100% with them running mostly at about 2000 to 2400 RPM~. Note: That is because I am using dust filters on the intake. So if I take them off the fan RPM would go even lower....but the unit become dirty on the inside and needs to be cleaned out.
I let avalon-auto do the overclocking. 350 is where this one was staying, for days and days. Fans are at 100%, it's a batch 3 and the temp always hovered in the mid 60's.
Just my luck... another burnt part, in a different unit. Unlike my other one there were no unusual symptoms beforehand. Same settings as the last unit.
Now I'm wondering if unplugging the affected miner from the bus would work. Might be tough to do, but it would let me use the other seven miners on that module without having to try and repair the broken one.
Now I'm wondering if unplugging the affected miner from the bus would work. Might be tough to do, but it would let me use the other seven miners on that module without having to try and repair the broken one.