? Ah ok and why? I see a screenshot with 4 accepted shares for the dev in around 1 minute? So why you think the fee is bigger? now you have to prove your statement. just make a 24 hour video of mining( after count shares )- you will get it Donīt count the shares  you must count the time. Shares depends on luck, for the dev and also for you. The dev can get 1 share in his time or 20 shares, the same happens to you. And why i must make a video? I can read the log files from the miner  |
|
|
|
? Ah ok and why? I see a screenshot with 4 accepted shares for the dev in around 1 minute? So why you think the fee is bigger? now you have to prove your statement. |
|
|
|
Bios Flash with the right vcore. |
|
|
|
Nice update Patrike. One question. The Power Usage is only show if i set "Distplay Profit in addition to revenue" in the general options. Is it normal or a bug?
Right now Awesome Miner only calculates the power usage/cost if profit calculations are enabled - but that's not very user friendly. So I would say it's a bug and I will correct this in the next release so you will be able to display Power without also showing Profit. Thank you for the fast response. |
|
|
|
Awesome Miner Version 5.7.6 ( Development preview of 5.8 ) Features - Significant speed optimizations for the Performance History feature - Performance History also includes estimated revenue and profit - Performance History export to CSV allows selection of data to export - The profit switching setting to ignore pools with no accepted shares can now be configured for up to 20 minutes (was 10 minutes previously) - Diagnostics includes information about MS VC++ runtime versions installed, as these runtimes are required by some GPU mining software Integration - Block Explorer configuration for wallet balance to allow balance unit of 1E-7 and 1E-24 to support a wider range of number formats - New algorithms added to the predefined Yiimp-based pools will automatically be available if the algorithm is known to Awesome Miner - BlockMasters pool configurable for region - Mining Dutch Lyra2REv2 profit unit adjusted to latest API changes - CoinCalculators.io setting for filtering of exchanges will still include coin values for coins without an exchange - Siacoin algorithm changed from Blake2b to Sia, which is a modified version of the Blake2b algorithm API - Added HTTP API for returning the assigned miners and users accounts for each user group (/api/groups/details) - A random HTTP API key can be generated with a button click in the Options dialog Rules - Triggers looking at hashrate and accepted shares can now be configured for looking back at statistics for up to 20 minutes (was 10 minutes previously) - The predefined trigger for Accept Progress will by default be set to 16 minutes (was 8 minutes previously) on new installations User interface - Display of power usage per miner group and as a total for all miners. Configurable via the Options dialog, General section. - Display of power usage for the selected Profit Profile on the Coins and Online Services tabs - Improved user interface for configuring predefined pools for the profit switcher and for custom wallets for miners - Additional coin images added Mining software - CryptoDredge 0.9.6 - T-Rex miner 0.7.3 - Z-enemy Miner 1.23 Corrections - Improved detection of nVidia GPU driver version - Correction to scenario where user defined Online Services are being removed, to ensure no old statistics are listed on the Online Services tab - Correction to the Profit Profile properties, Override section, where the feature to add a new custom pool didn't work correctly in some scenarios - Correction to profit switching with TeamRedMiner where the pool changes wasn't performed correctly - Minor corrections To get access to development versions, open the Options dialog in Awesome Miner. In the General section, enable Check for development versions. Then go to the Menu and click Check for updates Direct download links http://www.awesomeminer.com/download/setupdev/AwesomeMiner.msihttp://www.awesomeminer.com/download/setupdev/AwesomeMinerRemoteService.msi Nice update Patrike. One question. The Power Usage is only show if i set "Distplay Profit in addition to revenue" in the general options. Is it normal or a bug? |
|
|
|
Win10 updates are a complete lottery - disable them via policy manager and only apply them when forced to. If it ain't broke...
Win10 updates are no lottery, make the right settings (i must only change 2 thins in windows) and it will never make an update. I donīt now why all people canīt disable this and make win10 so bad. For me it is better then all other mining softwares (stable, no reboot, higher hash then linux, easier to use for the most people, and i find failure faster and better then in ethos or something like this) My Win10 Rigs run for 3 Month without reboot or restart miner. |
|
|
|
The Sia network hardforked to reject all ASICs on the network except for Obelisk miners on October 31st at a block height of 179,000. I tried to mine it after fork using CCminer on GTX 1070 and had no sucess. Anyone mining SIA on GPU?
I think you can mine SIAcoin with Claymore Miner you check their thread here https://bitcointalk.org/index.php?topic=1433925.0Download the latest Claymore miner and then remove the ethereum pool from the bat script and put your siacoin pool you can also find the guide from the the link above. Why delete ethereum pool from bat script? Your answer is stupid. You cannot mine original SIA with dual Miner. Sia has forked and so claymore must update his miner too. |
|
|
|
hello can anyone help me after the w10 update, every time i reboot the machine to amd lose the cards i can not put the 5 plates anymore the minera ja formatted reinstalled amd drivers but not to being able to put the 5 together again will i have to to put the newest amd drivers? I have 480x which should I use? thank you.
Any errors encountered? HAng? miner error? bluescreen? would greatly help if you could also indicate your current hardware infos the only error that the update of the windos 10 lost my card works only 2, I have pro btc h81, even changing all the riser and only 2 card works after the update of this month of the windos, formatted and recognized all, after updating again he lost again , I put the Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23 driver and it only recognizes 2 and 2 gets problem flagging! windows update mess If roll back couldnt do the trick, i guess you would do a fresh install of windows then do these https://bitcointalk.org/index.php?topic=2878646.0I already tried to disable everything but anyway he does the update a hehehe terror, but thank you all Did you reinstall offline? Yes it was working the 5 cards, but the other day it updated anyway, and lost 3 card only 2 works, I have 2 others and did not give problem only that this in the pro h81btc, I am thinking that the amd drivers but I put another and not worked with the most current, so I do not know which one to use with this Win10-64Bit-Radeon-Software-Adrenalin-Edition-18.3.4-March23 without updating the w10 works the 5 cards, I am now using this Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23 and only recognizes the 2 cards, Just disconnect LAN, reinstall w10, install 18.5.1 driver , turn 365 days in ...Updates/Advanced and than connect LAN and update and do all rest What? Disconnect Lan? Reinstall w10? What the hell? First asking him if he has flashed the bios of his cards. The cards has the yellow flag with error 43? You must use Pixelclockpatcher after installing the driver and then reboot. it has nothing to do with the win version other things. |
|
|
|
Hey JCE, Issue still persists!: For Windows 64-bits
Analyzing Processors topology...
Intel(R) Celeron(R) CPU G3930 @ 2.90GHz
Assembly codename: generic_aes
SSE2 : Yes
SSE3 : Yes
SSE4 : Yes
AES : Yes
AVX : No
AVX2 : No
Found CPU 0, with:
L1 Cache: 32 KB
L2 Cache: 256 KB
L3 Cache: 2048 KB, shared with CPU 1
Found CPU 1, with:
L1 Cache: 32 KB
L2 Cache: 256 KB
L3 Cache: 2048 KB, shared with CPU 0
Detecting OpenCL-capable GPUs...
Found GPU 0, with:
Vendor: Intel
Processor: Intel(R) HD Graphics 610
Device: ff:ff
Compute-Units: 12
Cache Memory: 256 KB
Local Memory: 64 KB
Global Memory: 1592 MB
Addressing: 64-bits
Found GPU 1, with:
Vendor: AMD
Processor: Ellesmere
Device: 06:00
Compute-Units: 36
Cache Memory: 16 KB
Local Memory: 32 KB
Global Memory: 8192 MB
Addressing: 64-bits
Found GPU 2, with:
Vendor: AMD
Processor: gfx900
Device: 09:00
Compute-Units: 64
Cache Memory: 16 KB
Local Memory: 32 KB
Global Memory: 8176 MB
Addressing: 64-bits
Found GPU 3, with:
Vendor: AMD
Processor: gfx900
Device: 03:00
Compute-Units: 64
Cache Memory: 16 KB
Local Memory: 32 KB
Global Memory: 8176 MB
Addressing: 64-bits
Preparing 7 Mining Threads...
+-- Thread 0 config ------------------------+
| Run on CPU: 0 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: generic_aes |
+-------------------------------------------+
+-- Thread 1 config ------------------------+
| Run on GPU: 1 |
| Multi-hash: 1984 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 8 |
+-------------------------------------------+
+-- Thread 2 config ------------------------+
| Run on GPU: 1 |
| Multi-hash: 1984 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 8 |
+-------------------------------------------+
+-- Thread 3 config ------------------------+
| Run on GPU: 2 |
| Multi-hash: 1984 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 8 |
+-------------------------------------------+
+-- Thread 4 config ------------------------+
| Run on GPU: 2 |
| Multi-hash: 1984 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 8 |
+-------------------------------------------+
+-- Thread 5 config ------------------------+
| Run on GPU: 0 |
| Multi-hash: 1120 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 8 |
+-------------------------------------------+
+-- Thread 6 config ------------------------+
| Run on GPU: 0 |
| Multi-hash: 1120 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 8 |
+-------------------------------------------+
Cryptonight Variation: Cryptonight V8 fork of Oct-2018
Low intensity.
Starting CPU Thread 0, affinity: CPU 0
Thread 0 successfully bound to CPU 0
Allocated shared Large Page at: 0000000008400000
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 0 of NUMA node 0 at: 0000000008600000
Starting GPU Thread 1, on GPU 1
Created OpenCL Context for GPU 1 at 0000000007d644b0
Created OpenCL Thread 1 Command-Queue for GPU 1 at 0000000007d64610
Scratchpad Allocation success for OpenCL Thread 1
Allocating big 3968MB scratchpad for OpenCL Thread 1...
Compiling kernels of OpenCL Thread 1...
Kernels of OpenCL Thread 1 compiled.
Starting GPU Thread 2, on GPU 1
Created OpenCL Thread 2 Command-Queue for GPU 1 at 000000000d18a620
Scratchpad Allocation success for OpenCL Thread 2
Allocating big 3968MB scratchpad for OpenCL Thread 2...
Compiling kernels of OpenCL Thread 2...
Kernels of OpenCL Thread 2 compiled.
Starting GPU Thread 3, on GPU 2
Created OpenCL Context for GPU 2 at 0000000007f1ff40
Created OpenCL Thread 3 Command-Queue for GPU 2 at 00000000118530b0
Scratchpad Allocation success for OpenCL Thread 3
Allocating big 3968MB scratchpad for OpenCL Thread 3...
Compiling kernels of OpenCL Thread 3...
Kernels of OpenCL Thread 3 compiled.
Starting GPU Thread 4, on GPU 2
Created OpenCL Thread 4 Command-Queue for GPU 2 at 0000000011852b70
Scratchpad Allocation success for OpenCL Thread 4
Allocating big 3968MB scratchpad for OpenCL Thread 4...
Compiling kernels of OpenCL Thread 4...
Kernels of OpenCL Thread 4 compiled.
Starting GPU Thread 5, on GPU 0
Created OpenCL Context for GPU 0 at 000000001160b0b0
Created OpenCL Thread 5 Command-Queue for GPU 0 at 0000000011598020
Scratchpad Allocation success for OpenCL Thread 5
Allocating big 2240MB scratchpad for OpenCL Thread 5...
Compiling kernels of OpenCL Thread 5...
Kernels of OpenCL Thread 5 compiled.
Starting GPU Thread 6, on GPU 0
Created OpenCL Thread 6 Command-Queue for GPU 0 at 0000000011598190
Scratchpad Allocation success for OpenCL Thread 6
Allocating big 2240MB scratchpad for OpenCL Thread 6...
Compiling kernels of OpenCL Thread 6...
Kernels of OpenCL Thread 6 compiled.
Keep-Alive enabled
Devfee for CPU is 1.5%
Devfee for GPU is 0.9%
21:01:42 | MoneroOcean Mining session starts!
During mining time, press:
h display hashrate for each mining thread.
r display full report.
p pause all.
u pause CPUs.
0-F pause GPU 0-15.
t GPU temperature and fan speed.
q quit.
21:01:42 | GPU Compute allocation starts at 80% and reaches 100% after ~5min,
21:01:42 | during this time, the hashrate may be unstable and inconsistent.
21:01:42 | Let the miner warm-up if you're tuning for performance.
21:01:43 | Connecting to mining pool gulf.moneroocean.stream:10064 ...
21:01:43 | Connected to pool. Now logging in...
21:01:44 | Successfuly logged as //PRIVATE INFO//
21:01: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 . . . You run double thread with 1120 Multihash on the Intel IGPU (GPU 0)? It is not a Miner issue, it is config issue. |
|
|
|
Someone has good settings for MoneroV8 for the RX550? I canīt get a stable hashrate. I have 6 similiar RX550 with same bios. Hashrate is very unstable and mostly 1 card is slower then all other, and this change all 5min. Monero V7 works stable, and with SRB it works stable too, but with srb the effective pool hashrate is 400h slower then the reported hashrate.
Memory is 2Mb? Try this parameters: { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 1, "multi_hash":464 }, { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 1, "multi_hash":464 } Then try to increase both multi_hash parameters untill your card have enough memory or speed became lower even at start. I have RX550 4GB. I tried worksize 8,12,16 and Multihash i tried 400,416,432,448,464,480,496 in many configs. In every Config it jumps up and down. Driver is 18.6.1. With SRB i get stable hashrate at around 2850 hashes. I manage over 150 GPUīs, so i am not a noob ^^ Maybe it is a driver problem? On my other rigs with JCE Miner i have the beta blockchain driver installed and old pitcairn and tahiti cards, there it works perfect. |
|
|
|
|
Someone has good settings for MoneroV8 for the RX550? I canīt get a stable hashrate. I have 6 similiar RX550 with same bios. Hashrate is very unstable and mostly 1 card is slower then all other, and this change all 5min. Monero V7 works stable, and with SRB it works stable too, but with srb the effective pool hashrate is 400h slower then the reported hashrate.
|
|
|
|
OCTOMINER here. We work tightly together with a big AMD factory in China and we have received info that the RX 680 will only perform around 10-15% better than the RX580. Maximum 20% but currently it looks more like 10-15% increase in hashrate and efficiency. Also, around 10% retail price drop incoming for the RX 580 at the end of this month. We will post more here when I get more info and a sample in hand. We will try to be one of the first to also offer OEM RX 680 GPUs bulk to our bigger customers with already modded BIOS loaded onto them. Currently we buy RX 580's BULK directly from the factory with already modded BIOSes, the GPUs perform better than Sapphire Nitro RX580 out of the box. Our OEM RX 580 8G GPUs get 30.5MH/S at 128-130W power draw, we noticed our RX 580's are around 5-10W more efficient than BIOS modded MSI ARMOR RX580 8G. (this is real life power draw, the AMD GPU power measurements from software are not accurate).  30.5Mh / s at 130w? This is to slow and consume to much. Every of my RX570 does 31 - 32 MH @ 0.85 voltage. This consumes less then 130w. I will measure one rig in the next days. |
|
|
|
or run Windows 10. you will no longer have: lower hashrates poor overclocking tools poor bios flashing tools less access to windows only software (certain miners, nicehash, etc) all of the problems you listed for windows are not real problems and easily solved or avoided. Driver problems --> dont install shit drivers and properly uninstall any old drivers (try and tell me how linux nvidia drivers are in any way better/more stable, I'll hear your response when i'm finished laughing)Reliability problems --> again none. this only becomes a problem with people who overclock too much or have conflicting driver versions that werent properly uninstalled Windows update breaking things --> can be turned off without too much trouble. and even ubuntu has pesky update warnings and will auto-install if you dont stop it. linux isnt a magical savior hereRandom blue screens --> doesnt happen on stable setups. see the same point about reliabilityLicensing issues --> windows 10 is free to use. there is ZERO functional change by simply not activating the software. about the only thing you cant do is change the desktop background.  and 152 days uptime on a simple system with 1 GPU thats likely stock clocked?  much wow. very impress . Actually I manage about 1500 GPU rigs. 350 of em are Windows. Guess which ones require the most attention and weekly reboots? (hint: its not linux) My advice comes from having more mining experience than any 500 average people combined on this forum. lower hashrates - no? Go ahead and try and prove it poor overclocking tools - My machines are all upclocked via simple scripts poor bios flashing tools - Polaris BIOS editor works just fine in linux less access to windows only software (certain miners, nicehash, etc) - Nicehash is for the lazy and ignorant and my linux machines each support at least 18 different miners with the ability to add more. There is nothing useful on Windows that doesnt work in linux. P.S. Go count the threads of people with windows problems versus linux and tell me windows is the superior choice.... You manage 1500 GPU Rigs and you must weekly reboot windows? you are a really bad miner. My windows10 runs faster then linux (ethos), more stable than linux, i need no reboot for over 2 month (no miner restarts or what ever). Do the right job, then windows works fantastic. i work with windows 1703, 1803, 1809 and alle works perfect. my windows make no updates, you must find the right solution Windows Hashrate 185mh with 6x RX 570, no hardware errors Ethos Hashrate 178mh with 6x RX 570, i must clock down the cards. with the same speed as in windows, the miner stops working after several hours. This is my opinion and my experience, i am not a linux hater, but i canīt read this shit about windows, from people who do not work properly with windows. |
|
|
|
"us people" are the ones not losing our ass in scams either.
I'll take that.
there's three separate threads here involving some kind of FPGA group buy, and they are all gigantic train wrecks.
This is not a scam as of today. So dont call it a scam. I truly expect to be refunded next week. Do you read discord if you did you would not post it as a scam. What I will say it has been less then desired in terms of running it. I truly do think they will deliver the gear and make the refunds no later then Veterans Day . May I have the link for the Discord channel? thank you I will go to my pc that has the links give me a bit of time. Sorry dude the acorn are scam or what is your explanation that the guy who sell it donīt write anything in this thread here? Oh i must read on discord. Sorry but this is stupid, the seller start this thread here so he have to answer here and not on discord or where else. |
|
|
|
for some reason when i change the default clock speed in the powerplay tab, after i save the bios and flash it.. windows wont install drivers.. code 43.
any ideas?
these cards arent signed.. so its not that.
im trying to OC the card in the bios so i dont have to run any 3rd part programs.
amd pixelclock patcher if you flash your bios you must use this patcher that the amd driver can recognize your card. old and often discussed. |
|
|
|
|
Use SRB 1.6.8 it works, speed is not fast for older cards, but enough at the moment. In 1 or 2 weeks JCE wants to release his GPU miner for V8, then i will use this miner again.
At Monero V7 i switched with 2 Rigs from Claymore 11.3 to JCE, my effective Hashrate is raised from 9000 hashes to 11000 hashes.
|
|
|
|
I started using phoenix from yesterday. Good surprise that i get better hashrate and lower power consumption than claymore. Thought that claymore is good:) Better dev fee too. I'm using linux based miner.AMD OpenCL 16.60 claymore 300.3mhs 715w phoenix (same clocks and green kernels) 304mhs 708w https://hiveos.farm?ref=14664maybe today is few degrees colder Nice joke, but maybe you havent ever tried PM3.5d. For me it is 0.3% higher hash rate, 0.7% lower power consumption and 0.3 lower devfee than Claymore. Not joke, I have such effect if ambient temp drops 5 celsius. Less power a bit and more hash (poolside) I'll try 3.5 and compare but percentage you mention are just tiny better, like same miner with lower fee. Had no improvement on Atis with previous versions but Nvidias did like PM over CM Yes cooler cards use less electricity, this is called physics. A bit more hash is not possible. What you see is a normal daily fluctuation. You need to take the average hashrate of several days, 1 day is not enough to get a reasonable average. |
|
|
|
|
We speak about 1 (in words ONE) fuzzball coin? Really? 0,006 Cent? And you open a thread?
|
|
|
|
Prices seem pretty good? Really? XD use your calculator and your head and re-calculate it |
|
|
|
|
Show Posts
