Bitcoin Forum

Bitcoin => Bitcoin Technical Support => Topic started by: gigawatt on June 18, 2011, 02:05:06 AM



Title: Bitcoin server eating CPU
Post by: gigawatt on June 18, 2011, 02:05:06 AM
Ok, so I've been participating in Bitcoin mining for almost a month now and it's been going smoothly on my desktop rig (NVidia Card).

(Edit: Question one removed and title changed.  Turns out that I was misreading GUIMiner's status screen.  Now I feel like a doof.)

So I've been running Bitcoin solo mining on my old desktop for a few weeks now and it works absolutely fine running Bitcoin 3.21.  My new rig that I built (dual 5830s OC'd to 900Mhz) works fine connecting to mining pools and to my other desktop.  The issue I'm having is that whenever I try to connect to a locally running Bitcoin server (version 3.23), the Bitcoin application CPU usage spikes to consume a whole core and doesn't respond to mining clients.  I copied over my desktop's 3.21 version and it works fine.  What could be causing this and what can I do to fix it?
TLDR: New rig runs Bitcoin 3.21 as a server fine, but on client connect with Bitcoin 3.23, process CPU usage maxes out and server goes unresponsive.

If you need any details on my system setup, please feel free to ask.

Any advice or help is appreciated.  I'm a fairly technical person, so feel free to get nitty gritty.

Thanks in advance!


Title: Re: Bitcoin server eating CPU
Post by: bsd on June 21, 2011, 06:36:08 PM
Do you have a multicore CPU? The best thing to do for now is to run the miner on one core only by changing the "affinity". This way the miner can only max out one core. You can do this by doing a ctrl-alt-del and going to the miner process and right mouse click - affinity. The better way to set the affinity is by using a batch script to start the miner and/or bitcoin.exe and have it start with "start /affinity 1 ..." Also, I don't see why it would be a problem using a slightly older bitcoin.exe if it works.

There are a lot of people whose CPUs are maxed out by miners in Windows. Use the search (there are 5+ threads on this). Unfortunately, it appears that very few people are able to fix the problem without switching to Linux. The general advice is to downgrade the ATI Catalyst video drivers and SDK.