Overclocked my GPU but...

[Killfranzy]

So I overclocked my GPU from 1411mhz (core) and 2000mhz(mem) to 1480mhz(core) and 2100mhz(mem) then I ran Valley Benchmark (no strange things happened) but when I try to run MSI Kombustor, a couple of seconds later It hangs then display off for 2-3secs then crash. Should I lower my OC or is there something wrong with kombustor?

[Judd]

Is that the only program it happens in? Have you tried any games?

[Tabs]

12 minutes ago, Killfranzy said:

So I overclocked my GPU from 1411mhz (core) and 2000mhz(mem) to 1480mhz(core) and 2100mhz(mem) then I ran Valley Benchmark (no strange things happened) but when I try to run MSI Kombustor, a couple of seconds later It hangs then display off for 2-3secs then crash. Should I lower my OC or is there something wrong with kombustor?

It basically means the overclock was unstable. The screen turning off means the display driver crashed and Windows restarted the device (so anything using the GPU at the time like Kombustor would also crash).

 

What type of GPU do you have? It's possible your card doesn't have much thermal headroom.

 

I'd generally try to suggest that if you're going to overclock, overclock one thing at a time - push core up in steps until you become unstable (with memory at stock speed), then dial it back a few notches and start on memory in the same way. This means you always know which clock is unstable when you get a crash.

[Killfranzy]

5 minutes ago, Judd said:

Is that the only program it happens in? Have you tried any games?

Havent try playing games atm...

[Killfranzy]

5 minutes ago, Tabs said:

It basically means the overclock was unstable. The screen turning off means the display driver crashed and Windows restarted the device (so anything using the GPU at the time like Kombustor would also crash).

 

What type of GPU do you have? It's possible your card doesn't have much thermal headroom.

 

I'd generally try to suggest that if you're going to overclock, overclock one thing at a time - push core up in steps until you become unstable (with memory at stock speed), then dial it back a few notches and start on memory in the same way. This means you always know which clock is unstable when you get a crash.

Ok i'll try bringing the mem to stock. I have Nitro+ rx570 8gb

[Jurrunio]

Kombustor hits your GPU unreasonably hard so I would avoid using it if possible. Unlike Prime95 on CPUs, graphics cards actively drop clocks when using Kombustor (which is a reskinned version of Furmark), making finding out the right overclock difficult.

[Killfranzy]

3 minutes ago, Jurrunio said:

Kombustor hits your GPU unreasonably hard so I would avoid using it if possible. Unlike Prime95 on CPUs, graphics cards actively drop clocks when using Kombustor (which is a reskinned version of Furmark), making finding out the right overclock difficult.

I see. I'll just stick to valley then. I'll run valley over and over again if i found the right numbers just to make sure it's stable.

[Killfranzy]

Well I guess I found the right numbers 1480mhz and 2250mhz (max mem clock, cant go beyond that)

[Jurrunio]

6 minutes ago, Killfranzy said:

Well I guess I found the right numbers 1480mhz and 2100mhz 

nothing beats proper games when it comes to a proper stress test, so be prepared for a crash. You crashed Kombustor, so you shouldnt be far from the limit.

[Killfranzy]

2 minutes ago, Jurrunio said:

nothing beats proper games when it comes to a proper stress test, so be prepared for a crash. You crashed Kombustor, so you shouldnt be far from the limit.

Alright I'll be on guard.