High number of rejects and HW errors about diablominer HOT 9 CLOSED

What pool?

from diablominer.

Slush's pool with stratum mining proxy.

from diablominer.

Hrm, pool shouldn't effect hardware errors anyhow. Also, poclbm does not detect hardware errors (one of the reasons I wrote DiabloMiner in the first place). Shut your machine completely off for 10 minutes, start it back up with default GPU clocks and default voltage, and then try mining.

from diablominer.

I had already lowered the core clock to its default. I never touched the voltage (only the power limit).

What did the trick was resetting the memory clock. I had lowered it 50% of its default, since that doesn't affect poclbm at all and allows the card to run cooler.

With default memory clocks, I can overclock the GPU core without hardware errors.

from diablominer.

GCN has a limit to memory clocks. 79xx cannot have a memory clock below core clock minus 150, 78xx I believe is core clock minus 100. The drivers usually refuse to let you set it slower than that and set default instead, I guess in your case they did set it too slow.

from diablominer.

CCC has the limit you said, but I'm using MSI Afterburner. You can go as 625 MHz from the default 1250 MHz. Since GUIMiner doesn't report HW errors, it seemed like a good idea at the moment...

from diablominer.

GUIMiner doesn't report HW errors at all. I really recommend not reducing memory clocks below the limit I stated because it is a limit in the hardware itself, not inside the drivers, the drivers will however set it to the default if you input an invalid rate. CCC and MSI Afterburner depend on the drivers and the hardware, and trying to go below the limit will still be enforced by the drivers.

from diablominer.

Sadly. This makes the values reported by GUIMiner rather useless.

I don't know how Afterburner does it, but with "unofficial overclocking" enabled, it's able to clock the memory to 50% of its default. CCC, GPU-Z and Afterburner itself all report 625 MHz memory clock after setting it to that value, and I can verify that empirically (more lagging than with higher clocks).

from diablominer.

This is why no one enables unofficial overclocking mode anymore: it lies. CCC and Afterburner may report a slower speed, but the hardware is running at the default clocks. Someone on the Bitcointalk forums verified this awhile back by measuring power usage of the machine with a Kill-a-watt.

from diablominer.