Sims 4 causes computer to restart
Starting about a week ago, whenever I started playing Sims 4, my computer would just randomly restart itself without warning. At first I thought it was an issue with my actual computer, Google was s...
Forum Discussion
@StairFax1705 Are you seeing BlueScreens while playing Sims 4, then the computer shuts down and restarts; or are the BSODs a separate issue, and your computer just straight restarts while playing? I ask because I see two different types of BlueScreen in your dxdiag, and while they should be addressed regardless, it's important to know whether there's also a separate issue with non-BSOD-related restarts.
One way to tell is to check the timestamps on the crash dumps associated with the BSODs. Open a File Explorer window and enter this in the address bar:
C:\Windows\Minidump
You'll see files from the recent BlueScreens, and you can compare their timestamps with the restarts. Please let me know whether these happened while you were playing Sims 4, and regardless, I'd also like to see the most recent three or four files. Right-click on each and select Copy, then right-click the desktop and select Paste. From there, you can zip the files together, upload the .zip to a free filesharing site (Google Drive, Dropbox, etc.) and link it here.
I'd also like to see the results of some hardware logging. Please download hwinfo (it's free) from here:
https://www.hwinfo.com/download/
You don't need to install anything; just choose the Portable version, unzip it, and launch it from Downloads or wherever you like. If you do want the full installer, be sure to click the button for hwinfo itself, not for lansweeper.
Restart your computer, open hwinfo, choose Sensors Only, and click the button that's a sheet of paper with a + to start logging. Save the log file to your desktop for easy access. Wait five minutes, then open Sims 4 and play until your computer crashes. The log should be intact up until that point.
Please upload the log to the third-party filesharing site of your choice (Google Drive, Dropbox, etc.) and link it for me. Either leave it in .csv format or, if you're going to use OneDrive, create a .zip file, and don't open the log before uploading it, or else my log reader might not be able to interpret it.
Finally, please list the specs for the computer's power supply, for example Corsair 750W 80+ Gold. The info should be on the documentation that came with the computer and also printed on the side of the unit itself.
First, I want to thank you for getting back to me.
To answer your first question, there is no BSOD; it just cuts straight to black and the computer restarts itself. Unfortunately, I cannot open .dmp files on my computer, but I have them compiled as a zip on google drive which I will link here.
I will also upload the .csv file like you have asked.
And as for the power supply, it is a EVGA Supernova 850 G5, 80 Plus Gold 850W.
If you need anything else form me or if I did something wrong, please let me know. And thank you again for your help.
Bluescreen files: https://drive.google.com/file/d/10q3WJW5ekEMcX80CriXln3u8Tmxh4vlY/view?usp=sharing
HWinfo: https://drive.google.com/file/d/1AE850zrvCjEuSLputNEE2md5VLFbS4JZ/view?usp=sharing
@StairFax1705 Sorry for the late-ish reply. I looked over everything you sent me, and I will admit that I don't understand all of what I'm seeing. But a few things are clear. First, there is nothing in your hwinfo log that would explain these problems. The power supply is stable and so are the power inputs into the various components; the temperatures are actually on the low side for gaming, and certainly nowhere near the point of thermal throttling; there are no suspicious readings elsewhere, that I could find anyway.
Most of your crash dumps reference a component of Windows itself, one that's unlikely to be corrupt. (By that I mean both that it's unlikely to get corrupted and that if it were, it's unlikely you could use your system effectively at all.) The errors are all distinct, not even all in the same category, so I think the best place to start here would be by running some tests on your RAM. A faulty module is one of the few single causes that could explain a wide variety of errors like this.
The gold standard of memory diagnostics is MemTest86, testing each module separately and in at least two different slots on the motherboard.
https://www.memtest86.com/index.html
https://www.overclockersclub.com/guides/memtest86_memory_guide/
If you're not comfortable with this test, you could start with the built-in Windows tool instead:
I wouldn't consider a pass from this tool to be even close to definitive, but if it does flag an error, that's probably accurate.
I'd also like to know what RAM you're using, by product number. If you don't have that handy, you can find it on the modules themselves.
Nah, you're fine. You're doing this out of the generousness of your heart; I'd understand if you had more pressing matters to attend to. If anything, I'm just grateful someone is responding at all.
To address the latter two items, the product number for my memory sticks is F4-3200C16-8GVRB. There are two of them in my machine, sharing the same number.
I also figured I run the Windows tool first since it seemed easier to understand, although that came up negative. Although I am wary of the inaccuracy of a negative result on that test like you said.
I'm having trouble unfortunately trying to get memtest86 to work properly; this might go beyond my knowledge of computers. If I can find some help with it though, I'll get back to you on what it says.Update: I figured out how to get memtest working and just finished a test. However, there were no errors that it could find.
Community Highlights
- EA_Cade9 months ago
Community Manager
