Crashing to desktop with no crash report

[Arthwen]

This has been happening to my sister and I on a regular basis.
I recently did a fresh reinstall of Windows, so my GPU drivers should be good. We’ve also set the worker threads to 6. This has happened with Dx12 and without it, so that shouldn’t have any effect.

Any help you could provide would be greatly apprectiated!

crash_dump-2021-04-05-19.45.48-cdbfe13f-e0a6-4dc8-98a7-791c73a6c0ea.dmp (624.7 KB)

If it helps, the Windows Event Viewer reports the following error:
"Faulting application name: launcher.exe_Vermintide 2, version: 1.0.415.0, time stamp: 0x5fa26d0c
Faulting module name: KERNELBASE.dll, version: 10.0.19041.906, time stamp: 0x26452a2a
Exception code: 0xe0434352
Fault offset: 0x0012a6e2
Faulting process id: 0xff0
Faulting application start time: 0x01d72a53f91815fe
Faulting application path: D:\Steam\steamapps\common\Warhammer Vermintide 2\launcher\launcher.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 0a841a79-d081-40df-a400-f86eb7b18438
Faulting package full name:
Faulting package-relative application ID: "
And .net runtime error happened just a milisecond before as well, but I’m unaware if it’s connected or important to the crash.
“Application: launcher.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ComponentModel.Win32Exception
at MS.Win32.UnsafeNativeMethods.PostMessage(System.Runtime.InteropServices.HandleRef, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr)
at System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean, System.Nullable`1)
at System.Windows.Interop.HwndTarget.UpdateWindowPos(IntPtr)
at System.Windows.Interop.HwndTarget.HandleMessage(MS.Internal.Interop.WindowMessage, IntPtr, IntPtr)
at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)”

[FatsharkLev]

@Arthwen

Faulting module name: KERNELBASE.dll

Hi @Arthwen,

This error usually indicates a corrupted Windows User Profile.

Check that you have the latest updates for Windows installed.

You can also try running the Windows System File Checker, which will replace any corrupted Microsoft DLLs.

1. Launch ‘Command Prompt’ as an Administrator
2. If prompted for an administrator password or confirmation, enter the password or select ‘Allow’
3. Enter the command: sfc /scannow
4. Restart your PC once complete

Otherwise, you may need to create a new Windows User Profile.

[Arthwen]

Does this mean I’d have to make an online Windows account instead of an offline one, which I currently have set up?

[Arthwen]

I’d like to provide some further details about this crash in hopes it might illuminate the situation further. I have freshly reinstalled Windows and it has all the latest drivers, updates, bells and whistles.
We’ve tried to run sfc /scannow before and while it did find some corrupted files that it claimed to repair, the crash persisted and it kept occuring for some reason.

My sister, a friend and I have all experienced this crash and it only seems to occur to the one of us that is currently hosting.

[FatsharkLev]

Thanks for the added info @Arthwen

I’ve passed this along to the development team and someone will take a deeper look later this week.

[Arthwen]

Any updates on the situation?

[FatsharkLev]

Hi @Arthwen,

We’ve actually uncovered two issues that require code fixes our end. Unfortunately, I can’t provide an immediate solution for you - but be assured we’re working on it. Sorry for the inconvenience in the meantime!