Author

Topic: [GUIDE] How to prevent 100% CPU usage in Windows when mining (Read 6346 times)

full member
Activity: 196
Merit: 100
GUIMiner has this feature built in and it saves your settings so you never have to do anything manually again.

I have guiminer but I get much better performance out of aolcbf for whatever reason.  my 5830s run 320 to 330 mhash each no problem... in guiminer I just can't get past 280 to 300
sr. member
Activity: 418
Merit: 250
On my lower-end dedicated single-core miner, I actually sometimes get higher performance by settings the phoenix.exe's to below-normal process priority.

A bit anti-intuitive, but it works.


(start /belownormal phoenix.exe ... )
hero member
Activity: 630
Merit: 500
GUIMiner has this feature built in and it saves your settings so you never have to do anything manually again.
full member
Activity: 196
Merit: 100
What about phoenix though?  I use AOCLBF 1.74 with the modified phatk kernal because I get so miuch more performance.

sr. member
Activity: 476
Merit: 250
moOo
damn you slippy pinky


thanks myself.. link fixed


BTW.. i use 11.6 cats with cgminer and I have no cpu bug.. My cpus sit at about 9%
sr. member
Activity: 476
Merit: 250
moOo
you can also use process lasso and set up some rules
full member
Activity: 302
Merit: 100
Presale is live!
If people are on windows 7 (i imagine this would work on vista and server 2008 as well) they can place this in the start of their bat file: start /affinity X and replace X with the core they want to start set affinity to  Smiley
newbie
Activity: 48
Merit: 0
My mining rig is also my database server, so I can't have the mining processes consuming 100% of the CPU. Unfortunately, this driver issue is as yet unresolved by AMD.

However, the problem can be alleviated, though not completely eliminated, if your processor has more than one core. In the screenshot below, you can see my mining processes are very low now. They still fully consume the resources of one core, however.

Furthermore, this action may increase the hashing rate on some systems. In my case, I went from 1.3Ghash/s to 1.5Ghash/s (dual 6990) with this change, because the database server was competing with poclbm.exe for CPU resources.

Here's how:

https://i.imgur.com/c8znu.png

Jump to: