my rig just freezes and reboots with the new version 1.8.0...cards are rx550.
it works fine with 1.7.9
Give more info, "just freezes" isnt too much info, you must admit that.. |
|
|
|
tried a new graft algorithm
I post a log
[2019-03-06 16:49:33] Startup monitor attached
[2019-03-06 16:49:33] Miner version: 1.8.0
[2019-03-06 16:49:33] Windows version: 10.0 build 16299
[2019-03-06 16:49:33] Video driver version: 22.19.659.0
[2019-03-06 16:49:36] AMD Platform ID: 0
[2019-03-06 16:49:36] AMD platform FOUND
[2019-03-06 16:49:36] Found 6 AMD devices
[2019-03-06 16:49:36] CPU AES-NI: FALSE
[2019-03-06 16:49:36] GPU0: AMD Radeon R7 200 Series [pitcairn] [2048 MB][I: 15.0][W: 16][T: 2][F: 8][BUS: 8]
[2019-03-06 16:49:36] GPU1: Radeon(TM) RX 460 Graphics [baffin] [2048 MB][I: 15.0][W: 16][T: 2][F: 8][BUS: 4]
[2019-03-06 16:49:36] GPU2: AMD Radeon R7 200 Series [bonaire] [2048 MB][I: 11.0][W: 8][T: 2][F: 8][BUS: 10]
[2019-03-06 16:49:36] GPU3: AMD Radeon (TM) R7 370 Series [pitcairn] [2048 MB][I: 15.0][W: 16][T: 2][F: 8][BUS: 9]
[2019-03-06 16:49:36] GPU4: AMD Radeon (TM) R7 370 Series [pitcairn] [2048 MB][I: 15.0][W: 16][T: 2][F: 8][BUS: 11]
[2019-03-06 16:49:36] GPU5: Radeon(TM) RX 460 Graphics [baffin] [2048 MB][I: 12.0][W: 8][T: 2][F: 8][BUS: 1]
[2019-03-06 16:49:36] ADL is enabled
[2019-03-06 16:49:36] NOT using any of the recommended drivers: Adrenalin 18.5.1, 18.5.2 or 18.6.1
[2019-03-06 16:49:36] Algorithm: Cryptonight Graft
[2019-03-06 16:49:36] Algo switching: disabled
[2019-03-06 16:49:36] Startup monitor: enabled
[2019-03-06 16:49:36] Gpu watchdog: enabled [gpu disable mode]
[2019-03-06 16:49:36] Coin forking: disabled
[2019-03-06 16:49:36] Starting init of mining threads
[2019-03-06 16:49:36] Created OCL context
[2019-03-06 16:49:36] Using fragments 8 for DeviceID 0 (Thread 0)
[2019-03-06 16:49:36] Using heavy_mode 1 for DeviceID 0 (Thread 0)
[2019-03-06 16:49:36] Using thread_delay 319 for DeviceID 0 (Thread 0)
[2019-03-06 16:49:37] Created OCL input buffer for DeviceID 0 (Thread 0)
[2019-03-06 16:49:37] ctx->headers[0] created for DeviceID 0 (Thread 0)
[2019-03-06 16:49:37] ctx->Program created for DeviceID 0 (Thread 0)
[2019-03-06 16:49:37] Compiling [graft] kernel for DEVICE BUS_ID[8]
[2019-03-06 16:49:38] Error CL_INVALID_KERNEL_NAME when creating kernel aи¬ for DeviceID 0 (Thread 0)
[2019-03-06 16:49:38] Error initing GPU's. Stopping miner process
[2019-03-06 16:49:38] Stopping miner process
yes, the good old gcn1 cards that i dont have and can't test the implementation. will try to blind fix it edit: re-download 1.8.0 and try |
|
|
|
V1.8.0- Added new algo 'Graft' (graft, cryptonight_graft, cryptonight_reversewaltz, cryptonight_v8_reversewaltz) - Added cmd parameters giveuplimit, retrytime, mainpoolreconnect, minrigspeed, shutdowntemperature, rebootscriptgpuwatchdog, rebootscriptminrigspeed - No more mixing of cmd line setup and config files, now it's one or the other (of course you can still define failover pools if using cmd setup) - It is enough to set ccryptonighttype, cpool, cwallet in cmd, gpu's will be auto setup - Fixed a few bugs + Graft will fork these days, so their new algo called CN Reverse Waltz added. You can set cryptonight_type to any of these : graft, cryptonight_graft, cryptonight_reversewaltz, cryptonight_v8_reversewaltzTo use the auto switch on fork option do this : start.batSRBMiner-CN.exe --enablecoinforking --config Config\config-normalv8.txt --pools pools.txt Explained : 1. Start mining with normalv8 algo, because Graft still uses that algo 2. Add --enablecoinforking parameter so miner knows you want to use the built-in (predefined) fork informations 3. When pool sends a job for the new algo, miner will auto switch to the new algo,if you have it defined in algos.txt (and you do by default in algos.txt) + Added a few more parameters to cmd, that were already available through config files. Now every important parameter can be used also in cmd line. What's new is that now you can use one or the other method for defining things, so you use cmd line setup or config file. No more mixing as before. Algo switching still needs the config method to be used. The minimum config needed to start mining is : SRBMiner-CN.exe --ccryptonighttype normalv4 --cpool pool:port --cwallet walletThis will auto setup every AMD Gpu you have, and start mining with normalv4 algo on pool:port you set. + Still trying to fix those nasty random crash bugs.. Also fixed a few more 
|
|
|
|
Cool, thanks.
Last question. Is there any option / way to have the miner quit without any restarts when one of GPU's crash?
"reboot_script_gpu_watchdog" : filename to a batch file in miner directory, if set it turns off built in miner reset procedure on gpu failure, and instead runs this script You can guess, the script can be empty. |
|
|
|
Does anyone know if "reboot_script_gpu_watchdog" command can be set in the start.bat file?
No, but next version will support full cmd line parameters Thanks for reply. Do I need to create config.txt for this command or can it go in Config/config-normalv8.txt ? It goes in the appropriate config file, so yes, put it in normalv8 config if you want it to be enabled when using that config file. |
|
|
|
After I've ran a new benchmark, now it is working. But I will tidy up the algos.txt, thanks for the info. Could a VCredist reinstall help? For the priority, I understand, no problem. Sometimes a few good words helps also.  If you could login to MO earlier then its not the bug i described your problem, then probably just MO wasn't working properly. MO pools disconnect a lot... |
|
|
|
Hello After I've started using the 1.7.9 version in algoswitch mode (MoneroOcean) the miner crashes ~every two days. In the Event Viewer I found the following: Faulting application name: SRBMiner-CN.exe, version: 1.7.9.0, time stamp: 0x00000000
Faulting module name: msvcrt.dll, version: 7.0.17763.1, time stamp: 0x05c26c69
Exception code: 0xc0000005
Fault offset: 0x0000000000074a80
Faulting process id: 0x102c
Faulting application start time: 0x01d4d24e970fbb40
Faulting application path: C:\Moria\SRBMiner-CN-V1-7-9\SRBMiner-CN.exe
Faulting module path: C:\Windows\System32\msvcrt.dll
Report Id: 1a859332-31c6-4ffa-bcd0-39e5f5df992c
Faulting package full name:
Faulting package-relative application ID: Should I reinstall the VCredist? Is there any built-in option to run a watchdog that restarts the SRB Miner after a crash? This is my .bat file: SRBMiner-CN.exe --config Config\config-gpu.txt --pools pools-algoswitch.txt --logfile algoswitching_%LOGTIME% --usealgoswitching --resetmineronalgoswitch My config: Win10 up-to-date, Adrenalin 18.6.1, 6*Vega56 Strix Thank you in advance! Hello Doc, New error: [2019-03-05 08:43:27] Cryptonight type is not set for this pool. Currently using gpu
[2019-03-05 08:43:57] Couldn't login to pool, please check your wallet address
[2019-03-05 08:43:57] Switching to next pool gulf.moneroocean.stream:20128 [0]
[2019-03-05 08:43:57] Just a moment... In the morning it has started to mine after a reboot, but shortly after this the error comes again. Regarding rhe crash, i cant really help, i have a few different crash cases that i am trying to hunt down and fix.. As with the login, try to remove a few algos that are not used from algos.txt, theres a bug that will be fixed in next version and its related to too many algos in algos.txt |
|
|
|
Hi, Doc!
1. In the last version there is a bug with watchdog, which cause random restart:
[2019-03-04 20:10:50] miner_result: Pool accepted result 0x0000A16F [39ms]
[2019-03-04 20:10:48] watchdog: No share sent for more than 71582788 minutes! Miner will restart
[2019-03-04 20:10:48] Restarting miner process
2. And what about to add feature to set up password for api and http access?
1. Going to check it out, but how is 20:10:48 after 20:10:50 ?  2. Stats are read only, so really no need to protect anything, but i will consider it for a future version Does anyone know if "reboot_script_gpu_watchdog" command can be set in the start.bat file?
No, but next version will support full cmd line parameters Jason has set up a Graft test pool, so I have found info below. I think you can test your implementation. fork will be at 286500 block. testnet explorer https://testnet.graft.observer/testnet testpool https://testnet.graft.communityYou can use my test wallet address below. F9BptkHtPuRVRWv3WEa78uidriZZkxh3u5DjNSuYRqbhaW1hEiCfX1ZGMyf4EGfJt3EEMBVDoxGk9N7 MRUBGmZkhVnMVbjS Yes, i'm on discord, but thanks for your effort Now we wait for block 286500 |
|
|
|
4 days till graft fork. will u support reverse waltz? xmrig&stak will.
It is ready, but im waiting for a stratum testpool from their team, to test my implementation. But it looks like they can't setup one. |
|
|
|
Tried different algos but after day of mining miner crashes. I dont know why,same settings. Back to 1.7.8 and all fine
same trouble on mix card rigs. strange carsh. reinit card and dont work. press h s r only show key on screen and dont mining. back to 1.7.8
Ok, i want to help but we need to clear up a few things first, you just dont call everything 'miner crash'. 1. MINER CRASH Miner window closed, or windows returned a message the app crashed, or miner just quit and all you got in the cmd window is a "press any key to continue message". Basically miner isnt running anymore. 2. VIDEO DRIVER CRASH When miner is reacting to keypress, but hashing with 0 hs. Also if you had a message from os saying the driver crashed, or stopped responding. Win10 says graphic hardware is blocked. This is not 1 (miner crash), it means you should check your OC settings mainly, or lower intensity in miner. |
|
|
|
i have the same issue. randomly closes at multialgo and work like a charm for weeks at single algo. rigs 8-9 vegas. nothing unusual in logs.
The developer said he hoped this would be fixed in this new version, but today I experienced it again: the miner window closed by itself and there wasn't anything unusual in the logs, just normal mining. Could you guys tell me which version of windows 10 are you using? I have a feeling it is older than 1809. |
|
|
|
a logical thing to do would be to try out your wow settings without algo switching, so you will know is it related to gpu's not released correctly, driver crash, or it's just the algo.
Agreed. I left the miner mining exclusively cn-wow for the last 5 hours and had zero problems so far. In an algo-switching scenario I'd have already encountered at least 6-7 crashes in the same time frame - it really depends on how many times the algorithm switches. It might be also helpful to say that this crash happens sometimes and right after the algo switch. Sometimes it will switch to cn-wow and mine normally, sometimes it will lead to crashing GPUs and subsequently mining with 10-15% of the hashrate until miner restarts. I can leave it mining wownero for a longer time, but I'm almost ready to discard this being an overclock issue. Is the miner crashing or the video driver? Do you get the 'hardware blocked..' system message ? |
|
|
|
Sometimes when pool requests an algorithm change to cn-wow, I think the miner doesn't release GPUs correctly and it ends up crashing them. The miner reports that one or more GPUs crashed, and it also shows they're hashing with maybe 10-15% of the normal hashrate. After a few minutes the miner restarts because I've set a minimum rig speed. I didn't have this issue before when cn-wow wasn't present, so I think it's related to the algo itself. I was under the impression this algorithm would work with cnv8 clocks/settings.
a logical thing to do would be to try out your wow settings without algo switching, so you will know is it related to gpu's not released correctly, driver crash, or it's just the algo. |
|
|
|
1.7.8 is Ok with this:
1.7.9 will be ok too just remove the algoswitching or enablecoinforking parameter, you dont have any of those enabled on 178 thats why it is working. Also you dont need the coinforking param right now if you are mining turtle |
|
|
|
SSL seems not working at version 1.7.9 for turtle:
 pools.txt: {
"pools" :
[
{
"pool" : "turtle.miner.rocks:5005",
"wallet" : "TRTLuzNq4PSFDEPAjcDMHm6xbQd6aYzh881J9s3acucxD1zvdvdxmxP6tsE5GmRAvkbuz7KnVoNS8ACsKFCuZyyShnDcFhh3nfv.30000",
"password" : "x",
"pool_use_tls" : true
}
]
}
|
|
|
|
its more stable now...less self closing windows
less closing or no closing ? |
|
|
|
V1.7.9
test tube2 algo with rx 570 4gb 1.7.8 rate 896 1.7.9 rate 862 back to 1.7.8 Every time i release a new version you write some wrong information. And that's really every time Same card, same settings, same pool, just SRB version is different.  |
|
|
|
The same problem on MOX, also the farm began to be overloaded. Returned to V1.7.8.
rx552/ W10(1709)x64/ 18.6.1
Mox algo in 1.7.9 is the new POW that will go live in a few days, so that's why its not working right now (you could read this few posts above). |
|
|
|
|
Cn/R hashrate will be +-3% because of the random math on every new block.
|
|
|
|
|
Show Posts
