[1.16]Error Popups

[Enderminion]

Game Setting: Austria, Manual Build, Historical Resources, Larger than Superlarge Fleet Size

I'm getting 2 errors every 2 months it seems in RTW 2 v. 1.16
The Second is "Error in CheckErrorInCoupMinor procedure! [line break] Access violation at address 0055E7D5 in module 'RTW2.exe'. Read of address 00000070"
The First is "Error in GetRandomPossession procedure! [line brea] Access violation at address 0055C4C4 in module 'RTW2.exe'. Read of address 800060A0"

Screenshots of the Error Reports and a Copy of the Save are included. War with Italy just broke out, sorry.

Attachment Deleted

[Enderminion]

Starting a Second Game of RTW2, Superlarge Historical Fleets, as the United States, Manual Build of Legacy Fleets, Harsher Peace Deals; the same error messages have come up.
Save attached.

[ursamaior]

Attachment DeletedAttachment Deleted1920
Germany
Large fleet
AI harder
Harsher Peace deals
No Versaiiles Treaty
Random Treary (12" 30k ton for 20 years!)

AFter upgrading to 1.16 I keep getting these messages.

[williammiller]

Thanks for the reports, we will check on those two error messages.

[Fredrik W]

Thanks! We'll get a fix out for this ASAP.

This error will have no ill effects except generating an annoying popup every few turns.

[rimbecano]

Feb 3, 2020 11:49:57 GMT -6 oldpop2000 said:

Access violations are generally caused by software interfering with the running of the game or app. Try turning off your antivirus before playing the game. Also, check windows security and turn it off. Someone could develop a batch file which will turn off the antivirus, then run the game. After the game is over, it will turn the antivirus back on. Many AV have a whitelist for a files that are considered safe and they won't be interfered with. I know Webroot has that function. Check you AV and see if it has a whitelist that you can add the game executable to the list. The team will know more about this. Just some ideas.

Unless the AV is force-loading itself as a library into every process's address space (in which case it becomes a part of whatever process is currently running), it shouldn't be able to cause an access violation in other processes on modern Windows. (On Win16/Win9x, processes weren't so well isolated from the kernel or each other, and misbehaving code could cause trouble outside its own process, up to and including bluescreening the entire system).

The only thing that can cause a process to suffer an access violation on a modern system is a bug in the program being run, or in one of the libraries it calls (or potentially in the kernel or a device driver, but that would tend to cause system-wide issues, including bluescreens). That said, I'm not familiar with the technical details of how AV packages are implemented, and it's possible that they are loaded as libraries into other processes' address spaces. In that case, I would still expect to see system-wide issues if there were a bug in the AV package (but no bluescreens, as in the kernel/driver bug case), but if turning off the AV solves the issue, a bug should certainly be filed with the AV vendor.

[Fredrik W]

This is an internal bug in RTW, nothing else.

[oldpop2000]

Post deleted as unnecessary.