I mine with overclocked NVidias. Using poclpm.
I slowly tweak them as high as I can with riva, and I do get "Verification failed. check hardware" as I approach (or rather slightly cross) their limit.  I find it is a good test of how high I can overclock my cards.
dM

Guess my computer's just is really good at fooling Slush's pool, then.

Twice I have run this miner overnight on my PC and twice I have woken up to the CMD window saying "problems communicating with RPC server" or something of the like.

Yes, it was working fine when I left it (i.e. displaying the khash rate).
Bitcoin was still running (with -server) fine.

Os: winxp

not much point using this program if it cannot reliably mine 24/7.
anyone else have this problem?

In linux I issue a

$./poclbm

and get in return

•    AMD Phenom(tm) II X2 555 Processor
[1]   Cypress
[2]   Cypress

yet I have HD 5970 installed, so it should return 2x "Hemlock"no?, or is it really just two Cypress GPU's on same card?

Has anyone actually seen this command query return "Hemlock".

I don't have a 5970, but my understanding is the 5970 is just two 5870s together on one card with an internal crossfire bridge and a slight downclocking. So I think Cypress x2 is the correct report.

I have a weird problem about cpu utilization.

Using 2x HD6950 with 2 separate process the total cpu utilizzation is around 15%. Starting a 3rd process on the 3rd card makes the cpu utilizzation rise to around 40% (13% each process as shown in the task manager). I'm using an i7 920 atm.

For some reason two of my CPU cores are maxing out with poclbm running on my 5970.

Any ideas anyone?

What i was saying is that it uses too much cpu.

OK, first off I need to thank you for making this miner. It's giving me much better performance than DiabloMiner ,which for some reason was giving me less than 40 Million Hashes per second with two 5970's, using all four graphics cores.

However, I'm seeing a huge parade of invalid/stale results when I run the miner, with a few accepted results between them (About 80% of results are invalid/stale). I've tried down-clocking the cores (they are running at 625 MHz now), removing the -v option, removing the -f option, and decreasing the work-unit size. Nothing seems to have helped it much. ATIConfig reports all core temperatures below 70 Celsius. I'm mining with slush's pool.

Any ideas as to why this is happening?

EDIT: I tried using Deepbit instead of slush's pool, and all of the invalid/stale results are gone. Is this something to do with using slush's pool, or does the deepbit server work differently? They say that "no block confirmation is needed", but does that mean that I'm still submitting invalid blocks, and that they aren't checking them?

ANOTHER EDIT: Tried changing drivers to Catalyst 10.11, as I read that was more stable and reliable. I am using it with Stream SDK 2.1. Nothing doing.

UNLIMITED EDIT WORKS: Anyone know of a verification program that I can run to ensure that the OpenCL Libraries are installed correctly? I got the list program to run correctly and return all of the GPU cores, but I don't know if there is one that will tell me whether or not the calculations going on in the cores are valid.

Yes, this was an temporary issue of the pool, bitcoin client crashed for no particular reason. Now it is OK.


Yes, there is difference between those pools. My pool is analyzing every submitted share in realtime and deepbit accept all submits and analyze them later. So the fact that you see more stale shares in my pool is not a bug, it is a feature.

But yes, the thing you reported was an issue of the pool, it's without debate.