Quantcast
Channel: Mining — Ethereum Community Forum
Viewing all 10806 articles
Browse latest View live

Zealot/Enemy (z-enemy) NVIDIA GPU miner +10% overall

$
0
0
Zealot/Enemy (z-enemy) NVIDIA GPU miner.
x16r, x16s, Bitcore, Phi1612, Xevan and more coming …
=========================================================

Z-ENEMY VER 1.09a ( PUBLIC )

For Windows (Cuda 9.1)
zealot/enemy-1.09a (z-enemy) From: Dk & Enemy

Link: https://mega.nz/#!iK4nUCrD!4NZYaCX9SJVRewFd9hQ8ulA7tF4BmmBiPv5Fb2iSK7s

-Kernel speed improvements, mostly for GTX 1080 Ti (+10% overall)
-Added x16s ( up to 10-20%), faster Bitcore(BTX), faster Phi1612(LUX)
-also made misc miner improvements



- Kernels speed improvements 1.08 vs 1.09a, for all 9x0 and 10x0 GTX:
x16r +5-8%, x16s +5-10%, bitcore +5-8%, xevan +5-20% ( vs basic public), phi + 2-3%, x17 (basic), vit (new algo).

- Support new algos : Xevan (-a xevan) and Vitality (-a vit), recommended intensity for Xevan 19-20, for Vitality 19-21

- "Search mode" is enabled on 1.09a! This means that if you use a low diff you may see extra shares come through on your miner. You may see something like "2 shares" or "3 shares", up to 10+. This is a BONUS!.If you can find more than one share on your scan range you’ll find them all.If you have a bigger farm and use a higher diff you may also see the double or triple shares ,but it will be more rare. I still advise larger farms to continue to use higher diff.

- Revised dev-fee mechanism. Now the miner does not break off connection with a pool and does not drop work of video cards. Everything works without switch-offs.

- Now supporting failover pool! It is now possible to add additional pools incase your main pool loses stratum connection. Here is an example for your .bat file:
z-enemy -a x16r -o stratum+tcp://ravenminer.com:6666 -u RFQXKVKpHMwyJ86YqQUJSZK1S8m8oRbC5h -p d=16 -o stratum+tcp://krawww-miner.eu:3636 -u RFQXKVKpHMwyJ86YqQUJSZK1S8m8oRbC5h -p d=3

- Duplicate output into log file (-l, --log=logfile.txt )

- Better error reporting. Now you see device number with its name if you encounter any cuda errors.

- Pool latency. When submitting shares now you see pool's response time in milliseconds.



Linux ( Hive OS, Ubuntu ) Z-ENEMY VER 1.09a ( PUBLIC )

Cuda 8.0
https://mega.nz/#!VDBEhYAI!j-WB0FzmyO3sBG_NXlmSI7apD89zmUHpgGdZpoAkRNQ
Cuda 9.0
https://mega.nz/#!cDhgGBZS!DKsdS6HdgBr8-O2qvYkKnOya_RiY-N5-xTCwSqcY8_w
Cuda 9.1
https://mega.nz/#!VSY3QAQT!xnJ1e2lMgBKYPY_ytipNtEjpCTkWkj-UmJRcUJzWPBE


First time or troubleshooting x16:
- First time users - ver. 1.08 works on Cuda 9.1 and it is recommended to make sure you've updated your NVIDIA drivers. You can find drivers here: http://www.nvidia.com/Download/index.aspx ver., 390+++
- Next important thing is intensity. We recommend intensity -19 at first, however if your PC has 8GB or more, fast SSD, and big swap file on it you may use -20/21.
- X16r algo is very wild and eratic. *Very important* Make sure to have enough power reserve on PSU. Please be sure you have a minimum 20% headroom on your PSU or set your PL on 70-80% usage.
- Using +core and +mem is useful but, use no OC at first until you verify stability.


Performance and fine tuning x16:
- This release z-enemy 1.08 is reported to be more stable when it using higher PL (90-110%) and +core and +memory overclocking, feel free to experiment with it.
- Updating drivers can provide more gains
- Recommended intensity is 20, set 21 only if you know what you are doing. ( 16GB RAM or/and good SWAP file on SSD) Use caution
- Recommended memory 0 or +
- Recommended core +50+150 ( 1800-1900MHz 1080 Ti)
- Overclock slowly and allow plenty of time to verify stability (12-24hrs) before making anymore adjustments. x16r is a very chaotic algorithm so just because it works for 1 hr doesn't mean you can't crash over longer time. Sometimes hash order can lead to 2000+mhz and crash system. Keep in mind – overclocking is always at your own risk!
- Yiimp pools recommend manual diff (-p d=16) - for small farms or (-p d=48 ) - for good farms like 5-6 1080 Ti If you need to name your rigs as well as set diff you may try -p rigname,d=16

Diff x16 can be calculated by mutliplying the following:
Number of 1060's multiplied by 3-4
Number of 70ti's or 80's multiply by 4-8
Number of 80ti's multiply by 6-12

example: If you have 3 1060's then diff would be 9-12
if you have 8 70ti's then your diff would be 48-96


Dev fee:
- low dev fee 1%
- Dev fee will start randomly when miner is first started. After 1% of time mined then automatically switches back to user pool.

Information about x16:

Every block contain 16 random algos.

All algos have Fast, Medium and Slow speeds so depending on the order and what speeds they are will determine your hashrate at any given time.

Fast: Blake (Blk),Bmw512(Bmw), Keccak (Kck), Skein(Ske), Shabal(Shb), Sha512(Sha)
Medium: Jh512 (Jh5), Luffa (Luf), Cube(Cub), Shavite (Shv), Fugue (Fug), Whirlpool (Wrl)
Slow: Groestl (Gro), Simd (Smd), Echo (Ech), Hamsi (Ham)

Example:
Block 181085, difficulty 20228.532
Hashorder: EchFugBmwShaJh5FugShvEchSmdBmwHamWrlJh5KckSkeHam

Means first algo is Slow Echo (Ech)> next Medium Fugue (Fug) > …> last Hamsi (Ham). The more fast algos in a block is what drives miner speed to the moon! (more MH)


Samples:

Yiimp pools:

z-enemy -a phi -o stratum+tcp://pool.bsod.pw:6667 -u LQCifDiNVXjM_your_wallet_CUqZJBa75p11 -p x

z-enemy -a x16r -o stratum+tcp://yiimp.eu:3636 -u RWgpF9GefjD_your_wallet_1gQmQjpYtYt.GTX950 -p d=3 -i 19

z-enemy -a bitcore -o stratum+tcp://yiimp.eu:3556 -u 1D2dKSprpK_your_wallet_1wa8b2LnJ826uf -p x -i 20

Suprnova pool:

z-enemy -a x16r -o stratum+tcp://rvn.suprnova.cc:6667 -u your_Login.your_worker_name -p x -i 20



FAQ:

I cannot start miner, it says I'm missing msvcr120.dll?
Download and reinstall drivers from http://www.nvidia.com/Download/index.aspx

My miner crashed - cuda error in funk `cuda_check_cpu_setTarget` why ?
This error is caused by overclocking, lower your GPU and VRAM clocks.

Latest drivers recommended?
Yes however, sometimes a new driver can cause an issue and using a previous version may work better. You will need to verify. We recommend at least NVIDIA drivers of 390+++

What is restart-fix.reg in windows download folder?
This file will fix pop-up window and lets the miner restart after crash. Run once.

How many GPU's can I run?
We have confirmed reports on 12 cards

Is there an easy way to auto restart miner if it crashes?
Yes, check our samples *.cmd file in windows build. Like:
:start
z-enemy -a phi -o stratum+tcp://pool.bsod.pw:6667 -u LQCifDiNV_YOUR_WALLET_F3CUqZJBa75123 -p x
goto start

Does z-enemy 1.08 not support api?
Yes, try --api-remote and/or --api-allow= ( simple 0/0 )

Claymore's miner environment variables

$
0
0
In the Readme file of Claymore's miner I read the following:

For AMD cards, set the following environment variables, especially if you have 2GB cards:

GPU_FORCE_64BIT_PTR 0
GPU_MAX_HEAP_SIZE 100
GPU_USE_SYNC_OBJECTS 1
GPU_MAX_ALLOC_PERCENT 100
GPU_SINGLE_ALLOC_PERCENT 100

Are these environment variables required for Nvidia cards as well, and where can I find the description of these variables?

Asus B250 Mining Expert weird hashrate fluctuations

$
0
0
I notice that my Asrock H110 mining rigs run way more stable than my B250 mining expert rigs.

I decided to swap my motherboards between the rigs and the problems moved with the motherboard.
My hashrate jumps all over the place. (from 50mh/s to 380 mh/s on 13 RX 580 cards)

Has anyone else noticed weird hashrate consistency issues with the B250 mining expert board?
Anything I can change in the bios to fix this?

Ethereum valuation

$
0
0
Hi All

I have recently started up a blog which has my approach on how to value Ethereum, it has a lot of detail on mining costs analysis.

http://www.digitalassets.blog/ethereum-valuation/

For those of you that don't want to read it, by my estimations it currently costs around US$570 to produce one Ether coin.

I'd value your comments

Asic Miners - Baikal Giant B, Giant N, Ebit e10, Pangolin m3 etc.

Atikmdag Patcher 2.0.1

$
0
0
Version 2.0.1 is compatible with Catalyst 15.12 to Crimson 18.2.3. It can be used with future versions if it finds the limits you need.
Getting started:
Run atikmdag-patcher.exe.
If all limits are found, click "Yes" to patch and sign. If a limit is not found or if multiple matches are found, the patcher needs to be updated.
Reboot.
To restore the unpatched driver, run the patcher again and click "Yes" to restore from backup.



Known issues:
Legacy drivers may have issues with HDCP and video acceleration with the patch.
Workarounds for video playback issues with legacy drivers:
Disable hardware acceleration in the Flash Player settings (right-click on any Flash video and click "Settings...").
Use the Codec Tweak Tool to disable DXVA hardware acceleration under "Various Tweaks" (in the "Miscellaneous" section).
AMD/ATI cards have a design limitation unrelated to the patch that causes video acceleration to scramble the screen if the vertical blanking/total is below standard with the video card's memory overclocked or with multiple monitors connected. Skype is known to trigger this problem. Either don't overclock the video card's memory, or use the "LCD standard" vertical blanking/total in CRU.
AMD/ATI cards require the "LCD standard" vertical blanking/total to reduce the memory clock when idle. Horizontal values can still be reduced if necessary.


Download:

Link1_GitHub: https://goo.gl/eqQ2aW
Link2_Mega: https://goo.gl/nbhyg5

My 700 TH/s Bitcoin Farm, LEH, J&K,INDIA

$
0
0


hello guys finally 3 months long build completed and today we had our 1st run



LOCATION : LEH, J&K, INDIA
REASON : one of coolest place in India
Electricity : 0.2 INR/KWH
Temperature : -10 C ( https://www.google.co.in/search?q=leh+temperature )

INTERNET : as fucking India blocks internet access for us, we used 4G router [ TP-Link Archer MR200 AC750 Wireless Dual Band 4G LTE Router ]

AMAZON LINK : we have around 50 miners ( 5 routers X 10 Antminer S9 )


CURRENT SETUP :

50 X Antminer s9
11 X Antminer L3+
2 X Antminer D3
3 X ( 8 x 1060 3 GB RIGS )


MONITRING :
MONITORING ALL SYSTEMS USING RASPBERRY PI

WITH THIS SOFTWARE
https://goo.gl/YxAZ12





PICS COMING SOON, once ventilation work is done !


CURRENT : PROBLEMS

1> MOISTURE + MIST IN ENVIRONMENT
2> Wirings Are Not Good, Was Using Aluminium, switch to copper soon
3> 4% of antminer die, each month

PolarisBiosEditor_universal


Claymore's CryptoNote Windows CPU Miner 4.0

$
0
0
Claymore's CryptoNote Windows CPU Miner
=========================
GPU version is here:
MEGA | https://mega.nz/#!zO4hUT4D!FjgZY-2LVtxUMOIZUqI4UTlTeb2sEXbS3JV3MZ3HSMQ
Current version: 4.0
- removed devfee, miner is completely free now.
- added "-pow7" option to support Monero hardfork, use "-pow7 1" value to enable it.
Link:
MEGA | https://mega.nz/#!6OgjEDiZ!Ym90Em1xfhIx9UkX-QKVDvdAivWTVUlQwE7KiwAHyEU
This is POOL version.
This version is for Windows x64, Windows x86 is supported up to v3.4 only. No Linux support planned.
This version uses AES-NI if CPU supports it, but also works with older CPUs that don' support AES-NI.
Since v4.0 this miner is completely free and has no developer fee.
COMMAND LINE OPTIONS:
-o pool address. Both HTTP and Stratum protocol are supported. You can specify several "-o" parameters to use several pools, or use "pools.txt" file, or use both.
First pool specified via "-o" option is main pool: miner will switch to main pool every 30 minutes.
Miner also supports SSL/TLS encryption for all data between miner and pool (if pool supports encryption), it significantly improves security.
To enable encryption, use "ssl://" or "stratum+ssl://" prefix (or "tls" instead of "ssl").
-u your wallet address.
-p password, use "x" as password.
-t number of threads. "-t 0" - autoselection. Autoselection does not work fine in all cases, so try different values.
Optimal value depends mostly on L3 cache size.
For example, if your CPU has 8 MB of L3 cache (i7 CPUs), use "-t 4". For 6MB L3 cache (i5 CPUs) use "-t 3".
-pow7 option to support Monero hardfork, use "-pow7 1" value to enable it.
-lowcpu low CPU usage mode. In this mode only one CPU thread is used but the speed is much higher than in "-t 1" mode.
This mode is useful for mining in background when minimal CPU usage is required instead of maximal mining speed.
Possible values are "-lowcpu 1" or "-lowcpu 2". For example, on i7 4770 CPU "-lowcpu 2" shows about 180 h/s on a single CPU thread.
This option is available only for CPUs that support AES-NI.
-ee close miner if no more pools are available in the list. By default, miner tries all pools one by one, after last pool it tries first pool again and so on.
Use "-ee 1" to close miner when it tried all pools, so you can restart it from some script and do some additional actions related to internet connectins if necessary.
-dbg debug log and messages. "-dbg 0" (default) - create log file but don't show debug messages.
"-dbg 1" - create log file and show debug messages. "-dbg -1" - no log file and no debug messages.
-r Restart miner mode. "-r 0" (default) - restart miner if something wrong. "-r -1" - disable automatic restarting. -r >0 - restart miner if something
wrong or by timer. For example, "-r 60" - restart miner every hour or when some worker thread failed.
-retrydelay delay, in seconds, between connection attempts. Default values is "20". Specify "-retrydelay -1" if you don't need reconnection, in this mode miner will exit if connection is lost.
-ftime failover main pool switch time, in minutes, see "Failover" section below. Default value is 30 minutes, set zero if there is no main pool.
-mport remote monitoring/management port. Default value is -3333 (read-only mode), specify "-mport 0" to disable remote monitoring/management feature.
Specify negative value to enable monitoring (get statistics) but disable management (restart, uploading files), for example, "-mport -3333" enables port 3333 for remote monitoring, but remote management will be blocked.
You can also use your web browser to see current miner state, for example, type "localhost:3333" in web browser.
Warning: use negative option value or disable remote management entirely if you think that you can be attacked via this port!
By default, miner will accept connections on specified port on all network adapters, but you can select desired network interface directly, for example, "-mport 127.0.0.1:3333" opens port on localhost only.
-mpsw remote monitoring/management password. By default it is empty, so everyone can ask statistics or manage miner remotely if "-mport" option is set. You can set password for remote access (at least EthMan v3.0 is required to support passwords).
-colors enables or disables colored text in console. Default value is "1", use "-colors 0" to disable coloring. Use 2...4 values to remove some of colors.
-v displays miner version, sample usage: "-v 1".
CONFIGURATION FILE
You can use "config.txt" file instead of specifying options in command line.
If there are not any command line options, miner will check "config.txt" file for options.
If there is only one option in the command line, it must be configuration file name.
If there are two or more options in the command line, miner will take all options from the command line, not from configuration file.
Place one option per line, if first character of a line is ";" or "#", this line will be ignored.
You can also use environment variables in "epools.txt" and "config.txt" files. For example, define "WORKER" environment variable and use it as "%WORKER%" in config.txt or in epools.txt.
SAMPLE USAGE
unsecure connection:
NsCpuCNMiner64.exe -o stratum+tcp://mine.moneropool.org:80 -u 449TGay4WWJPwsXrWZfkMoPtDbJp8xoSzFuyjRt3iaM4bRHdzw4qoDu26FdcGx67BMDS1r2bnp7f5hF 6xdPWWrD3Q3Wf7G6 -p x
SSL/TLS connection:
miningpoolhub (this pool detects encryption automatically so it uses same port as for unencrypted connection):
NsCpuCNMiner64.exe -o ssl://us-east.cryptonight-hub.miningpoolhub.com:20580 -u YourLogin.YourWorker -p x
Do not forget to specify your wallet address!
FAILOVER
Use "epools.txt" file to specify additional pools. This file has text format, one pool per line. Every pool has 3 connection attempts.
Miner disconnects automatically if pool does not send new jobs for a long time or if pool rejects too many shares.
If the first character of a line is ";" or "#", this line will be ignored.
Do not change spacing, spaces between parameters and values are required for parsing.
If you need to specify "," character in parameter value, use two commas - ,, will be treated as one comma.
Pool specified in the command line is "main" pool, miner will try to return to it every 30 minutes if it has to use some different pool from the list.
If no pool was specified in the command line then first pool in the failover pools list is main pool.
You can change 30 minutes time period to some different value with "-ftime" option, or use "-ftime 0" to disable switching to main pool.
REMOTE MONITORING/MANAGEMENT
Miner supports remote monitoring/management via JSON protocol over raw TCP/IP sockets. You can also get recent console text lines via HTTP.
Start "EthMan.exe" from "Remote management" subfolder (Windows version only).
Check built-in help for more information. "API.txt" file contains more details about protocol.
PERFORMANCE
About 280 h/s on i7-4770 ("-t 4")
About 170 h/s on i5-4430 ("-t 3")
32bit version is slower than 64bit version in 1.5-2.0 times, about 190 h/s on i7-4770.
TROUBLESHOOTING
For most cases miner shows detailed error messages with explanations. To achieve maximal mining speed, start miner with admin rights once (miner must show "scfg: 1"),
it will configure system for optimal performance; then reboot computer to apply changes. For normal work no admin rights or other permissions are required. However,
if you use Windows UAC and start miner as admin in non-elevated mode miner will not work. Either create normal user and start miner there, or disable UAC.
Miner must show "FAST MODE ENABLED" message if everything is ok.
Sometimes reboot is necessary to clean RAM, otherwise miner can show "not enough memory" error.
Low speed in Windows 8.1 x64:
1. Make sure you are logged as admin. Create shortcut for NsCpuCNMiner64.exe on desktop.
2. Open shortcut properties, and specify command line parameters, for example:
C:\miner\NsCpuCNMiner64.exe -o stratum+tcp://mine.moneropool.org:80 -u 449TGay4WWJPwsXrWZfkMoPtDbJp8xoSzFuyjRt3iaM4bRHdzw4qoDu26FdcGx67BMDS1r2bnp7f5hF 6xdPWWrD3Q3Wf7G6 -p x
3. Press "Advanced" button, check "Run As Administrator". Also disable UAC and reboot (perhaps this step is not ncessary for your configuration).
4. Start shortcut, I get about 290 h/s on stock i7-4770 in Windows 8.1 x64.

PhoenixMiner 2.9e

$
0
0
Changes in version 2.9e (since 2.8c):

• Substantial improvements in the kernels for AMD GPUs, providing higher hashrate, lower percentage of stale shares, and slightly lower power consumption. The new kernels are used by default for AMD GPUs. You can still revert to using the old kernels with -clnew 0
• Note that the optimal -gt values for the new AMD kernels may be different than before (but should be in the same ballpark)
• Added alternative (-clkernel 2) kernels for AMD RX550, RX460/560, and 285/380. Just like the alternative kernels for Polaris (RX470/480/570/580), sometimes these can give you higher hashrate than then default (-clkernel 1) kernels.
• Added optimized kernels for AMD RX550, based on the Baffin kernels (but we can't test them as our RX550 turned out to use Baffin cores, so please let us know if they work for you)
• New Nvidia kernels, providing higher hashrate and much lower percentage of stale shares. You can still revert to using the old CUDA kernels with -nvnew 0. The mining intensity (-mi) is by default 12 when using the new Nvidia kernels and 10 for the old kernels
• New -clf parameter to control how often the OpenCL (AMD) kernels will sync (0 - never, 1 - sometimes (default), 2 - always). Try this if you have unstable hashrate on AMD GPU but in general, it is best to leave it alone
• New -nvf parameter to control Nvidia kernel sync frequency (it is similar to the -clf parameter for AMD cards). Try -nvf 2 if you have permanent hashrate drops after pausing and resuming mining on Nvidia cards
• Added -logfile parameter to be able to set the name of the logfile. If you place an asterisk (*) in the logfile name, it will be replaced by the current date/time to create a unique name every time PhoenixMiner is started. If there is no asterisk in the logfile name, the new log entries will be added to the same file. If you want to use the same logfile but the contents to be overwritten every time when you start the miner, put a dollar sign ($) character in the logfile name (e.g. -logfile my_log.txt$).
• Added -logdir parameter to specify different folder for the logfiles
• Added -logsmaxsize parameter to specify the max size of the log files (200 MB by default, 0 to turn off the automatic removal of oldest log files)
• Added detection of AMD Compute mode in the supported drivers and GPUs. The detection is performed when the miner starts and if the Compute mode is off on some of the GPUs, you will get warning messages.
• Added console command 'y' to turn on the AMD Compute mode if it is not turned on on some of the cards.
• Fixed a problem with miner restart on some CUDA errors with Nvidia cards when the miner crashes instead of restarting.
• Many small fixes and changes

PhoenixMiner is fast (arguably the fastest) Ethash (ETH, ETC, Muiscoin, EXP, UBQ, etc.) miner that supports
both AMD and Nvidia cards (including in mixed mining rigs). It runs under Windows x64
and has a developer fee of 0.65% (the lowest in the industry). This means that every 90
minutes the miner will mine for us, its developers, for 35 seconds.

The speed is generally faster than Claymore's Ethereum miner in eth only mode
(we have measured about 0.4-1.3% speed improvement but your results may be slightly lower or
higher depending on the GPUs). To achieve highest possible speed on AMD cards it may be needed
to manually adjust the GPU tune factor (a number from 8 to about 400, which can be changed
interactively with the + and - keys while the miner is running).

If you have used Claymore's Dual Ethereum miner, you can switch to PhoenixMiner with
minimal hassle as we support most of Claymore's command-line options and confirguration
files with the notable exception of the dual mining feature (yet).

Please note that PhoenixMiner is extensively tested on many mining rigs but this is the
first public release and there still may be some bugs. Additionally, we are actively working on
bringing many new features in the future releases. If you encounter any problems or have
feature requests, please post them here (in this thread). We will do our best to answer in timely
fashion.

Screenshot:




You can download PhoenixMiner 2.9e from here:

DOWNLOAD

Why I cannot see the transaction to my wallet after 1 day?

$
0
0
I got paid yesterday, but still I cannot see the transaction is valid or occurred...anything I should do? I am working in this pool for almost a year, without making a penny!

Undervolting issue on PULSE RX 580 with any values

$
0
0
Hi :#,

So I'm using the blockchain drivers from last year and I'm trying to undervolt using Claymore. I have only installed the drivers from device manager for Display Adapters and not used AMD software or anything.

I started with:
- cvddc 850
- cclock 1170
- mclock 2125

And I get random hangs from GPUs even for higher values of cvddc, even if those are getting very close to the default value. GPUs start having issues as soon as 20-30 minutes.

Seems to be running fine (for weeks) only with:
- cclock 1170
- mclock 2125

But I kind of need a bit of undervolting.


Also I'm not using the following parameters for Claymore:

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100


Anything that I could be doing wrong here?

Thanks,

Cracked the code. rx580 @ 48 mh/s

Cleaning Up This Forum... NEW MEMBERS, PLEASE READ.

$
0
0
Most of you already know that our forum has grown a lot, almost 100 new members a day. The forum is being flooded with a ton of discussions, most of which have already been talked about. I understand new members are trying to learn and need help, but now there is way too much clutter. I have to start deleting repeat posts.

To new members, please use the search bar for any question you may have BEFORE posting it, most likely your question has been asked before and you'll find an answer there. Just use keywords, go through the posts, and do research.

If anyone sees a post that is spam or a repeat topic, mark it as spam or PM the link to it and I'll take of it.

Thank you everyone...It's great to see our crypto community growing so much :)

MS Windows 10 : 1809 Feature Update - Avoid!

$
0
0
If you are a MS Windows user then avoid the Windows 10 Feature update 1809.

I have just been through a massive amount of pain and rolled back.

It is quite clear that Microsoft to not test with AMD Drivers.

I had massive amounts of stuttering and instability.

Well done Microsoft for not testing one of the most used component/driver in the market!

HWinfo64 no memory errors detection

$
0
0
Hi everyone!

On HWinfo64, I got "0" memory error from my 4 Sapphire RX 570 8GB GPUs but on ethermine's dashboard I got up to 8% stale shares. The current hashrate is very random also, it goes from 83,+ MH/s to 136,+ MH/s for a reported hashrate of 121,+ MH/s (reported on claymore also).

>> Hardware:
- MoBo: gigabyte H110-D3A
- CPU: Intel Celeron G3900
- RAM: Corsair Vengeance LPX 4GB DDR4
- SSD: Kingston A400 120GB
- GPU: 4x SAPPHIRE NITRO+ RX 570 8GB (3x Hynix and 1x Micron)
- 6 pins powered risers
- PSU: 2x Seasonic X-750 Gold

>> Software:
- OS : Windows 10 64-bit (18 GB virtual memory + registry tweaks)
- GPU driver: Adrenalin Edition 18.3.3
- Miner: Claymore 11.7 No-dev-fee
- OC: OverdriveNtool

>> GPUs mod:
- Polaris 1.6.5 one click timing patch
- GPU OC:
> Micron Memory: 29,+ MH/s
gpu core: 1150mhz / 850mV
memory: 2050mhz / 850mV
> Hynix Memory: 30,+ MH/s
gpu core 1150mhz / 850mV
memory: 2175mhz / 850mV
- Dual mining ETH (ethermine.org pool) + DCR (suprnova.cc pool, 3% of rejected shares generally)

When higher OC, I got errors on claymore only (or freeze) but still "0" error on HWinfo64.

I tried older versions of HWinfo64 and the latest Beta version without any change.

Anyone knows how to fix this HWinfo64 sensor problem please?

Application EthDcrMiner64. has been blocked from accessing Graphics hardware.

$
0
0
Hi!

I´ve built a mining rig consisting of roughly this hardware:

MoBo: MK MSI Z170A-S02
CPU: Intel Core i3 6100 3.7 GHz 3MB
RAM: 8GB DDR4
HDD: SSD
PSU: 1200W
GPUs:
5x ASUS ROG STRIX GeForce GTX 1070 8GB GAMING OC
1x EVGA GeForce GTX 1070 8GB ACX 3.0 FTW Gaming

I´m running Windows 10 Pro and NVIDIA driver version: 384.76. I´m mining with Claymore´s Dual miner 9.7 and I´ve been altering between Eth+SIA and Eth+LBRY.

To tweak my performance I´ve tried to follow the various tips and trix on this forum and anywhere else I could find them (a big thanks to those who contribute). I´m reaching 30MH/s Ethereum while dual mining LBRY on around 28.5MH/s per card. I´m using GPU Tweak 2 for clocking and I´ve right now got the memory up by 700mhz and the GPU clock down by 50mhz.

There seem to be only one thing left that irritates me and that keeps restarting my miner on irregular intervals and it´s this system log message:
Application EthDcrMiner64. has been blocked from accessing Graphics hardware.

From what I´ve read people recommend making exceptions to windows defender, I´ve tried both exceptions and disabling it the hard way (all the services are now disabled) but I still see this message.

I´ve seen recommendations of updating the drivers and windows update but I´ve grabbed the latest win update and NVIDIA driver from earlier this month so should be OK I guess.

Anyone have any tips on what I can do to get rid of this issue?

Cheers,
Chris

ETH Mining Rig Help Please :-) XFX R9 390 / WIN10 / Claymore's

$
0
0
I had been running my 5 card (XFX R9 390) Windows 10 rig since December of last year with no issues, just an occasional reboot every few weeks. However, on 5/16/17, I decided to move the rig into another room because of the heat. When I turned it back on, the mining cards were no longer firing back up. :/

(Note: I am only mining ETH using Claymore's dual miner (v. 7.3) within an Alpereum mining pool.)

When I connect my monitor, I find that EthDCRMiner64 continues to auto-boot as it should, but then shuts down shortly after the DAG creation process causing the miner to reboot.

I noticed the following message within the Windows 10 Action Center: 'Application EthDcrMiner64, has been blocked from accessing Graphics Hardware'.
Also, within the update history, it shows a driver update had occurred for the video cards on 5/16/17; ref. pictures.

I am finding several different videos on YouTube for resolving this error, but I don't think any are related to my particular circumstance.

I would appreciate any help from the expert user community. Thanking you in advance. :)

-Brian






Atikmdag Patcher 2.0.1

$
0
0
Version 2.0.1 is compatible with Catalyst 15.12 to Crimson 18.2.3. It can be used with future versions if it finds the limits you need.
Getting started:
Run atikmdag-patcher.exe.
If all limits are found, click "Yes" to patch and sign. If a limit is not found or if multiple matches are found, the patcher needs to be updated.
Reboot.
To restore the unpatched driver, run the patcher again and click "Yes" to restore from backup.




Known issues:
Legacy drivers may have issues with HDCP and video acceleration with the patch.
Workarounds for video playback issues with legacy drivers:
Disable hardware acceleration in the Flash Player settings (right-click on any Flash video and click "Settings...").
Use the Codec Tweak Tool to disable DXVA hardware acceleration under "Various Tweaks" (in the "Miscellaneous" section).
AMD/ATI cards have a design limitation unrelated to the patch that causes video acceleration to scramble the screen if the vertical blanking/total is below standard with the video card's memory overclocked or with multiple monitors connected. Skype is known to trigger this problem. Either don't overclock the video card's memory, or use the "LCD standard" vertical blanking/total in CRU.
AMD/ATI cards require the "LCD standard" vertical blanking/total to reduce the memory clock when idle. Horizontal values can still be reduced if necessary.


Download:

Link_Mega: https://goo.gl/HVzVbv

Cracked the code. rx580 @ 48 mh/s

Viewing all 10806 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>