I just built a new computer and have been having issues with playing the Sims 4. The game runs smooth as butter with no lag. The game crashes every half an hour. Here is what I've done so far.... -U...
Forum Discussion
@bcarlso88 This log only contains category headers and a single reading in each category. So either you happened to double-click and stopped the logging as soon as it started, or the memory issue (or some other hardware issue) interfered with the logging.
If you want to test your memory more thoroughly, MemTest 86 is the gold standard. Best practice is to test each module separately and in at least two different slots on the motherboard. While you're at it, blow out the RAM slots on the board too, in case the problem is dust or other particles and not the memory itself.
https://www.memtest86.com/index.html
https://www.overclockersclub.com/guides/memtest86_memory_guide/
This is somewhat time-consuming, so you'll want to run it while doing something else that doesn't require your computer to be available. The good news is, most quality RAM comes with a lifetime warranty, and Corsair is a reputable company. So even if you have to RMA the modules, you should be covered.
@puzzlezaddict sorry, I'll get this right one of these days. This one should work. I had it running while playing. Crashes within 12 minutes. Hopefully this well tell us what we need. As for the memory run, I don't have a USB at the moment so I can't run that. As always, thanks for the replies.
https://drive.google.com/file/d/1ysb05bf-hn9iCFa0-Pvx6U-bcXkJli_n/view?usp=sharing
@bcarlso88 Amazingly, this log was somewhat borked too: my log reader wouldn't even open it. But at least I got an error message and was able to fix the issue. (The timestamps were in an invalid format, somehow, unlike the ones in your first log, which is definitely not something you caused, and frankly somewhat strange.) And all I see is very low CPU utilization, which is unsurprising; somewhat low GPU utilization, which is more surprising but might be due to your using potato settings; more low-ish readings on the PSU's 12V rail, which isn't great but also doesn't look like it's affecting the processor; and no obvious reason for the crash.
The log was also just over 8 minutes long rather than 12. I've seen a couple of cases where a shorter log than expected pointed to a CPU or RAM issue, and that coupled with the results of the Windows memory test make your RAM the primary suspect here. I would strongly suggest you find a USB stick somewhere, even if you have to borrow one, but in the interim, you can run the same built-in Windows tests with one module installed at a time. Maybe you'll get lucky and find that only one stick is defective.
From the hwinfo readings, it doesn't look like the RAM is overclocked, but please let me know if that's not the case, or if you've overclocked the CPU. In either case, please revert to stock settings.
Please also list the exact memory modules you're using: they'll have product numbers printed on the sides. Please list the exact motherboard you have. The BIOS version in your dxdiag apparently applies to at least two Asus boards, and it also looks to be somewhat outdated, which could be part of or the entire problem. (By the way, you'd need a USB stick to update the BIOS as well.) Looking into it a bit last night, I read a few reports of Asus boards of this generation causing memory errors with older BIOS versions, although there was nothing definitive and not enough evidence to say this was a widespread issue.
The other alternative here, if you have the opportunity, is to test your computer components one at a time in another system. If you have a friend who could help, that's one option; so would be a repair shop that would presumably have all the necessary equipment. Some stores might only charge a nominal fee for testing, so call around and ask if this is the way you want to go.
- @puzzlezaddict I did a little searching around and looked at my AMD software and my FPS for the Sims 4 was turned all the way up to 140. I have a 60mhz screen so I put it down to 60FPS and it fixed the issue as long as I run the game on low graphic settings. I'm not sure when I'm going to get my GPU back but once I get it, I will set it up and see if I still have issues. I'll let you know. Thanks for all your help with this.
@puzzlezaddict I received my new graphics card and there is some improvement, but I'm still getting crashes every once in a while. See below for the error code.
Faulting application name: TS4_x64.exe, version: 1.98.158.1020, time stamp: 0x647fc8a8
Faulting module name: python37_x64.dll, version: 3.7.150.1013, time stamp: 0x60905efa
Exception code: 0xc0000005
Fault offset: 0x000000000004431b
Faulting process id: 0x0x2998
Faulting application start time: 0x0x1D9ACE2A30D88BB
Faulting application path: C:\Program Files\EA Games\The Sims 4\Game\Bin\TS4_x64.exe
Faulting module path: C:\Program Files\EA Games\The Sims 4\Game\Bin\python37_x64.dll
Report Id: 3dcf195b-9bd0-431d-87b3-dda1387a1f86
Faulting package full name:
Faulting package-relative application ID:I've seen this before with the crashes so I'm not sure how to proceed with this. Let me know your thoughts and thanks again!
@bcarlso88 That's an access violation, which means that Sims 4 tried to access memory in a manner or location that isn't permitted. Windows responds by shutting down the program. The problem is that access violations can be caused by anything from bad mods or custom content to a game bug to a problem with other software you're running to (rarely) a hardware issue. Mods are the most likely culprit though, so if you currently have any installed, please remove them and test again in a new save.
The next step would be to uninstall and reinstall Sims 4. If that doesn't help either, please post a new dxdiag.
- @puzzlezaddict I uninstalled and reinstalled it on July 2nd and was able to play with no issues. Just had a crash now and ran a dxdiag for it. See attached. Hopefully, it will find something. Thank you!
Here is the DxDiag. Thank you!
@bcarlso88 The only Sims 4 crash in your dxdiag is another access violation. I can't tell if it's the same one from a few days ago or a new one, but you can check the Reliability Monitor to find out. Your dxdiag then lists a number of more generic Windows errors, then one LiveKernelEvent 141 that might be old or new. Since you've made a few hardware changes in the time we've been troubleshooting here, I'd really like to know when these errors happened, especially relative to when you installed the new GPU.
Even though you clean-installed Windows recently, it's still worth running a repair install just in case the more generic errors are on the Windows side, as opposed to being triggered by something interacting with Windows.
https://www.elevenforum.com/t/repair-install-windows-11-with-an-in-place-upgrade.418/
This shouldn't delete any of your data, but if you get to step 14 and are NOT asked to keep personal files and apps, back out and start over.
Community Highlights
- EA_Cade10 months ago
Community Manager
