transportvur.blogg.se

Or is this exactly the problem, the program trying to open a 64Bit dll in C:\WINDOWS\System32\ and then of course getting error 0xc0000005, which means something like cant access, which would be true for a 64Bit DLL. What I dont know, and maybe somebody can help me here, do I look at the problem when I see the path C:\WINDOWS\System32\ in the crash log, or is this just the 32/64Bit mechanism of Windows reporting a C:\WINDOWS\System32 dll when its really the 32Bit dll in C:\Windows\SysWOW64\ ? If you start SupremeCommander with the command line option /nomovie /nosound you see that ProcessExplorer shows no dependency to xactengine2_9.dll (and the game will not crash, but will also have no sound). The module xactengine2_9.dll which crashed is responsible for the audio effects. If you compare this with the output of the Tool ProcessExplorer (procexp.exe from ) during run of SupCom you see that xactengine2_9.dll is used by SupCom, but with the path of a 32Bit Exe (C:\Windows\SysWOW64\xactengine2_9.dll) which should be the case with a 32Bit application. 0, time stamp: 0x46a06729įaulting application start time: 0x01d329baa147e855įaulting application path: F:\SteamLibrary\steamapps\common\Supreme Commander Forged Alliance\bin\SupremeCommander.exeįaulting module path: C:\WINDOWS\System32\xactengine2_9.dll

There you find your Supreme Commander crash and something like this (I took Naginooh's example because its in English):įaulting application name: SupremeCommander.exe, version: 1.5.0.1, time stamp: 0x4e5c092eįaulting module name: xactengine2_9.dll, version. After a crash I took a look into the Windows Event Viewer (Computer Management - Event Viewer - Custom Views - Aministrative Events - Application Events)