JCM3000 -> RE: Chains of war mission 1 repeatedly crashes (1/16/2018 5:29:57 PM)
|
quote:
ORIGINAL: JCM3000 I'm having the same issue specifically with Chains of War Scenario 1 Blue Dawn. It keeps crashing at random times about every 5 minutes. It's gotten to the point that I have to save every few minutes. I have autosave disabled to save system resources and to some degree reduce disk usage on my SSD. I've never had this problem with any of the standalone or community pack scenarios. With other scenarios I've sometimes had very laggy performance and occasional freezes that last a few seconds, but I've never had crashes that result in the game completely shutting down and the Windows prompt appearing that says the application has been closed and that Windows will send an error report to Microsoft, yada yada. Here's a save file. The game crashed about 4 minutes after this, but I was able to reload and play for about another 10 minutes after that before it crashed again. So the problem seems intermittent as I've reloaded several times from this same save point and gotten varying degrees of time before it crashes again. Btw, I'm running the Steam version. As a follow up to my post above, I took a look at the Windows error logs. All of the crashes show the same error, an application error with the following details: - System - Provider [ Name] Application Error - EventID 1000 [ Qualifiers] 0 Level 2 Task 100 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2018-01-16T18:12:39.417130700Z EventRecordID 6452 Channel Application Computer JM-Laptop Security - EventData Command.exe 1.0.0.0 5a19a6ce lua52.DLL 5.2.3.0 55dc8abc c0000005 00019f38 1cc4 01d38ef4f6463440 C:\Program Files (x86)\Steam\steamapps\common\Command Modern Air Naval Operations\GameMenu_CMANO\..\Command.exe C:\Program Files (x86)\Steam\steamapps\common\Command Modern Air Naval Operations\lua52.DLL 2af0e6ad-045c-49e6-93a0-10630a24fb75 and a .Net Runtime error at the same timestamp: [image]local://upfiles/58352/ED455E3B9C29428C8FC7C1972451B764.jpg[/image] The Details tab of the .Net Runtime error log is as follows: This event is not displayed correctly because the underlying XML is not well formed. Below is the raw text of the event. 1026200x800000000000006451ApplicationJM-LaptopApplication: Command.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException at KeraLua.NativeMethods.LuaNetGetGlobal(IntPtr, System.String) at NLua.Lua.get_Item(System.String) at Command_Core.Lua.CMANO+.(Command_Core.ActiveUnit, System.Object) at Command_Core.Lua.CMANO+.€(Command_Core.ActiveUnit, System.Object) at Command_Core.ActiveUnit_DockingOps.(_DockingOpsCondition) at Command_Core.Submarine.†() at Command_Core.Submarine.(Command_Core.Engine, Command_Core.FuelRec, Single) at Command_Core.Submarine.Š(Single) at Command_Core.GameGeneral.(Command_Core.ActiveUnit, Command_Core.ActiveUnit[], Single) at Command_Core.GameGeneral+.(Int32) at System.Threading.Tasks.Parallel+<>c__DisplayClass17_0`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].<ForWorker>b__1() at System.Threading.Tasks.Task.InnerInvoke() at System.Threading.Tasks.Task.InnerInvokeWithArg(System.Threading.Tasks.Task) at System.Threading.Tasks.Task+<>c__DisplayClass176_0.<ExecuteSelfReplicating>b__0(System.Object) at System.Threading.Tasks.Task.InnerInvoke() at System.Threading.Tasks.Task.Execute() at System.Threading.Tasks.Task.ExecutionContextCallback(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef) at System.Threading.Tasks.Task.ExecuteEntry(Boolean) at System.Threading.Tasks.Task.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback() Hopefully that helps!
|
|
|
|