I have been over at the MSFSX forum here on avsim and been had a reply from Jim (firehawk) about my crashes without any error and he said that it may be because of my overclock. Now I have been running this overclock (4.7GHz @ 1.35V) for quite a while and its been as solid as a rock with everything else but it seems maybe not FSX. So I would just like to get some other hardware enthusiasts thought on this one.

 

Thanks,

Does any burn test run stable ?

LinX, p95 all run stable.

why not try a RAM test and GPU test. Have you tried going back to stock settings ?

 

does it reboot or it's a CTD ?

Just a crash to the desktop, but no error message shows up for me to diagnose it.

Does it happen on a specific flight like scenery / aircraft ?

Usually happens at high altitude but since the NGX is all I fly high up it, I have only ever seen it with the NGX.

Could you try with a diff. aircraft

LinX, p95 all run stable.

 

How long (Linx how many runs)? RAM tests with Memtest also done, at least overnight?

 

This is a pretty high OC for a very low voltage. In comparison, I can't run lower than 1.48 for 4.8Ghz. Just as a comparison.

 

I had a Starcraft 2 reset my computer while in game if my Vcore was just whee too low. P95 and all would go well, but once twice in a month, SC2 would crash. Then I upped the core just a bit, been calm since then.

Just a crash to the desktop, but no error message shows up for me to diagnose it.

 

The crashes are logged in the Event Viewer

1.35V is indeed a little low for 4.7 GHz as Word Not Allowed says. However, there are CPU's that make it on that voltage. I need at least 1.39V to get mine stable and have no problems in FSX. Try to increase your voltage a notch, to 1.36V.

 

Oh and Word Not Allowed, 1.48V for 4.8 GHz seems very high to me. I do believe that you can't get any lower, but you obviously got very unlucky with your chip!

but you obviously got very unlucky with your chip!

 

Aaaah... nah! It gets to 4.8 without problems, and temperatures are OK with the watercooling!

The crashes are logged in the Event Viewer

I really cant find them, anywhere. Is there a specific directory to them?

 

I will up the VCore to 1.365 or so and run linx tomorrow.

I really cant find them, anywhere. Is there a specific directory to them?

 

I will up the VCore to 1.365 or so and run linx tomorrow.

 

I'll try helping you do find this directory. Please note that my WIndows is in Dutch, so I translate everything to English litterally and thus it might be a little different.

 

Ok, first go to the Start button, then right-click on the "Computer" button, now click "Manage" (the second option). Now a window will open. In the pane on the left side, you should see several buttons, next to each button you see a " > " , sort of a triangle pointed to the right. Now click on the > next to "Logbooks". Now click on the > next to "Windows Logbooks", now click on "Applications". Right now a list should open. Everything marked with a red ( ! ) indicate a CTD of a programm. Now, after you had your FSX crash, go to there and open the last entry with the red ( ! ) next to it. Now you'll see some information, the part we are interested in especially is the faultmodule. Most of the time, the faultmodules that crashed caused by an unstable overclock are ntdl.dll and API.dll.

Just type "Event Viewer" in the start menu search