Author

Topic: Randomly Low Hash Rate w/ 7850 (Read 1014 times)

member
Activity: 72
Merit: 10
May 11, 2013, 05:47:31 AM
#8
Whenever your hash rate goes lower than expected, check that absolutely nothing else is running on your system. If you're browsing the web for example, Firefox by default uses hardware acceleration and this can cause a slight drop in hash rate. Video players or flash video (youtube) in the background can also decrease your hash rate significantly. CPU intensive tasks (even if they don't use 100%) can have an impact on your has hash rate as your CPU is what feeds your GPU its workload. You may have already covered all of this, but I figured I'd mention it as whenever my hash rate has strangely decreased, one of the above has always been the culprit.

I hope you get your problem resolved, good luck! Smiley
sr. member
Activity: 308
Merit: 250
May 11, 2013, 04:05:22 AM
#7
I have the same problem with my 7850. Sometimes when I close cgminer and restart it I only get ~15kh/s. Only thing that helps is restarting computer. Works fine after that!
newbie
Activity: 56
Merit: 0
May 11, 2013, 01:14:06 AM
#6
I installed MSI Afterburner and I'm not seeing anything unusual. I was able to get it up to about 255 Kh/s by lowering the clock to 940/1350, but that still doesn't explain the drop in hash rate even though I haven't changed anything else.

EDIT: Yeah it's actually really weird. I restarted CGminer and now it only gets 230 Kh/s at the same 940/1350.
newbie
Activity: 56
Merit: 0
May 11, 2013, 12:38:13 AM
#5
Use a program such as MSI Afterburner to monitor your clockspeeds. You might notice dips or irregularities. These can normally be fixed by increasing the power limit on the cards.

Don't worry about TheSwede75, he is angry at the world.

Thanks, any idea why this would start happening even though I haven't changed any settings from a few days ago?
member
Activity: 98
Merit: 10
May 11, 2013, 12:16:21 AM
#4
Use a program such as MSI Afterburner to monitor your clockspeeds. You might notice dips or irregularities. These can normally be fixed by increasing the power limit on the cards.

Don't worry about TheSwede75, he is angry at the world.
newbie
Activity: 56
Merit: 0
May 11, 2013, 12:10:22 AM
#3
And how does this post belong in the alternate cryptocurrencies forum? Learn to post in the correct forum and someone might actually care to help you.

No need to be rude, I was going to put it in the Mining subforum, but considering that's a subforum of "Bitcoin" and this is specifically a problem about mining scrypt I don't think it belongs there. Also there's another thread in this subforum about a problem with mining.
full member
Activity: 224
Merit: 100
May 11, 2013, 12:07:44 AM
#2
And how does this post belong in the alternate cryptocurrencies forum? Learn to post in the correct forum and someone might actually care to help you.
newbie
Activity: 56
Merit: 0
May 11, 2013, 12:02:04 AM
#1
So I have a 7850 that I've been mining scrypt coins with fairly consistently. I have two "setups", one is at intensity 13 w/ clocks of 980/1350 for when I'm using the computer and the other is intensity 17 w/ clocks of 1050/1350 for when I'm not. I usually get about 270-280 Kh/s with the first setup and 350-360 Kh/s with the second.

Here is my conf file for the first setup:

Quote
{
"pools" : [   

   {
      "url" : "x",
      "user" : "x",
      "pass" : "x"
   },
   {
      "url" : "x",
      "user" : "x",
      "pass" : "x"
   }
]
,
"intensity" : "13",
"vectors" : "1",
"worksize" : "256",
"kernel" : "scrypt",
"lookup-gap" : "2",
"shaders" : "1024",
"thread-concurrency" : "8192",
"gpu-engine" : "980",
"gpu-fan" : "42",
"gpu-memclock" : "1350",
"gpu-memdiff" : "0",
"gpu-powertune" : "0",
"gpu-vddc" : "0.000",
"temp-cutoff" : "85",
"temp-overheat" : "75",
"temp-target" : "63",
"api-port" : "4028",
"expiry" : "30",
"failover-only" : true,
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"gpu-threads" : "1",
"hotplug" : "5",
"log" : "5",
"no-pool-disable" : true,
"queue" : "1",
"scan-time" : "30",
"scrypt" : true,
"temp-hysteresis" : "3",
"shares" : "0",
"kernel-path" : "/usr/local/bin"
}

Everything is the same for the second setup except the intensity and clocks.

Starting about today though, I've been getting much lower hash rates with my intensity 13 setup, around 200 Kh/s. Another problem that popped up today was that it started randomly dropping down to ~20 Kh/s and the only way to fix that was to change the thread concurrency to 8192 (I had it at 12288 before).
Jump to: