2 years ago
Sims 4 crashing my computer
Hi. About a week ago, The Sims 4 started to crash my computer, I have no idea what triggered this, but I just purchased the new for rent expansion and been playing with the same save file for about a...
@puzzlezaddict Thank you for the advice.
So after cleaning the PC, unistalling Windows and reinstalling, I thought it's windows that is causing this issue. I have nothing else (game) but the Sims 4 on the PC. I've let the game run for about 1 hour and it was all fine, I did not download anything from gallery or anything, I let a default household run the game.
20 minutes ago I pasted back my old save file, it worked for 30 minutes, then I travelled to another lot with my Sim and it crashed again. Well at least now I have a new dxDiag file with the new Windows..
The search with the perfmon /rel indicated a hardware malfunction: LiveKernelEvent, 141, and something with WATCHDOG. I have attached a screenshot of it, do you maybe know what is this error?
@vivas2001 LiveKernelEvent 141 is the same error as I mentioned before. Specifically, it's a video driver timeout: Windows detects that the driver hasn't responded in a timely fashion, it attempts to recover the driver, and if that doesn't work, it shuts it down. This error should never happen under normal circumstances and especially not after clean-uninstalling and reinstalling the driver.
Just in case this isn't about the driver itself, but rather some kind of conflict, please try playing in a clean boot:
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 that doesn't help, it's worth running a couple of GPU benchmarks. You can download the free trial of 3DMark from Steam and run Time Spy and Firestrike. I would run each one once and get the results pages, which you can do without an account; feel free to post the links here. Then run Time Spy four times, back to back with no pause in between, and let me know how it goes.
Hey @puzzlezaddict . So I wanted to do the the check with only the EAbackgroundService, but after I followed rhe description and disabled everything except the EA, I rebooted but I could not enter to my computer becase the windows process that deals with pin code has been disabled as well😂 and restart did not work, so I had to reinstall windows.
BUT, here comes the shocker! (check the attached picture🥲)
Probably it was caused due to the plugs not being firmly tightly connected. 🤦🏽♀️
I will have a new cable on Wednesday. Do you think that this could be the reason for the crash? Or is it possible that the crash caused the burn and there is another underlying issue?
@vivas2001 That burned cable could absolutely be the reason for all the crashing. It could have happened because the cable wasn't inserted properly or for some other reason; it's difficult to tell without more disassembly than most regular users want to try. For now, just make sure the new cable is properly plugged in, and check it after each of the first few play sessions.
When you clean boot, you need your password, not your PIN. Every Windows account has a password, even if you don't know it; it might be the same as your Microsoft account's password.