Quote:
Originally Posted by bfish
If I raise my qpi over 1.3 I get blue screens until I bring it back down.
If you're getting BSOD's with error code 124, it usually means you need to either raise or lower qpi (took me a while to figure out that it actually needed less voltage for stability for my chip).
It also seems like most stable overclocks I've seen on 930s generally have lower qpi than 920s... Don't know if it's true, just seems to be that way.
I'm out of town for work atm, but I have stable clocks written down for my 930 for 3.8, 4.0 and 4.2 that I can post on Tuesday. Every stable settings for me has the qpi quite a bit lower than core voltage.
I started with my qpi @ 1.20625. For a 100% stable 4.0, I have 1.23125 qpi.
|
When I did my OC, I read the guide here that suggested bsod 124 meant qpi changes, but that only lead me to more heat and confusion.
Instead, I decided to isolate and test each setting individually. Since qpi is related to the bclk and affects memory, to test it I set bclk to 200 and the CPU multiplier to something low like 13x, so that I could be certain that the CPU had plenty of vcore to run at that speed. My qpi was at 1.300 from following the previous guide so I started here and ran memtest86+ to verify that there were no errors. Then I dropped it a little bit and tested some more. This lead me all the way back to 1.200, which was the lowest setting on my mb and I found that 200 bclk ran stable with it.
Then I resumed testing speeds by setting my multiplier back to 21x and lowering my bclk back down to something like 180, which was the last speed I had ran IBTx20 successfully (at the time). Then I upped bclk by 5 and tried IBTx20 again. If it failed, I upped vcore--even on bsod 124. This quickly led me to stable settings all the way up to 200x21, all with qpi set to 1.200. In the end, I chose to run at 190x21 as it wasn't much slower, but ran much cooler.
TLDR: bsod 124 results don't usually mean qpi changes are needed. I would only bump qpi if several vcore bumps don't help.
