Overclockers BSOD code list

setter · 14 Jan 2014 at 21:00

qpi/vtt are known as system agent and io voltages. On my asus theyre listed as.

system agent
ioa
iod

But ive found that with ram left at stock or xmp theese were fine on auto but still got 0x124 which upping vcore helped. When clocking ram the errors i got were 1a and 0x50. I was running the asus rog bench and upping sa and io helped with the 1a error.

Dirk Diggler · 14 Jan 2014 at 21:03

setter said:
qpi/vtt are known as system agent and io voltages. On my asus theyre listed as.

system agent
ioa
iod

But ive found that with ram left at stock or xmp theese were fine on auto but still got 0x124 which upping vcore helped. When clocking ram the errors i got were 1a and 0x50. I was running the asus rog bench and upping sa and io helped with the 1a error.

I've got ram set on XMP so I assume that means it's purely vcore? I have no intention of overclocking ram, by the way.

Nickolp1974 · 14 Jan 2014 at 21:05

String said:
I've got ram set on XMP so I assume that means it's purely vcore? I have no intention of overclocking ram, by the way.

Anything over 1600mhz is considered an overclock, what is your rams frequency?

Dirk Diggler · 14 Jan 2014 at 21:06

Nickolp1974 said:
Anything over 1600mhz is considered an overclock, what is your rams frequency?

1600mhz.

setter · 14 Jan 2014 at 21:07

All xmp does is set the dram voltage, timings and speed. Other voltages like io and sa arent influenced by the xmp profile. As your rams default setting is 1600mhz, id hazard a good guess that vcore is the one you should be concentrating on.

Nickolp1974 · 14 Jan 2014 at 21:08

String said:
1600mhz.

Sa and io should be fine left on auto
Also enter your sticks timings manually as per there rating.
It will be vcore.

setter · 14 Jan 2014 at 21:14

0x124 can pop up everytime you run a new program/game etc. Just when you think your stable and all is good, something will come along and expose your oc.

Dirk Diggler · 14 Jan 2014 at 21:18

Thanks guys.

As I say, the OC has been "stable" for weeks so I've upped vcore by a small amount. Have run 5 passes of ROG stress test without a problem. Currently going through half hour runs of Aida tests, so hopefully it holds up.

To be honest, I see stress testing as a quick indicator but nothing beats encoding video or gaming for hours, after all that's what the machine gets used for 99% of the time.

setter · 14 Jan 2014 at 21:24

I was able to pass real bench a few loops at the weekend, (slight vcore bump to 1.267 as well). But it was only when running superpi that it errored yesterday then blue screened. For my tasks running ram and cache as high as i had them doesnt show big gains. Nice for benchmarks though. Tbh ive found clocking hw to be quite different from even ivy bridge as theres a few more options. Prior to that i was on x58 which was extremely easy to oc.

Nickolp1974 · 14 Jan 2014 at 21:27

setter said:
I was able to pass real bench a few loops at the weekend, (slight vcore bump to 1.267 as well). But it was only when running superpi that it errored yesterday then blue screened. For my tasks running ram and cache as high as i had them doesnt show big gains. Nice for benchmarks though. Tbh ive found clocking hw to be quite different from even ivy bridge as theres a few more options. Prior to that i was on x58 which was extremely easy to oc.

Guessing your ram was at 2600 when it got errors in superpi??

I do find these days that people are getting obsessed with using the lowest possible voltage for a given overclock, i know that some are temp limited but if your not i'd always advise adding more.

For instance my oc in sig will pass any stability test at 1.4v, playing battlefied 4 requires 1.425v, so i just set to 1.45v to be safe and it hasn't missed a beat, rock solid.

setter · 14 Jan 2014 at 21:30

It was mate, completed two loops then failed with a rounding error message. Shortly after that i shut down the system and it blue screened in the middle of this.

Nickolp1974 · 14 Jan 2014 at 21:35

setter said:
It was mate, completed two loops then failed with a rounding error message. Shortly after that i shut down the system and it blue screened in the middle of this.

If there the CL11 2400 kit and 95% of the time work at 2600 i would defo tune them down. CL10, 1T then work on the rest.

My kit will nearly go 2600 but a tuned 2400 profile is faster in every benchmark for me.

setter · 14 Jan 2014 at 21:39

Theyre the slightly more expensive c10 kit, 10-11-11-31, 2T. 1.65v rated. Was running 11-12-12-32 1.75v. 2600mhz.

Nickolp1974 · 14 Jan 2014 at 21:41

Have you tried at c9?? Have a bash at 9-12-12-25-1t-196 @1.75v

setter · 14 Jan 2014 at 21:44

Ill give it a blast tomorrow and see how it fares.

Nickolp1974 · 14 Jan 2014 at 21:52

setter said:
Ill give it a blast tomorrow and see how it fares.

You should! I like my ram tuning more than doing the cpu!! Were not all blessed with our chips so tuning the ram helps to close the gap in benchmarks, every little helps.

OLDPHART · 14 Jan 2014 at 23:14

Nickolp1974 said:
Guessing your ram was at 2600 when it got errors in superpi??

I do find these days that people are getting obsessed with using the lowest possible voltage for a given overclock, i know that some are temp limited but if your not i'd always advise adding more.

For instance my oc in sig will pass any stability test at 1.4v, playing battlefied 4 requires 1.425v, so i just set to 1.45v to be safe and it hasn't missed a beat, rock solid.

When l find the lowest volts for the CPU depending on the overclock l go up 1 or 2 notches..

weewyum · 19 Jan 2014 at 19:58

Thankyou for this thread! Helped me realise the SA voltage was causing the instability beyond 4.4ghz. Finally stable at my goal of 4.6!

Nickolp1974 · 3 Mar 2014 at 20:44

Bump for all the bsoders!

whyscotty · 4 Mar 2014 at 12:18

Is there a reason as to why this is not a sticky?