This made it drop further to 125 Mhash/s and it makes my Windows 7 Aero interface lag.

I thought people lowered the memory clock because it didn't affect their hash rate while simultaneously reducing heat and power consumption.

I don't see any core overclock pushing my hash rate from 160 Mhash/s over 230 Mhash/s... Stock core is 775, so 925 is already a fairly big overclock, and at 925/300 I get 160 Mhash/s.

Posted this in the newbie forum first but got no replies.

I'm currently running my HD6850 at 925/1150 and I get 230-235 Mhash/s. If I lower the memory clock using MSI Afterburner, my hash rate drops correspondingly. If I go all the way down to 300 Mhz, my hash rate drops to around 160 Mhash/s. I have tried tons of different memory clocks in steps of 50-100 between 300 and 1150 and a higher memory clock always gives me a significantly better hash rate. What's up with that? Seems like I'm the only one experiencing this problem.

I use Diablominer with -v 19 -w 128 (gave me the best performance) and -f 30 (so I can play games if needed without closing my miner, when not playing games this setting does not affect my performance).

Anyone know what's up? I'd like to be able to underclock my memory without destroying my hash rate.

My first try was rejected. I only provided my IP address and my password because I figured my password was complex enough (uppercase, lowercase, digits and quite long) but evidently not. On the second try I got kinda frustrated and provided heaps of info, it worked.

I have a HD6850, my miner says 225 Mhash/s and BTCguild says 95 Mhash/s after a few hours. 

I'm trying the Mt Red pool and it seems like every pool reports my Mhash/s to be <100 at all times. I'm thinking something may be wrong with my miner..  or is this normal?

Confirmed Rewards   0.00000000   
Unconfirmed Rewards   0.00000000   
Estimated Rewards   0.00340574      Estimated reward from current round.

After 6 hours of mining on BTCguild! What is this madness? I've seen the Estimated Rewards reset multiple times and according to my miner I've submitted 450 shares, but it seems like nothing is being permanently registered? The site also reports my hash rate at <100 Mhash/s the entire time even though it's 225. It also rejects an unusually high amount of my blocks, around 7% vs 1% on Slush's pool.

Could you explain? Exactly why is their score based system so unfair? If my results are lower than expected then I'm assuming someone else's results are higher than expected..  how can a biased pool like that exist? 

I've been mining an average of 20 hours a day at full capacity (220-230 mhash/s) for about 10 days now and I'm only at 0.9 BTC. My average share per unlocked block is ~0.0027, which is around 1/18000 of the reward. My rig has around 1/8500 of the pool's processing power. What's going on here? Something seems to be cutting my rewards in half, this is WAY lower than expected. Is this pool biased towards more powerful miners? I feel like I'm being scammed here. A friend of mine mines at over 800 Mhash/s on BTCguild, a little less than 4x my speed, and he gets around 1-1.2BTC per 24 hours. I'm very lucky if I can get 0.15 BTC in 24 hours, usually closer to 0.1.

I plan on moving to a different pool after I've reached 1BTC, hopefully that will fix the problem, but I'm wondering if anyone else has experienced this.

Anyone?

Can't post in the hardware section yet..

I'm currently running my HD6850 at 925/1150 and I get 230-235 Mhash/s. If I lower the memory clock using MSI Afterburner, my hash rate drops correspondingly. If I go all the way down to 300 Mhz, my hash rate drops to around 160 Mhash/s. I have tried tons of different memory clocks in steps of 50-100 between 300 and 1150 and a higher memory clock always gives me a significantly better hash rate. What's up with that? Seems like I'm the only one experiencing this problem.

I use Diablominer with -v 19 -w 128 (gave me the best performance) and -f 30 (so I can play games if needed without closing my miner, when not playing games this setting does not affect my performance).

Anyone know what's up? I'd like to be able to underclock my memory without destroying my hash rate.