Sim City Societies Crashes

First and foremost, if anyone is taking the time to read this, thank you! I know the game is ancient and pretty much dead, but I have a big soft spot for it and at around 2GB it's great to play while I am traveling.

While trying to run Sim City Societies it consistently crashes. The game installs fine, the game launches without issue, starting a new city produces no problems. The game is stable when starting a new city. Once the city is a bit more established it begins to consistently crash. 

Computer specifications:

Device: OMEN Transcend Gaming Laptop 14

Intel(R) Core(TM) Ultra 7 155H   3.80 GHz (Meteor Lake chipset)

DDR5 Ram 16.0 GB (15.4 GB usable)

NVIDIA® GeForce RTX™ 4060 Laptop GPU (8 GB) + 16 GB(Onboard)

Windows 11 Home 24H2

Reproduceable error captured in event viewer: 

Event ID 1000

Faulting application name: SimCitySocieties.exe, version: 1.0.0.6, time stamp: 0x4716aa5f
Faulting module name: MSVCR80.dll, version: 8.0.50727.9680, time stamp: 0x6090c909
Exception code: 0x40000015
Fault offset: 0x000046b4
Faulting process id: 0x42E0
Faulting application start time: 0x1DB907010B98FA0
Faulting application path: C:\Program Files\EA Games\SimCity Societies\SimCitySocieties.exe
Faulting module path: C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9680_none_d090cb7c44278b28\MSVCR80.dll
Report Id: ed5ce1c7-db41-4257-b4fa-09029b5f1546
Faulting package full name: 
Faulting package-relative application ID: 

(Information error in event viewer right after the crash)

Event ID 1001

Fault bucket 2260470418983654465, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: SimCitySocieties.exe
P2: 1.0.0.6
P3: 4716aa5f
P4: MSVCR80.dll
P5: 8.0.50727.9680
P6: 6090c909
P7: 40000015
P8: 000046b4
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ce33962e-17fa-4753-b379-d434fc8c93d8.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.7e06b608-0e06-420f-b121-30acc866547f.tmp.WERInternalMetadata.xml
WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20250305_1_EC_0_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a3e3a8d1-3dd0-45be-88f8-a71dffd5f23c.tmp.etl
WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.7e17a8a8-5314-47a3-a270-6bb7874c55db.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.7e42fda0-0bcb-4f7e-910c-851cb3288786.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e02735af-1f66-463c-b130-f98ec516888f.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f97097e5-60cd-45b3-9a3a-179906d27fde.tmp.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_SimCitySocieties_f1fc8b3fbf6543b32d922b7befc81ea56345_af79cd01_7c7582cb-10f8-48e6-a4dd-252e6437eff3

Analysis symbol: 
Rechecking for solution: 0
Report Id: ed5ce1c7-db41-4257-b4fa-09029b5f1546
Report Status: 268435456
Hashed bucket: 31e05b63970254370f5ecdde9ccc9441
Cab Guid: 0

Trouble shooting steps taken:

• Computer reboot.
• Uninstall and reinstall the game.
• Repair the game.
• Run in compatibility mode for Windows 98, Windows XP SP1, Windows XP SP2, Windows XP SP3, Windows Vista, Windows 7, and running it in native Windows 11.
• Run as administrator.
• Try launching the game from the actual file directory as administrator.
• Removed ALL Visual C++ redistributable and manually installed all of them.
•  Manually increased virtual memory from 2000 to 4000.
• Opened command prompt as administrator and ran sfc /scannow and found no issues
• Opened regedit and here are my current configs for the game ~ DISABLEDXMAXIMIZEDWINDOWEDMODE RUNASADMIN HIGHDPIAWARE WIN98
• Set all settings to low and run the game in windowed mode.

The faulting module is MSVCR80.dll, version: 8.0.50727.9680

Thank you for any assistance provided! I hope someone can help me get this ancient relic to run stable.

I am trying to upload a .wer file but it is not supported. I am uploading it as a .txt, all of the information is still there. I am hoping this can isolate the cause of the issue.