You might try passing the fanspeed min. argument along with claymore's args. You could use the -ttli argument to make sure temps stay safe while you're trying to figure it out. If there are other software out there to adjust fans for 1060s, maybe give them a shot (or try different/updated or older) drivers. Also, if you've got an infrared thermometer, you might take the temp of the cards and make sure they seem to be reporting correctly. Only other thing I can think of is make sure you're hardware is all straight & you've got enough power going to the rig. As you probably know, low power can cause some strange issues.

What cards, brand and and driver version? Also, what are you using to set the fanspeed? Could be several things going on, depending. Some driver versions had issues with fanspeeds for AMD, and I programed fan curves into the bios of my Tahitis, so something might be overriding youre settings. Also, if you're setting fanspeed in the miner group command line (with your miner args) and its getting overridden elsewhere by SMOS, it could cause this. For example if you have -minfanspeed -maxfanspeed, -tt, -ttli, etc. in Claymore's they may be interfering.

Anyone know what this is?

04:03:21:942    aa9c2700        OC v5, Reset control for GPU 0, close miner right now if you want to use default control from Catalyst

I've got Tahiti cards and this keeps popping up at the beginning of my logs and not sure what this is. Anyone?

"Already very fast" compared to what? Do you mean it is already very efficient, or is there some other technical standard you're using? I think that may sound rude, but I would really like to know.

I don't even try to find out what errors like that mean these days. I just reflash a clean install (I use SMOS for Tahitis) and flip it back online. Fixes the "problem" 9 times out of 10, especially with Tahiti cards.

I spent way way too much time trying to get Tahitis to work right in Linux, Win 10, Win 7 and fglrx, catalyst 15.12, blockchain driver, AMD-GPU (yeah, I didn't get the memo), etc. It was a pain in the ass on every OS and always fragile if I got it working. I use SMOS because it's plug and play for my 7950s. YMMV, but I would suggest you at least make an installable image of your drive as soon as you get the drivers running in any OS.

Those clocks seem tame for 7950/7970/280x. The reference 7950s I have that aren't dying on me run 1475m/1225e and hash 315 s/s (according to Claymore's) stable. I was 290-300 sol/s before Adaseb hooked me up with newer bios timings ... I hadn't updated the bios since I undervolted for litecoin. I've also got them juiced up pretty good these days at 1.2v because my energy costs permit it, but they can run 305 sols right at 1.01 volt if i recall.

They start selling when the market makes them sell. It's likely a combo of 2 markets, the mining landscape and 2. the hardware landscape. They can probably guess, based on difficulty, when competitors begin to "burn in" similar models. Really, though, they'd err on the side of selling too soon rather than selling too late. You have to understand that the first to market (and first to hash) with new generations of tech make the most money. Every wave that follows theoretically should make less money than the first because each subsequent wave waters down the market and increases the difficulty.

Additionally, it's important to understand that Bitmain and similar companies are not mining companies. They deal in hardware. As such, they are at the top of the food chain. They really should only mine if they can do so easily, for clear profit, and with little or zero expense. To the extent that their mining business ever impedes their hardware sales, they're moving themselves down a rung on the food chain and profits take a hit.

Was in the SMOS chat today and the topic of not hving a torrent came up, so I thought I'd get one started if anyone wants to seed.

This is a torrent file for SimpleMiner R Series build v1118. If you've already downloaded the zip image file and still have it, you shouldn't have to re-download it to seed. Just grab the torrent, verify integrity, and seed please: http://s000.tinyupload.com/download.php?file_id=96108634241154136716&t=9610863424115413671606656

Ideally Tytanik or someone official would do this for verification but i assume that's not absolutely necessary since you all can confirm my hash matches the one offered by smosmining.net.


Regardless, smosmining.net SHOULD (if they don't already) post a checksum value of the official images for the security of their customers.

Sha for the image I have up:

MD5: be28c26ec93d9e0dbaec1dff0513d49c
SHA1: e9d6e56ba3f6e09b4127521c12498b1d72e6b49c

Can anyone tell me any specifics on what method Claymore uses to get gpu temps?

I'm trying to troubleshoot a 7950 reference card that recently started reporting high temps to Claymore, but aticonfig --odgt fails to retrieve temp (or clocks). Claymore gets the temperature, but the card is actually about 20C cooler than reported temps. It'll hash; and temp seems fine best I can tell with an infrared thermometer on the PCB & comparing with identical cards in the rig.

Anyone suggest a possible fix or route for troubleshooting? I've flashed original bios, i've tried down-volted and down-clocked bios and all get the same overheating results.

I can use claymore's low intensity mode (-li 50) and turn the clocks down to 850, 1000 and use -asm 2 and it'll hash at about 30 sol/sec but says it's 80C and really isn't.

Just a follow-up here in case anyone has the same issue.

I was able to get into the account, created in Jan. 2014. My issue was: I had two valid-looking hashes when I ran blockchain2john.py against the wallet.aes.json. If I ran blockchain2john without args, I got a hash that began: $blockchain$704$.... If I ran blockchain2john with the argument --base64, the hash began $blockchain$528$...

Each hash was a different length and unlike modern My Wallet hashes, they did not specify the version. In my case, the second hash was the correct one and used 10 rounds of stretching or whatever it is.

My solution was to put both hashes into one hash file and run hashcat against both. Since my wordlist was very specific to me, and less than 10K words in length, it was no real addition in time. The --generate-rule function against my base list wound up finding the winner. Took 2 seconds; didn't even need the GPUs.

Is there a way to do this based on the year the wallet was created?

I'm trying to decrypt an old wallet.aes.json of my own. The blockchain.info MyWallet version is not listed in the hash, but I created the account in late January 2014. I want to make sure I'm using correct number of rounds against the encryption.

I'm using Hashcat (to leverage my GPUs) against the hash file, and the "blockchain2john.py" script to extract the hash from wallet.aes.json. (see here: https://raw.githubusercontent.com/magnumripper/JohnTheRipper/bleeding-jumbo/run/blockchain2john.py)

Any tips for making sure I've got the right hash?

Thanks.