Hello all,

 

I recently encountered this phenomenon and I would like to know if anyone else has seen it as well:

 

I have a SB 2700K and I initially OC it to 4.8 GHz with Vcore set to 1.35 with running OCCT suite stable at 2 Hr. Then when I start using FSX, I began seeing some random crashes, so I decided to increase the time I run OCCT. Lo and behold, OCCT start crashing after 2 hours, so I bumped up the Vcore to 1.36 and OCCT run fine for 5 Hrs. I then start noticing FSX crashes on exit, and or random report about not being to load the add-on DLLs. So I reset my system to the defaults, then no crashes on exit no crashes whatsoever.

 

Using the no crash on exit as a stability criterion, I was only able to push my system to 4.5 GHz with Vcore at 1.35. More than this and the FSX crash on exit and random load Dlls error start to occur. The test I did is simple, start at KSEA (default), with the Trike, then exit. I have Dlls for LD-767, MAddog and NGX in the DLL.xml, and when the system is not stable for FSX, it would report that there is error loading LVLD Dll or the MAddog Dll.

 

So the general question for those who OC the SB or even IB CPU, does anyone see this?

 

Thanks

I guess you just discovered that fsx is the best stress tester of all, it stresses everything. i run prime 95 for 3 itterations. if i can get a 1 hr flight out of fsx than i am stable.

Hi Vu;

Welcome to the "overclocking blues"! :(

 

Here are some 2600K settings which will work fine on the 2700K, and you will be able to get that 4.8 or 4.9 quite easily. There is a BSoD Code chart and an ASUS Notes doc there, too.

First I would recommend downloading IntelBurnTest as the load medium, and then change the BIOS, using the 4.8 settings, and making sure that all of these settings are done as shown.

Run IBT through 5 cycles, if it passes - then run twenty cycles. If it is still stable - you can run Prime95 overnight, but it's unlikely to fail. If it does fail, you can move the vCore up to 1.39 or 1.395 in small steps, using 1.4 as a maximum, providing the temps are still under control. There are lots of pc's out there that have vCore set higher, but 1.4 ins my "comfort" limit!

 

Use CPU-Z and CoreTemp to monitor while you're testing.

 

I have to assume you have adequate cooling for that proc, (though the stock cooler is pretty good, too) as you've touch 4.8 already - only the temp is what will limit you, and this series, when compared to the 900-series i7's, run quite cool even when pushed.

 

All the Best,

Hi Vu;

Welcome to the "overclocking blues"! :(

 

Here are some 2600K settings which will work fine on the 2700K, and you will be able to get that 4.8 or 4.9 quite easily. There is a BSoD Code chart and an ASUS Notes doc there, too.

First I would recommend downloading IntelBurnTest as the load medium, and then change the BIOS, using the 4.8 settings, and making sure that all of these settings are done as shown.

Run IBT through 5 cycles, if it passes - then run twenty cycles. If it is still stable - you can run Prime95 overnight, but it's unlikely to fail. If it does fail, you can move the vCore up to 1.39 or 1.395 in small steps, using 1.4 as a maximum, providing the temps are still under control. There are lots of pc's out there that have vCore set higher, but 1.4 ins my "comfort" limit!

 

Use CPU-Zand CoreTemp to monitor while you're testing.

 

I have to assume you have adequate cooling for that proc, (though the stock cooler is pretty good, too) as you've touch 4.8 already - only the temp is what will limit you, and this series, when compared to the 900-series i7's, run quite cool even when pushed.

 

All the Best,

Thanks Paul. I have the Noctua 14H so cooling is good. I just followed your suggestion and increase the Vcore to 1.375 and get back to 4.8 Ghz. I use OCCT software (which use Intel Prime95 variant under the hood) to stress test and it ran continuously for 7 hours straight without any trouble. However, after I stop the stress tests and loading up FSX -> BSOD after loading a flight. Bumping up Vcore to 1.385 have same results. May be the machine is still hot after running 7 hours straight? I will try again tomorrow and see.

You probably have power saving features like speedstep and C1E halt states enabled that are causing "idle" BSODs. Turn them off and try again to find out. Otherwise, see the link in my signature for specific troubleshooting steps.