Looks like release 3.5.5 broke it for me.  I just got a crash but in another place and a different error (not the one I patched).  This time it's a "You cannot call a method on a null-valued expression". 

I'll dig into it.

Don't forget to close down and restart the miner!

Ok @nospampls and @Khazore I have a fix for you.

It may not be the ideal fix as I've never worked with PowerShell before but it addresses the .NET crashes.  I've been running for almost 24 hours and by now I would have had at least 1 crash on each machine so I'm considering this addressed.

I'm making a bunch of assumptions here as to how PowerShell works.  While I do program, I've never worked in this environment so take the notes below as my best guess as to what's happening.


Open the file "NemosMiner.ps1" (notepad should be fine)

The issue is with this line:

$PSItem.ToString() | out-file .\logs\excepUI.txt -Append

It's meant to log errors to the exceptUI.txt error log but sometimes it ends up on this line with a NULL $PSItem object.  Powershell isn't happy about doing a .ToString on a null object and errors out.  However since it's already on this line because of a different error (likely the fact that the object is NULL   ) it just crashes out as an unptrapped error.

So, simple fix:  Add a # in front of $PSItem.  That turns the line into a comment.  You lose the logging of UI errors but I'll take that over an untrapped crash any day!   The new line should look like this:

# $PSItem.ToString() | out-file .\logs\excepUI.txt -Append


Enjoy!

I'm seeing this outside of bechmarking.  Just noticed that CryptoDredge was running 3 instances. 

On a side note, reading the last several posts you'd think "why the hell are these people still running the software??".  The fact is I really like NemosMiner.  Comfortable to use, lots of good information and good mining results.  I believe if these bugs could be eliminated it would be the best choice for mining.

Ok, restarting the miner again resolved the wallet address and Trust is working again.
The HashRate is hit and miss.  Some miners reports it, others don't.

Still seeing the .NET error referencing "out-file" that I mentioned before.  It's occasional.

I updated to 3.5.4 (and after that switched from blazepoolplus to blazepool).  The following happened:

1. The update did not go well on either machine.  In one case the NemosMiner status window ended up running in a blue PowerShell window and in the other case the NemosMiner Runtime window did not display at all.  Exiting and restarting fixed both.
2. Trust is staying at 0 and the mining profitability as well.  Seems to be because the wallet address is empty in the black dos window yet the wallet is being shown in the "Running:" section at the bottom.  See below:
3. The "Running Miners" section in the white Runtime window shows a HashRate of "0 H/s" for some miners even though the miner is mining properly.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Pool name           blazepool
Wallet
Balance              0%
Trust Level         0% Avg based on [ 00 days 00:01 ]
Average BTC/H BTC = 0.00000000 | mBTC = 0.000
Average BTC/D BTC = 0.00000000 | mBTC = 0.000
Estimated Pay Date  Unknown > 0.003 BTC
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


But below that...


Running:

 Speed Started  Active   Cnt  Command
 ----- -------  ------   ---  -------
0  H/s 00:00:00 00:00:00 Once Bin\NVIDIA-CryptoDredge011\CryptoDredge.exe  --api-type ccminer-tcp
                              --no-color --intensity 6 --cpu-priority 5 --no-crashreport --no-watchdog -r
                              -1 -R 1 -b 127.0.0.1:4069 -d 0 -o
                              stratum+tcp://hmq1725.mine.blazepool.com:3747 -u
                              <my wallet address is here> -p ID=<my machine name>,c=BTC -a hmq1725

It just happened again.  The annoying thing is that every time it happens the Trust resets to 0% as do all the earnings numbers.

I'd be happy to work with the dev to resolve this.  Or, is there somewhere else I should report this error?

It just happened to me again a few minutes ago.  It was indeed during a cycle.  If I close the error box and try to stop the mining I get a page full of red errors referencing nonexistent functions.  It's almost like it's losing access to the .NET framework.

I talked with the guy who introduced me to NemosMiner and he gets it as well.  Hoping the dev can shed some light.

I'm getting the occasional .NET error while mining.  I've got 2 machines running and it's happened once on each one over a period of 2 days.  In both cases I've found it in the morning after it's been mining all night.  It's still mining, but the error box is on-screen and the main NemosMiner process is crashed.   You can click 'Continue' and the error goes away.  The miner keeps mining but the NemosMiner window no longer updates.  Any idea what the cause is?  The complete trace is below. I can post the whole error if needed.

System.Management.Automation.CommandNotFoundException: The term 'out-file' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
   at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)
   at <ScriptBlock><trap>(Closure , FunctionContext )
   at System.Management.Automation.ExceptionHandlingOps.ProcessTraps(FunctionContext funcContext, RuntimeException rte)
   at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)
   at <ScriptBlock>(Closure , FunctionContext )
   at System.Management.Automation.ScriptBlock.InvokeWithPipeImpl(ScriptBlockClauseToInvoke clauseToInvoke, Boolean createLocalScope, Dictionary`2 functionsToDefine, List`1 variablesToDefine, ErrorHandlingBehavior errorHandlingBehavior, Object dollarUnder, Object input, Object scriptThis, Pipe outputPipe, InvocationInfo invocationInfo, Object[] args)
   at System.Management.Automation.ScriptBlock.<>c__DisplayClass57_0.<InvokeWithPipe>b__0()
   at System.Management.Automation.Runspaces.RunspaceBase.RunActionIfNoRunningPipelin esWithThreadCheck(Action action)
   at System.Management.Automation.ScriptBlock.InvokeWithPipe(Boolean useLocalScope, ErrorHandlingBehavior errorHandlingBehavior, Object dollarUnder, Object input, Object scriptThis, Pipe outputPipe, InvocationInfo invocationInfo, Boolean propagateAllExceptionsToTop, List`1 variablesToDefine, Dictionary`2 functionsToDefine, Object[] args)
   at System.Management.Automation.ScriptBlock.InvokeAsDelegateHelper(Object dollarUnder, Object dollarThis, Object[] args)
   at System.Windows.Forms.Timer.OnTick(EventArgs e)
   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

It just happened again so I sent you a support request with logs.  I turned off SUMO again and it's back to mining ETN.

A small bug fix request, whenever you have the time:

Can you please make the winminer.com Statistics page be time-zone aware?  It's March 4 at 7:23pm here but the Statistics page is already saying that March.5 mining is in progress.

Thanks!

Thanks for the in-depth explanation.  Always good to know what's happening behind the scenes.
I did see it mining ETN this morning when I got to the computer but now it's working on SUMO again.  Hopefully things return to normal again soon.

The reason I had disabled mining certain coins is that I noticed from time to time WinMiner would switch to mining those coins and was making considerably less money than ETN.  It wasn't clear why it would do that so I just disabled that coin.

Both my machines stopped mining ETN overnight.  CPUs are enabled but were sitting idle.  I had previously disabled SUMO so I re-enabled it now and one machine started mining SUMO, the other is just sitting there with "Mining SUMO @ ∞ H/s"

I turned on the command window and the zcash miner came back with "Stream subscribe timeout".

Any ideas?