Computer randomly shuts off

[Slapo1]

So there are a couple games that when I play my computer will just shut off after playing for like 30 minutes. It happens with CS:GO, Blade and soul and a few others. The weird thing is it will shut off when playing a game like CS:GO which isn't that hard to run and when I play something like Fallout 4 that is hard to run it won't shut off. I have had this problem for years now and I am finally posting about it now. Anyone know what my problem might be?

 

[Ralston18]

Could be overheating maybe? However, I think if that were the problem it would be getting worse and worse.

My suggestion is that you do two things:

1) Press and hold the Windows key and the R key together. The the box that opens type "perfmon /res" to go into the performance monitor. You will be able to watch what is going on within you computer and hopefully identify some program or process that does something like grab all of the CPU time or all of the available memory.

2) Open the Event Viewer and likewise check the log entries for errors or warnings that occur just before or at the time of the shutdowns. Troubleshooting via the Event logs is a bit cumbersome and you may need to explore a bit to gain some understanding of the logs. Remember that you can right-click on an entry to get more details about that entry. The idea being to find an error code of some sort that can be researched for a fix.

 

[Slapo1]

Could be overheating maybe? However, I think if that were the problem it would be getting worse and worse.

My suggestion is that you do two things:

1) Press and hold the Windows key and the R key together. The the box that opens type "perfmon /res" to go into the performance monitor. You will be able to watch what is going on within you computer and hopefully identify some program or process that does something like grab all of the CPU time or all of the available memory.

2) Open the Event Viewer and likewise check the log entries for errors or warnings that occur just before or at the time of the shutdowns. Troubleshooting via the Event logs is a bit cumbersome and you may need to explore a bit to gain some understanding of the logs. Remember that you can right-click on an entry to get more details about that entry. The idea being to find an error code of some sort that can be researched for a fix.

I really don't know much about computers except for the basics what should I be looking for in those things I just see a bunch of things that don't make much sense to me and thanks for the help.

 

[Ralston18]

That's okay. There is always more to learn and figure out.

Just focus on one log at a time: start with Custom Views/Administrative Events then the various Windows logs.

What you want to look for are yellow or red icons that indicate errors and may contain descriptive information or even error codes (a number).

Double click the entry (left button) to get more details. (Or a single right click and select Event properties will do the same.)

Look at the dates and time for those errors and see if the dates and times correspond to a disconnect.

When you find some consistent pattern that matches past and current disconnects then post that information. The information may lead to the cause of the problem and a solution.

 

[Slapo1]

Could be overheating maybe? However, I think if that were the problem it would be getting worse and worse.

My suggestion is that you do two things:

1) Press and hold the Windows key and the R key together. The the box that opens type "perfmon /res" to go into the performance monitor. You will be able to watch what is going on within you computer and hopefully identify some program or process that does something like grab all of the CPU time or all of the available memory.

2) Open the Event Viewer and likewise check the log entries for errors or warnings that occur just before or at the time of the shutdowns. Troubleshooting via the Event logs is a bit cumbersome and you may need to explore a bit to gain some understanding of the logs. Remember that you can right-click on an entry to get more details about that entry. The idea being to find an error code of some sort that can be researched for a fix.

That's okay. There is always more to learn and figure out.

Just focus on one log at a time: start with Custom Views/Administrative Events then the various Windows logs.

What you want to look for are yellow or red icons that indicate errors and may contain descriptive information or even error codes (a number).

Double click the entry (left button) to get more details. (Or a single right click and select Event properties will do the same.)

Look at the dates and time for those errors and see if the dates and times correspond to a disconnect.

When you find some consistent pattern that matches past and current disconnects then post that information. The information may lead to the cause of the problem and a solution.

Ok so I have hundreds of errors ( https://gyazo.com/44353c169624282496482345409b2a09 thats just a bit of em ) so I am going to wait til my computer shuts off again, check the time, then see if that time corresponds with any errors. Does that sounds like what I am supposed to do? And thanks again for helping me out I really do appreciate it.

 

[Ralston18]

Good - you are getting on track.

Which log were you looking at? Scroll up and down and look for different errors as well. And in other logs. Windows 7 - Yes/No?

Open up (double click) one of the errors and post the "details".

However, per a Microsoft site:

"repeated NTFS Event ID 55 errors in my system event log that says "The file system structure on the disk is corrupt and unstable".

Source:

http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/repeated-ntfs-event-id-55-errors-in-my-system/e58d1d62-d9ba-4486-b175-24bcf744b971?auth=1

Sort of leads me to believe that the file areas used for game play are going or have gone bad....

One solution given is to run ChckDsk with the /R option. But best if we determine if that is truly the thing to do. And consider other possible errors that confirm my belief or even dispute it. (No ego here - I can be wrong....)

Most important action now is, while stable, to get your data backed up immediately.

Have you ever done any disk cleaning or defragmentation? (Note: Solid State Drives are not defragged.)

Maybe a few little maintenance steps will be a good start on fixing it all.

 

[Slapo1]

"The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume2." Thats what it says on one of the Ntfs errors.
I haven't defragged my computer or anything but I have had 2 different hard drives on this computer (one of them died) and with both of them I still had the problem with my pc turning off.

 

[Ralston18]

If the PC has been turning off long enough and seriously enough to do in one hard drive and now possibly another then it is all the more important for you to get your data backed up.

Plus explore the logs even more to find out what else may be happening.

Back up your data and then go ahead and run the chkdsk utility. Clear the logs and start looking for new entries that may point to some other problem or possible cause.

Do you still have the original PSU (power supply unit)? Any other changes in your system? Any noted household electrical problems such as lights flickering, breakers tripping? Anything that would cause your PC to suddenly and unexpectly shutdown.

 

[Slapo1]

The first hard drive didn't die because of the computer it water got spilled onto it when it was out of the computer and I tried running the chkdsk check but when I click it a black box shows up for half a second then disappears idk if it is going through