Game crashes immediately after launch

[Orange Popsicles]

When I try to run the game from Steam, a smaller Steam window pops up momentarily and then disappears - faster than I can see what it says. In my game library list, the game gets the "Running" status for a few seconds, but then that goes away. In my Windows Task Manager, I can see the "platformines.exe" executable pop up under the Processes tab, and then it goes away after a second or two.

I am running Windows 10 x64, fully up-to-date. All drivers up to date as well.

I took a look in the Event Viewer, and for every attempt to run the game, I find 3 events, as follows:

Event 1:

Application: platformines.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
   at   .()

Event 2:

Faulting application name: platformines.exe, version: 1.0.2.0, time stamp: 0x533ec2c6
Faulting module name: KERNELBASE.dll, version: 10.0.14393.479, time stamp: 0x58256d37
Exception code: 0xe0434352
Fault offset: 0x000da832
Faulting process id: 0x103c
Faulting application start time: 0x01d278463f2e00bb
Faulting application path: E:\Games\Steam\SteamLibrary\steamapps\common\Platformines\platformines.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 25e99059-742b-49a7-a8ec-90cf077f584e
Faulting package full name: 

Event 3:

Fault bucket 108618887980, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: platformines.exe
P2: 1.0.2.0
P3: 533ec2c6
P4: KERNELBASE.dll
P5: 10.0.14393.479
P6: 58256d37
P7: e0434352
P8: 000da832
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB6C.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_platformines.exe_cbec368246446777485eb4db9d5d60fc5569df62_240641a3_15efce3a

Analysis symbol: 
Rechecking for solution: 0
Report Id: 25e99059-742b-49a7-a8ec-90cf077f584e
Report Status: 0

Any help would be greatly appreciated. Thanks!
-Doug

[bidus.vidal]

Hello,
This link could(?) help you:
https://social.msdn.microsoft.com/Forums/vstudio/en-US/2556a86b-f82e-4efb-bcdd-19919facbff6/application-error-faulting-module-name-kernelbasedll-version-61760016385?forum=vcgeneral
Search for "Faulting module path: C:\Windows\system32\KERNELBASE.dll", it seems that people facing the same error as you solved their problem.
Please inform me.
Regards

[Orange Popsicles]

Thanks for responding!

So I followed your link, and didn't find too much help. I noticed one person mentioned starting/enabling the "Performance Logs & Alerts" service. Another person mentioned running the app as Administrator. Still another talked about a Data Execution Prevention (DEP) setting. I tried each of these and still get the same behavior.

I then tried performing some similar searches relating to .NET applications, the faulting module, the error codes, etc. One result included someone using the SysInternals Process Monitor application to try to see what is happening at the crash. So I grabbed it, and while I am unfortunately a novice in its use, I did come up with a few entries that may or may not be significant.

When filtering on the "platformines" string and then attempting to launch the game, I see multiple "NAME NOT FOUND" and "PATH NOT FOUND" results. For example, it shows that the "platformines.exe" executable is attempting to open or query the following files/paths in the application directory:

• BASE.INI
  
• Microsoft.Xna.Framework.Game.dll
  
• Microsoft.Xna.Framework.Game/Microsoft.Xna.Framework.Game.dll
  
• Microsoft.Xna.Framework.Game.exe
  
• Microsoft.Xna.Framework.Game/Microsoft.Xna.Framework.Game.exe
  
• platformines.PDB

There's also a few registry keys in that list that I didn't include, but can do so if you think it is helpful. I have manually checked, and all of those named files/paths/regkeys are missing. Should these have been created when the game is installed?

Shortly after this, there is a big list of "QueryNameInformationFile" operations that have the result "BUFFER OVERFLOW", but I can't seem to gather any meaningful information about them. Then, after that, a few normal-looking lines, and then a bunch of stuff originating from the "WerFault.exe" executable, which I assume has to do with Windows logging the actual crash, etc.