 Show Posts
|
|
Pages: [1]
|
|
That is the thing, I replaced the card with errors with a "STOCK" card, that is not overclocked at all and it still gives millions of errors.
jaja
|
|
|
|
|
Hey All,
I'm a bit puzzled here. I have a rig with 7 cards on an ASUS PRIME Z270-A. Motherboard is powered by 850W PSU with 2 cards and 5 cards are on an 1300W. All are powered via MOLEX risers from the main PSU.
Recently the last card I added (MSI Gaming X RX-580 8gb) to the system started generating millions of GPU memory errors. Initially I thought it was because of it having modified ROM but I took the card to another rig that only has two cards installed and it performs in there flawlessly, ZERO errors for more than 24 hours.
I then added a brand new Sapphire Nitro RX 580 8gb *unmodified* straight out of the box to the original rig and still got errors, in the millions. I then tried an MSI Armor RX-580 8gb, both modified and unmodified. Same thing, million of errors.
I replaced the riser, cables, swapped the molex power around, re-seated the risers on the motherboard, replaced the motherboard riser. Same result... I then DDU all the drivers, reinstalled brand new ones, still same issue. Millions of errors on every card I add, modified or not.
The remaining 6 cards which all have modded ROMS do not generate any errors (maybe one card does like a 100 errors in 24 hours).
So what could be reason for this?
jaja
|
|
|
|
Using the Kill-a-watt meter is the way to go.
A method is as follows:
1) Have the rig setup and running using its nominal mining software settings and the kill-a-watt installed. Start with the full complement of cards. Make a measurement on your N cards.
2) Power down the system and completely remove one card. Setup and run the rig with N - 1 cards.
3) Do 2) till you get down to one card.
4) Plot Power on the y axis versus card number on the x axis. Fit a straight line (ax + b).
5) b, the y intercept will be the non GPU power consumed. Subtract b from the power draw for the full N card system. Divide by N and you have the power draw per GPU.
To save time, I just do this once for a particular MB/GPU/processor combination. The important part is getting the b measurement. As a working assumption, I assume b is constant going forward. For a ASUS Z87 plus with celeron, which runs 5 cards, b is about 25 watts.
That's kind of overdoing it and if you want super accurate numbers it's also skewed since GPU mining also requires some CPU so without cards you get less consumption if the CPU is downclocked. I just assume each rig uses 60 watts and work around that. And since the rig will always be running, it's advised to measure the power consumption at the wall with all the cards being idle (mining software not running) and measure it when mining is running for a while. The difference is your true GPU power consumption. Ok that sounds like a good approach. thank you! jaja |
|
|
|
|
I do have the kill-a-watt plug but for an in-depth analysis it is not good. I can't go an see day-by-day power draw. Plus there are stories of it burning up when used with high wattage use. For that reason I am afraid of using it with my rig.
So are we saying that the on-board sensors in cards are not accurate?
thanks
jaja
|
|
|
|
|
Hi,
Can someone tell me how to calculate the total power drawn by a GPU?
I'm logging various GPU metrics with HWiNFO64 and would like to know which values constitute the total wattage drawn by a GPU. In the log file I'm seeing the following (these were captured while the card was mining):
GPU Core Voltage (VDDC) [V] 1.194
GPU Core Current [A] 78.313
GPU Core Power [W] 93.486
GPU Chip Power [W] 129.578
GPU VRM Voltage Out (VOUT/VID) [V] 1.193
GPU VRM Voltage In (VIN/+12V) [V] 12.125
GPU VRM Current In (IIN) [A] 6.438
GPU VRM Current Out (IOUT) [A] 56.5
GPU VRM Power Out (POUT) [W] 67.25
GPU VRM Power In (PIN) [W] 78
Is the total the card drawing the Core Power + Chip Power? What about VRM? Is there a way to validate the wattage drawn vs Power In/Current In?
I think understanding these values would be really helpful in deciding how to approach overclocking/underclocking of a specific card (based on historic data) instead of taking a shot in dark, right?
thanks
jaja
|
|
|
|
Yes, you can power the VGA inputs from different PSU's. What's important is that all the risers are powered by the same PSU that powers the motherboard. BBT has built more rigs than many of us put together and in several of his videos he adamantly says you MUST set up multiple PSU rigs that way. Otherwise you will create ground loops. The links in my post also explain why you need to set it up that way.
After 5 days of trying to get my 8 GPU rig working by splitting riser power evenly among two PSUs I finally switched and powered all 8 risers with the Master PSU (that is powering the motherboard) and MAGIC HAPPENED! it all started to work... So what is said above is 100% true and highly recommended. The other issue I had is my SLAVE 850w PSU is not sufficient to power 6 cards (I have 2 GPUs powered by MASTER, 6 by SLAVE). Interestingly I built this rig based on a Youtube video where a guy is using 8 Red Devils on two 750w EVGAs and he is splitting both the riser and video card power evenly. I bumped my PSU wattage to 850 x 2 just to be safe when I built my version of it and it is still way insufficient to power 4 cards on the MASTER. Somehow it works for him, but we can't really tell from the video how long that arrangement actually lasted  jaja |
|
|
|
I know this is a very old article but would the solution explained here mitigate the DAG allocation issue? http://cryptoyeti.com/ethereum-mining-gpu-cant-allocate-the-dag-in-a-single-chunk/I'm no expert in crypto currencies but from what I understand as the DAG size grows older cards with less memory will not longer be able to mine and as a result of that the overall network hashrate will drop. Lets put it this way; it will weed out every Tom, Dick and Harry and their grandma from mining on their laptops, old video cards and so on. jaja |
|
|
|
|
Hi,
First post!
I went through few pages of posts about failovers, I also read the readme text file on the same topic and honestly I can't figure out what parameters are mandatory in epools.txt and what is optional. I've had few instances where the failover failed and Claymore exited. So I am trying to find out what is wrong with my file.
here is what I have in the text file:
POOL: us1.ethermine.org:14444, WALLET: 0xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.Jaja1
POOL: us2.ethermine.org:4444, WALLET: 0xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.Jaja1
POOL: eu2.ethermine.org:4444, WALLET: 0xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.Jaja1
POOL: eu1.ethermine.org:4444, WALLET: 0xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.Jaja1
I see the sample/commented out POOL lines have PSW: x, ESM: 0, ALLPOOLS: 0 values in them:
# POOL: eth-eu.dwarfpool.com:8008, WALLET: 0xD69af2A796A737A103F12d2f0BCC563a13900E6F/YourWorker, PSW: x, ESM: 0, ALLPOOLS: 0
For ethermine.org failovers do I need to specify ESM and/or ALLPOOLS?
thanks in advance
jaja
|
|
|
|
|
