Anyhow, I'm getting a Kernelbase.dll error several hours into my flights just prior to or during descent.
Yes; I'm running the application as an administrator, and I'm by no means out of VAS.
I'm using FTX: Global, FSLabs A320X, ActiveSky Next, REX, GSX, (VFX Central) & Chaseplane.
No FSUIPC because of glitches caused.
Did you look into graphics drivers being the culprit? I seen some reference to this error being from graphics drivers, and I just had to roll back my up-to-date Nvidia to much older one to avoid crashes. I went back to 376.33 and now the freezes and crashes went away. I had different errors but it's worth considering if it's a new problem.
· Updating or reinstalling their video card drivers.
· Scanning your system for corrupt/missing files.
· In Windows 7, disable startup programs by typing msconfig in the Windows search box. When open, look at the Startup tab and disable all startups (they are all not needed for operation of your computer). In Windows 10, CTRL+ALT+DEL and open the Task Manager and click on the Startup Tab and disable all of those tasks. Restart Windows.
. User Profile Corrupted – last resort, fix possible corrupted user profile.
The Guide has links to the fixes shown in bold letters above.
The Kernelbase.dll is memory related (not VAS) and belongs to your computer system files and has nothing to do with P3D. P3D just happened to be running when the error occurred.
Forgot to mention there's a neat little program I use occasionally that fixes Windows installations without changing anything on your current Windows Installation or your installation of P3D. It's freeware and a very safe program to use. It's called Windows Repair from Tweaking.com. With this program, you will never have to reinstall Windows (and then P3D and all of your add-ons). It was developed by former Microsoft Techs (and there might be a couple of current techs helping out too.
I'll try this and report back my findings.
Will doing so, however, result in anything...well...bad?
No, just save or remember any Nvidia inspector settings you have. I screen cap mine. Then install the older driver and perform a clean install. Then recreate your Nvidia inspector profile with the settings you like and give it a try. I saw no change, other than my sim now runs without crashing.
I have run the program several times in Windows 7 and Windows 10 and have never had any problems. I never had the program change my display driver settings for FSX or P3D or my system but then I mainly use the Nvidia Inspector (but definitely do not for P3DV4!!). It backs up your registry. Provides a restore point. You do the repairs in Safe Mode. I think the developers of the program made it very safe. There are logs in the Tweaker folder that show all of the things it did and all of the errors found (if any).
Unfortunately neither of these solutions worked.
to the user DESKTOP-N7C076F\cp1gm SID (S-1-5-21-976831345-3193547911-917370624-1002) from address LocalHost (Using LRPC) running in the application container Microsoft.WindowsStore_11703.1001.45.0_x64__8wekyb3d8bbwe SID (S-1-15-2-1609473798-1231923017-684268153-4268514328-882773646-2760585773-1760938157). This security permission can be modified using the Component Services administrative tool.
Only "solution" left is to reformat your HDD or SSD and reinstall Windows. Unfortunately there is no known solution for the Kernelbase.dll crash but some people have accidentally fixed it by doing some of the things listed in the AVSIM CTD Guide. I got those possibilities by Googling the error and found the solutions were used to fix a persons kernelbase.dll error. I personally have reformatted my SSD and reinstalled Windows.
This is an older thread but I wanted to post the solution that fixed my KERNELBASE.DLL errors.
The symptom was K..B..dll errors when closing FSX. Didn't matter what plane, scenery, airport or any of my other addons that were run or used.
I am 100% certain the cause was something related to the ConcordeX product from Flight Sim Labs.
The fix was to uninstall my ConcordeX, reboot, re-install ConcordeX, reboot, done. No more errors.
Sorry for bumping this thread back up but I am also experiencing this issue after upgrading my p3d from 4.4 to 4.5. Didn't happen before the update.
Its happening randomly. I don't have FSL Concorde but I do have FSL A320.
However this crash first occurred yesterday with FSL A320 approaching into FlyTampa OMDB with traffic set to 0.
Today it happened using QW 787 loading Imaginesim WSSS scenery.
Addons I use are Orbx FTX Global, ASP4, ASCA, GSX Expansion.
Right now I am updating my Nvidia driver from 419.35 to 425.31. I can't be sure if it occurs again because it happens randomly very occasionally.
I can't be sure if it occurs again because it happens randomly very occasionally.
Since it happens occasionally, I would suggest it is a corrupted User Profile and issue with permissions. In order to fix your problem you will need to investigate by going to page 10, AVSIM CTD Guide, How to Fix Most CTD's with P3Dv4.4 and 4.5. For scenery and if you are using the Lorby Si Addon Organizer, you simply go to C:\Documents\My Prepar3Dv4 Addons. Move the contents inside this folder to a temporary folder. If this fixes the problem, then it is one of your sceneries not compatible.