ACCESS_VIOLATION reading address 0xf1698107
Hi! Can anyone help diagnose this? Much appreciated! Application: Sims3 BuildTime: 2015-1-6-0801 BuildUser: Unknown BuildHost: Unknown BuildConfig: Release BuldVersion: 0.2.0.32 Comma...
Forum Discussion
The short answer is no, no one can really diagnose that. Since that statement alone would be exceedingly unhelpful, let me explain.
Crash logs are notorious for not really providing much useful information and this one is no exception. The only things we can see from this one are that you have TONS of RAM on your system, so lack of it is not an issue, and your game crashed. You would already know both of those things, though.
What the Access Violation bit is referring to is a specific RAM address. It means the game program found some data in there that it cannot possibly work with, it would have lost its mind if it had been allowed to continue on, so Windows stepped in, said something to the program like "You're drunk and it's time to go home," and crashed the game for you. Knowing which exact combination of 0s and 1s might have been in that RAM register or which precise one it is doesn't help at all.
It's not always but often enough "bad" CC or a mod that causes these crashes. But it could also be the TS3 game program trying to reach for more than ~3.7 GB of RAM, which is certainly there and available to it, but as TS3 is a 32-bit only program it cannot be used without very bad things happening. In that case, either the program will crash or Error 12 upon trying to save, which is just as bad since no one wants to play a game that they cannot save. And sometimes it's both, meaning it's the bad CC or mod that is causing the game to suddenly call for more RAM than it can possibly use.
Does this happen often and does any of the above give some clues as to what might have happened there?
Crash logs are notorious for not really providing much useful information and this one is no exception. The only things we can see from this one are that you have TONS of RAM on your system, so lack of it is not an issue, and your game crashed. You would already know both of those things, though.
What the Access Violation bit is referring to is a specific RAM address. It means the game program found some data in there that it cannot possibly work with, it would have lost its mind if it had been allowed to continue on, so Windows stepped in, said something to the program like "You're drunk and it's time to go home," and crashed the game for you. Knowing which exact combination of 0s and 1s might have been in that RAM register or which precise one it is doesn't help at all.
It's not always but often enough "bad" CC or a mod that causes these crashes. But it could also be the TS3 game program trying to reach for more than ~3.7 GB of RAM, which is certainly there and available to it, but as TS3 is a 32-bit only program it cannot be used without very bad things happening. In that case, either the program will crash or Error 12 upon trying to save, which is just as bad since no one wants to play a game that they cannot save. And sometimes it's both, meaning it's the bad CC or mod that is causing the game to suddenly call for more RAM than it can possibly use.
Does this happen often and does any of the above give some clues as to what might have happened there?
