Ok, same problem here.. the miner has been working flawlessly for a month and now I have experienced this behaviour - and that was actually after I have increased cooling and airflow.
Do you have any tips what is actually causing this problem?
Topic: OC --> Huge load --> Xorg 100% CPU (Read 2009 times)
I had the exact same problem. I was able to mine for 15 minutes to 3 hours but at some points XORG take 100% CPU and everything freeze.
My solution is to use the default voltage for the card. Hope you find something better.
My solution is to use the default voltage for the card. Hope you find something better.
Just watch temps when overvolting.
It wont let you go higher enough that it explodes since the voltage control is limited to max of 1.3V but thats enough to get get the chip hot enough to damage it on air cooling.
It wont let you go higher enough that it explodes since the voltage control is limited to max of 1.3V but thats enough to get get the chip hot enough to damage it on air cooling.
try to increase the gpu voltage
Any rules of thumb or guidelines or should I just wing it?
hmm, can't tell you nothing about that, cuz I don't know shit hehe
but I guess it's no problem to increase a little bit, for example, from 1.088 to 1.150
try to increase the gpu voltage
Any rules of thumb or guidelines or should I just wing it?
try to increase the gpu voltage
So I'm mining on a single 6870 in Natty on my personal workstation that doubles as an apache2/Minecraft server. Not a clean install, updated twice (?) through Lucid and Maverick. I am running Catalyst 11.6, SDK 2.4, pyopencl 2011.1.2, python-jsonrpc rev. 19, and poclbm 2011.b7. Everything runs fine at stock speeds (900 core, 1050 mem --> 280 mhash) but when I try to over/underclock at all (e.g., 1000 core, 300 mem) it works for a bit (310 mhash) then the load shoots up to 10+ (normally <<<1), everything becomes slow but not unresponsive, then after a few minutes the load drops to ~6-8 (quad core) while Xorg shoots up to 100% CPU and will not respond to kill -9. The only way to resolve this is to reboot the machine. Anyone have any ideas as to what could be going on?
Jump to: