Game CTDs from plugins

[Oidaas 1,650]

I've got an issue with my plugins, especially Mattb325 since the game ctds. The thing is that they worked on my old computer. I dont know what is causing this, would be grateful for help on the matter,

[CaptCity 4,893]

Hi @Oidaas

Is this a new game install on a different computer? If so, and if you use NAM and just copied it over, did you re-apply the 4gb patch? That might be one thing to check.

Or did you narrow it down to something with one of Mattb325's plugins? 

[rsc204 21,857]

16 hours ago, Oidaas said:

The thing is that they worked on my old computer. I dont know what is causing this, would be grateful for help on the matter,

So are you saying that the game itself is crashing, because that doesn't necessarily mean that your Plugins are the cause, if as you state the same ones worked fine before, the issue is with your SC4 setup, not the mods.

The most helpful thing to know is when these CTDs are occurring, that will likely make it clear. The most common problem for SC4 is needing to force the game to use just a single core of your CPU, failure to manually set this will lead to much instability. If you forgot to add this when you installed the game on your new machine, that would explain it.

[Tarkus 6,933]

If you're running the NAM (especially a full/full-ish configuration of it), did you by chance make sure to install the 4GB Patch over your new install of the game on your new system?  Trying to do so without the 4GB Patch will typically cause a CTD when attempting to load a city.

-Tarkus

[Oidaas 1,650]

Thanks alot for the response. I've installed the 4g patch but no result. The only thing that works i deleting all plugins.

[bob.blunderton 47]

Common crash with DLL's is the game closes out with no mention, or gives you 'memory can not be read' or something similarly memory related / something along those lines.

The game can and will still crash without DLL's, first off, just to be clear, but the following describes results of using them.  I've played this game 20+ years now since it came out, so yeah I have just a bit of time under my belt here to test them out.

This is often due to a memory protection and isolation feature built into the hardware of the computer, specifically to do with a setting in the UEFI (BIOS) of the PC enabling a hardware memory-protection feature in modern (last 10~12 years) processors to keep programs (virus/worm for example) from writing to OTHER memory that it doesn't have normal permission to.

Now, due to MY OWN bad memory issues, I forget what this is called, but yeah that feature being enabled can cause a whole lot of crash-tastic behavior with DLL mods.  On some computers, you can't even turn it OFF, or turning it OFF doesn't even help because the function might not work properly.  On my computer however, DLL's *DO* crash out with a 'memory cannot be read/written' type error even though this PC stability is rock solid / not overclocked / has been stress tested to heck and back / can crank out max CPU use for hours and never have an issue, regardless of the setting in BIOS.  So it's either Windows (there is a setting for memory protection!), BIOS/UEFI settings NOT working, or the option is on or got reset and I don't have a clue.  I built this (3950x based) tower in 2019, and it's still going strong after doubling the RAM to 64gb and throwing in a used-but-solid and cheap 3090 the other year; so I just accept that some things just will not play nice and these DLL's happen to be it.  I'm not going to make another computer just to run this game on only to have the same exact issue in the end, and in reality, a faster PC just makes it quicker for the game to get to the point with which it will crash out.

I know this thread is old, but I just was searching for something and this came up.  I also had this error, and it is still a thing.

Use DLL mods and such - get an issue with it writing out of range or reading out of range for memory.  It's either directly due to the DLLs or it's due to it overrunning the amount of memory it's allowed to use / allotted / over the 4gb or 32-bit limit.

If there's one thing we all want to do, it's to make SimCity 4 crash *LESS*, not make it crash MORE.  It certainly does crash a whole lot more (4x~10x) with DLL's in the mix, at-least for me here, and unfortunately I can't blame the hardware, throw money at it and thus fix it / solve the issue.

Sorry for the necro-bump if it offends anyone, but at-least a little more info is out there.  A debugger and a brain good with programming knowledge would shed more light on this topic, surely.