I recently got my Asus Radeon RX 580 8GB and decided to test it out on mining. It has default core clock speed 1380 MHz, and memory clock 2000 MHz.Now, my first test with stock settings (no OC, no modded bios), I get around 23 Mh/s.Second try with modded bios, without OC, I get merely 26 Mh/s, mostly stayed at 25.9 Mh/s or so.After some researches, I found some other people's settings in Afterburner that claimed to have high hash rate like around 30 Mh/s, so I tried theirs and it only lowered my hash rate a bit, and not increasing it at all. For example claimed 29-30 Mh/s, with his settings applied, I get nowhere near 30. Similarly with, but his settings doesn't get me the same hash rate neither.So I decided to tweak around Afterburner myself, and it seems that my core clock at 1250 Mhz, and memory clock at 2100 MHz can get me up to just 27 Mh/s. If I go higher with those 2 settings, it doesn't affect too much and sometimes even drop down.So here I am, wondering what settings affect the mining performance? Core clock and memory clock? And how do they affect the performance, because it's clear that it's not the higher the better!Another thing I don't understand is with the same settings in Afterburner applied, some users claim they get up to 30 Mh/s, and I reach around 25 Mh/s only.
What's the catch here? Not sure if this question is off-topic, but broadly speaking, there are a few things that affect a GPU's performance given a particular algorithm being executed (for mining Ethereum and otherwise), assuming adequate power being available:.
It has default core clock speed 1380 MHz, and memory clock 2000 MHz. Now, my first test with stock settings (no OC, no modded bios), I get around 23 Mh/s. Second try with modded bios, without OC, I get merely 26 Mh/s, mostly stayed at 25.9 Mh/s or so.
compute performance,. instruction pipeline performance,.
VRAM performance,. chance?. temperature. voltageThe faster the GPU can perform computations, the faster you can get an answer to a calculation.
For example, a pocket calculator is much faster than you are at doing arithmetic. Its arithmetic compute performance exceeds that of your brain. The limiting factor of a pocket calculator is your ability to enter instructions - i.e., how quickly you can give it new work.
That's the instruction pipeline performance. Fetching instructions from your CPU/RAM is slow, so a GPU has its own cache to store instructions. But there is only so much that can fit in there, so it depends on the algorithm as to how much time it spends waiting for new instructions.Also while performing computations, the GPU will likely need to store/access data.
The speed at which the video card's RAM (VRAM) is able to provide that data will affect computations, especially those that require frequent memory access. Changing the VRAM's memory access speed may also change its latency in preprogrammed steps. So speeding up the throughput of your RAM may actually result in decreased performance because latency increases. Different GPUs will have different memory speeds, latencies, and bus widths.Depending on the algorithm and the hardware architecture, the instruction pipeline may have to be flushed frequently, causing the GPU to be briefly idle on the main computation. The effect of this depends on the data that's being operated on (all else equal). Sometimes, that's just pure chance.If the GPU gets too hot, it should slow itself down to prevent overheating. Intermittent spikes in power use while doing heavy computation may also cause involuntary clocking down of one or more components.
It will take some non-zero time to return to the default speed.If the voltage to the GPU's components is too low, you may end up with memory corruption and/or incorrectly executed instructions. This may result in seemingly random errors. In the context of mining, small numbers of errors may manifest as wasted shares (or worse).There are interaction effects between several of these and it's difficult to say what any particular bottleneck you are hitting are.
E.g., changing the ratio of GPU processor speed to VRAM speed (even excluding the effects of memory straps - the latency changes) may result in the GPU and VRAM operating 'out of sync', so to speak, causing inefficient use of resources. This can be affected by the computations being executed. This is why, for example, a program tuned for the use of an FPU on one CPU model might behave relatively poorly on a machine with a faster, but different model CPU.What values are attainable for the hardware aspects also vary from unit to unit. Regarding OC-ing.
I highly recommend downloading the blockchain drivers for your card. I'm using Sapire R9 380 Nitros, using the stock drivers and OC-ing at best I could get 19.5 MH/s but the system was very unstable and was dropping-out way too often. Having installed the blockchain drivers all my cards raised to 21.5 MH/s without any overclocking.
What Is Core Clock Gpu
That said I do have another system mining Electroneum and the blockchain drivers only made a 20 H/s difference. This system I have OC'ed (same cards) and managed to get +65 H/s (on average). It's a strange method but once raising the processor clock and RAM clock I then Lower just the RAM Clock and magic happens! I never pump the RAM to the max speed and then lower it as the system will fail! I find pumping up to 1660MHz on the RAM and then down to 1450MHz gives me the highest Hash rate and stability - but remember every graphics card has its own sweet spots, this is just an example of one of my cards, all are set individually with afterburner (not synced!!)Happy mining people! Hope this info is of some use.
(, 07:04 PM)Martin Wrote: The reset value is valid only for min/max/average values. Current value is not reset and HWiNFO accumulates this counter because whenever the GPU goes idle, the counter is switched off.It's sufficient to restart HWiNFO (or close the sensors window) to reset the current value.That's the problem. It doesn't reset. The max doesn't reset, the average doesn't reset and the minimum doesn't reset.
The current value just keeps steadily climbing. If I close the whole application, delete the files, download them again and install it again it just picks up where it left off.
The ONLY way to reset that sensor is a hard PC reset. The GPU I am using is an Asus R9 280. It's a custom PCB (not sure if that matters). (, 08:57 PM)Martin Wrote: Then it must be the GPU hardware counter that doesn't reset. It should do when the GPU goes idle and you restart HWiNFO. If not, then I'm afraid I can't do anything.It's possible.
Might be something Asus changed on the board design. A friend with an Asus 290 told me that for him this value was basically a random number generator.So i take it that this means the random errors it reports are likely either false positives or a result of something Asus have changed?
(, 09:49 PM)Martin Wrote: Hard to say exactly, but I don't think OEMs can change the way how those errors are measured, they can only do something that causes those errors (bad memory, high timings, etc.).Are you getting the errors at stock settings (clocks+voltages)?How many errors are you getting, does it rise constantly?Do you observe screen artifacts?All stockwhen gaming - about 1 every 2 hours is reportedno screen artifacting. Same with my friend with his 290. He got about 54 without any artifacts.EDIT: I am also using 2 screens so the card's memory clock is always at 1300MHz (5200MHz effective)EDIT 2: I've also tried downclocking but that doesn't change anything. I also can't get Unigine to cause an error to be reported - only games. I've ran OCCT error checker and it doesn't find anything. I don't even understand what these errors are. (, 10:30 PM)Martin Wrote: That's a very low amount of errors, though it should not happen at all with stock settings.
Users pushing memory clock too high or with artifacts are getting hundreds to thousands of errors per second.You might try with a single monitor when the memory clock drops to lowest state and then restart HWiNFO whether the counter resets to 0.I did ask a friend of mine who works in this field and he told me that any type of memory, be it HDDs or Flash, accumulates errors and that is the reason for algorithms being implemented to catch and correct them. I'm still not sure what the nature of these is but from what I've read in the only article I could find - GDDR5's EDC is a sensor that monitors the bus for corrupt data and requests a re-send when it encounters errors. Please correct me if I am wrong.Also - yeah, when I restart HWiNFO with a single screen it resets properly.
Though the 'Reset' button still doesn't work. I'm also using the Portable version if that matters.VRAM is SK Hynix, again, if that matters. (, 10:58 PM)Martin Wrote: Yes, that's right. This EDC counter doesn't differentiate between correctable and uncorrectable errors, so we don't know what kind the reported ones are.Since there are only so few of them, I wouldn't worry about it. If you do, you might try to RMA the GPU.Running with a single display confirms that the hardware counter works properly and resets when the memory clock drops to low state.I doubt I can get an RMA when the system is working fine.
Good Clock Speed For Gpu
I also tried an old DX8 game which requires compatibility mode to work fine on my system (if I don't use it I get a weird bar flickering in the middle of the screen) and the counter didn't notice that at all. Also, I tried to push the memory as hard as I could and got to 2.4GB/3GB usage and that didn't really affect the error rate in any way.
And so far only 3 games have shown to trigger it - Witcher 3, CS:GO and Divinity Original Sin - all of which I run in borderless window. I did run Shogun 2 for 2 hours and it didn't register anything. Yoyo.I'm running a Sapphire R9 390 Nitro. Memory running at stock speed but there is a factory core overclock. I have not noticed any issues with my card until HwINFO recently added ability to detect GPU Memory errors.As I am playing Battlefield 4 or World of Warcraft I accumulate about 50-60 errors also. I am assuming it is normal to have a small amount of errors on these graphics cards?
Since you and your friend are experiencing the same issue and my card is brand new. Although it is disheartening to see any kind of error popping up I won't lie it is giving me the 'OCD eye twitch'.
I considered RMA'ing the card but I haven't noticed any real world performance loss and all benchmarks are consistent with the performance of this card I suppose we just have to no worry about it? Sadly not much solid information on this right now. Perhaps that your card does not have enough capacity to supply chains, such as PSU wires for low current consumption device. The recommended allowable current density of 5 A/mm square.
Gta game download for windows 8. For copper and 3 A/mm square. For aluminum. This is due to the different conductivity of various metals and the value of losses in them. The higher the current the greater the loss in the wires, and cheap PSU manufacturer often saves it in their section. And yet, it can also help - the cause of the error may be interferences in the supply chain and the input line filter will not eliminate them because there is usually a varistor or zener diode bridge in diagonal (in the more expensive models) that limit the noise amplitude.
Multilink LC-filter plants pose rare - inductance power inductors at frequencies 50 - 100 Hz is large enough, and do chokes are quite expensive, but they are better as a technical solution as the slope of the roll-off LC filter unit (oscillating circuit) outside its bandwidth is 20 db per decade and more of them, the greater the attenuation of the filter (the number of its units should be multiplied by 20 db). You can solder as close as possible to the jack load power to break the power wires (they are colored) high-frequency ceramic capacitors are communicating with capacity of 0.1 uF and their body connected to a common wire (black), but they are not cheap, and most importantly they have to look at catalogs of specialized firms. The easiest way to buy and replace the PSU. Put example Chiftec, Delta, Hipper Power, Inwin senior (non-budget) series - they correct circuitry and wires, these plants do not save.