Hi Jim. 

 

I did already try the fsx.cfg rebuild a couple of weeks ago when I first had the problem and started this thread but it still crashed.
 

I have read the DEP can be linked to stackhash errors so I have disabled that to see if that helps. I will try a couple of flights this week to see how I get on.

If still no joy I will look into the BIOS and overclock settings as I am running an overclock so maybe something has gone wrong there. Maybe a voltage tweak is needed or a slight drop down in clockspeed (I have a i5 3570K running at 4.4ghz on an artic cooler). Do you usually use memtest for 24 hours for testing a stable overclock?

Sorry, of course I meant prime 95 not memtest for testing over clocking! It was late last night when I wrote that

 

 

Do you usually use memtest for 24 hours for testing a stable overclock?

 

I found that stability testing for fsx is a waste of time.  I have used several.... Prime95, Intel Burn Test, etc., and the Windows test and all passed with flying colors.  But I continued to get the errors so lowered my overclock from 4.4GHz to 4.2GHz and the crashes stopped.  Some other times I set my ASUS Z87 motherboard back to the optimized defaults and that fixed it on other occasions. 

 

I know it is a pain to reset an overclock and your BIOS but lowering your overclock a notch or two won't hurt at all.  Going to the optimized defaults will hurt as you will have to reset everything.  You can also play with the cpu voltages and move it up or down a notch but that requires a lot of patience and testing.  I have found that overclocking can work most of the time and you think your system is stable and you are all happy as all get out and then an unexplained CTD, a StackHash, or NTDLL.dll error.  Perhaps you raise your settings higher in your config putting more stress on your system.  In any case, I have been successful fixing most of my crashes by lowering the overclock or resetting to the BIOS to the optimized defaults.

 

Best regards,