OK I have it at 1.35V. I had CPU-Z up and it showed on idle that it was at 1.056V, is this normal. I am sure it is because otherwise it would have crashed by now.

It sounds normal, but how are you testing stability?

I have been using OCCT. Just wondering if anyone knew of a registry cleaner/fixer. I have been doing some research and I think it could help with the BEX error.

If you have LLC enabled then it is normal under an IDLE load. However, having that enabled can cause stability issues, because the motherboard is controlling the voltages itself. Do you want a permanent overclock, or are you looking to have it overclocked under load only? (Mainly a power consumption issue there, because the processor is durable enough to run at 4.5 constantly). Have you looked at my link yet?

CPU Core Voltage is the voltage you want to change for CPU OC'ing. 1.3V should be more than enough for a 4.5 GHz OC. Intel has a max VID of 1.52V, but that doesn't really help us much since max VID =/= max safe voltage. I'd personally stay under 1.45V and that should be enough for OC's in the 4.8 – 4.9 GHz range.

How do i disable LCC. I have my LCC set at Level 7, what should I be doing with it.

LLC should be able to be disabled in the BIOS. But again, that's only if you want a constant overclock. [EDIT] Typo

Edited August 7, 201114 yr by FrankG2625

I want the most stable OC i can have. So if I disable will that help. I just want to know if it will help with the stability and performance within FSX.This is my exact error: Problem signature: Problem Event Name: APPCRASH Application Name: fsx.exe Application Version: 10.0.61637.0 Application Timestamp: 46fadb14 Fault Module Name: API.DLL Fault Module Version: 10.0.61637.0 Fault Module Timestamp: 46fadb58 Exception Code: c0000005 Exception Offset: 0005b8e6 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 3081 Additional information about the problem: LCID: 3081 Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt hope this can help.

Stability with your processor will enhance stability in FSX. That's just a given. I will add this disclaimer: before you fiddle with the settings, read up online on tech forums and such before you go and disable/edit things. One bad setting can fry your motherboard. Quickly.

Ok thanks. But if FSX is stressing the CPU it should put the CPU up to 4.5GHz right?Here is the other crash. Happened on FSX shutdown. Problem signature: Problem Event Name: BEX Application Name: fsx.exe Application Version: 10.0.61637.0 Application Timestamp: 46fadb14 Fault Module Name: StackHash_02da Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Offset: 00300039 Exception Code: c0000005 Exception Data: 00000008 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 3081 Additional Information 1: 02da Additional Information 2: 02da1588180b547a81b797b9aa69076d Additional Information 3: 08de Additional Information 4: 08defbc07b6ae21e9cad6f307e939dc5 Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt

Try replacing uiautomationcore.dll with a fresh one... I'm reading online that that may be the source of your problems. http://flywestwind.com/communityserver/forums/thread/31583.aspx

I have tried but I will try again. I am thinking that the BEX is also caused by the registry problems. Anyone know a registry cleaner. I know Norton has one but I am waiting for my new PC to catch up with the others so I have trend on at the moment.

Just done some flying around Lukla and did not have a crash but that's not very stressful. During the flight I was maxing out at 106FPS.Damn, on the close I got an apphangB1 error, what is this one.

Caught the apphangb1: Description: A problem caused this program to stop interacting with Windows. Problem signature: Problem Event Name: AppHangB1 Application Name: explorer.exe Application Version: 6.1.7601.17567 Application Timestamp: 4d672ee4 Hang Signature: 1645 Hang Type: 513 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 3081 Additional Hang Signature 1: 164533f5d622452bf2531d186c321aa6 Additional Hang Signature 2: 72e2 Additional Hang Signature 3: 72e22df856c81c6acb30a25ae704f677 Additional Hang Signature 4: 1645 Additional Hang Signature 5: 164533f5d622452bf2531d186c321aa6 Additional Hang Signature 6: 72e2 Additional Hang Signature 7: 72e22df856c81c6acb30a25ae704f677 Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txtIt seems to happen every time I exit FSX if that helps. Look guys I will be away for 20hours or so so if anyone can find a possible fix I will be sending you cookies. The food type, no virus. Well I thought it was pretty good.

whenever I right click on the desktop then right click again it causes the AppHangB1. I am thinking I should just revert back to default clocks. Please help me out here.

Frank, I'm not sure I understand what you mean relating LLC to 'permanent' overclocks or to the stability. As I understand it, what happens is this- Under load, the processor consumes additional power. Accompanying this is a drop in voltage that some refer to as Vdrop/Vdroop. If you enable LLC, all that happens is that the motherboard increases the voltage to compensate. Therefore, when loading the processor with LLC enabled, you see the same or greater voltage- With speedstep/related power features enabled, under load the CPU will increase its multiplier to the BIOS specified maximum, and adjust the voltage accordingly. When idle, the CPU will drop the multipler (to 16x for the 2500k) and the voltage as well. If these features are disabled, the CPU will sit at its maximum multipler permanently- is this what you mean by 'permanent' overclock? AFAIK, this is completely independent of LLC- There are two ways to adjust the voltage- the CPU offset (which adds or subtracts from the 'base' voltage), and the Additional Turbo Voltage (ATV) which only takes effect when Turbo Boost is active (i.e. 100% load with speedstep etc. enabled). The offset voltage in theory raises everything including idle voltage with speedstep on, while ATV only increases the voltage under load- I have found that with speedstep enabled and LLC disabled, using ATV it is possible to destabilise the CPU by very quickly changing the load. In this case, I think the actual processor load is changing faster than the motherboard can change the voltages *and* crashes occur when the current voltage is too low to handle the new load. The solution is to raise the voltage using the offset, not ATV. Or to enable LLC- Other sources e.g. http://www.overclockers.com/forums/showthread.php?t=682932 demonstrate that enabling LLC can increase the stability of an overclock, this was my impression as well. Because when you think about it, the only real effect of LLC is to increase the voltage to something higher than it would otherwise be without LLC- The effect of LLC is clearest if you do a 'permanent' overclock by disabling speedstep. Then, with LLC disabled, you will see an idle voltage about the same as set in the BIOS, and a load voltage that is a fair bit lower. With LLC enabled, the voltage should not change at all VirginAus737- You should definitely do an overnight run of Prime95 to (virtually) rule out your overclock as being the issue. However, the fact that you can so easily reproduce the error suggests that it is not your overclock that is the problem. I would revert it back to default clocks and see if the "right click on the desktop then right click again it causes the AppHangB1" persists. If so, then we know that more optimization of the OC is necessary. Otherwise, you can focus on the software side