EA sims4 keeps closing

okay, I attached the file. thank you for being so patient with me!

@mtessh  Having only 4 GB RAM isn't helping Sims 4, although I'm not sure it's exactly the issue here.  Still, it's worth testing.  So please try playing in a clean boot:

https://support.microsoft.com/en-us/topic/how-to-perform-a-clean-boot-in-windows-da2f9573-6eec-00ad-2f8a-a97a1807f3dd

The one service to leave enabled is the EABackgroundService, which the EA App needs in order to run.  Disable the rest as described.

When you reboot your computer, go through the Task Manager's background processes list shutting down any service that doesn't absolutely need to be running, for example anything from MSI Afterburner to RGB software might still be enabled.  If you accidentally kill a critical process and it doesn't restart on its own, just reboot your computer again.

Don't open anything other than Sims 4 and the EA App while testing, not even a browser window.

If you get another crash, please repeat the test, except taking your computer offline as well.  You can sign into the EA App and put it in offline mode, then disable wifi and/or disconnect the ethernet cable before pressing Play.

Did as you stated. When I tried to open EA it didn't work. The one thing I couldn't figure out, is what to close in task manager after rebooting 

@mtessh  Please uninstall the EA App with Revo Uninstaller (the free version is fine), and restart your computer, not in a clean boot (reverse the process) before reinstalling the App.

Then repeat the clean boot process, and make sure the EABackgroundService or anything else that starts with EA is still enabled.  You can skip closing other processes in the Task Manager at first, but if your game crashes again, that's the next step.  Basically everything that doesn't belong to Intel or Microsoft should be closed, although some processes will restart on their own.

Well I finally got time to go back on and try playing. And it worked for a couple hours and it did it again. 

@mtessh  Please look for a related error in the Reliability Monitor.  Hit Windows key-R and enter "perfmon /rel" without quotes, and you'll see a chart of errors and updates with a column for each day.  Today is on the right.

Look for an error that happened at exactly the time of your most recent Sims 4 crash.  If you find one, double-click it to see more details, then copy that info and paste it into a reply here.  If you don't see a new error, check back in an hour or so—the Reliability Monitor doesn't always update right away.  If you still don't find one, that's useful information too.

Here is what it came up with. *see attached 

@mtessh  This looks like an error of the page file, which is stored on your system drive by default.  So please run chkdsk to check the health of the drive:

• Hit Windows key-X
• Choose either “PowerShell (Administrator)” or “Windows Terminal (Administrator),” whichever option is offered
• Inside the window that appears, copy and paste "chkdsk /f /r c:" without quotes, and enter
• You'll be asked to allow a restart; say yes
• When the scan is done, use this guide to find the results

You should be able to attach the report to a post as well.  Running chkdsk will take some time, so you may want to leave it while you're doing something else.

It's not letting me 

@puzzlezaddict 

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 7/31/2024 5:53:06 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: 2024comp_reset
Description:

Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
687360 file records processed.

File verification completed.
Phase duration (File record verification): 6.71 seconds.
20372 large file records processed.

Phase duration (Orphan file record recovery): 8.83 milliseconds.
0 bad file records processed.

Phase duration (Bad file record checking): 1.21 milliseconds.

Stage 2: Examining file name linkage ...
49895 reparse records processed.

783884 index entries processed.

Index verification completed.
Phase duration (Index verification): 20.95 seconds.
0 unindexed files scanned.

Phase duration (Orphan reconnection): 496.91 milliseconds.
0 unindexed files recovered to lost and found.

Phase duration (Orphan recovery to lost and found): 3.61 seconds.
49895 reparse records processed.

Phase duration (Reparse point and Object ID verification): 901.35 milliseconds.

Stage 3: Examining security descriptors ...
Cleaning up 7172 unused index entries from index $SII of file 0x9.
Cleaning up 7172 unused index entries from index $SDH of file 0x9.
Cleaning up 7172 unused security descriptors.
CHKDSK is compacting the security descriptor stream
Security descriptor verification completed.
Phase duration (Security descriptor verification): 236.83 milliseconds.
48263 data files processed.

Phase duration (Data attribute verification): 1.17 milliseconds.
CHKDSK is verifying Usn Journal...
37604984 USN bytes processed.

Usn Journal verification completed.
Phase duration (USN journal verification): 178.09 milliseconds.

Stage 4: Looking for bad clusters in user file data ...
687344 files processed.

File data verification completed.
Phase duration (User file recovery): 1.95 minutes.

Stage 5: Looking for bad, free clusters ...
16375353 free clusters processed.

Free space verification is complete.
Phase duration (Free space recovery): 11.54 seconds.
Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.
No further action is required.

108595199 KB total disk space.
42167892 KB in 166500 files.
119084 KB in 48266 indexes.
0 KB in bad sectors.
806807 KB in use by the system.
65536 KB occupied by the log file.
65501416 KB available on disk.

4096 bytes in each allocation unit.
27148799 total allocation units on disk.
16375354 allocation units available on disk.
Total duration: 2.70 minutes (162010 ms).

Internal Info:
00 7d 0a 00 f7 46 03 00 bb 19 06 00 00 00 00 00 .}...F..........
22 00 00 00 c5 c2 00 00 00 00 00 00 00 00 00 00 "...............

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2024-07-31T22:53:06.7942911Z" />
<EventRecordID>3342</EventRecordID>
<Correlation />
<Execution ProcessID="1004" ThreadID="0" />
<Channel>Application</Channel>
<Computer>2024comp_reset</Computer>
<Security />
</System>
<EventData>
<Data>

Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
687360 file records processed.

File verification completed.
Phase duration (File record verification): 6.71 seconds.
20372 large file records processed.

Phase duration (Orphan file record recovery): 8.83 milliseconds.
0 bad file records processed.

Phase duration (Bad file record checking): 1.21 milliseconds.

Stage 2: Examining file name linkage ...
49895 reparse records processed.

783884 index entries processed.

Index verification completed.
Phase duration (Index verification): 20.95 seconds.
0 unindexed files scanned.

Phase duration (Orphan reconnection): 496.91 milliseconds.
0 unindexed files recovered to lost and found.

Phase duration (Orphan recovery to lost and found): 3.61 seconds.
49895 reparse records processed.

Phase duration (Reparse point and Object ID verification): 901.35 milliseconds.

Stage 3: Examining security descriptors ...
Cleaning up 7172 unused index entries from index $SII of file 0x9.
Cleaning up 7172 unused index entries from index $SDH of file 0x9.
Cleaning up 7172 unused security descriptors.
CHKDSK is compacting the security descriptor stream
Security descriptor verification completed.
Phase duration (Security descriptor verification): 236.83 milliseconds.
48263 data files processed.

Phase duration (Data attribute verification): 1.17 milliseconds.
CHKDSK is verifying Usn Journal...
37604984 USN bytes processed.

Usn Journal verification completed.
Phase duration (USN journal verification): 178.09 milliseconds.

Stage 4: Looking for bad clusters in user file data ...
687344 files processed.

File data verification completed.
Phase duration (User file recovery): 1.95 minutes.

Stage 5: Looking for bad, free clusters ...
16375353 free clusters processed.

Free space verification is complete.
Phase duration (Free space recovery): 11.54 seconds.
Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.
No further action is required.

108595199 KB total disk space.
42167892 KB in 166500 files.
119084 KB in 48266 indexes.
0 KB in bad sectors.
806807 KB in use by the system.
65536 KB occupied by the log file.
65501416 KB available on disk.

4096 bytes in each allocation unit.
27148799 total allocation units on disk.
16375354 allocation units available on disk.
Total duration: 2.70 minutes (162010 ms).

Internal Info:
00 7d 0a 00 f7 46 03 00 bb 19 06 00 00 00 00 00 .}...F..........
22 00 00 00 c5 c2 00 00 00 00 00 00 00 00 00 00 "...............
</Data>
</EventData>
</Event>

@mtessh  It doesn't look like there's a problem with the drive itself, which is of course a good thing.  Since the last error you saw referenced the computer's page file, please delete the page file and then allow it to be recreated.  Here's how (option four):

https://www.elevenforum.com/t/manage-virtual-memory-paging-file-in-windows-11.8618/#Four

So you'll go through all these steps, restart your computer, and then reverse the steps to allow a page file again.  You can allow the system to manage the page file size on it own; there's no need to set a custom size.

@puzzlezaddict did all that, unfortunately still not working.

I have the same problem. I tried swapping ram and GPU from my other PC and i even replaced the Motherboard, tried new windows and it still randomly crashes Mostly on the opening screen. 

@mtessh  Please post a new dxdiag, and look for a new error in the Reliability Monitor that corresponds to your most recent attempt to play Sims 4.

@lady_absentia  Since this thread is specific to the original poster, please create your own thread describing your issue.  Include the model numbers or SKUs of the components you've replaced, for example the RAM has its model number printed on the side of each module.  Please post a dxdiag as well.

https://help.ea.com/en-us/help/pc/how-to-gather-dxdiag-information/

@puzzlezaddict 

see attached. thanks!

@puzzlezaddict 

here is the bit from the reliability monitor

Faulting application name: TS4_DX9_x64.exe, version: 1.108.335.1020, time stamp: 0x66a31f19
Faulting module name: ntdll.dll, version: 10.0.22621.3733, time stamp: 0x67ca8829
Exception code: 0xc0000006
Fault offset: 0x0000000000020762
Faulting process id: 0x0x1A80
Faulting application start time: 0x0x1DAE401D8865BA5
Faulting application path: D:\sims4\The Sims 4\Game\Bin\TS4_DX9_x64.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 00a34c9a-e370-4ca2-9247-a454c114121a
Faulting package full name:
Faulting package-relative application ID:

@mtessh  Now that you've rebuilt the page file, please try a clean boot again, as described in post 10, with your computer completely offline.  It's important to have no internet connection at all.  If that doesn't help, please post the Reliability Monitor from the newest crash, as you've done before.

I've asked for a second opinion on your issue in case I'm missing something.

@puzzlezaddict it only lasted about an hour, unfortunately. 

first one: 

Faulting application name: TS4_DX9_x64.exe, version: 1.108.335.1020, time stamp: 0x66a31f19
Faulting module name: ntdll.dll, version: 10.0.22621.3733, time stamp: 0x67ca8829
Exception code: 0xc0000006
Fault offset: 0x0000000000020e59
Faulting process id: 0x0x2068
Faulting application start time: 0x0x1DAE69D2F8B9D6E
Faulting application path: D:\sims4\The Sims 4\Game\Bin\TS4_DX9_x64.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 5cd29021-f789-494a-874c-79c9033d8d3e
Faulting package full name:
Faulting package-relative application ID:

second one: 

Description
Faulting Application Path: D:\sims4\The Sims 4\Game\Bin\TS4_DX9_x64.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: TS4_DX9_x64.exe
Application Version: 1.108.335.1020
Application Timestamp: 66a31f19
Fault Module Name: ntdll.dll
Fault Module Version: 10.0.22621.3733
Fault Module Timestamp: 67ca8829
Exception Code: c0000006
Exception Offset: 0000000000020e59
OS Version: 10.0.22631.2.0.0.768.101
Locale ID: 1033
Additional Information 1: abcc
Additional Information 2: abcc8f7853b48d9807d6d51eb1fa5df9
Additional Information 3: abcc
Additional Information 4: abcc8f7853b48d9807d6d51eb1fa5df9

Extra information about the problem
Bucket ID: eb179d2a9de903cd506d48c011e64cbf (1183682266839534783)

@puzzlezaddict 

I wanted to ask if there was anything to do to make the game process smoother. It is very 'frame by frame" when I play. And it's not a space problem because I have over 800gb free on the drive I'm using. I also have all the graphic settings to low