1 minute ago, ttbq1 said:

you don´t have do anything, it is in automatic, the way it should be.

what Nvidia driver version do you have?

446.14 (updated yesterday) 

Windows update v2004

1 minute ago, skysurfer said:

446.14 (updated yesterday) 

Windows update v2004

Did you clear shader folder after the driver update?

I think with your current setup you shouldn´t have any problems with P3D V5 HF1. I will try to help you with that sharing my experience since I started using V5.

Do you use MSI afterburner with RTSS?

when you update the driver yesterday, did you previously reset all the NCP (or NVI in case you use it) to default?

Lets start by troubleshooting the Video drivers and then we move on 

I updated client about 15 minutes ago (as it was suggested above) and deleted cfg file and shader folder. 

I updated the driver using NVCleanstall program. 

"when you update the driver yesterday, did you previously reset all the NCP (or NVI in case you use it) to default?"  -  No, I did not 

I do have MSI afterburner 

Thanks Ramon 

Edited June 15, 20205 yr by skysurfer

1 hour ago, ttbq1 said:

Did you clear shader folder after the driver update?

I think with your current setup you shouldn´t have any problems with P3D V5 HF1. I will try to help you with that sharing my experience since I started using V5.

Do you use MSI afterburner with RTSS?

when you update the driver yesterday, did you previously reset all the NCP (or NVI in case you use it) to default?

Lets start by troubleshooting the Video drivers and then we move on 

Did client update. Setting per P3D guide. Flying QW787 I have low fps about 20-25 (but I use surround across 3 monitors. Usually fps is around 45-50) and CPU temps is too high 90-100C. But at least I was able to start the sim and fly without CTD so far. 

Edited June 15, 20205 yr by skysurfer

52 minutes ago, skysurfer said:

and CPU temps is too high 90-100C

How did you overclock it? With an automated OC by Gigabyte?

12 minutes ago, JoeFackel said:

How did you overclock it? With an automated OC by Gigabyte?

No OC. The person who assembled this PC said he was able to get OC up to 4.6 but after that I went to MOBO settings and set everything back to AUTO. The base frequency is 3.6 and max turbo 5.0. I see in MSI afterburner that iit reads 4700 pretty much all the time when fly. I must have missed something in MOB settings  

Edited June 15, 20205 yr by skysurfer

1 minute ago, skysurfer said:

No OC. 

So why does it run on 4.7 GHz (like its written in your sig)? Stock clock would be 3.6 in idle and 5 GHz in turbo mode.

2 minutes ago, JoeFackel said:

So why does it run on 4.7 GHz (like its written in your sig)? Stock clock would be 3.6 in idle and 5 GHz in turbo mode.

I just updated my reply. Thanks for pointing it up 

1 hour ago, skysurfer said:

Did client update. Setting per P3D guide. Flying QW787 I have low fps about 20-25 (but I use surround across 3 monitors. Usually fps is around 45-50) and CPU temps is too high 90-100C. But at least I was able to start the sim and fly without CTD so far. 

could you please share your p3d settings?

AA: try 2MSAA or 2SSAA

framerate limiter to unlimited (we’ll modify it later)

what is your monitor refresh rate? could you set it at 30hz? if so, set vsync on in p3d

 

It's running WAY to high on temps with this clocks, especially with water cooling. I'm pretty sure your CPU is running too high on volts as your Motherboard will alter the volts with higher clock. You should easy reach 5.0 GHz permanent clock with around 75°.

Edited June 15, 20205 yr by JoeFackel

8 minutes ago, JoeFackel said:

It's running WAY to high on temps with this clocks, especially with water cooling. I'm pretty sure your CPU is running too high on volts as your Motherboard will alter the volts with higher clock. You should easy reach 5.0 GHz permanent clock with around 75°.

I may need to do some research how to manage that. 

8 minutes ago, JoeFackel said:

It's running WAY to high on temps with this clocks, especially with water cooling. I'm pretty sure your CPU is running too high on volts as your Motherboard will alter the volts with higher clock. You should easy reach 5.0 GHz permanent clock with around 75°.

true that, that 9900k at 90c is too high

Just now, skysurfer said:

I may need to do some research how to manage that. 

p3d v5 will work perfectly fine with stock 9900k. At least try to bring your Bios to default while testing what could be wrong. then you can start oc again

I did load optimized defaults but CPU still reads 4700 and now I cannot start the sim. Same freaking KERNELBASE.dll CTD

I agree, in v5 you should be able to run stock on your GPU and CPU and that's the place to start for stability.

I know everyone has their own homebrew solution, but I'll share how I got v5 to run stable in the event that you find a useful nugget in here. I flew six legs yesterday in the same sim session without a CTD, and it has been like that for me for the last week or so. (see https://www.avsim.com/forums/topic/576927-what-did-you-fly-in-prepar3d-today/?do=findComment&comment=4255038)

I have every single add-on installed via the XML method. This allows me to easily remove them from the sim in the event that I start having a stability problem. I've added add-ons one (or two) at a time and tested stability before adding more. If I get a CTD, I remove the most recent XML entry and try without to see if I can isolate it.  That said, I haven't found any add-ons that cause crashes. They were all VRAM related - see below.

I have a completely default prepar3d.cfg file except for my AM setting, which just forces P3D to use all of my cores and is likely not relevant to anything. I have found that my cfg file gets corrupted about once a week in v5 and so I have made and keep a backup of what it should be and anytime I have a problem, I am "prepared" to just delete and swap in the old working one.

Here's where my stability really came from. After extensive testing, I noted that P3D has VRAM spikes that are very temporary and hardly noticeable. For example, as I approach my arrival airport, there's a VRAM spike that is temporary. No clue why, but I'll be cruising along at 4.5GB/7.1GB, then as I approach the arrival it starts creeping up, maybe to 5.5GB. Then, it spikes by about 1.5GB to 7GB before falling again to about 6GB.  This lead me to the conclusion that there are various situations that cause VRAM to temporarily spike and this was the cause of many of my CTDs at various stages of flight, prep, etc. What I learned was that anytime my VRAM was above 5.6GB/7.1GB I was in the danger zone. I had previously been living in the high 5s and 6s, and had a lot of instability.  I changed my resolution down from 4K to 1440P ("2K") and my VRAM utilization fell about 1GB and I haven't crashed since, and I never go above about 6.2GB/7.1GB. P3D needed a larger VRAM buffer than I was giving it previously. I was able to turn UP my texture resolution 1K-->2K and increase my AA from 2xSSAA to 4XSSAA, which pretty much compensated for the lower overall resolution and I am now flying multiple legs for hours at a time without CTDs.

Anyhow, the moral of the story is that there are VRAM spikes that last a short time and that were causing most of my CTDs. I'd suggest getting your VRAM way down and seeing if you are stable there and then, if so, find your sweet spot - for me it is aiming for 1.5GB free at all times.

Lastly, I have found that EA bogs down my system after an hour or so causing stutters - I just turn it off and on again and all is good again.

None of this is ideal, but it is workable for now.