Re: Freezing Sims 4 Issue

The settings for the dump are as you described. T

+he overwrite box was checked so I unchecked that. Write event was checked. The file location does say. %SystemRoot%\MEMORY.DMP. Deployment Image Servicing and Management tool was run successfully, Got to 100% without any errors being thrown.

System scan had this as the output:

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

I have attached the CBS log.

Motherboard: ASUS Maximus VI Impact

PSU:  Seasonic G-650

@hotpink4956  Alright, that's good news at least.  Did you try playing again?  Sometimes the repairs sfc completes are enough to make the game work.

I'm still thinking about the BlueScreen without a BlueScreen though.  There are plenty of reasons one might not be written; one is a faulty hard drive.  Yours is high quality, but to be thorough, please run chkdsk:

• Hit Windows key-X
• Choose either “PowerShell (Administrator)” or “Command prompt (Administrator),” whichever option is offered
• Inside the window that appears, copy and paste "chkdsk /f /r c:" without quotes, and enter
• You'll get a message that you can't run the scan unless you allow a restart; say yes
• When the scan is done, hit Windows key-X again, and choose Command prompt (admin) or Powershell (admin) again
• Copy and paste this command without the outside quotes: "get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt"
• A .txt file with the chkdsk results will appear on your desktop.  Please attach it to a post.

The next step would be hardware monitoring, to see how your other components are performing.  Let me know if you'd like instructions.

Here is the chkdsk results.

by the way I did try and play again and it froze and gave me a blue screen again. The error this time was whea_uncorrectable_error. was also again no file in the minidump folder either.

@hotpink4956  Okay, I think it's time for some hardware monitoring.  Download hwinfo from here:

https://www.hwinfo.com/download/

You don't need to install anything if you don't want to; just choose the Portable version, unzip it, and launch it from Downloads or wherever you want.  (If you would like to install, be sure to click the green button, not the orange one.)  Do another clean boot, and don't open any other apps.  Please also shut down your antivirus/firewall, if you have a third-party app installed.  Launch hwinfo, choose "sensors only," and click the icon that's a sheet of paper with a + sign to start logging.  Save the file to your desktop for easy access later.

Wait five minutes, then launch Sims 3 and play for 20 minutes or until it crashes or you get a BlueScreen.  Click the same button to end logging.  Then upload the log to a third-party free filehosting site and link it here.  Please leave it in .csv format, or if you use OneDrive to share, please compress it in .zip format instead.

http://www.mediafire.com/file/e17rkdwhbaszlbr/please.CSV/file

Hey, here is the link to the csv file. It blue screened with CLOCK_WATCHDOG_TIMEOUT this time.

Thank you

@hotpink4956  I'm so sorry I for the late reply.  I put aside your post to read your hwinfo log and... I just forgot about that particular list until tonight.  I don't have a good excuse.

Anyway.  Your processor and graphics card run hot while you play, topping out at 80º C and, in the case of the GPU, staying there for a while.  This isn't necessarily damaging to the hardware: the components are doing their job and throttling to protect themselves.  But you should definitely clean your fans, both on the CPU cooler and GPU and the case fans.

However, I'm not sure the high, but not dangerously high, temperatures would account for the BlueScreen errors you're seeing.  It really would help to see a crash dump.  If you can't find one in C:\Windows\Minidump, look in C:\Windows for a Memory.dmp file, which is larger but would have the relevant information as well.  I don't think it would be there if the minidump didn't get written, but it's possible.

Among the many reasons you might not find a crash dump is having a program running that automatically cleans up temp files.  If you do have one, please disable it for now.

If that's not the issue though, please go back to the recovery options you accessed earlier (Windows key-R, sysdm.cpl, Advanced > Startup and Recovery > Settings), and choose "complete memory dump" rather than the automatic one.

If none of this gets you anywhere, I'll ask for a second opinion; this is kind of at the edge of my understanding, at least what to do when the system won't create the info it's being told to write.  And I will make sure to check back a lot sooner this time.  Sorry again.

Hi for the late reply this time. double checked that the internals were clean and they were. tried to running the game without the case cover on just to check if more air circulation would help, still got blue screen (clock_watchdog_timeout). Changed to complete memory dump and still empty. I should also mention that these blue screens stay at 0% and never go through, i always have to hard reset the computer. I also wanted to mention that i downloaded a different game off of steam (Planet Zoo) and it also is causing the same problem.

Thank you again!

@hotpink4956  Just to clarify, a complete memory dump would leave a .dmp file in the C:\Windows folder, not in the Minidump folder inside it.  But it sounds like the BlueScreen data really isn't being written, rather than it being cleaned up or corrupted after the fact.

Please detach and reattach all the cables in your computer at both ends.  This goes for the connectors between the PSU and motherboard, graphics card, and SSD; and the SATA cable between the SSD and board.  Take a look at the connectors themselves, and blow out any dust you see; let me know if anything appears to be bent.  Please also remove the RAM sticks, blow out any dust from the slots and on the RAM itself, and reseat them.

If you've ever overclocked any component, let me know, and please undo that setting.  Please also boot into BIOS and restore everything to defaults.

The fact that another game would produce a BSOD is completely unsurprising.  Whether hardware or software, these are system errors, and while they can be triggered by a game or other demanding application, that app isn't the root cause of the problem.  Please keep listing the name of any BlueScreen you see, or get the error code if you prefer.  (For example, clock_watchdog_timeout is 0x101 or 0x00000101.)  Either will do.

Hi, my fiancé pulled everything out of the case and reconnected everything. Said it was the cleanest inside of a computer he’s seen... his sits on a stand on the floor while mine is up on the desk. I went in to play, it didn’t blue screen this time but it did freeze the computer like it’s been doing. What is the file name of the dump called when it goes into the windows folder?

@hotpink4956  The file should be something like MEMORY.dmp, but you'll know it by its .dmp extension.  (Make sure you have your system set to display file extensions, which is a setting in File Explorer.)  A freeze may or may not produce a .dmp file, depending on what kind it is.  You can also try generating a crash dump, which is a bit different than the other files you've been looking for but functions in the same way.  Here's how:

• Hit the Windows key, type "command prompt" in the box, right-click on Command Prompt in the search results, and select Run as Administrator
• In the window, paste "reg add "HKLM\Software\Microsoft\Windows\Windows Error Reporting\LocalDumps\devenv.exe" /v DumpType /d 2 /t REG_DWORD" without the outside quotes into the box, and enter
• Launch Sims 4 and wait for it or your system to crash (whether you can play at all or not)
• After it crashes, wait for any crash dialogs to finish
• Then hit Windows key-R and paste "%LOCALAPPDATA%\CrashDumps" without quotes into the box, and enter
• Upload the last .dmp file to the third-party filehosting site of your choice, and link it here
• When you want to undo the auto crash log dumps, open Command Prompt as before, paste "reg delete "HKLM\Software\Microsoft\Windows\Windows Error Reporting\LocalDumps" /f" without the outside quotes, and enter.

I honestly don't know if you'd get a crash dump from this, considering you haven't been getting the automatic ones.  In your position, I'd run hwinfo and log the session as well, just to see if there's anything that happens right before the freeze/crash/BSOD.  Even though there was nothing obvious in your earlier log, maybe this one will catch something.

Hello,

so i was unable to do the steps after the computer crash because the whole computer freezes up. Thank you for your continued help.

@hotpink4956  When you rebooted, could you find a crash log?  If not, it's fine, just let me know.  I'm sorry this process has become so convoluted; I'm just trying to come up with other ways of getting information aside from the ones that aren't working, for whatever reason.

Do you have access to other computer components that you could use to test?  For example, borrowing a power supply from a family member or friend, or switching out RAM sticks.  In the absense of good information, sometimes the best thing to do is test each component separately, starting with the most suspect.  If you can test, I'd start with the memory, since RAM is extremely easy to install and remove.  Even if you can't borrow someone else's RAM, you can test each of your modules separately, in different slots just to be thorough.

You can also test with the onboard graphics rather than the dedicated card.  It's not overly complicated: boot into BIOS, disable the dedicated card (the manual for your motherboard should describe the settings), and plug the monitor into the board.  The game would run badly on the integrated chip, but it should run on low settings without freezing your computer.  I think it's unlikely that your graphics card is the problem, but this is an easy test.

From what I can gather, the most likely culprits are your processor and memory.  But it's difficult to test a processor, especially since it uses an older socket: you can't just drop the CPU into a newer motherboard, or put a newer CPU into yours.  If you do have access to another system that uses the same socket—you can check the board's specifications to see whether it supports your CPU—it would be a good idea to swap and test.  Otherwise, you'd probably need to test the other components in your computer separately, then guess it's the processor, or the board, if nothing else causes a problem.

Still, you can test other components first, and maybe it'll turn out to be a bad RAM module or something easily fixed.  While doing this, please keep looking for crash dumps in any form.  You can search This PC for *.dmp (with the asterisk), which instructs the system to find any .dmp files, wherever they may be.  And please do upload any you find, whether they're recent or perhaps older ones hiding somewhere else.

Hey so tried to find any kind of *dmp file but did not find anything. We switched most of the parts with my fiancé’s computer except the CPU and the Motherboard, still froze whole computer or blue screened. Also tried to use the onboard graphics and it froze the computer also.

Thank you again!

Hey @puzzlezaddict!

So we ended up taking my computer into a local computer repair place where they swapped out my CPU. Problem has gone away! Thank you so much for your help and recommendations you are my computer savior!

Extremely Grateful,

Hotpink4956

@hotpink4956  Thanks for letting me know, and I'm sorry it was such a long process to figure it out.  I'm really glad to hear that it's solved.