Quote from: ReploidX9 on June 16, 2013, 04:14:36 PM

Quote from: ranlo on June 16, 2013, 04:09:29 PM

Quote from: ReploidX9 on June 16, 2013, 03:37:37 PM

Ok, managed to fix it with a couple of tweaks:

--shaders 1792 --intensity 16 --worksize 256 -g 1 --thread-concurrency 21712 --lookup-gap 2 --gpu-engine 1000 --gpu-memclock 1400

lowered the gpu engine and meclock, and upped int by 1. Going fine so far. I'll let it run for a while longer, see if anything comes up.

On a side note: the GPU seems to be running a bit hotter, might drop Int back down to prevent it.

EDIT: I rummaged through some of the CGminer options, and it lists my current gpu engine at 810 rather than the 1000 my batch file asks for. Any suggestions?

The faster you hash, the hotter it's going to get. Basically you're overclocking the system AND running it at max capacity 24/7. This is really where you have to decide "how hot is too hot" for you. IIRC 10c difference is essentially a 50% cut on estimated life of the device.

I prefer using 75C as my max limit, since im always afraid I'll one day wake up to find a melted 7950....

My room is somewhat hot so mine's usually at 77-79. When it hits 80 that's when I worry. Wish I had a lower ambient temperature, lol.