miner freezes after few hours
version 1.6.8
So many info... Extrasenses are thinking now about your problem! |
|
|
|
I have a Rig x8 RX 580 8gb Mining cryptonight heavy. Sometimes Mining at 960 h/s each and after restart a lot of times can reach 1100+ h/s. Why?
Hello I have some RX 570 rigs and I see Hashrate 900 h/s. Use AMD adrenaline 18.6 Driver you'll see the problem solved. also, Not sure its every been explained specifically, but opening certain software after the drop usually brings them back up (gpuz and cycling through the cards, or reapplying overclocks through a .bat file for OverdriveNTool, HWinfo64) something about having the cards re-initialized(probably not the right term) gets them back up and keeps them up. If updating to 18.6.1 works then thats the better bet. I havent been on cnHeavy for a few months. Used 18.6.1, 18.5.1 and 18.5.2, all same results. Every restart, different results. Cause of bad compiled kernels or wrong intensity parameters. Place good kernels in cache folder and set right intensity - you will get good results. I deleted the kernels, used ddu uninstaller, instaled driver 18.6.1 and same problema, im crazy with this problem, Mining monero v7 berore same problem with the hash What intensity you're use? 59 is the Max, but tried less intensity, the total hashrate is random when wait 5 minuts mining Try 59.5 and other values with decimals. 5 minutes is too small period of time to stabilize speed especcially on heavy algo. You must every try wait at least 10-15 minutes. Sometimes speed is became stable after 10-12-15 minutes. And often it became faster! |
|
|
|
I have a Rig x8 RX 580 8gb Mining cryptonight heavy. Sometimes Mining at 960 h/s each and after restart a lot of times can reach 1100+ h/s. Why?
Hello I have some RX 570 rigs and I see Hashrate 900 h/s. Use AMD adrenaline 18.6 Driver you'll see the problem solved. also, Not sure its every been explained specifically, but opening certain software after the drop usually brings them back up (gpuz and cycling through the cards, or reapplying overclocks through a .bat file for OverdriveNTool, HWinfo64) something about having the cards re-initialized(probably not the right term) gets them back up and keeps them up. If updating to 18.6.1 works then thats the better bet. I havent been on cnHeavy for a few months. Used 18.6.1, 18.5.1 and 18.5.2, all same results. Every restart, different results. Cause of bad compiled kernels or wrong intensity parameters. Place good kernels in cache folder and set right intensity - you will get good results. I deleted the kernels, used ddu uninstaller, instaled driver 18.6.1 and same problema, im crazy with this problem, Mining monero v7 berore same problem with the hash What intensity you're use? |
|
|
|
I have a Rig x8 RX 580 8gb Mining cryptonight heavy. Sometimes Mining at 960 h/s each and after restart a lot of times can reach 1100+ h/s. Why?
Hello I have some RX 570 rigs and I see Hashrate 900 h/s. Use AMD adrenaline 18.6 Driver you'll see the problem solved. also, Not sure its every been explained specifically, but opening certain software after the drop usually brings them back up (gpuz and cycling through the cards, or reapplying overclocks through a .bat file for OverdriveNTool, HWinfo64) something about having the cards re-initialized(probably not the right term) gets them back up and keeps them up. If updating to 18.6.1 works then thats the better bet. I havent been on cnHeavy for a few months. Used 18.6.1, 18.5.1 and 18.5.2, all same results. Every restart, different results. Cause of bad compiled kernels or wrong intensity parameters. Place good kernels in cache folder and set right intensity - you will get good results. |
|
|
|
Great thanks to you! This is real what I was searching! Speed on worksize 8 is almost the same as on v7 - only a bit less! |
|
|
|
Please, who have rx 580 card and 18.6.1 driver, launch SRB with worksize 8 and share with me file g2_CNV8_w8_k1.srb from cache folder inside miner folder.
I'll give you something better but for worksize 16 / intensity 58. Not compiled with any recomended driver. https://www107.zippyshare.com/v/goLUMrVU/file.htmlrx570/580 Thanks! I'll try it! But can you make same file with 8 worksize? |
|
|
|
|
Please, who have rx 580 card and 18.6.1 driver, launch SRB with worksize 8 and share with me file g2_CNV8_w8_k1.srb from cache folder inside miner folder.
|
|
|
|
I think I saw messages here about the successful launch of srb on v8 on pitcairn, but I could not find it. Install recommended driver first and then try to use the settings that are in this message for tahiti.
Radeon R9 270X 4Gb (Pitcairn) with manual modded bios, Windows 10 x64 Pro, 18.10.1 driver. Gives 500 h/s on v8 with kernel 1, with kernel 2 speed slower. Owners of 580 8Gb please share your settings and wich kernel file you're use? Please, how you use this parametr "kernel" or --cgpukernel 1? And where? Type you config, please... I use config.txt file. Here on 270X: "gpu_conf" : [ { "id" : 2, "intensity" : 36, "worksize" : 16, "threads" : 2, "kernel" : 1}, ] P.S. I need file g2_CNV8_w8_k1.srb from cache folder. Who can share it compiled with 18.6.1 driver? |
|
|
|
I think I saw messages here about the successful launch of srb on v8 on pitcairn, but I could not find it. Install recommended driver first and then try to use the settings that are in this message for tahiti.
Radeon R9 270X 4Gb (Pitcairn) with manual modded bios, Windows 10 x64 Pro, 18.10.1 driver. Gives 500 h/s on v8 with kernel 1, with kernel 2 speed slower. Owners of 580 8Gb please share your settings and wich kernel file you're use? |
|
|
|
|
Who can give best settings and binary for v8 on RX 580 8Gb? Using latest drivers... Wich binary file from binarykernels folder are best for RX 580?
|
|
|
|
100 раз было сказано, что майнер GPU не работает на Windows 7. Под 7-ку уже дрова скоро перестанут писать новые, зачем на ней сидеть... |
|
|
|
|
It's strange... But, why if I manual set cpu_architecture to "vishera" (I have FX8320) then miner use assambly "generic_aes", but if I set cpu_architecture to "auto", then miner use assambly "generic_aes_avx"? I think with avx it's better?
|
|
|
|
@Uaciuganadu: What GPU do you use? Don't forget to add parameter --variation 15 to mine v8, in case you hadn't did it. Pitcairn: other already reported the Pitcairn compile fails, I documented it on the Github page, but cannot fix yet, as I said, i'm away from my rigs until november. That fork is a very bad timing for me. I barery had time to test the OpenCL, and had just none to optimize. Even when it works, the performance of the code, which is not mine but the naive reference one, is very very bad, as expected.  Same GPU`s as before 2Vega and one rx580, but the 33 version is broken for me on both v7 and v8. 13:49:44 | Pool changes Difficulty to 64000.
Abort was called at 318 line in file:
D:\qb\workspace\19992\src\vpg-compute-neo\runtime\os_interface\windows\wddm.cpp
Press any key to continue . . . I will have to switch to something else till November or when you get the time to debug the code again. On my RX580 v8 works normal, except low speed. Try to launch only RX 580... Or check port of pool and variation of algo... |
|
|
|
|
Tested v8 on 64-bit CPU's. On AMD FX8320 and Core i3 6100... Noticed significant drop in speed compared with v7 with the same config... About 25-30% less...
|
|
|
|
|
Version GPU 0.33a didn't compiles kernel for v8 for Pitcairn 270X 4Gb card. No errors, just hangs on building kernel for thread 1.
For other algos all wroks fine...
|
|
|
|
I know the performances are bad, i didn't even optimize it, i use the reference implementation from Monero. I rushed to provide a version that just works on common cards before the fork, but that's a very bad timing for me as i've almost no time to dev until november.
The CPU version however has been optimized and should be the fastest miner in all cases.
Yes, v8 works but speed is low... Now it's need optimizations... On nicehash exists so v7 as v8... But profit on v8 is very-very low yet... Maybe on nicehash you make auto-chosing of algo due to adress pointed to connect? This would be pretty nice... If I point cryptonightv7.eu.nicehash.com I can mine only v7 not any other algo... |
|
|
|
JCE still contains all historical forks, Monero V8 is just the 15th in the list.
XMR and WOW wallets default to V8 (xmr in advance of 2 days), other are unchanged. So, to mine XMR before the fork, force it back to V7 with --variation 3. After, keep automatic mode.
Internally, V8 is not a superset of V7, like MSR or B2N are, it's a very new fork, with a very different scratchpad loop. And for the first time, it involves floating-point compute.
Does it means that after the fork V7 stops to works and v8 will be instead of it? What about heavy and other v7/cryptonight childs algos? |
|
|
|
Windows 8.1 is supported too. And on the CPU version, that's all from Vista.
I'm releasing the V8 GPU version, based on the reference implementation provided by Monero. I'll work on the optimization later. I've had time to optimize the CPU assemblies, but i won't have any for the GPU.
I had to do the CPU first because the GPU version requires a working CPU implementation for the double-check.
0.33a GPU to be online in a few hours.
edit:
GPU version is online
Unlike what I said previously, i did not include the Heavy optim, i prefered doing an exact same version as 0.32, plus V8 support.
It still includes the CPU fixes for ETN introduced by CPU version 0.33a
I'm sorry for offtopic, and didn't want to spend your time, but please explain me in two words V8 fork. Does it remooves v7, or it just will be new algo? |
|
|
|
I know it, but most wouldn't search this... Thanx for direct link. |
|
|
|
|
@JCE-Miner, now you must explain to them, why only Windows 10. And why Windows 7 isn't support by miner...
|
|
|
|
|
Show Posts
