CTD- Hard to Trace (Full Version)

All Forums >> [New Releases from Matrix Games] >> Gary Grigsby's War in the East 2 >> Tech Support



Message

kahta -> CTD- Hard to Trace (8/20/2021 1:32:19 AM)

I recently installed WITE2 on a new computer. I am experiencing a CTD that is difficult to trace and within the first few minutes of starting to play a game.

It happens under any of the following circumstances:

Sometimes it is possible to play a full turn, but then the game crashes during the AI turn (at different phases)
Sometimes it crashes after a successful quicksave
Sometimes it happens during the air phase.

I am running 1.01.03, but it also happened with 1.01.07.

I've uploaded the dump files to the Bug Saves folder on the beta FTP site into a folder called "Kahta CTD".

Please let me know if you have any questions or if there is anything I can do to help trace this.



kahta -> RE: CTD- Hard to Trace (8/23/2021 6:01:26 PM)

It appears this is related to the graphics; trying to play on full screen mode results in a near instant crash as opposed to windowed which happens after 30 seconds to a minute.



Joel Billings -> RE: CTD- Hard to Trace (8/23/2021 9:23:23 PM)

Can you check if you have a crash dump file named like WarInTheEast2.exe.<number>.dmp in C:\Users\<your username>\AppData\Local\CrashDumps ?

If you find one, please zip and attach it to the forum message. Thanks. Be sure to let us know what version you were running when the crash dump file was generated. Thanks.



kahta -> RE: CTD- Hard to Trace (8/23/2021 10:31:06 PM)

quote:

ORIGINAL: Joel Billings

Can you check if you have a crash dump file named like WarInTheEast2.exe.<number>.dmp in C:\Users\<your username>\AppData\Local\CrashDumps ?

If you find one, please zip and attach it to the forum message. Thanks. Be sure to let us know what version you were running when the crash dump file was generated. Thanks.



The file is almost 100MB, so they are too big to upload here. I've uploaded them to the beta ftp site in /Bug Saves/Kahta CTD/

The bug is happening in 1.01.03.

Thanks again!



Joel Billings -> RE: CTD- Hard to Trace (8/26/2021 6:03:42 PM)

Do you know what versions you were running for each crash dump. This can be very important info for Pavel. There are two crash dumps dated later than the others. Were these on 1.01.07 and the earlier ones on 1.01.03?



kahta -> RE: CTD- Hard to Trace (8/27/2021 7:24:33 PM)

The older ones were 1.01.07 and the newer ones are 1.01.03



Joel Billings -> RE: CTD- Hard to Trace (8/27/2021 9:40:50 PM)

I've put your report in our database system for Pavel to look at, but I can't say how soon he's going to be able to look into it. He was busy this week with a few other bugs and the Multiplayer connectivity issue (for players with bad connectivity), which we think is now resolved. It is strange that you're getting it on the new computer. I will say that I had my son build a new computer for me 2 1/2 years ago. After trying to play WitE2 (pre-release) but having it constantly crashing on me in strange ways, it turned out I had a defective (brand new, at least we thought it was when we bought it) Intel chip. We had to get a new chip and then everything worked great. It had nothing to do with the game.



kahta -> RE: CTD- Hard to Trace (9/9/2021 4:37:17 PM)

I doubt it is that; I've tried playing other games and doing other things and I don't have any issues with this computer except for WITE2. Changing the display scaling from auto to 100% seemed to make the game last longer, but it still crashes. I also noticed that it doesn't crash until I close the turn summary window. If I leave that open, it seems to work fine.

I have tried the newest 1.09 and 1.10 patches and I am still experiencing the issue. The first 3 files are from 1.09 and the last one is from 1.10. I've uploaded them to the beta FTP site with the name "Newest 4 Crashes.zip"



Joel Billings -> RE: CTD- Hard to Trace (9/9/2021 5:40:47 PM)

I have just attached these to the bug item so Pavel can take a look. He reported that 1.01.03 was a bad exe. Hopefully he can use the 1.01.09beta crash dumps to get an idea of what the problem might be.



kahta -> RE: CTD- Hard to Trace (9/9/2021 7:17:39 PM)

Excellent! Please don't hesitate to let me know if I need to do anything on my end to try to help troubleshoot the issue.



Helpless -> RE: CTD- Hard to Trace (9/13/2021 2:31:24 PM)

I've checked dump files provided. It is crashing in igdumdim32.dll module which seems to be Intel's video driver.

Unfortunately I don't think it could be addressed in the game code. The only recommendation would be to check newer video driver.

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 00000001
EXCEPTION_PARAMETER2: 00000000

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
0e04fc8c 6845632d 00000000 08cc2900 00001240 igdumdim32+0xd152
0e04fd00 683d250e 10258c58 683d250e 06836f00 igdumdim32+0x9632d
0e04fd2c 68405661 06836f00 06836f00 00000006 igdumdim32+0x1250e
0e04fd40 684047b6 06836f00 00000004 0e04fd68 igdumdim32+0x45661
0e04fd7c 69e88a17 06836f00 0dd8f0fc 0dd89040 igdumdim32+0x447b6
0e04fda4 69e89a91 0dd892dc 00000001 69e88760 d3d9!CBatchFilterI::ProcessBatch+0xc3
0e04fdbc 69e8876d 0e04fdd4 75aefa29 0dd89040 d3d9!CBatchFilterI::WorkerThread+0x2d
0e04fdc4 75aefa29 0dd89040 75aefa10 0e04fe30 d3d9!CBatchFilterI::LHBatchWorkerThread+0xd
0e04fdd4 774c7a7e 0dd89040 afb2bb56 00000000 kernel32!BaseThreadInitThunk+0x19
0e04fe30 774c7a4e ffffffff 774e8a11 00000000 ntdll!__RtlUserThreadStart+0x2f
0e04fe40 00000000 69e88760 0dd89040 00000000 ntdll!_RtlUserThreadStart+0x1b

SYMBOL_NAME: igdumdim32+d152
MODULE_NAME: igdumdim32
IMAGE_NAME: igdumdim32.dll
STACK_COMMAND: dt ntdll!LdrpLastDllInitializer BaseDllName ; dt ntdll!LdrpFailureData ; ~4s ; .ecxr ; kb
FAILURE_BUCKET_ID: NULL_POINTER_WRITE_c0000005_igdumdim32.dll!Unknown
OS_VERSION: 10.0.19041.1



kahta -> RE: CTD- Hard to Trace (9/15/2021 2:01:56 PM)

Thank you, I had to update it from the Intel website. That seemed to fix it



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
1.078125