Another user had the same KERNELBASE.DLL error, and looked for a solution. He took the time to write down and post here what he did, and I am, with his permission, taking the liberty of re-posting the essential parts of his post here:
"So my steps are as follows:
Searched Google for "kernelbase.dll crash p3d v5" and got directed here https://www.prepar3d.com/forum/viewtopic.php?t=133018
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 it...so 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: https://www.drivereasy.com/knowledge/fi
(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: https://www.minitool.com/news/kernelbase-dll.html
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: https://www.lifewire.com/how-to-fix-ker
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 https://www.tweaking.com/content/page/w
that repairs windows files. Follow their steps, keeping in mind that I did the tweaking.com tool BEFORE running the registry cleaner (I elected to go with https://www.wisecleaner.com/wise-registry-cleaner.html
) 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: http://www.prepar3d.com/forum/viewtopic.php?t=118095
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: https://www.youtube.com/watch?v=bP-2B14Nckw
Super helpful video on how to safely remove and reinstall your graphics drivers. Here's the link for the program to unistall the drivers: https://www.guru3d.com/files-details/di
Here's the link to download new ones (NVIDIA): https://www.nvidia.com/Download/index.aspx
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 https://www.avsim.com/forums/topic/5110
... 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. https://forum.pmdg.com/forum/main-forum
That leads me here: https://forums.hifisimtech.com/threads/
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."
Now, this is a long process, but this IS a Windows error that can be fixed.....