|
doktor83 (OP)
|
 |
March 20, 2019, 03:55:55 PM |
|
can you see your windows event viewer and see what log save there ? last crash (and all the previous). source: Application error, event code: 1000, category: (100), and full path to SRBMiner exe file. Nothing else near. I'm catching error 1000 event via scheduler and run reboot.bat in case of it. Rig reboots and goes well for next 6 or more hours Are you mining V4 ? Im curious are the crashes happening only on V4 ? If so, im probably not releasing some of the CL resources as i should.. |
|
|
|
|
|
|
|
|
Each block is stacked on top of the previous one. Adding another block to the top makes all lower blocks more difficult to remove: there is more "weight" above each block. A transaction in a block 6 blocks deep (6 confirmations) will be very difficult to remove.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
|
doktor83 (OP)
|
|
March 20, 2019, 03:56:50 PM |
|
On my 280X video cards I keep getting these warnings with V4:
WARNING: Linking two modules of different data layouts!
WARNING: Linking two modules of different target triples: input.bc: 'amdil64-pc-unknown-amdopencl' and 'amdil-pc-unknown-amdopencl'
WARNING: Linking two modules of different data layouts!
WARNING: Linking two modules of different target triples: input.bc: 'amdil64-pc-unknown-amdopencl' and 'amdil-pc-unknown-amdopencl'
WARNING: Linking two modules of different data layouts!
WARNING: Linking two modules of different target triples: input.bc: 'amdil64-pc-unknown-amdopencl' and 'amdil-pc-unknown-amdopencl'
WARNING: Linking two modules of different data layouts!
WARNING: Linking two modules of different target triples: input.bc: 'amdil64-pc-unknown-amdopencl' and 'amdil-pc-unknown-amdopencl'
Apart from that, it seems to be working.
I will need to figure out the best settings next.
These warnings are harmless, nothing to worry about  |
|
|
|
chimaeraa
Newbie
 Offline
Activity: 49
Merit: 0
|
|
March 20, 2019, 04:41:20 PM |
|
can you see your windows event viewer and see what log save there ? last crash (and all the previous). source: Application error, event code: 1000, category: (100), and full path to SRBMiner exe file. Nothing else near. I'm catching error 1000 event via scheduler and run reboot.bat in case of it. Rig reboots and goes well for next 6 or more hours Are you mining V4 ? Im curious are the crashes happening only on V4 ? If so, im probably not releasing some of the CL resources as i should.. not V4 with other algo i get seam problem i see some other error come with this crash ( i use intel graphic for monitor ) it's about intel graphic services . |
|
|
|
|
RuMiner
Member
Offline
Activity: 168
Merit: 15
|
|
March 20, 2019, 06:31:21 PM |
|
Are you mining V4 ?
Im curious are the crashes happening only on V4 ? I was digging previous Monero algo on 1.7.x versions till income dropped below power consumption, and rig was weeks-stable. Then I switched to ETH miner for several months, it was stable also. Crashes began after launching Monero v4 on 1.8.0 and 1.8.1. |
|
|
|
|
rdome
Newbie
Offline
Activity: 14
Merit: 0
|
|
March 21, 2019, 05:45:04 AM |
|
I think it is v4 problem. 1.8.1 is better than 1.8.0 but still not 100% stable. It was no problem on other algos in srbminer, eth rock stable, mined beam for weaks rock stable, everything i was trowing at vegas just worked. Then it came v4 and it came problems. I just love srbminer cause it is best miner for vega cards, but when v4 cam and it was unstable, i tried other miners for v4, you have at lleast 4 of them, and they crash even faster, teamredminer crashed under 10min on same settings as srbminer. Tried to underclock gpu,mem for stability and same. Problem is only on v4, other algos are fine  Something is very bad with new algo, just put loop in bat file and it will at least run again when it crashes |
|
|
|
|
badral07
Newbie
Offline
Activity: 8
Merit: 0
|
|
March 21, 2019, 08:37:20 AM |
|
No more crashes thank you, Doc.
|
|
|
|
|
GKumaran
Member
Offline
Activity: 203
Merit: 10
|
|
March 21, 2019, 09:22:09 AM
Last edit: March 21, 2019, 01:22:14 PM by GKumaran |
|
can you see your windows event viewer and see what log save there ? last crash (and all the previous). source: Application error, event code: 1000, category: (100), and full path to SRBMiner exe file. Nothing else near. I'm catching error 1000 event via scheduler and run reboot.bat in case of it. Rig reboots and goes well for next 6 or more hours Are you mining V4 ? Im curious are the crashes happening only on V4 ? If so, im probably not releasing some of the CL resources as i should.. Can confirm that the same happens on vega runnin non cn4/r algos. |
|
|
|
|
Mananier
Newbie
Offline
Activity: 1
Merit: 0
|
|
March 21, 2019, 10:36:15 AM |
|
I have vega 56. All algorithms work fine, except CNv4. Vega resets the hashrate, the miner restarts several times within 10 to 24 hours. Then the whole system hangs up.
Before the update of the butterfly, the monero was mined normally.
|
|
|
|
|
Bllacky
Newbie
Offline
Activity: 22
Merit: 0
|
|
March 21, 2019, 11:33:49 AM
Last edit: March 21, 2019, 02:06:22 PM by Bllacky |
|
Feedback on
V. 1.7.5
Now it finally works when I have mix of 270X and 280X video cards.
Hashrates are very good for normal V8 algo:
280X 450 H/s
270X 345 H/s
290 530H/s
I do not OC.
I also sometimes get lots of STALE shares.
Good job!
Awesome, thanks for reporting. Also stales shown in miner are not a problem because those are accepted shares. Its just more a 'cosmetical thing'. Feedback on V. 1.7.6 Hashrates have gone up for normal V8 algo: 280X 455 H/s 270X 400 H/s 290 650H/s Temperatures seem to be better on the 270X with this version, or maybe now they are read correctly. Feedback on V. 1.7.7 Hashrates have gone up by very little for normal V8 algo: 280X 460 H/s 270X 405 H/s 290 655H/s Fan rpm on the 270X is now correctly reported. Thank you! Feedback on V. 1.7.8 Hashrates have gone up by very little for normal V8 algo: 280X 460 H/s 270X 405 H/s 290 655H/s Basically no change. Miner has gotten a lot more stable in the past 2 months. Feedback on V. 1.8.1 Hashrates are similar to normal v8 with normal V4 algo: 280X 450 H/s 270X 400 H/s 290 750H/s Runs pretty stable for me. Ran for 1 week without any crash. Settings are almost the same as on normal v8 except that intensities need to be adjusted for optimal performance. |
|
|
|
|
vmozara
Member
Offline
Activity: 190
Merit: 59
|
|
March 21, 2019, 06:52:55 PM |
|
Guys, can you please help with one small issue
7x vega 56 rig 1450mhz core 1100 mem
srbminer 1.8.1
adrenalin 18.6.1
intensity 62,
miner is always startying HAVEN at 12600H/s. But if i stop it many times and restart, it will eventually start at 13000H/s. How can i get it to always start at maximum performance?
Thanks!
|
|
|
|
|
|
doktor83 (OP)
|
|
March 22, 2019, 05:57:37 AM |
|
I think it is v4 problem. 1.8.1 is better than 1.8.0 but still not 100% stable. It was no problem on other algos in srbminer, eth rock stable, mined beam for weaks rock stable, everything i was trowing at vegas just worked. Then it came v4 and it came problems. I just love srbminer cause it is best miner for vega cards, but when v4 cam and it was unstable, i tried other miners for v4, you have at lleast 4 of them, and they crash even faster, teamredminer crashed under 10min on same settings as srbminer. Tried to underclock gpu,mem for stability and same. Problem is only on v4, other algos are fine Something is very bad with new algo, just put loop in bat file and it will at least run again when it crashes The whole concept of how v4 works is bad on gpu's. Compiling code on every new block, then need to release that memory, but it is known that the amd cl_release api is buggy and it wont always work as it should. For cpu's this concept of create code + compile is not a problem , but for gpu's it is. I am trying out various things, hope for the best  |
|
|
|
chimaeraa
Newbie
Offline
Activity: 49
Merit: 0
|
|
March 22, 2019, 08:23:55 AM |
|
I think it is v4 problem. 1.8.1 is better than 1.8.0 but still not 100% stable. It was no problem on other algos in srbminer, eth rock stable, mined beam for weaks rock stable, everything i was trowing at vegas just worked. Then it came v4 and it came problems. I just love srbminer cause it is best miner for vega cards, but when v4 cam and it was unstable, i tried other miners for v4, you have at lleast 4 of them, and they crash even faster, teamredminer crashed under 10min on same settings as srbminer. Tried to underclock gpu,mem for stability and same. Problem is only on v4, other algos are fine Something is very bad with new algo, just put loop in bat file and it will at least run again when it crashes The whole concept of how v4 works is bad on gpu's. Compiling code on every new block, then need to release that memory, but it is known that the amd cl_release api is buggy and it wont always work as it should. For cpu's this concept of create code + compile is not a problem , but for gpu's it is. I am trying out various things, hope for the best hi doc v4 algor , designed for cpu not gpu. do you test new amd driver ? it's very good. it's work for few day just few crash .  |
|
|
|
|
|
doktor83 (OP)
|
|
March 22, 2019, 08:25:27 AM |
|
I think it is v4 problem. 1.8.1 is better than 1.8.0 but still not 100% stable. It was no problem on other algos in srbminer, eth rock stable, mined beam for weaks rock stable, everything i was trowing at vegas just worked. Then it came v4 and it came problems. I just love srbminer cause it is best miner for vega cards, but when v4 cam and it was unstable, i tried other miners for v4, you have at lleast 4 of them, and they crash even faster, teamredminer crashed under 10min on same settings as srbminer. Tried to underclock gpu,mem for stability and same. Problem is only on v4, other algos are fine Something is very bad with new algo, just put loop in bat file and it will at least run again when it crashes The whole concept of how v4 works is bad on gpu's. Compiling code on every new block, then need to release that memory, but it is known that the amd cl_release api is buggy and it wont always work as it should. For cpu's this concept of create code + compile is not a problem , but for gpu's it is. I am trying out various things, hope for the best hi doc v4 algor , designed for cpu not gpu. do you test new amd driver ? it's very good. it's work for few day just few crash . Haha, no, i test only on 18.6.1 and blockchain. Which new version do you refer to? |
|
|
|
nordmann666
Member
Offline
Activity: 354
Merit: 16
|
|
March 22, 2019, 09:27:23 AM |
|
19.3.2/19.3.3 works really good - one day without crash - same settings as 18.6.1 = little bit more performance and i can little bit lower in mv with same speed
Vega56 @64
GPU_P7=1450;855 (was 865 with 18.6.1 to get it stable) -> hwinfo 1410MHz / 831mv -> 2090kHs
i think the new timing level for mem is doing great - same tight timings as with vega56 BIOS but with possibility to run 100Mhz mem
|
|
|
|
|
chimaeraa
Newbie
Offline
Activity: 49
Merit: 0
|
|
March 22, 2019, 09:59:17 AM |
|
I think it is v4 problem. 1.8.1 is better than 1.8.0 but still not 100% stable. It was no problem on other algos in srbminer, eth rock stable, mined beam for weaks rock stable, everything i was trowing at vegas just worked. Then it came v4 and it came problems. I just love srbminer cause it is best miner for vega cards, but when v4 cam and it was unstable, i tried other miners for v4, you have at lleast 4 of them, and they crash even faster, teamredminer crashed under 10min on same settings as srbminer. Tried to underclock gpu,mem for stability and same. Problem is only on v4, other algos are fine Something is very bad with new algo, just put loop in bat file and it will at least run again when it crashes The whole concept of how v4 works is bad on gpu's. Compiling code on every new block, then need to release that memory, but it is known that the amd cl_release api is buggy and it wont always work as it should. For cpu's this concept of create code + compile is not a problem , but for gpu's it is. I am trying out various things, hope for the best hi doc v4 algor , designed for cpu not gpu. do you test new amd driver ? it's very good. it's work for few day just few crash . Haha, no, i test only on 18.6.1 and blockchain. Which new version do you refer to? Radeon-Software-Adrenalin-2019-Edition-19.3.2-Mar14 you don't need soft power table . just overdriventool 0.2.8 . you can edit p0 to p7 and new fan setting. and memory timing .... |
|
|
|
|
chimaeraa
Newbie
Offline
Activity: 49
Merit: 0
|
|
March 22, 2019, 10:17:24 AM |
|
I think it is v4 problem. 1.8.1 is better than 1.8.0 but still not 100% stable. It was no problem on other algos in srbminer, eth rock stable, mined beam for weaks rock stable, everything i was trowing at vegas just worked. Then it came v4 and it came problems. I just love srbminer cause it is best miner for vega cards, but when v4 cam and it was unstable, i tried other miners for v4, you have at lleast 4 of them, and they crash even faster, teamredminer crashed under 10min on same settings as srbminer. Tried to underclock gpu,mem for stability and same. Problem is only on v4, other algos are fine Something is very bad with new algo, just put loop in bat file and it will at least run again when it crashes The whole concept of how v4 works is bad on gpu's. Compiling code on every new block, then need to release that memory, but it is known that the amd cl_release api is buggy and it wont always work as it should. For cpu's this concept of create code + compile is not a problem , but for gpu's it is. I am trying out various things, hope for the best hi doc v4 algor , designed for cpu not gpu. do you test new amd driver ? it's very good. it's work for few day just few crash . Haha, no, i test only on 18.6.1 and blockchain. Which new version do you refer to? |
|
|
|
|
GKumaran
Member
Offline
Activity: 203
Merit: 10
|
|
March 22, 2019, 11:23:22 AM |
|
19.3.2/19.3.3 works really good - one day without crash - same settings as 18.6.1 = little bit more performance and i can little bit lower in mv with same speed
Vega56 @64
GPU_P7=1450;855 (was 865 with 18.6.1 to get it stable) -> hwinfo 1410MHz / 831mv -> 2090kHs
i think the new timing level for mem is doing great - same tight timings as with vega56 BIOS but with possibility to run 100Mhz mem
Can u redo the test after deleting the old kernal ? |
|
|
|
|
zeef
Newbie
Offline
Activity: 296
Merit: 0
|
|
March 22, 2019, 03:21:39 PM |
|
I think it is v4 problem. 1.8.1 is better than 1.8.0 but still not 100% stable. It was no problem on other algos in srbminer, eth rock stable, mined beam for weaks rock stable, everything i was trowing at vegas just worked. Then it came v4 and it came problems. I just love srbminer cause it is best miner for vega cards, but when v4 cam and it was unstable, i tried other miners for v4, you have at lleast 4 of them, and they crash even faster, teamredminer crashed under 10min on same settings as srbminer. Tried to underclock gpu,mem for stability and same. Problem is only on v4, other algos are fine Something is very bad with new algo, just put loop in bat file and it will at least run again when it crashes The whole concept of how v4 works is bad on gpu's. Compiling code on every new block, then need to release that memory, but it is known that the amd cl_release api is buggy and it wont always work as it should. For cpu's this concept of create code + compile is not a problem , but for gpu's it is. I am trying out various things, hope for the best hi doc v4 algor , designed for cpu not gpu. do you test new amd driver ? it's very good. it's work for few day just few crash . Haha, no, i test only on 18.6.1 and blockchain. Which new version do you refer to? Radeon-Software-Adrenalin-2019-Edition-19.3.2-Mar14 you don't need soft power table . just overdriventool 0.2.8 . you can edit p0 to p7 and new fan setting. and memory timing .... I use it too with overdriventool and very good stability and more hashes than 18.6.1 U should consider look at it doktor xD |
|
|
|
|
|
doktor83 (OP)
|
|
March 22, 2019, 03:37:09 PM |
|
I use it too with overdriventool and very good stability and more hashes than 18.6.1 U should consider look at it doktor xD I will try it, maybe there is even room for some small optimisations too |
|
|
|
tvukoman
Jr. Member
Offline
Activity: 69
Merit: 5
|
|
March 22, 2019, 08:36:22 PM |
|
I think it is v4 problem. 1.8.1 is better than 1.8.0 but still not 100% stable. It was no problem on other algos in srbminer, eth rock stable, mined beam for weaks rock stable, everything i was trowing at vegas just worked. Then it came v4 and it came problems. I just love srbminer cause it is best miner for vega cards, but when v4 cam and it was unstable, i tried other miners for v4, you have at lleast 4 of them, and they crash even faster, teamredminer crashed under 10min on same settings as srbminer. Tried to underclock gpu,mem for stability and same. Problem is only on v4, other algos are fine Something is very bad with new algo, just put loop in bat file and it will at least run again when it crashes The whole concept of how v4 works is bad on gpu's. Compiling code on every new block, then need to release that memory, but it is known that the amd cl_release api is buggy and it wont always work as it should. For cpu's this concept of create code + compile is not a problem , but for gpu's it is. I am trying out various things, hope for the best hi doc v4 algor , designed for cpu not gpu. do you test new amd driver ? it's very good. it's work for few day just few crash . Haha, no, i test only on 18.6.1 and blockchain. Which new version do you refer to? Radeon-Software-Adrenalin-2019-Edition-19.3.2-Mar14 you don't need soft power table . just overdriventool 0.2.8 . you can edit p0 to p7 and new fan setting. and memory timing .... I use it too with overdriventool and very good stability and more hashes than 18.6.1 U should consider look at it doktor xD Interesting. On 18.6.1 too long time here... Can you share pics of the settings on new overdriveNtool 0.2.8 without ppt? |
|
|
|
|
|
