![]() To that effect, you may have to actually resort to re-installing the game. You may also wish to read the Company of Heroes 2 manual, which includes detailed explanations of the tactics youll need to master to succeed in Company of Heroes 2: Ardennes Assault. So, yes, it may be an obscure bug, but it may be that your game files got corrupt somehow. This manual lists both general controls and controls specific to the US Forces in the Company of Heroes 2: Ardennes Assault campaign. What I suggest, is that you notify Relic about it, either through the integrated "Send Report" functionality or through THQ support. I would not be able to tell you exactly what goes wrong inside RelicCOH.exe because I do not have access to the resources to do that. ![]() The fact that you always get it at a specific moment supports that. So, to sum up, it seems not to be a DirectX, graphics driver or sound driver related crash. The faulting module seems to be Debug.dll, which is provided by Relic and is responsible among others for the crash reports! The instruction that causes the crash is inside a function named dbCrashRunBugReport and follows immediately after instructions executed inside RelicCOH.exe, the main CoH executable. ![]() Well, it seems pretty weird stuff going on in the dump file. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |