Wattman is showing 0 when you set it that way, but it's really not 0. (can't be zero  ) I think it's a bug in wattman. Also you need to have vddc offset added in your bios if you want it to work the way you say. There are only a few cards that have vddc offset added in stock bios. |
|
|
|
You got it already, there is a vddc offset already in VOI in this bios. |
|
|
|
|
Yes it's better, but voltage setting by states is not working on every card.
|
|
|
|
To be honest i don't understand what you are talking about and what are you trying to say  On your first picture there is no vddc offset set (0). On the second two there is an offset of -125mV and like i said voltage drops by -125mV on every state. |
|
|
|
Hi, can you add more steps to the offset. My cards are on core 1100 and auto voltage -150 offset is about 925mv but the can handle less then 900. Also isnt it better the clock to be set on all 7 states, because i think the offset is for all states and if the card is stable on the last state with -150 it can crash lets say on state 4 if for some reason the load of gpu drops for a second during mining?
when setting vddc offset that means every state's voltage is changed accordingly to the offset you chose. |
|
|
|
What's the difference between hynix and micron memory and how to check, which I have?
Different manufacturers. You can see in gpu-z |
|
|
|
|
it should run on wine if it supports .net 3.5
|
|
|
|
i won't rewrite it neither for console usage or linux. As wolf said it contains nothing about the VBIOS everyone and their mother doesn't know, so i think anyone could write a console or linux app easily, right ? |
|
|
|
is this question like for real ?  Considering I got effectively 5 different answers, yes, this question is for real. What's your contribution? why do you need licensed windows for mining anyways... ? |
|
|
|
is this question like for real ? |
|
|
|
you won't get warning for mem. errors from the miner Test the card by letting it work for 24h. If it survives 24h its good and stable Hmmm, well the errors im referring to are the ones reported by HWINFO, after dialing it back to 2025 mem freq then they no longer occur at the cost of Hashrate of cause , so you are saying these errors don't matter? well it looks like they don't really affect found shares, or not in a way i'm aware of. |
|
|
|
you won't get warning for mem. errors from the miner Test the card by letting it work for 24h. If it survives 24h its good and stable |
|
|
|
|
we all do, but you can't know that without opening the box and looking at the stickers on the card.
|
|
|
|
|
do what the guys said, if you don't have onboard gpu, plug in another card in pcie 16, boot in windows and flash bad card.
|
|
|
|
i know, i made that easier one , for the simple man |
|
|
|
|
They mean you need to click on the "Strap 1500 to upper" button, and the magic is done for you automatically.
|
|
|
|
@doktor83
Do you know if the tool works with rx 570 powercolor red dragon 4gb card bios?
Im thinking of putting these in a future rig.
Unfortunately i don't have RX5.. cards, so maybe someone here who tried it can help you |
|
|
|
Ok, do GPU Mem errors shown in HWinfo affect the number of found shares ?
I mean more errors mean less found solutions, or it has nothing to do with it?
In my experience,If error in the millions, yes. usally you can see share rate decline and eventuelly a crash a the end. i have millions of errors, and very rarely rejected share. So it looks like its not really a big problem |
|
|
|
Lately too much threads have the word "reward" in their title  |
|
|
|
|
Show Posts
