Having updated Prepar3D to version 4.5.13.32097 it now 'crashes' just after becoming airborne. From the event viewer I get the following:

Log Name:      Application
Source:        Application Error
Date:          23/12/2019 21:09:05
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-DVPQJF5
Description:
Faulting application name: Prepar3D.exe, version: 4.5.13.32097, time stamp: 0x5d8abf93
Faulting module name: KERNELBASE.dll, version: 10.0.18362.535, time stamp: 0x50cc8d5a
Exception code: 0xc0020001
Fault offset: 0x000000000003a839
Faulting process ID: 0xc20
Faulting application start time: 0x01d5b9d44ca9d002
Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report ID: 12abcbdf-8302-4cf8-89f4-78775505ada6
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-12-23T21:09:05.342159000Z" />
    <EventRecordID>1955</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-DVPQJF5</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>4.5.13.32097</Data>
    <Data>5d8abf93</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>10.0.18362.535</Data>
    <Data>50cc8d5a</Data>
    <Data>c0020001</Data>
    <Data>000000000003a839</Data>
    <Data>c20</Data>
    <Data>01d5b9d44ca9d002</Data>
    <Data>C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe</Data>
    <Data>C:\WINDOWS\System32\KERNELBASE.dll</Data>
    <Data>12abcbdf-8302-4cf8-89f4-78775505ada6</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

 

and the details from the same source the details given are:

Log Name:      Application
Source:        Application Error
Date:          23/12/2019 21:09:05
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-DVPQJF5
Description:
Faulting application name: Prepar3D.exe, version: 4.5.13.32097, time stamp: 0x5d8abf93
Faulting module name: KERNELBASE.dll, version: 10.0.18362.535, time stamp: 0x50cc8d5a
Exception code: 0xc0020001
Fault offset: 0x000000000003a839
Faulting process ID: 0xc20
Faulting application start time: 0x01d5b9d44ca9d002
Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report ID: 12abcbdf-8302-4cf8-89f4-78775505ada6
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-12-23T21:09:05.342159000Z" />
    <EventRecordID>1955</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-DVPQJF5</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>4.5.13.32097</Data>
    <Data>5d8abf93</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>10.0.18362.535</Data>
    <Data>50cc8d5a</Data>
    <Data>c0020001</Data>
    <Data>000000000003a839</Data>
    <Data>c20</Data>
    <Data>01d5b9d44ca9d002</Data>
    <Data>C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe</Data>
    <Data>C:\WINDOWS\System32\KERNELBASE.dll</Data>
    <Data>12abcbdf-8302-4cf8-89f4-78775505ada6</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

 

Any help would be much appreciated. [Oh, and a Happy Christmas to all!]

roadrabbit

Was your sim stable before the update? Kernelbase crash often refers to unstable memory, but could also be numerous other things. Also make sure that your video and device drivers are up to date, including Windows updates.

Hello and Happy Christmas to everyone who’s mad enough to look after his sim these days…

I have used this forum for many years and got solutions for any problems I had in the past for FSX or P3d but this one seems to be a tough one.

It appears I’m having the same problem like roadrabbit since a week or so. I’ve been troubleshooting with hardware and software, no success at all. (CPU / GPU stress tests, memory test, all ok.) Followed plenty of advice for system checking and fixing – nothing. So, I did what everybody hates, clean reinstall of Windows 10 Pro and P3D. What happened? Same story, every time I attempt to load a flight with a ga plane the sim freezes and ctd’s. I can load flights at heavy airports anywhere else. This happens with a fresh Windows and a plain P3D without addons, just some Carenados and Alabeos. It happens with stock planes (few) as well. The sim was running for months under much higher settings and with Orbx regions without any problems.

I don’t know any more what to do now, if anyone had this problem – I would really appreciate any input.

Thanks for reading this

Michael

Sorry, I forgot to say it only happens on busy airports on US westcoast like KLAX / KSFO

After updating always clear the contents of the Shader folder and delete Prepar3D.cfg allowing a new one to be built. You’ll need to setup your preferences again.

Update your sound and video drivers to the latest. If this doesn't help check if you are performing Overclocking. If you do perform another system stability tests as you might need to re-adjust your OC settings. Many times when we apply windows updates, etc. it changes the way the operating system behaves and it is required to re-stabilize the system overclocking settings.

Regards,
Simbol

Check your power setting in Nivdia Control Panel -- Should be set to "Prefers Maximum Performance". That solved the problem for me.

All my drivers are up to date, including chip set and bios and I run stock clocks for troubleshooting. Wonder if a better mainboard would help???

Hey Micko,

A frustrating problem indeed...

I don't think a motherboard replacement will help, unless it is actually faulty perhaps.

Latest Bios reports as:

https://www.msi.com/Motherboard/support/X470-GAMING-PRO

Version:               7B79v1E

Release Date:     2019-11-12

And the latest AMD chipset driver package is:

https://www.amd.com/en/support/chipsets/amd-socket-am4/x470

Revision Number:    1.11.22.0454

Release Date:           2019-11-25

 

Confirming all are as above?

 

You've mentioned busy airports as in all is fine until hitting these busy airports?

Is there third party AI installed?

What happens if traffic is reduced to zero at those (previously) busy airports?

And yes as others have recommended clearing the shaders cache and the scenery index cache are typcially a first stop goto for any sort of issue given they can be acomplished quite simply and will regenerate when P3D is started.

Shader Cache: \AppData\Local\Lockheed Martin\Prepar3D v4\Shaders

Scenery Index Cache: C:\ProgramData\Lockheed Martin\Prepar3D v4\SceneryIndexes_x64

Cheers

 

Hi Rogen,

Thanks for looking into that. Just an idea with the mainboard, it's not the best board and designed for Ryzen 2 it might not be up for 3900X - physically.

Yes I can confirm the updates, all the latest. As I'm still troubleshooting after fresh install I have no addons at all, just a few carenados and traffic  settings are zero. When I set autogen and scenery draw distance to medium I could load a flight. Before it all happened I was able to set it to high and the rest dense or very dense, frames low to mid twenties in a smooth flight. and remember no addons, just plain P3D scenery. I load a flight at KJFK with all sliders to the right. Very strange.

Anyway, I try the scenery index tomorrow, do the generated files and report back then.

Thanks again

Mick

Good news for now, I have done delete generated files thing, documented every single change in the sim and p3d.cfg and restarted the sim after every change. installed Rex Sky Force, Texture Direct and Reality XP. Hard to believe but not a single Kernellbase.dll error so far - knock on wood. Hard to believe because it's the 2nd time I have done the generated files, the only difference is I made the changes step by step. Now I'm going to install the rest like ai traffic, meshes and the Orbx. Let's see what happens after a few flights tomorrow I keep you posted

Cheers Mick