1.8.1.1 Pre-release

[DillonN]

Please post issues here regarding the pre-release!

[navjack]

great so far!

[pducharme]

Skunk doesn't benchmark, either Precise or normal. It always end up "Terminated".

Don't know why, the miner for that wasn't just downloaded, so I got the Bin and it's working fine.

[DillonN]

@pducharme interesting, maybe AV removed it? In next ver it will use one of the existing ccminers anyway though

[pducharme]

I think it's because I copied over the bin folder from 1.8.1.0. NHML told me that they were unbenched algo, but I don't remember seeing a download miner progress. Anyway, it's fixed now, just got the bin folder and it worked right away.

[DillonN]

@pducharme Ah yes that would do it since I didn't add the check for new miners yet

[DillonN]

Pre-release 2 is up with Prospector miner (AMD Skunk) https://github.com/nicehash/NiceHashMinerLegacy/releases/tag/1.8.1.1-Pre2

Prospector supports Skunk, Sia, and Dagger on AMD and NVIDIA, although most of these will probably be disable since there are other miners that do it faster (to reduce clutter). Currently in my testing it's only fastest on Skunk AMD, but if someone finds it is for something else drop a comment here

[p1r473]

Dagger Prospector is giving "terminated" too. I let the client download the bin.

[navjack]

prospector is sooooo confused on what gpu it should be running on in my one rig. and on my main rig it wants to use the cpu for opencl. NO BUENO

[DillonN]

@p1r473 some algorithms seem to not work on prospector, you can try running it manually to see if it's giving an error

@navjack could you post the output from running prospector.exe list-devices in a command prompt in the bin_3rdparty\prospector folder?

[navjack]

my main machine shows this

03:54:46 - INFO   prospector 0.0.8-ALPHA starting
03:54:46 - INFO   Platform 0 - Intel(R) OpenCL
03:54:46 - INFO   Device (0:0) - Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
03:54:46 - INFO   Platform 1 - NVIDIA CUDA
03:54:46 - INFO   Device (1:0) - GeForce GTX 1080 Ti

my other rig shows this

03:56:31 - INFO   prospector 0.0.8-ALPHA starting
03:56:32 - INFO   Platform 0 - AMD Accelerated Parallel Processing
03:56:32 - INFO   Device (0:0) - Ellesmere
03:56:32 - INFO   Device (0:1) - AMD Ryzen 7 1800X Eight-Core Processor
03:56:32 - INFO   Platform 1 - NVIDIA CUDA
03:56:32 - INFO   Device (1:0) - GeForce GTX 980 Ti

on the ryzen computer it is just swapped around, in the GUI its running the 980ti when i have the rx480's miner checked and visa versa.

[DillonN]

@navjack thanks, I thought there would be some consistency to platform numbers but yours are completely different from mine. Will probably have to come up with a solution that runs that command and saves which platform numbers are which

[CryptoFire24]

hey not real sure where to ask this but, with pre release 1 i have a 1060 6gb and a 970 and at the start with both cards i was making projected 5.50$ a day with skunk, 1.2mBTC... then profitability changed back to 3$ a day projected. then with pre release 2 same numbers, i am kind of new to this. can anyone tell me what happened? thank you in advance

[DillonN]

@CryptoFire24 Skunk paying rates have gone down in the last couple hours so profit for it has gone down

[CryptoFire24]

well hell that was fast... and that sucks lol thank you for the quick response! do you know what caused that?

[DillonN]

The paying rate is based off the buying orders on NH, it could go up again if more orders are placed

[CryptoFire24]

@DillonN ohhh that makes sense now thank you for the information!

[semtexzv]

Hello, I am the author of prospector, and I don't know why the returned Platforms are randomly ordered. Currently, default config ignores all intel devices, and uses only AMD/NVIDIA.

I am currently working on a rewrite of configuration handling, and will move to Toml format very soon. So if there is anything you would like to be included, I can do something about it. :)

[DillonN]

Hello @semtexzv, thanks for reaching out. I think I have worked out a way for NHML to first get the platform numbers before launching using the list-devices command. Having a simple way to index GPUs would be helpful, e.g. in Claymore Dual you can select AMD devices with just their bus index and then NV device indexes are incremented by # of AMD devices (e.g. if a user has 2 AMD and 2 NV and wants to mine on NV only, the indexes passed are just 2 and 3). This is easy for NHML to understand

On top of that there are some other features NHML is built around that would be nice (bypass config with command line options, timed benchmarking, HTTP API) but I have found workarounds for most of that so nothing urgent.

Thanks for your work!

[rekcahboon]

Testing the new prerelease 2 and getting the following error:

[2017-08-15 11:19:40] [INFO] [PROSPECTORSQL] System.NullReferenceException: Object reference not set to an instance of an object. at NiceHashMiner.Miners.Prospector.ProspectorDatabase.QueryLastSpeed(String device) in C:\Users\dillo\Documents\Code\NiceHashMiner\NiceHashMiner\Miners\prospector.cs:line 49 [2017-08-15 11:19:45] [INFO] [PROSPECTORSQL] System.NullReferenceException: Object reference not set to an instance of an object.

Thanks.

[DillonN]

@77wayne77 this may be because of the indexing problem that will be fixed, if not could you post the info.db and config_x.json files located in the prospector directory?

[semtexzv]

Current adressing scheme is "(Platform:device)". On the next release it will change to "Platform-device". I could implement special adressing scheme - something like "amd-device" and "nvidia-device". would that be acceptable, or do you need indexes consisting of single number interpreted as you described ?

[DillonN]

@semtexzv being able to select with "amd-device" etc would definitely help, since we could bypass need to get Platform number. The (Platform:device) value is also used to show speeds in NHML display though, through accessing last values in info.db. If it were possible to just get total speed/recent average from info.db that would be best, since NHML only shows total speed anyway (device indexing is currently used to make sure all device hashrates are accounted for in speed display)

[semtexzv]

i can give you scritpts used by miner to read these value from db for its own reporting.

[DillonN]

That would help. Alternatively, will info.db always update with working GPUs sequentially? If so I could just sum the last x entries if there are x GPUs working

[DillonN]

@77wayne77 @navjack Pre-release 3 is out with hopefully indexing workaround fix https://github.com/nicehash/NiceHashMinerLegacy/releases/tag/1.8.1.1-Pre3

[semtexzv]

Well, You need to get unique devices for this session by utilizing session_id foreign key, and then retrieve latest entries for each individual device.

here are 2 reporting scripts: https://gist.github.com/semtexzv/b119d3857b2602cc232373cdc0530de9

[rekcahboon]

@DillonN, apologies for the delay - at work so trying to multi-task :-)

files.zip

[rekcahboon]

@DillonN Testing Pre-release 3 now

[DillonN]

@semtexzv Thanks those scripts help! If you make an update to select devices based on AMD/NVIDIA then we won't need to get Platform number

@77wayne77 No worries thanks. It looks like you are having a different problem but these methods will be changed

[madest13]

Testing the new prerelease 3:

System.NullReferenceException: Ссылка на объект не указывает на экземпляр объекта. в NiceHashMiner.Algorithm.get_CurPayingRatio() в C:\Users\Dillon\Documents\Code\NiceHashMiner\NiceHashMiner\Algorithm.cs:строка 64 в NiceHashMiner.Forms.Components.AlgorithmsListView.SetAlgorithms(ComputeDevice computeDevice, Boolean isEnabled) в C:\Users\Dillon\Documents\Code\NiceHashMiner\NiceHashMiner\Forms\Components\AlgorithmsListView.cs:строка 98 в NiceHashMiner.Forms.Form_Settings..ctor() в C:\Users\Dillon\Documents\Code\NiceHashMiner\NiceHashMiner\Forms\Form_Settings.cs:строка 76 в NiceHashMiner.Form_Main.buttonSettings_Click(Object sender, EventArgs e) в C:\Users\Dillon\Documents\Code\NiceHashMiner\NiceHashMiner\Forms\Form_Main.cs:строка 703 в System.Windows.Forms.Control.OnClick(EventArgs e) в System.Windows.Forms.Button.OnClick(EventArgs e) в System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) в System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) в System.Windows.Forms.Control.WndProc(Message& m) в System.Windows.Forms.ButtonBase.WndProc(Message& m) в System.Windows.Forms.Button.WndProc(Message& m) в System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

[mat875]

With PreRelease 3, I have problems with the Skunk prospector algorithm. It uses all my Memory (RAM) and Swap (Page file) and crashes ... I have 8Go of memory and a swap of 24Go.

[semtexzv]

is this the nicehash software, or my miner ? Try running the miner on its own.

[rekcahboon]

@DillonN, So testing pre3 and the benchmark works for all except Sia (Prospector). So disabled Sia and started mining, waiting for mining results/pswitch to see what the miners do.

Let me know if you require a copy of the logs.

Thanks

[mat875]

@semtexzv It seems to be prospector. I launched your client only, and it's acting the same on the Memory and Swap. http://i.imgur.com/U0pVdv6.png

[semtexzv]

Well, I gotta fix that, does it only do that on signatum ? I havent experienced this issue myself.

Also, lets move this into Prospector github page, can you create an issue here : https://github.com/semtexzv/Prospector/issues ?

[mat875]

@semtexzv Here's one of the config.json files :

{
  "pools": {
    "sigt": {
      "url": "skunk.eu.nicehash.com:3362",
      "username": "address.worker1",
      "password": "x"
    }
  },
  "gpus": {
    "(0:0)": {
      "enabled": true,
      "label": "GeForce GTX 1080 Ti"
    }
  },
  "cpu": {
    "enabled": false,
    "label": "CPU"
  },
  "gpu-coin": "sigt"
}

[p1r473]

Prospector crashing... Maybe because I use Nvidia?

Faulting application name: prospector.exe, version: 0.0.0.0, time stamp: 0x599043c4 Faulting module name: prospector.exe, version: 0.0.0.0, time stamp: 0x599043c4 Exception code: 0xc0000409 Fault offset: 0x00000000000326a1 Faulting process id: 0x119c Faulting application start time: 0x01d3158fb5776838 Faulting application path: C:\Users\J\Desktop\NiceHashMiner\bin_3rdparty\prospector\prospector.exe Faulting module path: C:\Users\J\Desktop\NiceHashMiner\bin_3rdparty\prospector\prospector.exe Report Id: cd56ed13-60b3-46db-b283-8de452010de2 Faulting package full name: Faulting package-relative application ID:

[Nicheuji]

Benchmarked DaggerHashimoto and Skunk Prospector without any issue

GTX 1060 6GB 1.8.1.1-Pre3

[ChriscomIT]

Yeah works everything for me on Pre3 good job @DillonN . All benchmarks finished well but Prospector is sadly not as efficient as I hoped. Maybe for AMD, it will work better but for Nvidia, it has lower performance as all the other miners.

[semtexzv]

Yes, I'm using very unoptimized kernel for nvidia. I dont have cuda support yet, but it's coming together.

[ChriscomIT]

@semtexzv Sounds good!

[DmitryDMR]

PreRelease 3 DaggerHashimoto Prospector and Skunk ccminer crash videodriver on win7/10 gtx 1060 can`t benchmarking Sia Prospector on win7 rx 580. without benchmarks miner average hashrate error 0/0/0, but 40Mh/s in nicehash

[liranscu]

can i put the bin of 1.8.1.pre1 into pre3? i cant dowload the bin through the 1.8.1.pre3

[mikosmausos]

working great with my 2 Nvidia Cards, still having and always had a little issue with my onboard AMD R7 graphics with 2GB, for some algos its working fine, but most of them are crashing my pc to bluescreen. i tried to deactivate the ethash-algos to avoid mining eth because of any possible DAG, but its still not working...but if the AMD card is deactivated everythings working great so far!!

[liranscu]

@mikosmausos the Nvida Cards and AMD Cards work together on ur computer?

[mikosmausos]

@liranscu yes they do my friend, the onboard AMD graphics was deactivated since i installed the Nvidias, but was activated again in the BIOS

[liranscu]

@77wayne77 how to use this file ,thank u ,i m new miner,so i dont know how to use it

[3zero2]

using Pre3 I haven't been able to run any Prospector benchmarks. Output of list-devices follows:

C:\NHML-1.8.1.1-Pre3\bin_3rdparty\prospector>prospector.exe list-devices
00:45:36 - INFO   prospector 0.0.8-ALPHA starting
00:45:36 - INFO   Platform 0 - Intel(R) OpenCL
00:45:36 - INFO   Device (0:0) - Intel(R) Celeron(R) CPU G3930 @ 2.90GHz
00:45:36 - INFO   Platform 1 - NVIDIA CUDA
00:45:36 - INFO   Device (1:0) - TITAN Xp

also from the logs:

[2017-08-16 00:20:44] [INFO] [Prospector-MINER_ID(1)-DEVICE_IDs(NOT_SET)] NEW MINER CREATED
[2017-08-16 00:20:44] [INFO] [Prospector-MINER_ID(1)-DEVICE_IDs(0)] Starting benchmark:  list-devices
[2017-08-16 00:20:44] [INFO] [Prospector-MINER_ID(1)-DEVICE_IDs(0)] Using miner: bin_3rdparty\prospector\prospector.exe
[2017-08-16 00:20:46] [INFO] [Prospector-MINER_ID(1)-DEVICE_IDs(0)] System.IO.IOException: The process cannot access the file 'C:\NHML-1.8.1.1-Pre3\bin_3rdparty\prospector\logs\15_08_17 22;20;46' because it is being used by another process.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize, Boolean checkHost)
   at System.IO.StreamReader..ctor(String path, Encoding encoding)
   at System.IO.File.InternalReadAllLines(String path, Encoding encoding)
   at NiceHashMiner.Miners.Prospector.InitPlatforms() in C:\Users\dillo\Documents\Code\NiceHashMiner\NiceHashMiner\Miners\prospector.cs:line 186

[zaGuru]

Hi there,

I am running whql-win10-64bit-radeon-software-crimson-relive-17.7.2-july27.exe on HD7990 and all bench-marking. No failures. Just i have for a long time now had efficiency/hashing speed issues.

It has for some time now only been computing very low hash rates apx 10MHs (50% of is potential 20MHs per chip). I am not sure if you have testing equipment to try this or if i can provide you with any logs to see if this can be resolved.

Thank you

[Nicheuji]

@zaGuru http://support.amd.com/en-us/kb-articles/Pages/Radeon-Software-Crimson-ReLive-Edition-Beta-for-Blockchain-Compute-Release-Notes.aspx I don't have any AMD GPU so I can't test it out, but I don't see any harm in you testing it out