BSoD out of nowhere

Was playing the Sims 4 and got a BSoD

Attachment 158324

Thank you. However shortly after this my computer shut down again, this time however the power strip it’s plugged into is dead.

WHEA Summary:

Code:

AuthenticAMD_PROCESSOR_CACHE - Cache error - ICACHEL1_IRD_ERR (Proc 0 Bank 1) 
AuthenticAMD_PROCESSOR_CACHE - Cache error - ICACHEL1_IRD_ERR (Proc 0 Bank 1) 
AuthenticAMD_PROCESSOR_CACHE - Cache error - ICACHEL1_IRD_ERR (Proc 4 Bank 1)

"Cache Error": Could be caused by hardware problems, but also by overclocking, faulty drivers or BIOS problems.

0x124

WHEA_UNCORRECTABLE_ERROR

A 0x124 is one of the worst STOP codes to encounter for the sole reason that the dump files usually give nothing away as to the cause of the problem. WHEA (Windows Hardware Error Architecture) errors signify a problem with hardware but very rarely pinpoint the culprit. In these scenarios it is advised to run a series of hardware stress and diagnostic tests to try and pinpoint the problem. A template is offered below which covers the four main components (GPU, CPU, RAM, HDD) and gives you a fighting chance of narrowing down the problematic device.

Generic "Stop 0x124" Troubleshooting Steps:

1) Ensure that none of the hardware components are overclocked. Overclocking means pushing the components beyond what they were designed for. If you do not know what that is you probably are not overclocking so go to the next step
2) Ensure that the machine is adequately cooled. If this is a laptop use compressed air to carefully blow out the heat pipe and fan when the computer is turned off. If a desktop take the side cover off and blow a fan on the components
3) Update all hardware-related drivers: video, sound, RAID (if any), etc. Do not rely on windows when it says the most recent driver is installed. It may be the most recent but it may also be corrupt.
4) Update the motherboard BIOS according to the manufacturer's instructions and clear the CMOS. Check with the computer maker for directions on this procedure and as usual it is always a good idea to back up your data.
5) Update ALL OS Windows updates
6) Stress test the major components. Start with RAM, CPU, HD, etc.
For RAM, use Memtest. Instructions for which can be found here.
Computers are extremely sensitive to problematic ram so any errors on memtest should be considered an issue and even a clear report for less than 8 passes can give a false negative.
For CPU use Prime95
For hard drives, use CHKDSK /F finds any problems on the drive(s), notably "bad sectors". You should also go to the HD maker and download and run their HD checking utility
7) Perform a "vanilla" (clean) re-installation of Windows: Install nothing that is not from the OS (not even Malware) until you have seen that the computer is not crashing in this state.
When the vanilla installation has run long enough that you are convinced it is OK, start installing updates and applications a few at a time, and wait until you are again convinced it is OK. If the crashes resume it is obviously the last group of installations that is the issue and remove them.
8) Re-seat all connectors, ram modules, etc. You can use the same can of compressed air to clean out the RAM DIMM sockets as much as possible.
Only attempt this if you are FULLY knowledgeable about the procedures.
9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.

Read carefully before proceeding.

   Warning

If you're overclocking your system, revert back to stock clocks now.

Diagnostic Test

 CPU TEST

Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums

For Intel CPUs you can additionally use the Intel Processor Diagnostic Tool

   Warning

Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

   Note

Monitor CPU temperatures with Speccy or HWiNFO64

Speccy
Speccy gives you detailed information on every piece of hardware in your computer.

HWiNFO64
Hardware Info (HWiNFO) is a powerful system information utility designed especially for detection of hardware.

Take Screenshots of it and post it here.

Diagnostic Test

 GPU TEST

Run Furmark to stress test your GPU. FurMark - GPU Stress Test - Windows 10 Forums

   Note

Run Furmark for around 30 minutes.

   Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.

Take a Screenshot and post it here.

Diagnostic Test

 HDD TESTS

Run HDTune to check health and scan for errors.

   Note

It may take some time, but look for signs of any errors or failure.

You can also run a disk or health check using CrystalDiskInfo or chkdsk. Refer to the tutorial for details of how to do this.

Take Screenshots of it and post it here.

Diagnostic Test

 RAM TEST

Run MemTest86+ V5.01 to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

   Note

MemTest86+ V5.01 needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

More Info here: Memory problems. - Microsoft Community

Make a photo of the result and post it.

The event logs displayed multiple drive problems: paging, retired blocks, and corruption.
There were problems with the cdrom and this may be related to a problem disc or hardware.

In addition to the above tests in the prior posts please open administrative command prompt and type or copy and paste:

1) sfc /scannow
2) dism /online /cleanup-image /restorehealth

3) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

4) chkdsk /x /f /r
(this may take many hours so plan to run overnight)

5) When the chkdsk scan has completed the report will be located in the event.vwr
Use the information in this link to post the txt file into the thread:
Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials

Code:

Event[8965]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2017-08-23T13:29:15.232  Event ID: 140  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-E3C6UKV  Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume9.

Code:

Event[1964]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2017-06-21T02:48:17.420  Event ID: 140  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-E3C6UKV  Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: E:, DeviceName: \Device\HarddiskVolume8.(A device which does not exist was specified.)

Code:

Event[1958]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2017-06-21T02:48:17.420  Event ID: 140  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: N/A  User Name: N/A  Computer: DESKTOP-E3C6UKV  Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: E:, DeviceName: \Device\HarddiskVolume8.(STATUS_DEVICE_NOT_CONNECTED)

Code:

Event[1952]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2017-06-21T02:48:17.398  Event ID: 140  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: N/A  User Name: N/A  Computer: DESKTOP-E3C6UKV  Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: E:, DeviceName: \Device\HarddiskVolume8.(STATUS_DEVICE_NOT_CONNECTED)

Code:

Event[1959]:  Log Name: System  Source: Disk  Date: 2017-06-21T02:48:17.419  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-E3C6UKV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[1960]:  Log Name: System  Source: Disk  Date: 2017-06-21T02:48:17.419  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-E3C6UKV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[1961]:  Log Name: System  Source: Disk  Date: 2017-06-21T02:48:17.419  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-E3C6UKV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[1962]:  Log Name: System  Source: Disk  Date: 2017-06-21T02:48:17.419  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-E3C6UKV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[1963]:  Log Name: System  Source: Disk  Date: 2017-06-21T02:48:17.419  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-E3C6UKV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.

Code:

Event[2658]:  Log Name: System  Source: Disk  Date: 2017-07-06T23:29:47.038  Event ID: 153  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-E3C6UKV  Description: The IO operation at logical block address 0x0 for Disk 0 (PDO name: \Device\000000d9) was retried.

Code:

Event[1954]:  Log Name: System
  Source: atapi
  Date: 2017-06-21T02:48:17.419
  Event ID: 143
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-E3C6UKV
  Description: 
The storage device produced an internal dump.