Bitcoin Forum
July 27, 2024, 11:15:51 PM *
News: Help 1Dq create 15th anniversary forum artwork.
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Odd results with 280x  (Read 678 times)
Things (OP)
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
December 21, 2013, 11:23:01 AM
 #1

Hi all, well I decided to join the bandwagon and get mining (mainly doge just for fun Smiley )

I bought an XFX R9 280x, but seem to be having some really odd issues with it.

I hope it's OK, but since I'm restricted to this forum, I need a bit of help, I've been messing with this for 2 days and got nowhere.

Basically, my hashrates are bad. And not 690Kh from 700KH bad, but I can't even hit 600KH, no matter what I do.

In a nutshell, my setup is a single 280x, with an i3 something (2x 3.4Ghz), 8GB DDR3 RAM and a Antec 620W PSU on a B75M-D3H mobo, running Catalyst 13.9. I am running 2 monitors off the card, but disconnecting them makes basically no difference.

First, I tried all stock settings, 1000Mhz core, 1500 mem clocks, and simply set cgminer (version 3.7.2) to I 13 and let it figure out the rest. Result was about 540KH.

Next I tried setting shaders to 2048, result was about the same. Then I tried walking up the memory clock until it crashed, which was somewhere over 1700Mhz. Rebooted, dropped it down a bit and started walking up the core clock. Hashrate would climb about 4KH with each 5Mhz added, but I never got past about 1100Mhz before crashing, which gave ~550KH.

Did a bunch of googling, trying other peoples settings for the 280x, still can't break 600KH.

Changed -g 2 to -g 1, hashrate increased by about 40KH (wtf, literally EVERYONE else with a 280x uses -g 2??)

Next I tried leaving mem clock stock at 1500 and walking up the core clock. With thread concurrency at 8192, g 1, and clocks at 1080/1500, I've hit 560KH. This is the best I've ever seen it.

My bat file has
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1

in it before the cgminer call.

As a last resort, I tried ramping up the voltage bit by bit, but it wasn't having enough of an effect to make it worth the risk, and no one else has done it apparently, and are getting 700KH+. Temps are all fine at around 60C.

Now for the odd part, no matter what I do, the intensity will NEVER go above 13. If I go above 13, I get hardware errors, or at the best a drop in hashrate.

I have a suspicion something is going on with the GPU allocation however, and here's why:

I also have a 4890 I was using to mine previously, and when that was running at it's full capacity, my desktop was pretty slow and jittery. The 280x, not so much. Hell, I can run furmark at 28FPS AT THE SAME TIME, and don't even get a drop in hashrate.

If I change -g to 2, and set the intensity up, then I start getting a bit of jitter, however the hashrates are still horrible, usually only getting to ~510KH, and also hardware errors.

I've run out of ideas, I have NO idea what's going on. I've had to have tried at leas 30 different config examples from other people running 280x's, and I've never seen it over 600KH, ever.

Please help Sad

Sorry for the long, whiny post. Just don't like spending $380 on a card to find it's under performing by almost half.

Dan
bach
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
December 21, 2013, 12:00:28 PM
 #2

In case it helps, here are some figures I noted while following instructsion in the cgminer GPU readme. They are for my dual ASUS R9 280x DirectCU II TOP cards:

    Engine      Memory      HR              TEMP    RPM     STABLE

    1070        1550        540             72      1620    Y
     868        1550        592
     880        1550        602

     883.5      1550            = *0.57

     885        1550        606
     890        1550        610
     895        1550        614
     900        1550        618
     905        1550        618
     910        1550        625
     915        1550        630
     920        1550        628
     925        1550       
     930        1550        633 = *0.60
     935        1550        640
     940        1550        642
     945        1550        654
     950        1550        658
     955        1550        653
     960        1550        663
     965        1550        657
     970        1550        659
     975        1550        664
     980        1550        662
     985        1550        663
     986        1550        671
     987        1550        672
     988        1550       
     989        1550       
     990        1550        672
     991        1550        670
     992        1550        658
     993        1550        661
     994        1550        640
     995        1550        655
    1000        1550        575
    1005        1550       
    1010        1550       
    1015        1550       
    1020        1550        549
    1025        1550       
    1030        1550       
    1035        1550       
    1040        1550       
    1045        1550       
    1050        1550       
    1065        1550       
    1070        1550       

    1070        1600        >574k           72      1890    Y
    1070        1650        >595k           73      2300    Y
    1070        1700        >700k           
    1070        1750        >720 CRASH
    1070        1800        >732k CRASH
    1070        1825        >737k
    1070        1850        >740k CRASH

    1100        1825        >750k CRASH


The interesting thing is that with the engine/core clock, less is sometimes more as you have no doubt observed yourself.

This is what I've ended up with for now to keep the noise down:

cgminer.exe^
 --scrypt^
 --net-delay^
 -d 2^
 -I 13^
 -g 2 --thread-concurrency 8191 --worksize 256 --lookup-gap 2 --auto-fan --temp-target 80 --gpu-engine 987 --gpu-memclock 1550

Things (OP)
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
December 21, 2013, 12:13:15 PM
 #3

Thanks for that, yeah, I just started playing around with lower clocks after my post and was surprised they really do seem to help!

At the moment my values are 950Mhz core, 1500Mhz mem, with 12000 TC and I13, and I'm seeing about 650KH (Which WU seems to match kinda closely, too). I have read that WU is the value I should really be paying attention to, and basically ignoring the rest. Is this true? What about my thread concurrency? It seems very high compared to others, but if I try your settings, I get less than 100KH!  Huh
bach
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
December 21, 2013, 12:48:29 PM
 #4

What's WU?

I didn't get very far with other thread consurrency settings: TC=1024 and 4096 got HW errors. TC=12288 got some other kind of error.

Should also say that any CPU load reduces my HR by at least 10%.
Things (OP)
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
December 21, 2013, 01:02:30 PM
 #5

Think I'm gonna settle at 945Mhz core clock, 1500Mhz mem, I13, w256 and TC at 11240. Seems to be giving me a stable 650KH Smiley

WU is work utility, which AFAIK is basically how much of your hashrate is actually being accepted by the pool or something of that description, meaning you could have a very high hashrate in the miner, yet low in the pool.

I think that's what it is anyway, but if anyone can clarify, please do Smiley
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!