Hay Andrew. Sorry I'm so late to the party. I'll send you an email. =)

Actually, I'll post here in case this works, so that others can see a possible solution. If you haven't already done so, I would disable all startup processes except for the windows processes, restart the computer, and attempt to fly. Do this in msconfig.First off, I skimmed the thread so pardon me if I missed something here. Have you gotten any DEP errors? Even if you haven't, have you tried adding an exception for FSX with regards to Data Execution Prevention (DEP)?Do you have any utilities for FSX installed? (FS INN, FSCopilot, etc)I would recommend backing your CPU down to 4.5 and then running a ~2 hour stress test with Prime95. http://downloads.pcworld.com/pub/new/math___scientific_tools/p64v266.zipSometimes drivers or specific windows installations can conflict on a system that is identical to another system that has no issues. Therefore, I would recommend reinstalling/updating all drivers. Hopefully that will solve any driver installation issues. (I've heard of people getting BEX errors from bad driver installations before, so it worth a shot.)If nothing else above works, try doing a Driver Verifier. ...

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature). In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .Then, here's the procedure:- Go to Start and type in "verifier" (without the quotes) and press Enter- Select "Create custom settings (for code developers)" and click "Next"- Select "Select individual settings from a full list" and click "Next"- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"- Select "Select driver names from a list" and click "Next"Then select all drivers NOT provided by Microsoft and click "Next"- Select "Finish" on the next page.Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Hope this helps. Please report back.

But if I disable all start-up processes, doesn't that kick out things like drivers and important things like internet sercurity. I have had no DEP erros and no fs utilities inless you count fs passengers as one. I think disabling some processes will help so I don't think it'll come don to the thing from the seven forums. Thanks. I will report back with results.

I still have it at 4.7GHz 1.415V and am doing a 2h 20m stress test with OCCT. Reason I went to 1.415 is because I got another APPCRASH and a AppHangB1, got rid of a few more startup services though.

I did the stress test with OCCT without any errors. I guess its not so hard after all.

I may be wrong, but I read in several overclock forums to try to keep your VCORE under 1.4V. I'm guessing > 1.4 is fine for short durations.

No i think it is under 1.45 for 24/7 overclocks.

Actually, been looking around, can an overclocking specialist please help me out on this one. ---------------------------------------------- Ok I just put it back to 1.395 but if 1.415 is good I will put it back because it seemed more stable.

Andrew.1.35 is generally considered the max continuous that you want to set the SB processors. (1.35 allows for ~1.38 with VDroop)IMO you have your voltage set way too high. You must remember that were talking about tiny amounts of electricity, so the difference between 1.35 and 1.415 is huge! On computers that I build, 1.35 is the max that I will go. On my personal computer, the max that I will go is 1.365. IMO 1.4XX is way too high. You are kind of asking for a fried chip in 3 months. No offense.When you overclock, you can't just find a voltage that works, and leave it there. You need to bring it back a little bit at a time, stress test in between. When the chip fails, bring the voltage up one notch, and that is where you should be. Many people don't do it the proper way because they want to save time. However, you need to plan on spending several hours on stressing, adjusting, repeating.Here is what I would do right now: Bring your multiplier back to 45, and your BCLK Freq to 100.0. Set your VCORE to 1.35 (manual mode). Set VCCIO to 1.0, set VCCSA to 0.9, set DRAM to whatever the rated voltage for your RAM is (probably 1.5). Set Load-Line Calibration to Ultra High, set VRM Freq to Manual, set VRM Fixed Freq Mode to 370. Set Phase Control to Extreme, set CPU Current Capability to 130%. Set your memory timings manually. Check your RAM packaging to see what the timings are. (Probably 7-8-7-24-1T for CL7 RAM) Once you make these changes, boot your computer (if you can) and stress test with Prime (NOT OCCT). Use the link above to get Prime95. If your computer blue-screens during boot, or during testing, decrease the multiplier, DON'T increase the voltage. The first thing we want to do is verify that your CPU can get through a stress-test at 1.35 before going and upping the voltage. Report back here once you've done that. Let us know if prime gives you any errors. CPUs are like fingerprints. There are no two alike. Just because Billy John across the street can get to 5.2 at an acceptable voltage doesn't mean that you'll be able to, even though you have the same type of CPU. Also, about turning off processes: What I was getting at was for you to disable all non-windows startup processes. (bear with me here) Then try to fly. If you get no BEX or APPCRASH errors, then you know that one of the processes had something to do with it. You could then enable one at a time, rebooting and test flying in between until you find the one that is contributing to the errors. However, I would work on getting a stable CPU as we talked about above, before I worked on this. Hope this helps.....If you need help cpmpleting anything that was mentioned, let me know.

How about changing the machine back to a stock clock and troubleshoot the problem from there?

How about changing the machine back to a stock clock and troubleshoot the problem from there?

Yes, that's always a good start. He had specifically asked about overclocking, but yes....starting from stock is always a good idea when it comes to troubleshooting.

i have tried it at stock clocks and no luck. So how long should I stress test for with Prime 95.

Also, about turning off processes: What I was getting at was for you to disable all non-windows startup processes. (bear with me here) Then try to fly. If you get no BEX or APPCRASH errors, then you know that one of the processes had something to do with it. You could then enable one at a time, rebooting and test flying in between until you find the one that is contributing to the errors. However, I would work on getting a stable CPU as we talked about above, before I worked on this.

Its hard to test, they happen very unpredictably.OK, here are my troubles with the overclocking. Where can I adjust the VRM. Is it the QPI/Vtt Voltage or System Agent Voltage? I do have a Gigabyte mobo so its probably different to the ASUS ones. I am also pretty confused about the VCCIO and the VCCSA, what are they. And how can I change the CPU capability and the phase control.Could the CPU been at 1.4V affect the life span, it was only for about 3hours so I highly doubt it. They are pretty tough the Sandy CPUs.

I have decided to run LinX for 100 passes using all availible memory. I do have Prime95 but find it hard to anylise what exactly has happened.

i have tried it at stock clocks and no luck.

So you should get it working at stock clocks BEFORE you start to mess with overclocking! :(

Yeah I had it working pretty well and I was able to run it at 4.5GHz for about a week without any troubles, I think it was software.