@MrPlus The ccminer_x86.exe started crashing after my switch from a GTX 1080Ti to an RTX 2080Ti.  This is during a benchmark run but I believe it was also happening before I reset benchmark stats.
I copied the command line and ran it manually in a command prompt so I could capture the error.  It is below.  Any ideas on this?

The card is an Aorus RTX 2080 Ti Xtreme Waterforce, stock settings.

I did update the video driver to 418.81 when I installed the new card, so that is one other difference between the last time I ran it and now.

I did some reading and people indicated overclocked memory might be to blame so I dropped the mem clock speed, no change.  Same with core clock.

Ccminer-x64 seems to be fine.



C:\Temp\NPlusMiner>Bin\NVIDIA-ccminerxevan9\ccminer_x86.exe -b 4068 -R 1 -a xevan -o stratum+tcp://xevan.mine.blazepool.com:3739 -u 3MaKtu1NHJNKpE235mBgt1soXXXXXXXXXX -p ID=MainPC,c=BTC -N 1 -d 0
*** ccminer krnlx-xevan for nVidia GPUs from alexis78@github ***
*** Built with VC++ 2013 and nVidia CUDA SDK 9.0 (Not recommended prefer 7.5)

*** Based on tpruvot@github ccminer
*** Originally based on Christian Buchner and Christian H. project
*** Include some of the work of djm34, sp, tsiv and klausT.

[2019-02-09 07:22:19] Starting on stratum+tcp://xevan.mine.blazepool.com:3739
[2019-02-09 07:22:19] NVAPI GPU monitoring enabled.
[2019-02-09 07:22:19] 1 miner thread started, using 'xevan' algorithm.
[2019-02-09 07:22:19] Stratum difficulty set to 0.5 (0.00195)
[2019-02-09 07:22:19] xevan block 133795, diff 0.475
[2019-02-09 07:22:20] GPU#0:Intensity set to 22.5, 6291456 cuda threads
[2019-02-09 07:22:20] GPU#0:result for 0950be90 does not validate on CPU!
[2019-02-09 07:22:20] GPU#0:an illegal memory access was encountered
Cuda error in func 'quark_blake512_cpu_setBlock_80' at line 871 : an illegal memory access was encountered.

Cool, thanks!  Good solution.

@MrPlus Thanks for the ongoing updates!  Loving NPlusMiner.

Btw, small typo in the post above.  Should read "Released NPlusMiner 4.6.0" 

And a question:  Any issues you are aware of with RTX 2080 Ti cards?  I'll be getting one shortly, just wanted to make sure NPlusMiner won't have issues with it.

Thanks.

@MrPlus Can I request a small improvement?  When the miner has been paused, display some sort of really obvious indicator on the main screen to show that it's paused.  Like a red box or something.  I sometimes need to pause mining to do resource-intensive work and I often forget to resume mining it once I'm done.  There's no visual cue to tell me that.  I made a small change to the code in NPlusMiner.ps1 to make the form background red (just one line: $MainForm.BackColor = "Red") when paused.  It looks like crap (because the labels remain with a grey background) but definitely draws my attention  .  I'm hoping you can make it look more professional.

Thanks.

@MrPlus Looks like the miner cycle issue is resolved.  I haven't seen two miners running simultaneously on either of my two machines for at least the last 3 or 4 days for sure.  Also, I haven't seen the donation bug manifest itself since Dec.20.  
Running version 4.5.9 and everything's working as it should.  

Thanks, and great work on NPlusMiner!

PS. I'm not running anything AMD otherwise I'd offer to help.

Logs attached.

Thanks.

https://drive.google.com/open?id=1RZZqOwhDNvzzjuvoipTSYJFx9zhjc_vJ

@MrPlus I think there may be a problem with the 'Donate' mining.  I have it set at "Donate (min): 8".   Am I right in understanding that means I donate 8 minutes of mining per day to the you and the other people involved in the project?
It's been mining for a wallet address starting with "1QGAD", Username: NPlusMiner458 for over 20 minutes now, possibly longer.   When I looked at the window at 00:38:14 it was already mining for that wallet.  It's now 01:02:00 and it's still at it.
Miners have switched at least 5 times.

I noticed the following at 00:58:06

20181220 00:57:21 WrlLufEchLufShaLufShvLufWrlShvShbShaGroEchSkeSmd
20181220 00:57:27 [ OK ] 71/71 - 32.20 MH/s, 120ms
20181220 00:58:04 [ OK ] 72/72 - 32.97 MH/s, 125ms
20181220 00:58:06 Started mining dev fee
20181220 00:58:53 x16r block 499285, diff 52367.271
20181220 00:58:58 x16r block 499286, diff 52367.910
20181220 00:59:06 Done mining dev fee
20181220 00:59:08 [ OK ] 73/73 - 32.26 MH/s, 127ms
20181220 00:59:15 [ OK ] 74/74 - 31.53 MH/s, 124ms
20181220 00:59:19 [ OK ] 75/75 - 30.90 MH/s, 130ms
20181220 00:59:28 [ OK ] 76/76 - 29.67 MH/s, 119ms

However it neither started at 00:58:06 nor was done mining at 00:59:06.

I've restarted the miner at 01:04:00 and it's now mining for me again.  As much as I'm glad to contribute for the dev efforts, I also don't want it mining to that address all night.

Can you please check into it?

@MrPus It just happened again, this time two copies of CryptoDredge running.  I put back the old version of Start-SubProcess() and I'll monitor it.  This is on my second mining PC which just mines and nothing else, so stealing focus doesn't matter to me.  I'll leave it as-is on my main PC as stealing focus is really irritating because I use that PC while mining.

Also, point of interest, when I click 'Stop', it does shut down both instances of the miner.  Any chance you could just execute that code when performing a miner switch?

It's still happening with 4.5.6.  This morning I found t-rex and CryptoDredge running at the same time, with CryptoDredge being the one showing in the 'Running' section.  And it pretty much has to be the focus stealing code as it didn't happen before that.  It's still pretty rare - once a day or less.  If there's any trace or debug code you want to add into the logs I'll try and help you narrow down the cause.

Great work, thanks!!

Not sure what you mean by 'download from master' but NPlus did auto-update and I'm at 4.5.5.  Is it fixed there?

It's running and mining happily alongside Cryptodredge.  Both miners working correctly, except they're doing so simultaneously which isn't good. 

To me this means one of two things:  Ccminer launched and NPlusMiner thinks it failed to launch (and therefore launches another miner) or it failed to shut down.  I'm assuming it's the former.  It launches but NPlus registers it as a launch fail.
It's also rare.  I've seen it I think 3 times since I started using NPlus.  I always look at both miners and both are mining.  I then look at the "Running:" entry on-screen and terminate the miner that isn't shown there (and it's always cccminer).

Sorry for the delay in porting back.  Now that it's been running I can say that it's largely ok with the focus stealing code in place BUT I am now seeing the "Failed:" indicator showing in relation to ccminer.  That's the only miner I've seen that has an issue with the new code.  What it leaves me with is ccminer and cryptodredge running at the same time (with cryptodredge being the one which should be running).  I terminate ccminer and move on.  If you could figure out that issue, it would be perfect.


Here's what I'm seeing right now:


Running:

     Speed Started  Active   Cnt Command
     ----- -------  ------   --- -------
18.43 MH/s 00:02:51 01:05:17 24  Bin\NVIDIA-CryptoDredge\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:4068 -d 0 -o stratum+tcp://hmq1725.mine.blazepool.com:3747 -u
                                 <mywalletaddr> -p ID=MainPC,c=BTC -a hmq1725

Failed:  2

 Speed Exited   Active   Cnt  Command
 ----- ------   ------   ---  -------
0  H/s dd:hh:mm 00:00:00 Once Bin\NVIDIA-Alexis78v1.4\ccminer.exe -b 4068 -R 1 -a skein -o
                              stratum+tcp://skein.mine.blazepool.com:4933 -u <mywalletaddr>
                              -p ID=MainPC,c=BTC -i 28 -N 1 -d 0
0  H/s dd:hh:mm 00:00:18 4    Bin\NVIDIA-Alexis78v1.4\ccminer.exe -b 4068 -R 1 -a keccakc -o
                              stratum+tcp://keccakc.mine.blazepool.com:5134 -u
                              <mywalletaddr> -p ID=MainPC,c=BTC -N 1 -i 29 -d 0

Ok, @MrPlus, continuing our discussion from the other forum...

The cause of the focus stealing is the Start-SubProcess function in Include.ps1.  I compared Nemo's and yours and his has a load more code in it, plus the give-away comment "// http://www.daveamenta.com/2013-08/powershell-start-process-without-taking-focus/" 
I copied his routine into your Include.ps1 and testing it now.  It definitely works in that it does not take the focus away - I'm just waiting to see if it introduces any other issues.

Thanks, moving to th NPlusMiner forum. 
I found out what was causing the focus stealing issue but we can discuss it in the other forum.

@MrPlus It's been 2 days and no crashes with NPlus.  Looks like I've found my new miner 

Can you please look into one issue?  Whenever it switches miners, it takes focus away from my current window.  So, I'm typing and suddenly I can't type any more until I click back on the window I was previously on.  Can you launch the miner without focus?

Thanks.

Thanks,  I'll do that on the other PC when I move from Nemos.  Yesterday I updated one machine.  So far, interestingly enough, neither machine has crashed since yesterday.  I did disable the "monitoring" feature on Nemos.  I wonder if that may have been a contributing factor.
EDIT:  Nemos just crashed with a NULL error executing a $TimerUI event (I think).  NPlus still running error-free.

By the way, I got errors today which seem to indicate more like an environment corruption.  Never mind just a NULL object slipping through - it loses access to (what I presume are) built-in functions like "write-host" and IsLoaded


Error 1:

Write-Host : The term 'Write-Host' 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 C:\NemosMiner\NemosMiner.ps1:337 char:25
+                         Write-Host "Running:"
+                         ~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Write-Host:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

You cannot call a method on a null-valued expression.
At C:\NemosMiner\NemosMiner.ps1:381 char:13
+             $TimerUI.Start()
+             ~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: ( [], RuntimeException
    + FullyQualifiedErrorId : InvokeMethodOnNull


Error 2:

IsLoaded : The term 'IsLoaded' 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 C:\NemosMiner\NemosMiner.ps1:1519 char:19
+             if (!(IsLoaded(".\Core.ps1"))) {. .\Core.ps1; RegisterLoa ...
+                   ~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (IsLoaded:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Will do.  Means I'll need to re-benchmark everything but well worth it if it means helping fix these crashes!

The annoying thing is that I don't know where the error is happening.  The first one was easier to track down as it referenced 'out-file'.  That only happens in a few places.  The null error could be in a lot of places.  So far no luck. 

I wonder if this is pool-based.  Maybe the reason Nemo doesn't get it is the particular pool or combination of pools he uses doesn't hit that error.