 Show Posts
|
|
Pages: [1] 2 3 4 »
|
|
Minor note in version 5.3b, when the GPU stats print for my AMD 580 cards, they note the "cvddc" but are printing the value for the "mvddc". When first coming up, the values are getting set correctly per the log. It's just the periodic GPU stats print that has this mis-labeled.
|
|
|
|
I get the problem even when disabling the first GPU. The overhead is a poor excuse for a miner that is simply outdated. His Zcash miner is even more outdated.
So ... umm ... dont use it? The point is not to disable the first GPU. The point is that have the first GPU have enough extra memory for the OS overhead and still be able to load the DAG. Then the rest of the cards will run fine at 4GB. Disabling the first GPU does not solve the problem and misses the point entirely. |
|
|
|
|
I lost fan control on an MSI 580 with the 19.12.2 version. Once I reach the mid-60's, the fan control goes in reverse until it gets down to 13%. Then the temp goes into the 70's, throttles, and eventually faults. Even setting -fanmin won't stop it from dropping down into the teens. I need to roll way on back. I think fan control is one of the most iffy things about Claymore's miner.
|
|
|
|
Hello and thanks. What i win exactly undervolting the Cards?
Lower power usage and cooler GPU temps. |
|
|
|
|
19.9.2 is out. I hate playing driver roulette but I have some stability issues in 14.7 so I might take it for a spin.
|
|
|
|
|
19.9.1 is out. Anyone try it yet?
|
|
|
|
Does anyone use claymore 15.0?
I got problem with setting up obviously,
Bat script is running properly and it is showing increase in mhs but when I want to monitor through nanopool web site it is showing 0 mhs, anyone with same issue?
When I first started using Claymore years ago, I had the same issue as you. Basically it connected to the right pool but after 5, 15,30, 60 minutes of checking my pools stats it showed 0 MH/s and no shares submitted. The issue was that you need to manually change the epool.txt file with your info. Because by default it mines to Claymore's account. It was confusing because it was my pool but apparently the default Claymore pool was also the same one as mine. Eventually after 60 minutes of mining for Claymore it worked on my ETH address. Most likely this is your issue. Well,all comments considered,the thing I should do is paste into epool.txt : C:\Users\admin\\Downloads\Claymore12\Claymore12\EthDcrMiner64.exe -epool eu1-ethermine.org:4444 -ewall : address -epsw x - strap1 Before that I added -driver install and then reboot pc and then deleted from script and then it looks like above. Now I run the script and mining start but at the begining there is message driver is not installed and with the red letters written message try start the miner with command -driver uninstall and there is 0 mhs at nanopool as I stated before If someone have further instructions what could be issue I would be greatful open a command window in Administrator mode, change to the miner's directory, then execute "EthDcrMiner64 -driver install" from the command prompt. Or "uninstall" if you're removing. Once the driver is installed, you don't have to run in Administrator mode going forward. |
|
|
|
After AMD resolves the driver issue, how many Mhs at 5700/5700 XT are expected?
Claymore might be able to say, but otherwise we're just guessing. I'm going with 54Mh/s for a 5700XT. |
|
|
|
|
Using 14.7, I noticed that on my system if I don't strap a card, the rxboost command doesn't take effect for that card either.
For example, -strap 1,1 -rxboost 30,20 works fine and applies the new refresh timing to both cards.
Bit if I use, -strap 0,1 -rxboost 30,20 the strap is skipped, but so is the rxboost for card 0.
I never see -rxboost applied on card 0 on screen or in the log. I think it's just a command line processing error.
|
|
|
|
Does anyone know which is the last good Polaris driver version before they destroyed performance when re-writing for the 5700XT?
Destroyed performance? I'm running 19.8.1 on all my rigs and my performance is uneffected, if anything they're more stable across 15 Polaris model cards, 580's, 570's, 8GB and 4GB.... Not sure where you're getting the hit. As for the hanging on closing the miner mentioned above... I've seen that when under volting the cards, or trying to push the clock to high, however I do not experience hanging of the miner that often. I have 4 of my own rigs, and have provided support on well over 25 others... and that ranges on memory through all memory types. Very interesting you're experiencing it consistently. 19.4.3 runs fine for me but 19.8.1 runs about 8% lower hash. I know there was a 19.5.2 in there somewhere, not sure if it gets the same degradation. There was talk of lower gaming performance on Polaris with the newer Radeon drivers when Navi support was introduced. It was assumed that it would get worked out. I see the same on my rig using Claymore 14.7 in Win10 1903. Are you running under Windows? Also on mine, the strap and rxboost commands don't work. They say they work, but the values are unchanged and so is the hash rate. So I still have to run a modded BIOS with the straps burned in. |
|
|
|
|
Does anyone know which is the last good Polaris driver version before they destroyed performance when re-writing for the 5700XT?
|
|
|
|
It looks like the -strap command in Claymore is not being applied since both of the views in the AMDMemTweak tool seem to show the same data. So even though he's reporting that the strap was successful, the AMDMemTweak tool seems to show that it was not. Which is why you're not getting a reasonable hash rate ... you're getting the same for both no -strap and -strap 1. What version of Windows are you on? I've had trouble with Win10 release 1903 similar to this. |
|
|
|
Hello guys,
I am experiencing an issue.
I made a new rig with 6 Phantom Gaming D Radeon RX570 8G OC, the memory installed on the cards is Hynix.
They are not bios mod since I wanted to use -strap command directly in Claymore's miner.
I am using Claymore v14.7 miner, with driver 19.4.3 since it is with this driver that Claymore has most tests been performed.
Compute mode ON, with overclocking, I uninstalled and installed the driver in claymore to be able to use -strap command.
And I am mining at 22.5 MHs no matter what -strap I am using.
The strap is applied successfuly : "strap "POL8H1" is applied successfully" on each card.
but the hashrate just refuses to change ! (-rxboost does actually work and allow me to reach 24MHs)
Anyone can help me to get -strap working on my rig and to reach 30+ Mhs per card, maybe by also changing the OC settings?
I will give to the one who provides me with a solution 100$ worth of Ethereum Classic.
I'd suggest running @eliovp's AMDMemTweak tool to see if the strap settings are getting the modifications. Run it without -strap first and note some of the values (tCL, etc) and then run it with -strap to see if indeed they are being applied. There a thread in Mining (Altcoins) just for this program and the executable is up on GitHub. |
|
|
|
|
I assume @Claymore will let us know if the 19.8.1 driver just released fixes the DAG issue he's mentioned that's holding back the Navi cards.
|
|
|
|
how close test mode?
every reset win go in test mode.
c:\windows\system32\drivers\AmdGpuTweak.sys not exist
Look 10 messages back. bcdedit /set TESTSIGNING OFF |
|
|
|
|
Not sure I understand the reference to the file c:\windows\system32\drivers\AmdGpuTweak.sys on GitHub. Where is this file and is it required?
|
|
|
|
With the new XL version, I can only occasionally update the the values on the fly. Most often not. The added tools are nice to have though. My system always fails to read the injected strap ... pops and error dialog box to that effect.
I still regret moving to Win10 1903 as I think that's what took away my ability to modify things real-time, while Claymore is running.
You probably need an option or button to revert out of test mode. Obviously, you can flip into test mode if you don't detect it running but then there's no automated way back out in the XL Win tool.
Edit:
bcdedit /set TESTSIGNING OFF
just in case someone was looking for it.
I've tried to recreate your problem with the straps not injecting .. Just to be clear here, you can only inject a strap at the selected frequency. So if you're currently running your memory at 1900 Mh and you do a modification/strap injection for freq 2000, you're not going to notice any differences. However, that doesn't mean that you should get those error messages. It's the driver that fails to inject the strap. Probably something to do with Claymore's driver Button to turn test mode off has been added to latest release As well as NAVI10 support  Only Strap injection and Power Play support (read from vbios/registry and write to registry for now) Latest versionCheers! Thanks. I'm on Claymore 11.9 so I'm not using his newer strap injection version. I'm only trying to mess with the REF at this point, but other timing regs also refuse to update. I'll d/l the latest and keep at it ... see if I can find the common thread. |
|
|
|
|
With the new XL version, I can only occasionally update the the values on the fly. Most often not. The added tools are nice to have though. My system always fails to read the injected strap ... pops and error dialog box to that effect.
I still regret moving to Win10 1903 as I think that's what took away my ability to modify things real-time, while Claymore is running.
You probably need an option or button to revert out of test mode. Obviously, you can flip into test mode if you don't detect it running but then there's no automated way back out in the XL Win tool.
Edit:
bcdedit /set TESTSIGNING OFF
just in case someone was looking for it.
|
|
|
|
|
I'm going to go with not more than about 56MH/s ... based on memory bandwidth given the algorithm is memory bound.
|
|
|
|
My claymore its working fine but, when I start claymore a message appears in red that says Unknown option 1
It's simple - you must remove option "1" from command line to launch miner. %~dp0 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 :ini timeout /t 20 EthDcrMiner64.exe -epool eth-us-east1.nanopool.org:9999 -ewal 0x3f8c701099e6748bc44938467121d8ff2c165.RGCCS01ETH -epsw x -tstop 75 -ftime 10 -allpools 1 -allcoins -1 -asm 1 -cclock 1090,1090,1090,1090,1090,1090 -mclock 2070,2070,2070,2060,2070,2070 -mvddc 900,900,900,910,900,900 -cvddc 900,900,900,910,900,900 -r 3600 -estale 1 -gser 2 -mode 1 -etha 0 -erate 1 -ttli 75 -y -platform 1 -tstart 60 -retrydelay 5 -mport 3333 -strap 1 -rxboost 1 -mpsw 748 end Could you help me with what I should remove? You're missing the ' 1' after the -y it seems. |
|
|
|
|
