I'm trying to use XMR-STAK to mine Loki.

When I start the miner I get:
!!!Please download newest SimpleMiningOS image in order to use this miner!!!

so I just downloaded the newest version from the website and created a fresh USB -  but I still get the same message.

Any ideas?

Playing with overclocks and fanspeeds...anyone have any guesses what PCB & Chip temps are the limits for a Z9?

I have one available and sent you a note.
cheers.

Just tested slushpool with ZEC and 100% rejected.
(I use slushpool for BTC).

"Limit one per customer"

How are you guys buying multiples?

Bug Report:

Just upgraded to the newest version.

Bitcoin Private's value is still coming up as $0

Has anyone heard of Phoenix is going to be added to SM?

I'm getting better hash rates with nvidia than with claymore.

Hi JJ,

I'm curious as to what makes you think it is hosts related?   I've tried mapping to IP addresses without using host names and it still does it.

Sorry that you have the same bug... fingers crossed Patrike can help

I have tried many names for it... both in Awesome Miner and on the network.
I also tried connecting with the netbios name as well as the IP address (and manually tried different static IP address).

I have been in IT since 1994 and I have NO idea what is going on lol

The weird thing is all of the miners are configured the same way - static IP addresses etc... and one other miner is EXACTLY the same hardware.. and ONLY this one has the problem.

I am hoping Patrike knows whats triggering the remote agent .

Hi Gents,

This bug is driving me nuts .... does anyone have any ideas?
It is really hard to explain so I made a video about it.

Here is the video:

https://www.youtube.com/watch?v=qG16ENVpQlg



Notes:
There is exact matching hardware in this miner as some other miners without the issue.
They all have unique IP addresses.
I've tried changing the IP address of Miner 4.
I've completely uninstalled and reinstalled the Awesome Miner remote agent countless times.
I've completely removed Miner4 from Awesome miner and re-added it from scratch multiple times with different names, etc.

Still the same results.
 If I adjust any other miner or open any options menus... Miner 4 stops mining and has to be restarted.
Miner 4 won't start with the start button when this happens - I have to open its properties and click OK and then in starts again.

Please let me know if you have any thoughts.
Cheers,
Edwards

p.s. @patrike I mentioned this bug on here a few months ago and haven't had any luck.  It has spanned multiple versions of the software - both primary and the remote agent have been updated several times with the bug never going away.

Is there a parameter with this miner to mine with one card and not the others?

The equivalent of doing a "-di 0" in Claymore?

Thanks in advance.

I can't seem to find it - is there an intensity setting for this miner?

I have a machine mining with three 1080s that I need to use for some work several hours each day.
With EWBF I would turn the intensity down a bit and the machine was fully functional... then I'd turn it back up when done working.

With this miner, the machine is unusable so I have to shut it off completely for the hours I'm working.

Is there an adjustment I'm not finding?

tia.

Does anyone know how many CFM an S9's fans move?

We are building a sealed mining room and need these numbers to calculate that we are going to be moving enough air through.

thanks in advance!

I've been having a really annoying issue with the remote agent for a few months now.  I've tried all kinds of things and cannot fix it.

I have many mining rigs running via remote agent.  All in server racks, built properly, unique IP addresses, etc.
I'm running the newest version of everything - but this has been going on for several versions.

Miner4 is my problem rig.

Any time I stop or start ANY OTHER remote agent rig's mining, Miner4 ALSO shuts down (even though I didn't touch Miner4).

So for example if I shut down Miner7 to switch it from Eth to EtN - Miner 4 ALSO shuts down as soon as I tell Miner7 to shut down.  Same for every other Miner... shut any of them down and Miner4 shuts down.

When it shuts down it craps it out to the point that I have to remote desktop into Miner4, kill the awesome miner remote agent and then restart the remote agent to get it to mine again.

I've completely removed and reinstalled the remote agent on Miner4.
I've completely removed Miner4 from AwesomeMiner and rebuilt it's config from scratch.
I've updated the remote agent to the newest version on every rig.
I've tried changing permissions on the remote agent to administrator with no change.

Doesn't matter what I do.  If I touch any other miner - this remote agent shuts down mining.

Has anyone else seen this bug?

Is there a way to change the coins displayed in the bottom footer?

I've been going through the menus and cannot find one... (the UI really has become a needle in a haystack  )

The control machine is running 9.7 - no problem.  It goes and grabs it and starts it.
The remote machines all still grab 9.6.

I deleted everything in the control machine's appdata/local folder and in the remote machines appdata/roaming folders.
It pulls 9.7 on control machine and 9.6 on the remotes.

Interesting - I did that and it did indeed force a re-download but it redownloaded 9.6

I'm missing something... perhaps the link on the Awesome Miner website isn't to the latest version of the remote agent?

I'm using this link to re-download the agent:
http://www.awesomeminer.com/download.aspx

I did exactly that.
It worked on the local miner but didn't work on ANY of the remote miners.

Did you update your awesomeminer remote service or anything?

Maybe I'm missing something obvious - how do I force remote agent machines to switch to the new version of Claymore?

I updated the program.  Now Claymore 9.7 comes up in the app.
On the local machine, I stopped it mining, restarted it (set to auto download) and 9.7 came up and started mining as expected.

On all of the remote machines - they keep coming up as Claymore 9.6 (they are set to auto as well).

I tried downloading the latest remote agent from the website (which is dated 6/27 on there btw..) but no matter what the remote machines still come up with Claymore 9.6.

How do I force remote machines to re-download (switch to 9.7) with the auto software setting?

I haven't had time to read this thread but thought I'd take a second to share how I solved this exact same issue I was having on some of my rigs (but not others?) after the latest patch...

Created a shortcut pointing to the remote executable and put it here:
C:\Users\(User-Name)\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup

Now it is auto-starting again.

Having it enabled in the startup items in Windows 10 was NOT working but this does work.

Hope this helps.
cheers,
Edward

I assume you updated your BIOS because you said you set 4G encoding and that's missing if you have an old version
Your bios date should be 3/17 or newer'ish?

Did you set the PCI's to Gen-2?   Two locations in that bios...

Don't worry about that PCI error in the device manager.  Both of my Asus Prime Z270's show the same thing but both rigs mine fine (one nvidia rig and one amd rig).