So I don't know if anyone has run across this yet, but it's definitely an issue that I ran into. I'm trying to mine with SGminer, doing 2 different algo's at once.
I downloaded the latest compiled version and tried with that as well just to be sure.
My rig currently has 4 GPU's, and I'm trying to split them to run on different algo's.
The setup I use, is batch to tell pool, solo, or whatever, and the .conf has all the details specific to each GPU.
This works just fine, as long as all 4 GPU's run the same thing.
The problem starts at this command: "device": "2,3", as SGminer will not operate correctly using that. It will do "device": "0,1", just fine, but the 2,3 it will not even operate correctly if it is the first instance of SGminer.
I've tried it on the wolf0 build, tried it on this build - sgminer-5.1-dev-2014-11-10-win32.zip, and tried it on this build (the latest available here -
https://www.nicehash.com/index.jsp?p=software#sgminer)- sgminer_v5.1_2015-03-09-win32.zip
This screencap is using this build - sgminer_v5.1_2015-03-09-win32.zip, and it is the only instance of SGminer running. It shows GPU 0 & 1 acting exactly as they should be.
![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FjviEo6K.jpg&t=663&c=jRbg4-qokH8-YA)
This is the same version, also the only instance of SGminer running, but it's attempting to run GPU's 2 & 3. (note the GPU id's at the left of the screen, yet the temps are correct for the GPU's it's supposed to be running)
![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FgZUoafH.jpg&t=663&c=h9wkWnJQnJX_tw)
I even broke it down to single GPU's, and while GPU 0 shows correcly, nothing else does. And while the others (Anything started without "device" : "0" do actually mine at a greatly reduced rate, trying to run more than one will eventually crash the drivers.
Also notice the 2nd one building a bin, they are using the same settings that were used in the 4 GPU configuration, just pared down, there's no need to create a bin..
That's definitely a bug.