• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

help

twinmilll

n00b
Joined
Feb 13, 2014
Messages
14
Hey I just built my pc with a r9 270x. Well I was trying to learn to mine just to see how to do it.

I downloaded Cgwatcher and a litecoin wallet but even with watching youtube I cant manage to get it to work. I go to manage profile and don't understand how to create a path. I thought these forums had some stickies but I couldn't find any.

Any help would be appreciated or a walk through on how to get litecoin mining to work
 
yes thank you. So I got it running 450 khs at 67 degress. I think my graphics card may be artifacting however? my internet explorer has line and missing chunks. I noticed it before mining but it seems that its worse while minning.

Can anyone explain what a good number of accepted shares is?
 
yes thank you. So I got it running 450 khs at 67 degress. I think my graphics card may be artifacting however? my internet explorer has line and missing chunks. I noticed it before mining but it seems that its worse while minning.

Can anyone explain what a good number of accepted shares is?

That graphical distortion is normal while mining as IE is graphically accelerated.

You are looking for a WU/m of about 90% of the kh/s. Rejects are highly dependent on the pool you are mining.
 
thank you for the help. I also was wondering where it says device should i leave it as [0-0] pitcarin or select the [0-1] amd fx 8320?
 
Twinmill,
The important stats to notice in your miner GUI are:
HW (hardware errors - needs to be 0)
WU (work utility - effeciency number, needs to be shadowing your hashrate)
R (rejected, needs to be as low as possible, you will not get a 0% number unless you're on an amazing pool)

Your accepted shares will come along as the miner continues to mine. Leave your device set on your GPU.
 
so I lied I went straight to buying a second 270x lol. But mainly because arma is lagging on my single gpu. So with that being said Any tips on how to set this second car up for mining?

right now Im a little worried because ive mined 4300 shares but 200 were stale? I swapped pools from wemineltc to a futuresouth.us. Should my ratio improve?
 
disable hardware acceleration in your browser...you aren't really using IE are you?
 
Twinmill,
The important stats to notice in your miner GUI are:
HW (hardware errors - needs to be 0)
WU (work utility - effeciency number, needs to be shadowing your hashrate)
R (rejected, needs to be as low as possible, you will not get a 0% number unless you're on an amazing pool)

Your accepted shares will come along as the miner continues to mine. Leave your device set on your GPU.

Only thing I disagree with. Hardware errors, especially at less than 1 per hour, are acceptable in my eyes. Doesn't mean there is anything inherently wrong with the hardware, just that the hash errored out in the memory (could also happen from the ram sticks in your computer). If it means a boost of hashes and/or improves WU, it's ok in my book. It's great if you are rocking zero 24/7 but not a deal breaker if and when they come up, especially if they aren't spitting out at fast rates.
 
My brother has a few cards that, no matter what we do always gets a one to a couple HW errors a day. Still punch out hash like all the right though.
 
It's all fun and games until one of those hardware errors turns out to be a new block you just found...:eek:

Its very easy to get rid of hardware errors altogether. Usually its just a matter of trying a different TC or backing the clock speed off the card by 5-10Mhz.
 
It's all fun and games until one of those hardware errors turns out to be a new block you just found...:eek:

Its very easy to get rid of hardware errors altogether. Usually its just a matter of trying a different TC or backing the clock speed off the card by 5-10Mhz.

I don't get paid for finding a block in the pools I am in so why do I care.
 
Only thing I disagree with. Hardware errors, especially at less than 1 per hour, are acceptable in my eyes. Doesn't mean there is anything inherently wrong with the hardware, just that the hash errored out in the memory (could also happen from the ram sticks in your computer). If it means a boost of hashes and/or improves WU, it's ok in my book. It's great if you are rocking zero 24/7 but not a deal breaker if and when they come up, especially if they aren't spitting out at fast rates.

HW errors almost always indicate a problem with overclock or generally something wrong with your GPU. It's not good to ignore them no matter how high your hash rate is. In my case, I used to get 1 HW error every 2 or 3 days, but that still concerned me. Turns out it was most likely caused by the VRMs overheating on my GPUs. A small reduction to my overclock and voltage that resulted in the loss of about 3KH/s was all that was needed to reduce that to zero.

What good are high hash rates when the information you're sending out is now suspect?
 
HW errors almost always indicate a problem with overclock or generally something wrong with your GPU. It's not good to ignore them no matter how high your hash rate is. In my case, I used to get 1 HW error every 2 or 3 days, but that still concerned me. Turns out it was most likely caused by the VRMs overheating on my GPUs. A small reduction to my overclock and voltage that resulted in the loss of about 3KH/s was all that was needed to reduce that to zero.

What good are high hash rates when the information you're sending out is now suspect?

lol, I've had factory cards spit out HW errors on occasion and VRM temps aren't an issue considering the ambient temps of the cards themselves are sub-60, some even in the 30s. The majority of my cards are undervolted anyway, but like I said, I'm not going to worry about a HW error, even at 1 every few hours if it means a reduction in hash/WU. People blow HW errors completely out of proportion like seeing even one is the devil. Pahlease.

I'm just tired of seeing people parrot the HW has to be 0 bullshit. It doesn't. If you tweak it to the point where you are running at 0, great, but seeing a couple every now and then isn't a deal breaker and hardly means the shares are suspect. Now, if you are getting HW error after HW error, something is clearly wrong with your setup.
 
lol, I've had factory cards spit out HW errors on occasion and VRM temps aren't an issue considering the ambient temps of the cards themselves are sub-60, some even in the 30s. The majority of my cards are undervolted anyway, but like I said, I'm not going to worry about a HW error, even at 1 every few hours if it means a reduction in hash/WU. People blow HW errors completely out of proportion like seeing even one is the devil. Pahlease.

I'm just tired of seeing people parrot the HW has to be 0 bullshit. It doesn't. If you tweak it to the point where you are running at 0, great, but seeing a couple every now and then isn't a deal breaker and hardly means the shares are suspect. Now, if you are getting HW error after HW error, something is clearly wrong with your setup.

Ok Mr. expert. Good luck with that. :rolleyes:
 
Ima have to agree with oblox. I have an ASUS 280x that no matter what I do will spit out errors. I've tried it in different setups, different configs, and no matter what I do (underclock, overclock) it will spit out small amounts of HW Errors. I spent a ton of time trying to troubleshoot and got pretty damn frustrated at one point but now I just deal with it. I'm still pullin 720 Kh/s out of it and the HW Error % is minimal.
 
Every one said any more than 0 hardware errors was unacceptable but no was able to tell me why.

I had my Asus R9 280x overclocked to 1800 mem and it would do about 795kH/s but it would get like 1-5 hardware errors every 24 hours.
 
exactly! I googled all over the place and never got a definitive answer. So I finally just gave up. If your getting your desired hash rate and the HW error rate isn't spitting out instantly (something like 1 every sec) I think you are doing okay.

@Draksia damn! Almost 800?! I have that same 280x. I wouldn't dream of pushing it that hard without cooling with water or something. I'm currently running it at stock clocks with underclock mem. pics or it didn't happen! :D
 
exactly! I googled all over the place and never got a definitive answer. So I finally just gave up. If your getting your desired hash rate and the HW error rate isn't spitting out instantly (something like 1 every sec) I think you are doing okay.

@Draksia damn! Almost 800?! I have that same 280x. I wouldn't dream of pushing it that hard without cooling with water or something. I'm currently running it at stock clocks with underclock mem. pics or it didn't happen! :D

Figures I just overclocked it and i can't get it to do more than 780 or so.

I might play with it a bit see why.
 
In my experience HW errors are usually caused by incorrect thread concurrency setting. Too low and you get HW errors.
 
HW errors can be caused by bad settings as well, EG, take your 290, and set your TC to 5000 and see how many HW errors you get vs 25000
 
Yes this is all very true. I guess I should've mentioned that I also played with the TC. I'm still sticking with my point. Sometimes your hardware just won't cooperate sometimes it will. EG, I recently had to restart my rig with the finicky 280x. Since I started it yesterday, I have gotten no HW Errors a ~24 hour span but I am positive that after a while it will pop up with errors (this is it's MO and its not like its a bad card it just happens). This is all just my experience so YMMV as always.
 
HW are wasted hashing time, that's why it's bad. If you don't mind wasting power and time on errors, by all means shoot for the moon.
 
HW are wasted hashing time, that's why it's bad. If you don't mind wasting power and time on errors, by all means shoot for the moon.

Alternatively, trying to get it to 0 might mean wasting hashing time if you are only talking about a handful over the course of 24 hours. Different strokes for different folks.
 
I've never encountered that situation of balancing hw error to hash. Only time I've ever encountered them is from a bad TC setting.


Except two really old cards my brother has. Those have perfect settings and will still get a hw error once in 24 hours.
 
Back
Top