7im wrote:but it will tell you if the current clocks are working or show an error if not. Raise the clocks until it fails. That will give you an idea of what the real client and work units will handle. Ymmv.
Yeah, Im trying this way, but without errors shown, the GPU freezes after several hours
![Sad :(](./images/smilies/icon_sad.gif)
for example yesterday evening I've set 750,1100 and it worked perfectly until today 9:30 morning. Now I've lowered to 700,1100 and is working without any problems for over 12hrs.
bruce wrote:Normally, the FahCore does adjust memory clock down during computation (saving thermal headroom) and up when it's primarily moving data between RAM and VRAM does mean that Stanford has done some performance tradeoffs.
And that's why there's not much sense to manipulate with memory, but rather with core, isn't it?