Yes. The important point is that 0xe0434352 is a generic .NET/CLR exception, while KERNELBASE.dll is usually just where Windows reports the crash. It does not mean KERNELBASE.dll itself is necessarily faulty.
For NAV 2016, I would troubleshoot in this order:
Check Event Viewer → Windows Logs → Application at the exact crash time.
Look for a “.NET Runtime” event immediately before/after Event ID 1000.
This should contain the actual exception, such as FileLoadException, NullReferenceException, etc.
Check NAV Server logs
Event Viewer → Applications and Services Logs
Look for Microsoft Dynamics NAV Server events immediately before the crash.
Check customizations/add-ins
Especially any custom .NET assemblies, DLLs, integrations, or extensions.
A NAV 2016 Service Tier crash with this exception can be triggered by custom .NET code or integrations.
Check Web Services/integrations
SOAP/OData services
Power BI/integration middleware
Third-party applications calling NAV
Check your NAV build.
Your build is:
9.0.52055.0
Microsoft released later NAV 2016 cumulative updates containing additional fixes. For example, CU30 is build 50221 and includes previous NAV 2016 hotfixes.
If it still crashes, capture a crash dump for Microsoft.Dynamics.Nav.Server.exe. This is usually the fastest way to identify the actual failing assembly/code.
