BSOD....How to find out if CPU or GPU?

beany_bot · 23 Jan 2016 at 16:09

SO I got a BSOD. How do I find out if this was CPU OC or GPU OC related?
Havent had one in months. Thought I was stable... GPU is only overclocked 30Mhz. Stock Voltage. Didnt get time to take a picture of the Blue screen info. CPU is 4.5Ghz at 1.22v

beany_bot · 23 Jan 2016 at 16:15

I "think" this might be the error report. I was hitting the CPU pretty hard at the time. playing FSX, watching youtube and surfing the web. another .01volts maybe? It has been on this OC for a few months now with no crashes.

beany_bot · 23 Jan 2016 at 16:20

Could it be PSU related?

troops · 23 Jan 2016 at 16:22

Increase Vcore

P4Clock · 23 Jan 2016 at 16:34

Google a program call who crashed. Install and it will read crash dump info and change it to a format you can understand

P4Clock · 23 Jan 2016 at 16:37

troops said:
Increase Vcore

Yer with 1.22 for 4.5 on an ad chip I would think a bump in v core would be good.
if you have not had a crash for month what have you changed or done different

beany_bot · 23 Jan 2016 at 16:41

P4Clock said:
Yer with 1.22 for 4.5 on an ad chip I would think a bump in v core would be good.
if you have not had a crash for month what have you changed or done different

Nothing really, I've changed some raedon settings to push the gpu harder in FSX and was mid-flight. Not that I think the gpu causes the crash but with CPU and gpu working hard for a while wondering if it might be PSU related. I am cutting it pretty fine with the PSU limits.

What I will do is increase the Vcore. If that solves it I know that was the problem. However if it was the PSU then increasing the Vcore will not only make it happen again but probably quicker. And I will know it's the PSU.

beany_bot · 23 Jan 2016 at 16:42

P4Clock said:
Google a program call who crashed. Install and it will read crash dump info and change it to a format you can understand

Thanks!

deFiniLoGy · 23 Jan 2016 at 16:51

Also worth doing a memtest?

beany_bot · 23 Jan 2016 at 17:04

deFiniLoGy said:
Also worth doing a memtest?

Further down the chain yeah. But I did a memtest when I installed it not 2 months ago and it was perfect. At this stage I'm thinking the order of likelihood is CPU - PSU - GPU - RAM

beany_bot · 24 Jan 2016 at 08:54

Can I check with you guys I'm doing this voltage thing right? Because there is nowhere that specifically says VCORE and I am pretty new to this.

I think it's right because if i set it to 1.23v as shown. CPU-Z says its always sitting at 1.228v. Strangely it sits at 1.24v in Bios. but this doesnt seem to be an issue.

Disco_P · 24 Jan 2016 at 10:28

That is your vcore - yes. It'll never be exactly what you set it too but it should be close.

The other important thing is load line calibration or vdroop settings. The higher this setting the more vcore you'll have under load. However set it too high and your voltage can massively spike under load causing dangerous temps etc.

beany_bot · 24 Jan 2016 at 13:28

Disco_P said:
That is your vcore - yes. It'll never be exactly what you set it too but it should be close.

The other important thing is load line calibration or vdroop settings. The higher this setting the more vcore you'll have under load. However set it too high and your voltage can massively spike under load causing dangerous temps etc.

Thanks. I found out with Aida that voltage is (as you said) actually 1.248v under heavy load (when set to 1.23v) That seems totally fine. No crashes now so I think I am stable. Temps still OK for me (79 under stress test and 60's under heavy gaming load). Under 80 stress and under 70 gaming is my personal limits.

Thanks for help.