ntdl.dll

 

This one is typically associated with a bad GPU driver....

This one is typically associated with a bad GPU driver....

 

That's a core Windows library, what does it have to do with the GPU driver? I think you mean nvlddmkm.dll

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.

 

Also try the Intel Burn Test on maximum and 10 passes. I run Prime (Blend or Custom) to first test stability and IBT to verify.

 

If your machine can pass both you should be good.

This might seem a bit overkill, but after I had my experiences, I settled for 24hrs Prime95, and 400 runs on 4096 Linx. And at least overnight Memtest+.

nvlddmkm.dll

 

Thanks for the clarification.... That was the one oops.

This might seem a bit overkill, but after I had my experiences, I settled for 24hrs Prime95, and 400 runs on 4096 Linx. And at least overnight Memtest+.

 

Do you have a second computer to use while stablity testing your overclocks? I personally could not test for stability of overclocks for 24 hours straight on my 1 and only computer and one of the reasons why I don't keep my system permanently overclocked is because I just don't have the time and patience to keep my computer tied up for stability testing. I use my PC for work and internet besides gaming and FSX.

Well the problem with running a really long burn in test is that it keeps people awake, the fans are pretty loud so I may try one on the weekend during the day.

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.

I couldn't find any for FSX but there were a lot of VSS and CAPI2 errors. But nothing for FSX.

 

Some more stress tests all seem fine but really, I need a better cooler. The H60 just doesn't really cut it anymore. 1.355V 4.7GHz 83 degrees so maybe that and 8GB of RAM will be the next upgrade for it. I am now running it at 4.6GHz @ 1.3355 so maybe I can get better stability.

 

I will try a flight in the A320X going at high altitude to see if it crashes on me again.

Did it in the A320X as well this time on the ground though.

Do you have a second computer to use while stablity testing your overclocks?

 

I have a laptop and an iPad, yes. But using them only for surfing and if I need something badly. I say, those tests can also be run overnight, while sleeping. That should also be enough, if you can't afford 24hrs.

Well I am going to be away for a few days so if you have any questions it would be appreciated if you ask them now, thanks.

Well I am going to be away for a few days so if you have any questions it would be appreciated if you ask them now, thanks.

 

Nothing from me any more

You need to look for application errors in Event Viewer. FSX won't show in the header, it will only display an error 1000, you need to check the Faulting application name in the detail.

Oh ok, will do that Friday. Thank you everyone for posting and helping.

Well I am back and now on the computer again. Looking through the details of 1000 errors I can't find anything in the System or Userdata sub-menus related to FSX. Is there somewhere else I should look?