MultiMiner: Any Miner, Any Where, on Any Device (Free, Open Source, Cross Platform)

[crazyearner]

well after playing around got working with  bfg miner seems driver related prolem with this is constant and continues to bug out when trying to use cgminer with tool.

New bug found when loading more than 30 usbs on

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at MultiMiner.Xgminer.Miner.Launch(String reason)
   at MultiMiner.Engine.MiningEngine.LaunchMinerProcess(MinerConfiguration minerConfiguration, String reason)
   at MultiMiner.Engine.MiningEngine.StartMining()
   at MultiMiner.Engine.MiningEngine.StartMining(EngineConfiguration engineConfiguration, List`1 devices, List`1 coinInformation)
   at MultiMiner.Win.MainForm.StartMining()
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5472 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
MultiMiner.Win
    Assembly Version: 1.3.39.0
    Win32 Version: 1.3.39
    CodeBase: file:///C:/Users/Crazy/AppData/Local/MultiMiner/MultiMiner.Win.exe
----------------------------------------
MultiMiner.Utility
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Users/Crazy/AppData/Local/MultiMiner/MultiMiner.Utility.DLL
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5468 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
MultiMiner.Engine
    Assembly Version: 1.3.39.0
    Win32 Version: 1.3.39
    CodeBase: file:///C:/Users/Crazy/AppData/Local/MultiMiner/MultiMiner.Engine.DLL
----------------------------------------
MultiMiner.Xgminer
    Assembly Version: 1.3.39.0
    Win32 Version: 1.3.39
    CodeBase: file:///C:/Users/Crazy/AppData/Local/MultiMiner/MultiMiner.Xgminer.DLL
----------------------------------------
MultiMiner.Coinchoose.Api
    Assembly Version: 1.3.39.0
    Win32 Version: 1.3.39
    CodeBase: file:///C:/Users/Crazy/AppData/Local/MultiMiner/MultiMiner.Coinchoose.Api.DLL
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5476 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Core
    Assembly Version: 3.5.0.0
    Win32 Version: 3.5.30729.5420 built by: Win7SP1
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5476 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
lh_zvnir
    Assembly Version: 1.3.39.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
8jgoyayu
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
m9phuqo4
    Assembly Version: 1.3.39.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
swh7c-sm
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
Newtonsoft.Json
    Assembly Version: 4.5.0.0
    Win32 Version: 5.0.6.16206
    CodeBase: file:///C:/Users/Crazy/AppData/Local/MultiMiner/Newtonsoft.Json.DLL
----------------------------------------
bs9cdfzl
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
xgik_v9h
    Assembly Version: 1.3.39.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
jqrz0zc4
    Assembly Version: 1.3.39.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
Interop.IWshRuntimeLibrary
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Users/Crazy/AppData/Local/MultiMiner/Interop.IWshRuntimeLibrary.DLL
----------------------------------------
Interop.Shell32
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Users/Crazy/AppData/Local/MultiMiner/Interop.Shell32.DLL
----------------------------------------
MultiMiner.MobileMiner.Api
    Assembly Version: 1.3.39.0
    Win32 Version: 1.3.39
    CodeBase: file:///C:/Users/Crazy/AppData/Local/MultiMiner/MultiMiner.MobileMiner.Api.DLL
----------------------------------------
MultiMiner.Xgminer.Api
    Assembly Version: 1.3.39.0
    Win32 Version: 1.3.39
    CodeBase: file:///C:/Users/Crazy/AppData/Local/MultiMiner/MultiMiner.Xgminer.Api.DLL
----------------------------------------
Accessibility
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

[1714210319]

1714210319

[1714210319]

1714210319

[1714210319]

1714210319

[1714210319]

1714210319

[nwoolls]

New bug found when loading more than 30 usbs on

Can you please download and run the Debug build and then post the same error message again? It will include more information that I can use to track down that bug. Thanks!

[crazyearner]

New bug found when loading more than 30 usbs on

Can you please download and run the Debug build and then post the same error message again? It will include more information that I can use to track down that bug. Thanks!

no problem and also think choice coin is down maybe causing prob with client to maybe should look to adding coin warz and dustocin to profit swinging etc

edited

Tried running with cgminer setting does not detect. bfg miner is working and does not re reproduce error when running the one you sent

[nwoolls]

no problem and also think choice coin is down maybe causing prob with client to maybe should look to adding coin warz and dustocin to profit swinging etc

I'd be happy to support data from other profitability sites but, as far as I know, none of the other ones provide the data outside of their own website (no API, JSON feed, RSS feed, etc). I'd be happy to support any that don't require scraping HTML.

Tried running with cgminer setting does not detect. bfg miner is working and does not re reproduce error when running the one you sent

Glad to hear it!

[nwoolls]

Version 1.3.40 of MultiMiner is now available for download. This is a public release that includes the following changes (in addition to those found in the prerelease):

• MultiMiner will no longer automatically disable the last enabled coin configuration when all pools are down
• Coin configurations are now merged rather than overwritten when importing
• The device # for the Stratum Proxy is now included in the History output
• The wrong stats were displayed for the Stratum Proxy when multiple miners were pointed at it
• PDBs are now included in all releases so users will no longer have to download the Debug release to provide call stacks with line numbers

I have now tested MultiMiner's Stratum Proxy support with multiple miners pointed at it - not just an Erupter Blade. It works well with cgminer aimed at it on a Raspberry Pi which means - in theory - this should also work with KnC miners. If anyone has one to try I'd love to hear the results!  

Edit: 1.3.41 is up and fixes the broken cgminer support. My b!  

[enki74]

Can anyone help with getting bfgminer running? I have cgminer working but the asic's keep crashing? I think I heard that bfg miner is better for this but can not seem to get it to run.....

What problem are you having with bfgminer specifically? Any error messages or screenshots you can include? The only thing I can think of is that you will need to install the Silicon Labs UART to USB driver in order to use bfgminer with Block Erupters.

Should that be listed under the driver colum right now says ICARUS and opencl for the 7970GPU  thought I did this with zdig yes?

[nwoolls]

Should that be listed under the driver colum right now says ICARUS and opencl for the 7970GPU  thought I did this with zdig yes?

You use the Zadig tool to install WinUSB drivers when using cgminer. They are not used for bfgminer. For bfgminer you must install the UART to USB drivers.

In my experience, installing the WinUSB drivers will make ASICs stop working with bfgminer, and installing the UART to USB drivers will make ASICs stop working with cgminer.

[Metatron]

What I think leo was trying to ask is something like this (which I myself has though of too):

When strategies are enabled, say using the profitability 'setting', and you have both GPU and ASIC devices (don't have and thus cannot try it out), does the setting work like:
Most profitable scrypt coin mined by GPU AND most profitable SHA coin mined by ASIC simultaneously?

That is correct. Right now all my GPUs are mining Litecoin because it's the most profitable scrypt coin. All of my ASICs (on the same rig, same MultiMiner instance) are mining Bitcoin, because it is the most profitable SHA-256 coin that I have configured. The reason I posted the shot above is it shows all of the coins I have configured on my rig. There are both scrypt and SHA-256 coins in there and my rig (a mix of GPUs, USB Erupters, and a Blade Erupter) all mine the proper coins based on algorithm and profitability.

Thanks Nate for clearing this up!

Cheers.

[enki74]

Can anyone help with getting bfgminer running? I have cgminer working but the asic's keep crashing? I think I heard that bfg miner is better for this but can not seem to get it to run.....

What problem are you having with bfgminer specifically? Any error messages or screenshots you can include? The only thing I can think of is that you will need to install the Silicon Labs UART to USB driver in order to use bfgminer with Block Erupters.

Here is what I have =137784566&filters[recent]=1&sort=1&o=0]http://s1329.photobucket.com/user/enki74/media/Untitled-3copy_zps38efa25e.jpg.html?filters[user]=137784566&filters[recent]=1&sort=1&o=0

Anyone want to give the secret how to embed an image here please do.....

So no errors just will not show the acis devices when I select bfgminer will not detect them.  from what you say I have the right drivers loaded, thanks....

[nwoolls]

I put together this unofficial build for a couple of users to test but figured I'd post it here as well in case any of you want to try it out.

With this build MultiMiner will pop up a notification whenever a block is found for a coin. If you have MobileMiner installed and the option enabled to push MultiMiner notifications up to MobileMiner you will also get alerts on your phone and (optionally) email when finding a block. A few solo miners indicated this would be a good feature. Looking forward to the feedback!  

[coinviking]

Multiminer suddenly stopped detecting my video card. All of my ASIC miners (ICA) show up just fine, but no OCL any more. I clicked on the "Detect Devices" option but it still isn't seeing my video card. I am able to mine with my card using GUIminer Scrypt, but I want it to be able to automatically switch to the most profitable currency.

My computer did freeze up and I had to reset it when I got home. Since then Multiminer hasn't been seeing my card.

[balanghai]

Is there for reaper already? My 5970 won't start with CGMINER.

[nwoolls]

Multiminer suddenly stopped detecting my video card. All of my ASIC miners (ICA) show up just fine, but no OCL any more. I clicked on the "Detect Devices" option but it still isn't seeing my video card. I am able to mine with my card using GUIminer Scrypt, but I want it to be able to automatically switch to the most profitable currency.

My computer did freeze up and I had to reset it when I got home. Since then Multiminer hasn't been seeing my card.

MultiMiner uses cgminer and bfgminer to detect your devices. Which are you using? Try running those from the command line with the -d? argument. If that doesn't list your GPUs MultiMiner won't see them.

[nwoolls]

Do not update to bfgminer 3.3.0.

It breaks many things with MultiMiner. I'm working with Luke on it now.

Edit: Stick with 3.2.1 for now. There are several changes in 3.3.0 that I'll need to handle them in MultiMiner. Specifically:

• bfgminer no longer detects GPUs without using the -S opencl:auto argument
• bfgminer now lists GPUs after listing USBs which breaks things subtly
• bfgminer is no longer returning Intensity with the devs RPC API call

Edit 2: Here's some more information on why the order of the GPUs and USBs returned by bfgminer is causing such a problem. There were already some bugs and quirks in bfgminer prior to 3.3.0, but with this changing of the device orders it compounds things to the point of not being usable. I haven't found a solution yet.

Prior to 3.3.0, running bfgminer -d? would return GPUs first and then USBs. In 3.3.0, USBs are returned first and then GPUs. It seems like a small change until you factor in some other behaviors of bfgminer.

For instance, launching bfgminer --scrypt makes it ignore all USB devices. This was not a problem with GPUs returned first by the -d? argument. Now, however, if you try to launch bfgminer with the device index returned by -d? along with the --scrypt argument you get an invalid device error.

Pseudo Examples:
 
#1
 

Code:

bfgminer -S all -S opencl:auto -d?
 
0 USB
1 GPU
 
bfgminer -S all -S opencl:auto -d 0            // succeeds
bfgminer -S all -S opencl:auto --scrypt -d 1   // fails, USB device in-use, -d 1 is no longer valid

#2
 

Code:

bfgminer -S all -S opencl:auto -d?
 
0 USB
1 GPU
 
bfgminer -S all -S opencl:auto --scrypt -d 1   // fails, USB devices ignored, -d 1 is no longer valid

#3
 

Code:

bfgminer -S all -S opencl:auto -d?
 
0 USB
1 GPU
 
bfgminer -S all -S opencl:auto -d 1            // succeeds, GPU mining only
 
bfgminer -S all -S opencl:auto -d?
 
1 GPU                                          // where did the USB device go?

While I think this all seems like fairly odd and inconsistent behavior, Luke assures me that bfgminer was never designed to work the way it was up until 3.3.0. He indicates that the previous behavior, while it may have worked, was undefined.

I'll continue to look into this but, for now, stick with bfgminer 3.2.1 or cgminer.

[nwoolls]

MultiMiner v1.3.42 is now available as a prerelease. This has quite a few changes in order to address compatibility issues with bfgminer 3.3.0. If you have the time I ask you to please hammer on this prerelease and let me know if you have any issues. Getting things working with bfgminer 3.3.0 required changes to quite a few core areas of the software and I want to make sure things are solid before I do a public release.

• A notification is now displayed when a block is found
• Fixed compatibility issues with bfgminer 3.3.0

[coinviking]

Thanks, nwoolls! Just updated and now everything seems to be working fine. I'll keep you posted if anything goes awry.

[Phoenix48]

I don't know if i am alone with this but I have a problem with bfgminer each time a new version is out. I am assuming that the automatic update (and initial installation) of Multiminer is installing the Win32 version of bfgminer because, each time a new version is out and Multiminer install it, bfgminer IS working BUT it always report the SCRYPT hashrate as 0 (For unknown reason SHA256 is always reporting fine in Win32). I know it IS working because the accepted share is growing. Problem is that unless i uncheck the "Restart Sick/Frozen/dead miners" option in the Settings, Multiminer will always eventually restart endlessly because it is reporting a Zero hashrate. At first, a good while back, i simply thought it was a random weird thing and fixed the thing by copying the Win64 version over the Win32 in the bfgminer folder. But now, with bfgminer v3.3 coming out, it is happening again and i realise that i have to do the same thing with 2 completely different PC. And this time, it is a little trickier because for that to work, i had to swap files while Multiminer is open (not working but open). I say this in case other have the same problem and need to know how to fix it.

So obviously, there is a problem somewhere with the Win32 version, so is there a way that when there is an update or when doing the initial installation that Multiminer can ask for a choice of which version, Win32 or Win64, of bfgminer to install?

[nwoolls]

So obviously, there is a problem somewhere with the Win32 version, so is there a way that when there is an update or when doing the initial installation that Multiminer can ask for a choice of which version, Win32 or Win64, of bfgminer to install?

Your observations are spot on. I always have MultiMonitor download the 32-bit version as I had (until now) assumed it would work fine on a 64-bit OS. I run the 32-bit version of bfgminer myself on 64-bit Windows 7 Pro without any issues.

Is this something you can reproduce just running bfgminer directly using the arguments found on the Process Log? While I could detect the OS and download a particular bfgminer version, that would add more Windows-specific code and - as far as I understand - you shouldn't be having the problem with bfgminer to begin with.

[Phoenix48]

I tried with the stand alone version of Win32 with all the exactly same arguments as i use in Multiminer to see if it worked well with the scrypt and, honestly, i didn't see any problem. I also tried with the Win64 to see if any difference would pop up just in case but nothing came up. I even tried to run them each multiple times just in case it would be an intermitent problem, but nope, nothing special happened. I truly don't understand why it systematically happen in Multiminer with each update or even with a fresh install using the Win32. I am sorry but that is the only error i am able to reproduce. Sorry that i can't help more than that to pinpoint the problem.

By the way, i am running windows 8, not windows 7 like you, don't know if that can make any difference.

[nwoolls]

I tried with the stand alone version of Win32 with all the exactly same arguments as i use in Multiminer to see if it worked well with the scrypt and, honestly, i didn't see any problem. I also tried with the Win64 to see if any difference would pop up just in case but nothing came up. I even tried to run them each multiple times just in case it would be an intermitent problem, but nope, nothing special happened.

So when you run 32-bit bfgminer on the command line it shows a hashrate for scrypt, but when you run MultiMiner with that 32-bit copy of bfgminer it shows a 0 hashrate in MultiMiner? Can you zip up the contents of your %appdata%\MultiMiner folder (specifically the API log files) and send those to me? Email address is in my sig.