So My Prepar3D was working very poorly for awhile and so was my computer so I got it taken in for tweaking. A very long time later I got it back. I needed to renew and bugfix prepar3d again. So that's what I did. Anyway long story short The Sims fps is not very stable constantly changing between 10-30fps. My Sim has now started crashing every time I start or load it or try and fly. Here is my prepar3d.cfg file attached. My specs will be below aswell. If anymore information is needed just ask.

 

Attached is event viewer logs from typical crash as well.

 

Many thanks in advanced.

 

Bradley

 

CFG Config:

 

http://pastebin.com/huybqG2i

 

Specs:

 

Windows 7 64bit Ultimate

P3D v2 Latest (Not v3) with bug fix

GTX 970

I7 3770k

8gb Memory

 

Errors in Event viewer:

 

Error Part 1: http://pastebin.com/LUMuxxsh

Error part 2: http://pastebin.com/ixqVxsyd

Check your security settings in Windows (you installed P3D to the default directory which can cause issues with UAC), run P3D as administrator, exclude P3D from virus scans as well.  See if that helps.

 

-Jim

We have some suggestions for fixing crashes where Stackhash is the faulting module. See the AVSIM CTD Guide (link in my signature), page 15. The Buffer Exception Overrun (BEX) and ntdll.dll is involved too. Although I indicated fsx in the probable fixes, the guide is for fsx, fsx-se, fs9 and p3d. It took me several months to find the cause of my Stackhash crashes but mine turned out to be too high of an overclock or the cpu voltages were too high/too low. So, the only thing you can do is follow the guide, troubleshoot, and see if you can find the causes of your crash.

I would recommend moving your p3d, scenery, and dll.xml configurations to a temporary directory. Your p3d and scenery.cfg will be rebuilt. You don't need the dll.xml unless you are using an aircraft, say the PMDG, and you will need the entries in the dll.xml to be able to fly the pmdg aircraft. In that case you need to go to page 6 of the guide where it tells you how to disable the modules in the dll.xml one by one to see if any of them are the culprit.

 

I think StackHashes are the cause of too high settings for a particular scenario.  You will probably see the ntdll.dll as the faulting module occasionally too.

 

Best regards,