cryptoyes
Member

Offline
Activity: 297
Merit: 10
|
 |
February 19, 2019, 02:29:02 AM |
|
Once again: Ubuntu 16.04, Nvidia 415.27, CUDA 10, GTX1070, GTX1070Ti, GTX1080Ti. Motherboard is ASRock H110 Pro BTC+ (13 PCIe slots). Intel G3930, Intel G4600, Intel i3-7100.
Crashes happen on all machines (it's a farm). No malloc crashes and no CUDA "CopyEdges" or "CollectEdges" crashes on 14.x. Constant crashes on 15.0 for all of these.
To give you an idea of how often it crashes: 648 crashes in the past 24h for 17 different rigs. On average, *every* rig crashes about once every 40 minutes ... super wasteful.
|
|
|
|
NimaV
Newbie
Offline
Activity: 31
Merit: 0
|
 |
February 19, 2019, 03:20:04 AM Last edit: February 19, 2019, 04:05:20 AM by NimaV |
|
I can't mine grin31 with GTX 1080ti on Windows 10 build 1809. Bminer reports 9170MB free memory on the device and gives me insufficient memory error. I've checked it on several monitoring softwares and there is exactly 11264MB free dedicated GPU memory on the device. windows is running on another GPU and it does not use any amount of the GTX 1080ti memroy. why Bminer reports more than 2GB less free memory on my 1080ti? is there any way to fix this?
Also Bminer 15 doesn't work with my rig because of bcrypt.dll error.
|
|
|
|
admco
Newbie
Offline
Activity: 3
Merit: 0
|
 |
February 19, 2019, 03:56:16 AM |
|
Confirmed, it seems to be a Window 10 1809 issue. Builds 1803 and 1709 seem to work fine. The must have made changes to the bcrypt.dll library. I've tried using the 1803 version of the library on 1809 with no luck.
On a positive note, the Windows version appears to be pretty stable. I have it running on 6 rigs with no issue. 6x 1080Ti rigs work at full speed. Titan XP cards are getting 1.4 G/s with a 100 MHz core overclock.
|
|
|
|
cryptoyes
Member

Offline
Activity: 297
Merit: 10
|
 |
February 19, 2019, 04:19:10 AM |
|
Just to add to data...Getting constant crashes on one of my rigs on c31 w/15.0 release, "CUDA error DRIVER: '700' in func 'CopyEdges' line 173". Ubuntu 18.04, 1070tis. Current drivers.
Same here, see my posts above. Very buggy release  ... but a major effort from the developer, I have to appreciate that.
|
|
|
|
od1n
Jr. Member
Offline
Activity: 30
Merit: 1
|
 |
February 19, 2019, 05:03:09 AM |
|
HiveOS with v15 and 6x 1070 [Core +100 | MEM +0 | PL 85W] C29 is mining with 22,8 gps C31 is mining with 3,8 gps
C31 is running since 10 minutes, I will check if miner dies ...
1 hour update: Miner is still running but accepted share rate is <90%! With C29 Bminer finally reaced >95% accepted shares. After 2 hours I have nearly 15% rejected shares  But sparkpool predicts nevertheless 10% more revenue then with C29 before. Still running without freeze since 13 hours. But Hive shows 84% valid shares only, sparkpool too.
|
|
|
|
cryptoyes
Member

Offline
Activity: 297
Merit: 10
|
 |
February 19, 2019, 05:10:37 AM |
|
The new 15.0.0 crashes often. Ubuntu 16.04, Nvidia 414.27, CUDA 10.0, GTX 1070/1070ti/1080ti [INFO] [2019-02-18T00:51:38+02:00] [GPU 9] Speed: 0.76 G/s Fidelity 0.689 Temp: 34C Fan: 74% Power: 107W 0.01 G/J [INFO] [2019-02-18T00:51:38+02:00] [GPU 10] Speed: 0.72 G/s Fidelity 1.795 Temp: 40C Fan: 75% Power: 99W 0.01 G/J [INFO] [2019-02-18T00:51:39+02:00] [GPU 11] Speed: 0.74 G/s Fidelity 0.333 Temp: 43C Fan: 75% Power: 109W 0.01 G/J [INFO] [2019-02-18T00:51:40+02:00] Total 8.88 G/s Accepted shares 3 Rejected shares 0 [INFO] [2019-02-18T00:51:48+02:00] Received new job 90422 *** Error in `/node/bminer-15.0.0': malloc(): memory corruption: 0x00007fa883d43de0 *** ======= Backtrace: ========= /lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7faac48387e5] /lib/x86_64-linux-gnu/libc.so.6(+0x8213e)[0x7faac484313e] /lib/x86_64-linux-gnu/libc.so.6(__libc_malloc+0x54)[0x7faac4845184] /usr/lib/x86_64-linux-gnu/libcuda.so.1(+0x29b773)[0x7faac0921773] /usr/lib/x86_64-linux-gnu/libcuda.so.1(+0x21892d)[0x7faac089e92d] /usr/lib/x86_64-linux-gnu/libcuda.so.1(+0x1134c8)[0x7faac07994c8] /usr/lib/x86_64-linux-gnu/libcuda.so.1(+0x29c8d0)[0x7faac09228d0] /usr/lib/x86_64-linux-gnu/libcuda.so.1(+0x2bc099)[0x7faac0942099] /usr/lib/x86_64-linux-gnu/libcuda.so.1(+0x1e966d)[0x7faac086f66d] /usr/lib/x86_64-linux-gnu/libcuda.so.1(+0xfa8ce)[0x7faac07808ce] /usr/lib/x86_64-linux-gnu/libcuda.so.1(+0xfd9f3)[0x7faac07839f3] /usr/lib/x86_64-linux-gnu/libcuda.so.1(cuMemcpyDtoHAsync_v2+0x72)[0x7faac08d0d12] /tmp/miner[0x7c07be] /tmp/miner[0x7cb7be] /tmp/miner[0x7b2fd8] /tmp/miner[0x7cd846] /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xb8c80)[0x7faac578bc80] /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7faac4da86ba] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7faac48c83dd] ======= Memory map: ======== 00400000-00401000 r-xp 00000000 00:2d 3063903 /node/bminer-15.0.0 00401000-00dcc000 r-xp 00000000 00:00 0 00e00000-00e01000 rwxp 00000000 00:2d 3063903 /node/bminer-15.0.0 00e01000-018c3000 rwxp 00000000 00:00 0 01a00000-01a01000 r-xp 00000000 00:2d 3063903 /node/bminer-15.0.0 01a01000-01af5000 r-xp 00000000 00:00 0 01af5000-01af7000 -wxp 00000000 00:00 0 01af7000-01ecf000 r-xp 00000000 00:00 0 02000000-02d3b000 rwxp 00000000 00:2d 3063903 /node/bminer-15.0.0 02f3a000-02fc6000 rwxp 00d3a000 00:2d 3063903 /node/bminer-15.0.0 03f78000-077f4000 rwxp 00000000 00:00 0 [heap] 200000000-200200000 rwxs 00000000 00:06 727 /dev/nvidiactl 200200000-200400000 ---p 00000000 00:00 0 200400000-200404000 rwxs 00000000 00:06 727 /dev/nvidiactl 200404000-200600000 ---p 00000000 00:00 0 <snip>
Never saw this in the test. but it's interesting that it only happens in 15.0.0. Will dig into it. Actually I'm also getting malloc crashes on 14.3.1 when mining C31 on GTX1080Ti (same system, Ubuntu 16.03, Nvidia 415.27, CUDA 10). Never got this error when mining grin29. It seems linked to your c31 code more than the 15.0.0 version. The CUDA "CopyEdges" and "CollectEdges" errors are new to 15.0.0. With 15.0.0 I'm also now getting these: [INFO] [2019-02-19T07:01:58+02:00] [GPU 11] Speed: 0.68 G/s Fidelity 1.053 Temp: 58C Fan: 93% Power: 83W 0.01 G/J [INFO] [2019-02-19T07:01:58+02:00] Total 8.35 G/s Accepted shares 220 Rejected shares 24 bminer-15.0.0: tpp.c:87: __pthread_tpp_change_priority: Assertion `previous_prio == -1 || (previous_prio >= fifo_min_prio && previous_prio <= fifo_max_prio)' failed. and also [INFO] [2019-02-19T07:00:01+02:00] [GPU 9] Speed: 0.68 G/s Fidelity 0.967 Temp: 36C Fan: 82% Power: 108W 0.01 G/J [INFO] [2019-02-19T07:00:02+02:00] [GPU 10] Speed: 0.69 G/s Fidelity 0.877 Temp: 42C Fan: 83% Power: 120W 0.01 G/J terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc SIGABRT: abort PC=0x7f28a2b0a428 m=0 sigcode=18446744073709551610 signal arrived during cgo execution
[WARN] [2019-02-19T07:00:04+02:00] Miner died! It will be restarted soon... Very buggy version 
|
|
|
|
leoragraves666
|
 |
February 19, 2019, 07:43:19 AM |
|
C29 no crashes, but C31... damn I just woke up, on 187 rigs, thousands of crashes
|
PC & Mac repairs
|
|
|
realbminer (OP)
|
 |
February 19, 2019, 08:31:12 AM |
|
I can't mine grin31 with GTX 1080ti on Windows 10 build 1809. Bminer reports 9170MB free memory on the device and gives me insufficient memory error. I've checked it on several monitoring softwares and there is exactly 11264MB free dedicated GPU memory on the device. windows is running on another GPU and it does not use any amount of the GTX 1080ti memroy. why Bminer reports more than 2GB less free memory on my 1080ti? is there any way to fix this?
Also Bminer 15 doesn't work with my rig because of bcrypt.dll error.
We are working on fix the bcrypt.dll error. Sorry for the trouble.
|
When Crypto-mining Made Fast. @realbminer on TWTR
|
|
|
BTCspace
|
 |
February 19, 2019, 09:25:57 AM |
|
better performance on 2080Ti card ?
to use turing architecture?
|
running farm worldwide
|
|
|
|
jabujax
Newbie
Offline
Activity: 31
Merit: 0
|
 |
February 19, 2019, 01:15:42 PM |
|
Guys how are you able to get 1.2G/s per GTX 1080Ti at stock speed? I am unable to go above 0.6G/s per card with stock Cards are at 50°C, so definitely not an overheating issue. Is here anybody with 6 GTX 1080Ti's on one rig running total at 7G/s? OS: Win 7 x64 Drivers: 416.34 CPU: G3930 I get 1,33 G/s per 1080ti in a 6 card rig all 1080ti, but I'm using linux... It could depends on GPU model. I get from one card 1.3 G/s and from the second only 1.1 G/s. Both on WinX system I am able to get 1.2 G/s per every card, but only for 2 or 3 cards running at one time. When i add GPU 4,5,6 speed of all cards go down to 0.6 G/s. make separate bat files for every gpu. Same problem occured for me i solved like this.
|
|
|
|
jabujax
Newbie
Offline
Activity: 31
Merit: 0
|
 |
February 19, 2019, 01:16:53 PM |
|
> 1070ti on windows 7 for c31 algo. insufficient memory. +1 "Insufficient memory 7847.66 MB available on device" 418.81 drivers
mee too same problem. İs there anyone who can run 1070ti on win7?
|
|
|
|
jabujax
Newbie
Offline
Activity: 31
Merit: 0
|
 |
February 19, 2019, 01:23:04 PM |
|
C29 no crashes, but C31... damn I just woke up, on 187 rigs, thousands of crashes
Yes my rig is crashing too. But in long hours, 9 hours etc. My memory clock -502 , maybe because of this it is crushing long period. 1080ti hash 1.1 gps
|
|
|
|
UnclWish
|
 |
February 19, 2019, 02:42:13 PM |
|
Author, remove "AMD" from name of topic. Your miner didn't support AMD cards.
|
|
|
|
|
bakermining76
Jr. Member
Offline
Activity: 31
Merit: 7
|
 |
February 19, 2019, 02:56:47 PM |
|
Mining C31 with version 15.0.0 for 20 hours on SMOS: Rig 1= 1080 x2 (0/0/150W) + 1080Ti x2 (0/0/225W) with one crash and average 4.34gps in miner. Pool hashrate 4.1gps. Rig 2= 2080Ti x1 (0/0/225W) with no crashes and average 1.91gps in miner. Pool hashrate 1.83gps.
Mining C29 with version 14.3.0 for 24+ hours on Windows 10: One rig a single 2070 (75/750/80%) with no crashes and average 6.17gps in miner. Pool hashrate 5.97gps.
My 2070 would not run C31 on SMOS due to insufficient memory.
Prior to dropping my overclocks, I had stability issues on C31. Also, Bminer can't read the device status for the 2070 on Windows. (SMOS and Gminer on Windows both read it fine, so its not an issue with the card itself).
|
|
|
|
UnclWish
|
 |
February 19, 2019, 03:44:15 PM |
|
Speed is too low on BEAM on AMD cards. Not all pools supported.
|
|
|
|
Spill
Jr. Member
Offline
Activity: 95
Merit: 5
|
 |
February 19, 2019, 05:41:11 PM |
|
Getting this problem what is bad with my config file?
C:\bminer-v15.0.0-e143cb4>bminer -devices amd:1 -uri cuckaroo29://1LXQnVpwha7Up2LDZNdGd8rh3ba3R2dooW@grincuckaroo29.usa.nicehash.com:3371
Error i'm getting? what am i missing?^^^^
[INFO] [2019-02-19T12:33:50-05:00] Bminer: When Crypto-mining Made Fast (v15.0.0-e143cb4) [INFO] [2019-02-19T12:33:50-05:00] Watchdog has started. [INFO] [2019-02-19T12:33:50-05:00] Starting miner on 1 devices [FATA] [2019-02-19T12:33:50-05:00] Undefined but requested solver: cuckaroo29 [WARN] [2019-02-19T12:33:50-05:00] Miner died! It will be restarted soon...
|
|
|
|
george2019
Jr. Member
Offline
Activity: 83
Merit: 3
|
 |
February 19, 2019, 06:49:10 PM |
|
well i tested new gminer 1.33 build for few hours and bminer 14.0 build still has highest average 24 hour hashrate on f2pool, 31g/sec vs only 28g/sec with gminer latest build, bminer itself reports only 27.2g/sec on my rig (4X1080+1X1080Ti TDP 70% memory +500 + some core oc) while gminer has 28g/sec and about same hashrate on f2pool, maybe bminer has some extra tweaks that suits better f2pool, rejected shares is 1% for bminer and 0% for gminer, i think it's something to do higher fidelity in longer periods that bminer has, gminer has less fidelity per GPU than bminer for both 1080Ti and 1080 GPU
|
|
|
|
UnclWish
|
 |
February 19, 2019, 06:49:37 PM |
|
Getting this problem what is bad with my config file?
C:\bminer-v15.0.0-e143cb4>bminer -devices amd:1 -uri cuckaroo29://1LXQnVpwha7Up2LDZNdGd8rh3ba3R2dooW@grincuckaroo29.usa.nicehash.com:3371
Error i'm getting? what am i missing?^^^^
[INFO] [2019-02-19T12:33:50-05:00] Bminer: When Crypto-mining Made Fast (v15.0.0-e143cb4) [INFO] [2019-02-19T12:33:50-05:00] Watchdog has started. [INFO] [2019-02-19T12:33:50-05:00] Starting miner on 1 devices [FATA] [2019-02-19T12:33:50-05:00] Undefined but requested solver: cuckaroo29 [WARN] [2019-02-19T12:33:50-05:00] Miner died! It will be restarted soon...
You've done all right, but miner didn't support amd cards for cuckaroo29/31 algos.
|
|
|
|
|