Prepa3D crashes

Other problems or issues not covered by other troubleshooting topics.
Posts: 12
Joined: Sat May 23, 2020 11:24 am

Re: Prepa3D crashes

Postby Tazflyer » Tue Jun 02, 2020 10:27 am

Adding onto my last post, i can confirm the crashes are NOT caused by windows.
While running sfc testing, there are no issues with windows.

The errors only come up with P3DV4
How did you confirm what is causing
Faulting module name: KERNELBASE.dll (Windows file) error?

Do you have any Add-ons installed in your P3Dv4 setup?
I can confirm this error was happening with default p3d no addons
Intel Core i5 9600k 3.7GHz
ASUS TUF H310M-PLUS Gaming LGA1151-CL mATX Desktop Motherboard
Corsair 16GB Kit (2x8GB) DDR4 Vengeance LPX Black C16 2400MHz
Samsung 970 EVO Series 500GB M.2 NVMe SSD
RTX Geforce 2070 8GB gpu

Posts: 2761
Joined: Sun Mar 11, 2018 7:17 am
Location: 5 NM NE of EDXF

Re: Prepa3D crashes

Postby JorgenSA » Tue Jun 02, 2020 12:15 pm

I have personally not seen this error in v. 4.5 or 5, and I can guarantee you that it IS a Windows error, just try and google it. You will not like what you see.

Now, a friendly user of these forums experienced this error, and took the time to write down the steps he took to resolve it - this is a long document:

"So my steps are as follows:
Searched Google for "kernelbase.dll crash p3d v5" and got directed here
Which led me to this reply "I've had this issue too and solved it by removing Carenado's cmeteoxml.dll."
I removed that file and any other files that had to do with Carenado aircraft "Because, OFFICIALLY, Carenado installers do not direct to P3D v5, so my assumptions is that they didn't update their files to be v5 compatible.
Anyway, after that I flew a flight and three hours in, same event viewer error: kernelbase.dll
So alright, well that wasn't now I start looking into more generic kernelbase.dll error google searches and find a post here that gave me a few steps to follow: ... ash-issue/
(NOTE: From the above link, I ran fix number two only)
Well when I did that, there was an update, so I ran it and was like "alright, we'll see what happens" BUT, I was satisfied because my flights crash after about 4 hours in the air and I wasn't willing to test run the sim to see if it was fixed after only running windows updates; I desired more proof that there would be a solution. So back to Google....
Ended up here and ran method 3:
Basically, open the cmd prompt as admin and type "sfc/scannow" minus the quotes. Ran it and it found no "violations" as it so professionally put it, so that wasn't a problem.
THEN, I went back to google and came across THIS: ... rs-2623534
I ran steps 8 and 9 (Step 9 found a LOT of issues).
Then I saw somewhere (can't find the link right now) about a tool called ... n_one.html
that repairs windows files. Follow their steps, keeping in mind that I did the tool BEFORE running the registry cleaner (I elected to go with and again, they found lots of issues; 23,000 and change to be exact.
Now after all that was said and done, I wanted to make sure I didn't miss anything, so I looked and looked again (like Santa checking his list twice), and found this last thread: and reading the last post on it (Friday April 15, 2016 by 'downscc'), I decided to completely remove my graphics drivers and reinstall (even though NVIADIA GeForce Experience claimed I had the latest and greatest, at this point I was desperate; leave nothing untested). So I searched around for how to go about tackling this next task and found this:
Super helpful video on how to safely remove and reinstall your graphics drivers. Here's the link for the program to unistall the drivers: ... nload.html
Here's the link to download new ones (NVIDIA):
He references both programs in the video and shows how to use them. Have the programs downloaded before watching the video.
If ALL ELSE FAILS, read this ... elbasedll/ and read June 4, 2017 by Jim Young and reinstall windows completely. (I did not do this; after running ALL the steps listed above, I tried another flight and am currently about 5 hours into it with no issues yet; I land in another 8 hours, so we'll report back tomorrow and advise if I ran into any issues)
So long story short, all those steps (IDK which one) I listed above appear to have helped me. If the sim crashes on this flight i'm on right now, i'll be forced to take Jim's advice and reinstall windows (Or I could just throw the desktop out my window onto the driveway; we'll see how I feel when I wake up).
Hope this helped. Yea, it's a hell of a read, but hopefully you'll find some new luck as I seem to have found, too.
Another theory I have, which opens a whole new can of worms, is the crashes i've experienced so far have all been three-four hours into flights i've been flying during simulator day time. This flight i'm flying (and another one I flew two days ago without any crashes) was flown all in simulator night time. Maybe a factor? IDK, i've considered so many factors that hey, that might be another one to consider, huh? Not sure what to do with that information, but interesting none the less."

Turns out my problems were not from Carenado (I don't think - I haven't tried to reinstall those planes yet), nor were they from flying during the daytime. But in FACT, I found out yesterday morning, that my crashes were coming from ActiveSky Open Beta 2. So yesterday morning HiFi releases ASP3D v3 BETA and this is part of the change log:

"– Attempted fix for P3Dv5 CTD / crash issues including crash triggered by higher-latitude areas above 53N with EA mode off"

YES! I was getting these crashes with EA (Enhanced Atmospherics) off above 53*N. So finally, a fix to my issues! (DISCLAIMER**: I have yet to fly above 53*N to test this "fix") Well.....most things that are too good to be true; aren't true. Especially when the word "BETA" is involved. So now here's the issues I am having. ... -fps-issue

That leads me here: ... rol.12457/

So cool, they fix one issue and inject another. So now I need to fly with the WX RADAR OFF int eh PMDG 747 to avoid it from falling out of the sky. Sooooo....long story short, i'm not sure that all of the above steps with the registry cleaner and all that were 100% required; it appears it was just a bug with the AS P3D BETA, which I should've known better than to be on the verge of a windows reinstall honestly.

Anyway, everything seems to be running fine now. I flew SCEL-EHAM last night, and had some error overnight that didn't crash the sim, but said something along the lines of "AS unable to inject (cloud type) Restart P3D." So now i'm flying again to hopefully recreate that issue and jot down EXACTLY what it says.

Have fun with resolving this -

System: i7-7700K @ 4.66 GHz, ASUS Z170-A motherboard, 16 GB 3200 MHz DDR4 RAM, nVidia GTX 960 w/ 4 GB DDR5 VRAM, Windows 10 Home.

All views and opinions expressed here are entirely my own. I am not a Lockheed-Martin employee.

User avatar
Posts: 10113
Joined: Sun Mar 25, 2012 11:08 am

Re: Prepa3D crashes

Postby Martyson » Wed Jun 17, 2020 7:50 am

Who was the author of the document you re-posted and a link to the original forum post / discussion?
Best Regards,
Vaughan Martell (KDTW)

Return to “Other Support Questions”

Who is online

Users browsing this forum: No registered users and 51 guests