Pc random reboots when gaming

Jebonia · May 25, 2013

My pc randomly re-boots when gaming . However, it does not do this when i run kombustor and prime for 3 hours. I play BF3 on ultra settings and it takes about 20-30 minutes for it to restart. It have been happening only recently (last 2 days). I have 1100 mhz core and 1400 mhz on mem clock @stock voltage on 7950. Is it possible that my power supply is too weak? I have been running the same hardware and clock speeds since January and it has only started happening in the last 2 days. I haven't checked what my temps are when gaming but it maxes out on 72 when i am using kombustor. My cpu is also only running at 61c on the hottest core when prime 95ing. Is it possible that my psu is too weak or that it has degraded from running a 7950 on a decent 500w psu? i did research on it before i bought it and the only cons it had was failing atx hold up time of 16ms.

All my specs can be found on my signature

AGGELOS_970 · May 25, 2013

Could be the PSU...?

I have the same problem.

godlikegohan · May 25, 2013

just before it crashs . are your temps high

check with HWMonitor

it will all so show you voltages.

P3rad0X · May 25, 2013

If your PSU was too weak it will fail when you run msi kombustor. You can try Furmark and Intel Burn Test or Prime 95. Do memtest 86 aswell, you never know it might be a bad ram module

Jebonia · May 26, 2013

just before it crashs . are your temps high

check with HWMonitor

it will all so show you voltages.

No the temps aren't high. staying on 71c when on msi kombustor

If your PSU was too weak it will fail when you run msi kombustor. You can try Furmark and Intel Burn Test or Prime 95. Do memtest 86 aswell, you never know it might be a bad ram module

It only crashed when playing demanding games like bf3 but not when running artificial load like prime 95 and kombustor/furmark. However, i have re installed catalyst 13.4 and it hasn't been crashing yet. I am still seeing whether it is fixed or just not crashing today. But i think it could be drivers causing it to previously crash