 Show Posts
|
|
Pages: [1] 2 3 »
|
Hi, I get this error: CUDA error DRIVER: '2' in func 'bminer::cuckoo::CuckooStyleSolverCudaBase::InitializeCudaEnvironment' line 76
[FATA] Fatal cuda error in GPU 11. Terminate soon... bminer 15.7.4 1070 Ti's Windows 10 418.81 update: after restarting the rig, it works |
|
|
|
[FATA] CudaError: Unknown error:C:\WINDOWS\SYSTEM32\apphelp.dll
[WARN] Miner died! It will be restarted soon...
[FATA] CudaError: Unknown error:C:\WINDOWS\SYSTEM32\apphelp.dll
[WARN] Miner died! It will be restarted soon...
|
|
|
|
Grin31 with 1080ti version 14.2.0 give me errors
Insufficient memory 9171,7 MB available on device (#0). unable to run the solver
Miner died!
Me too.. same error same for me; I tried reducing memory usage by desktop without success. I also checked available RAM for the GPU and it was well over 10.5GB same here. |
|
|
|
Did you try to increase your swap file to 50-60 gb and try again?
Now this error appears randomly! [ERRO] [2019-01-27T19:39:46-04:00] Failed to fetch device Status for device id: 2, Error code: 999 [ERRO] [2019-01-27T19:39:48-04:00] Failed to fetch device Status for device id: 1, Error code: 999 [ERRO] [2019-01-27T19:39:49-04:00] Failed to fetch device Status for device id: 3, Error code: 999 [ERRO] [2019-01-27T19:39:51-04:00] Failed to fetch device Status for device id: 4, Error code: 999 [ERRO] [2019-01-27T19:39:53-04:00] Failed to fetch device Status for device id: 5, Error code: 999 CUDA 10 Drivers 417.71 I also experienced this randomly with 14.1.0 too. CUDA 10, 417.71 9 x1070 Ti, 80GB swap file tried with +0 core +0 mem, didn't help psu is oversized (I use it around 50%) |
|
|
|
Can't mine with bminer I always get this message: CUDA error DRIVER: '2' in func 'bminer::cuckoo::CuckarooSolverCuda::Initialize' line 116
[FATA] [2019-01-19T14:42:52+01:00] Fatal cuda error in GPU 11. Terminate soon... W10, nv 416.34, 12x1070 Ti edit: ok, it seems I had too little (80gb) virtual mem. with 85 works fine. |
|
|
|
Hi, I have a problem with a 12 gpu rig. OS: W10 64bit, driver 398.11, ram 8 GB, virtual 80 GB. The first 8 cards initialization is very fast, but then slows down. 9., so-so, but the rest seems stuck. output: http://pastebin.xyz/p?q=UzYyOE8I did not experience this problem with earlier versions (I mean with ewbf for 200,9). Maybe it was not very fast (the initialization), but it was not that bad. |
|
|
|
|
On some algo (e.g. PHI1612), enemy initialize my cards very slowly ( 10+GPU rigs on W10, 390+ ), I mean minutes.
I have experienced this "issue" with ccminer too, but a "--cuda-schedule 12" command solve my problem without high CPU usage (if I use any other number as 12 my CPU usages go to the moon and the system becomes unmanageable).
In enemy, I tried all options:
--cuda-schedule set CUDA scheduling option:
0: BlockingSync (default)
1: Spin
2: Yield
but unfortunatelly did not help (max CPU usage, except with 0).
Can you add the "old / original" --cuda-schedule options?
|
|
|
|
I want to see Darth Vader on the other wall too.   |
|
|
|
Fund Raiser (For Fee Listing Exchange ) Start on 6 March 2018 - End 13 March 2018
Target Exchange Bittrex 1 BTC ...
According to Bittrex
Bittrex does not currently charge a fee for listing a token on our Exchange.
Please do not believe any consultant, advisor, or individual that tells you that they can get your token listed on the Bittrex Exchange for a fee.
|
|
|
|
|
There is a problem with the concept for long term.
There will be no gap for long -> soon, we will not need a bridge.
In places, where is no electric chargers -> there will be very few electric cars -> small market
Anyway, how long does it take to fill a car using household power?
btw nice story bro.
|
|
|
|
blocks per interested time is blocks/hour or blocks per 24hr or whatever timeframe you are trying to figure the reward in. net hash / your hash = your share ( 1 out of XXXX). then take coin amount per block and divide that by your share. Multiply this number by how many blocks/hour the pool is getting on average. then you can multiply the hour average by 24 to get your per day earning estimate.
so lets say the network has 1.9 TH and my miner puts out 2.3 GH. 1,900,000,000,000/2,300,000,000=826.08. so I get 1/826th of the block reward. lets say block reward is 25. so 25/826=.0302 per block in the pool. multiply this by how many blocks per hour the pool finds. lets say they find 25 block an hour. .0302 x 25 = .7566/hour. then multiply the hourly earning by 24 to get a full day estimate. .7566 x 24 =18.15 coins per day estimate.
Edit - obviously you will want to compare more than just one hour to get your pool's average blocks/time. your pool may have had a good or bad hour of couple of hours. always check your block times and hashrate of your pool frequently.
And what happen with this calculation if the net hashrate is low but the difficulty is very high? The case is: when the difficulty is low miners hop and increasing drastically. At this point (increased, high diff) the same (lovelyNH)miners leave the coin. This can be experienced with lot of coins. These are waves. This happened with SIBcoin yesterday: - SIB difficulty drop to low, 300-400 - NH miners ON- Difficulty jumped to ~8600 - NH miners OFFand after loyal miners mined this block (~8640 diff) for 3-4 hours because the net hashrate was very low but the difficulty stucked at very high. Therefore I think, in general, it is better if you do the calculations using the difficulty, not the nethash. It works with most coins: Coins_A_Day = 86400 / (Difficulty * 2^32 / Your HashPerSecond) * BlockReward Highlighted HashPerSecond, it's your hashrate in H/s, not KH/s or MH/s or GH/s. As you know, but: 1 KH/s = 1000 H/s 1 MH/s = 1000000 H/s 1 GH/s = 1000000000 H/s Try it and check the result on WTM. There are some exception, example KMD: Coins_A_Day = 86400 / (Difficulty * 2^4 / YourHashPerSecond) * BlockReward |
|
|
|
Guys what's the estimated initial price?
30k sat I think around 3-7k sat. Maybe start higher but in this case will be dumped by fast hands (-> &diff drop). We'll see. |
|
|
|
It's been a couple of hours stable TDP 50% MEM-502 CORE 0 -i 19
if I add TDP or CORE or -i 20 immediately restarts the PC.
When using x86 it drops too, i have to use x64.
That picture looks terrible
try 18. hardly any hash difference with 19. Thanks for your tip & help reducing intensity helped a lot, my power peaks are gone! But one of my rig now instant restart (since intensity was reduce to 19), I don't know why, with other algos there are no problems. (tried with 0 core -500 mem and 50 TDP also) |
|
|
|
There is. You should use search or browse this topic few pages back and you will found.
Personally, I've got 19 mh/s on 1070, 21 mh/s on 1070ti and 32mh/s on 1080ti, but on 75-80% power limit and with spmod2 version of ccminer.
I'm not getting anywhere near 19 mh/s on my 1070s, at 75-80% power and +100 on the core mine average about 14-15 mh/s. What am I doing wrong? Try using the KlausT version. I used version 8.18 and it worked well. It is faster on other algos also. Thanks, do you have a link? I tried looking for this spmod or whatever and couldn't find it. Google, first result?  https://github.com/KlausT/ccminer/releases |
|
|
|
The low power consumption is great.
But the mining generate very high peaks in power% here (not infrequently 125%, with official ccminer and nVidia cards).
My rigs just shutdown/reset quite often even if I set low core clock and use curve for setting it (and I not set it higher than the factory settings over 900mV).
Also tried with lower mem clock but nothing, my rigs often shutdown.
I using lots of algo and there is no problem with them, but now I'm clueless and don't know how to mine GRLC safely, but efficiently.
Any idea?
I have exactly the same problem on rig 1080ti, rig 1060 are fine. It resets my PC even if I lower TDP 55, mem -500, CORE 0 For other algo, everything is ok. TDP 80 CORE +115 mem -500 / + 500 all stable Also 1080 Ti and 1070 Ti rigs here. I think it's not a power supply problem. E.g.: With 8 1080 Ti the power consumption with max TDP is ~300W * 8 = 2.4 kW. I'm using 2.4 kW server PSU's (little oversized at "normal" usage) what I tested with 2.8 kW (peak) power and there was no problem. + with GRLC, the peaks don't come on every card at the same time. For me the allium algo is a silent killer. Silent because low power consumption and killer because of the extreme high peaks. |
|
|
|
Blockreward 37->15  There were 25 in the past .. |
|
|
|
|
The low power consumption is great.
But the mining generate very high peaks in power% here (not infrequently 125%, with official ccminer and nVidia cards).
My rigs just shutdown/reset quite often even if I set low core clock and use curve for setting it (and I not set it higher than the factory settings over 900mV).
Also tried with lower mem clock but nothing, my rigs often shutdown.
I using lots of algo and there is no problem with them, but now I'm clueless and don't know how to mine GRLC safely, but efficiently.
Any idea?
|
|
|
|
|
