After updating to 100.2, I experience very frequent win32 exceptions. This could either be when the application is starting (map loading), entering a Remote Desktop Connection while the application is running, or other fun situations.
The attached debugger is not able to debug this information. Are there steps you would recommend for providing you with more information about these crashes to hopefully have them quickly fixed (hot fix if possible). As it is, upgrading looks like a big risk considering the number of crashes we have experienced so far.
I've started the sample application over remote, and will see if similar issues occur there when I get back to the office tomorrow morning.
This is just a small sampling:
Faulting application name: MapTestClient.exe, version: 1.0.0.0, time stamp: 0x5a5606fe
Faulting module name: ntdll.dll, version: 10.0.15063.608, time stamp: 0x802f667e
Exception code: 0xc0000374
Fault offset: 0x000d9aba
Faulting application name: MapTestClient.exe, version: 1.0.0.0, time stamp: 0x5a5606fe
Faulting module name: RuntimeCoreNet.dll, version: 100.2.0.1912, time stamp: 0x5a31e8b2
Exception code: 0xc0000005
Fault offset: 0x0167a89c
Faulting application name: MapTestClient.exe, version: 1.0.0.0, time stamp: 0x5a5606fe
Faulting module name: ucrtbase.dll, version: 10.0.15063.674, time stamp: 0xd8c924c3
Exception code: 0xc0000409
Fault offset: 0x000a543b
Faulting application name: MapTestClient.exe, version: 1.0.0.0, time stamp: 0x5a54ea80
Faulting module name: KERNELBASE.dll, version: 10.0.15063.726, time stamp: 0x32774c02
Exception code: 0xe06d7363
Fault offset: 0x000ecbb2
Faulting application name: MapTestClient.exe, version: 1.0.0.0, time stamp: 0x5a54b608
Faulting module name: VCRUNTIME140.dll, version: 14.10.25008.0, time stamp: 0x589abc77
Exception code: 0xc0000005
Fault offset: 0x0000dc07