Ok..I am going to do the following :

 

1st day: ~3 hour flights with .cfg recreated and no tweaks applied

2st day: ~3 hour flights with fotmated bios to default - no overlcock

 

If the problem is not resolved after that

 

3st day: ~3 hour flights with no cfg tweaks and no overclock

 

If problem continues, I really don't know what I can do..

Try it on FSX and see if the same things happen. Have you applied all the famous tweaks to P3D? They work there too.

 

Lee

I have not FSX installed, and it wouldn't be realistic I think to test in FSX without all the add-ons I have in P3D..

 

Yes, I use the common known tweaks in Prepar3D.cfg. I currently do a flight without any tweak applied to test if the tweaks create the problem..

I am able to get 30fps, like with the tweaks applied. The only drawback at the moment is that flight is not very smooth and I get some fps lags in times.  But it is flyable I think.

 

I will do 3 long flights without tweaks applied. If no problem appears it will mean that some tweak(s) are creating the problem and then I will start adding one by one and testing again for 3 flights. It will take much time, but it seems to be the only way to find the cause.

Ok..something does not want to find the solution. Now a blue screen ruined the flight ''Driver Verifier Detector Violation.."

Something outside of P3D might be causing this.

 

Lee

Something outside of P3D might be causing this.

 

Lee

I agree and have said so from the beginning. Looking in the Task Manager, there are a whole bunch of processes that *could* be the culprit. Disable EVERYTHING that is not needed by the system and start from there. You do NOT need Corsair Link, you do not need an AV - look for anything that might be operating in the background, either monitoring or actively taking part.

 

I guarantee the problem is NOT P3D.

 

So remove or disable everything that is not needed including some services ( search around, there are various lists of services that can be disabled with no issues) - then use a default a/c and fly the 3 hour flight.

 

Vic

Hello all,

 

After many days of experimenting, I finaly have the smoothest ever simulator expirience. 
What I did was to try to not use Windows 8 this time. So, I did a format and installed Windows 7.

I installed the following tweaks :

 

[bUFFERPOOLS]
UsePools=1
Poolsize=8388608
RejectThreshold=126976

[Main]

FIBER_FRAME_TIME_FRACTION=0.12

[Display]

TEXTURE_BANDWIDTH_MULT=120

 

The overclock is set to 4.4Ggz at 1.285 Vcore.

 

I hope I won't have any problems any more.

 

Hello all,

 

After many days of experimenting, I finaly have the smoothest ever simulator expirience. 

What I did was to try to not use Windows 8 this time. So, I did a format and installed Windows 7.

I installed the following tweaks :

 

[bUFFERPOOLS]

UsePools=1

Poolsize=8388608

RejectThreshold=126976

[Main]

FIBER_FRAME_TIME_FRACTION=0.12

[Display]

TEXTURE_BANDWIDTH_MULT=120

 

The overclock is set to 4.4Ggz at 1.285 Vcore.

 

I hope I won't have any problems any more.

 

Glad to hear you now have a smooth platform. I am only using Reject Threshold in my Bufferpools section, I thought you either used Reject Threshold or Pools? I learn something new everyday! :lol:

Thanks for your reply, Will!

This tweak was proposed to my by NickN from Flight1. I could possibly try different numbers but I will let it there as far as it works.

I don't have bufferpool in my cfg file
Can someone help me?

Hello!

 

Do you get the same issue?

Hello everybody,

 

usually I do not open old threads, but I have the same problem as the thread opener. I just have the question, if you solved the problem by just installing Windows 7 und the tweaks in the config-file?

 

I have done everything to solve this problem own my own, I installed windows and all the flightsim programs twice, changed the ssd and the graphic card, nothing helps. Clean config files, tweaked config files, nothing seems to work. I can´t do a clean approach with the Airbus A320 Extended from Aerosoft, it always crashes.

 

The only thing haven´t tested, is to use an older nvdia-driver. That is what I will do tomorrow.