This seems to be associated either with touching stacks of soldiers or redirecting the marching orders for such stacks.
A literally identical crash has occurred twice in 8 hrs, albeit with different circumstances. In one, armies are marching about in Prussia, in the other, armies are marching about in the Rhineland. (Both as England.)
The identical memory address exceptions in completely different application instances strongly suggest a coding error with a memory reference, as does the extremely low read destination address.
The explicit log is attached below. Please let me know if you need more "pointers".
######## EXCEPTION: 0xC0000005 at address: 0x0058A6A6: ACCESS VIOLATION read attempt to address 0x00000214
10/28/07 04:25:18
SymGetLineFromAddr(): GetLastError = 126
StackWalk(): GetLastError = 487
######## EXCEPTION: 0xC0000005 at address: 0x0058A6A6: ACCESS VIOLATION read attempt to address 0x00000214
10/28/07 13:08:41
SymGetLineFromAddr(): GetLastError = 126
StackWalk(): GetLastError = 487
A literally identical crash has occurred twice in 8 hrs, albeit with different circumstances. In one, armies are marching about in Prussia, in the other, armies are marching about in the Rhineland. (Both as England.)
The identical memory address exceptions in completely different application instances strongly suggest a coding error with a memory reference, as does the extremely low read destination address.
The explicit log is attached below. Please let me know if you need more "pointers".
######## EXCEPTION: 0xC0000005 at address: 0x0058A6A6: ACCESS VIOLATION read attempt to address 0x00000214
10/28/07 04:25:18
SymGetLineFromAddr(): GetLastError = 126
StackWalk(): GetLastError = 487
######## EXCEPTION: 0xC0000005 at address: 0x0058A6A6: ACCESS VIOLATION read attempt to address 0x00000214
10/28/07 13:08:41
SymGetLineFromAddr(): GetLastError = 126
StackWalk(): GetLastError = 487
Upvote
0