Topic: Back to "100% of processor" problem (Read 1043 times)
And yes, 2 cores, not one.
Thank you. I'll search cgminer's faq.
BTW, affinity DOES NOT help. Processor load, hash rate drop.
BTW, affinity DOES NOT help. Processor load, hash rate drop.
I use XP / 5770x2 / catalyst 11.3 / GUI Miner
I am not going to upgrade to Win7+ for different reasons, and all other drivers I tried either didn't work or resulted in an unstable system.
I am not going to upgrade to Win7+ for different reasons, and all other drivers I tried either didn't work or resulted in an unstable system.
Which OpenCL SDK?
I can't remember which Catalyst version did and didn't have the 100% CPU bug problem. But the dramatic hash rate problem is something else. I would investigate that independently of the CPU utilization.
That being said, read the CGMiner FAQ on the recommended Catalyst and OpenCL. Also search the CGMiner thread on which Catalyst does NOT have the CPU utilization bug. I have my notes somewhere as I saw them last week. If I find them again I'll post what I was using when I had a similar configuration as yours.
In the mean time you can set your processor affinity for your mining software to only use one core of your CPU, if you have more than one core on this system.
Sam
I use XP / 5770x2 / catalyst 11.3 / GUI Miner
I am not going to upgrade to Win7+ for different reasons, and all other drivers I tried either didn't work or resulted in an unstable system.
I am not going to upgrade to Win7+ for different reasons, and all other drivers I tried either didn't work or resulted in an unstable system.
Windows XP, 2x5770
I got a problem: whenever I do mining with some configurations, on 2 cards, it takes 100% of CPU (not GPU) and then mining speed drops to kHashes, instead of MHashes.
The problem is well-known, it is supposed to be curable with drivers (tried it, didn't work).
I got a problem: whenever I do mining with some configurations, on 2 cards, it takes 100% of CPU (not GPU) and then mining speed drops to kHashes, instead of MHashes.
The problem is well-known, it is supposed to be curable with drivers (tried it, didn't work).
100% CPU bug is well known. Hash rate dropping from Mhs to Khs? Never heard of that.
What driver's did you try? What mining software are you using?
My config file (we are talking about bitcoin config, correct?) contains only login and password.
No youre correct, however you stated above "I cannot mine, neither on pool, nor solo, on port 8332.", and hence my suggestion. please post your config when you can, i'm confident we can get your issues solved.
I'll send config first thing I get home.
As for opening port... The miner does work at approx. 180 MHs per card, for about one minute. I can see results in BTC Guild's cabinet.
Only then it goes down. I am not sure firewall can allow something to access a port for that long, and then suddenly block it.
Or can it?
As for opening port... The miner does work at approx. 180 MHs per card, for about one minute. I can see results in BTC Guild's cabinet.
Only then it goes down. I am not sure firewall can allow something to access a port for that long, and then suddenly block it.
Or can it?
Open port 8332 in xp firewall.
As for the cpu problem. which miner? can you post your config here?
As for the cpu problem. which miner? can you post your config here?
Windows XP, 2x5770
I got a problem: whenever I do mining with some configurations, on 2 cards, it takes 100% of CPU (not GPU) and then mining speed drops to kHashes, instead of MHashes.
The problem is well-known, it is supposed to be curable with drivers (tried it, didn't work).
However, here is an interesting twist: I can mine, in any pool, on port 3333. I cannot mine, neither on pool, nor solo, on port 8332.
Which is strange, but maybe someone advanced will be able to figure out what the problem is?
Example of such a pool: btc guild's merged mining (it is done through 8332). While it is fine on main BTC Guild (through 3333).
Suggestions?
I got a problem: whenever I do mining with some configurations, on 2 cards, it takes 100% of CPU (not GPU) and then mining speed drops to kHashes, instead of MHashes.
The problem is well-known, it is supposed to be curable with drivers (tried it, didn't work).
However, here is an interesting twist: I can mine, in any pool, on port 3333. I cannot mine, neither on pool, nor solo, on port 8332.
Which is strange, but maybe someone advanced will be able to figure out what the problem is?
Example of such a pool: btc guild's merged mining (it is done through 8332). While it is fine on main BTC Guild (through 3333).
Suggestions?
Jump to: