dual 5850 causing nearly 100% cpu use?!?!?

[CyberPhunk]

I couldn't find any specific solution for this issue, I'm using GUIMiner, and running two 5850 cards, and I'm getting nearly 100% cpu core usage on core 1, if I uncheck cpu affinity on both, then I get nearly 50% usage across all four cpu cores!

Help!

[1715550957]

1715550957

[1715550957]

1715550957

[malevolent]

Got the same problem, got with 2 5850s and a 6850
with 1 5850 and 1 6850 I didnt have this problem on phoenix, only on poclbm
after adding 2nd 5850 1st core has got 100% load. :/

[xurious]

I'm too lazy to dig up the thread, but this is apparently a driver bug. Just keep the affinity to 1 core. There is a work around here somewhere for it....

[cryptomint]

I'm too lazy to dig up the thread, but this is apparently a driver bug. Just keep the affinity to 1 core. There is a work around here somewhere for it....

This.

I tried very hard to fix this problem on my one windows rig.

I ended up unlocking the second core of my Sempron processor so the rig would be usable as a desktop.

If you have multiple cores/processors:

1. start the miners
2. go to the task manager (ctrl+shift+esc)
3. in the processes tab right click each miner process and click "Set Affinity..."
4. put all of the miner processes on the same cpu

[Auspician]

This problem is generally driver based.  Try a different version of Catalyst (avoid 11.2 and 11.3) or a different version of Stream SKD and it is likely to solve the problem.  You do want some CPU usage though (25% or so) to stabilize your computer in case your GFX cards try to do more than 100% occasionally.  This is fairly frequent; fortunately the software most commonly used takes this potential problem into account and runs the CPU at a reasonable rate to keep everything in line.

I'm using Catalyst 11.1 and Stream SKD 2.1 and I'm using 20% CPU on my Intel i7.

[haydent]

i have started a thread at amd dev forum - opencl section about the 100% cpu usage bug with >1 gpu installed. feel free to jump over there and post your support for this issue being addressed...

http://forums.amd.com/devforum/messageview.cfm?catid=390&threadid=153211&enterthread=y