PC shuts off, have to unplug and plug back in to get it back on

My Win 10 Pro PC has lately been shutting off without warning - screens go black, then the fans kick up for a few seconds and then everything powers off. But I can't just hit the power switch to turn it back on. I have to pull the power plug out of the power supply and plug it back in to get it to power back on.

It seems to have been happening mostly on my son's profile, and he plays Minecraft and Roblox all the time. He's constantly downloading shaders, add-ons and various other junk, which I'm wondering is having something to do with this issue. It pretty much never happens on my profile, but today it just did, after it happened 2 or 3 times within half an hour on my son's profile.

*edit* I couldn't find much info in Event Viewer that I could readily recognize as an issue, but I did notice 1,435 Event ID 13's from Source nvlddmkm, all of them happened at exactly 11:31:02 this morning, about 48 minutes before making this post. */edit*

Because of the power cord issue I'm wondering if it's a power supply issue. Back around last Christmas I did a major system upgrade with a new 6-core Ryzen processor, motherboard, nVME SSD, Corsair Vengeance 32 GB RAM and 6 GB GeForce GTX 1060 graphics card. But I kept the same Seasonic M12II 650W power supply that I've had since May 2013. It's basically a new machine other than my data HDD's and power supply.

Any insights would be greatly appreciated. I do a lot of remote work from home on this machine and can't afford to have it shutting down on me while I'm in the middle of work.

Hi PatrickGSR94,

Welcome to TF's BSOD forum.

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) bcdedit /enum {badmemory}

10) 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

11) Make sure that there is no over clocking while troubleshooting.



12) Post a share link using one drive, drop box, or google drive for C:\windows\memory.dmp

Code:

Crash dump found at C:\Windows\MEMORY.DMP
Creation date: 11/02/2019 11:33:07
Size on disk: 1599 MB

13) The BIOS: Version/Date American Megatrends Inc. P1.30, 7/4/2018
Upgrade the BIOS to the most up to date non-beta BIOS:
ASRock > B450 Pro4

Code:

Microsoft Windows [Version 10.0.17763.805]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some of 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.

C:\Windows\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.771

Image Version: 10.0.17763.805

[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.

C:\Windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.771

Image Version: 10.0.17763.805

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

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.

C:\Windows\system32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
  997888 file records processed.
File verification completed.
  20805 large file records processed.
  0 bad file records processed.

Stage 2: Examining file name linkage ...
  1244 reparse records processed.
  1214110 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered to lost and found.
  1244 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
  108112 data files processed.
CHKDSK is verifying Usn Journal...
  40359824 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

 468286463 KB total disk space.
 173625828 KB in 626672 files.
    430708 KB in 108113 indexes.
         0 KB in bad sectors.
   1127347 KB in use by the system.
     65536 KB occupied by the log file.
 293102580 KB available on disk.

      4096 bytes in each allocation unit.
 117071615 total allocation units on disk.
  73275645 allocation units available on disk.

C:\Windows\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\P-C-REVIT-BOX\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk2\\Partition2"'
Property(s) update successful.

C:\Windows\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\P-C-REVIT-BOX\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk2\\Partition2"'
Property(s) update successful.

C:\Windows\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier              {badmemory}

C:\Windows\system32>

Memory Dump file link:
ShareFile

The first and second scannow:

Code:

Windows Resource Protection found corrupt files but was unable to fix some of them.

Code:

Windows Resource Protection found corrupt files and successfully repaired them.

Run sfc /scannow again so that it displays that it no longer finds corruption.

The memory dump was corrupt.
It was bugheck 133.
It was not able to be debugged.


Read these links on windows driver verifier (do not use the tool until it is communicated in the thread):

Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983



For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

Also check the CPU and motherboard temperatures are not too high which could casue shutdown due to thermal overload - try HWMONITOR | Softwares | CPUID

*edit* I couldn't find much info in Event Viewer that I could readily recognize as an issue, but I did notice 1,435 Event ID 13's from Source nvlddmkm, all of them happened at exactly 11:31:02 this morning, about 48 minutes before making this post. */edit*

for info - that is your nvidia video driver.

i don't know what event viewer id 13 is off-hand.

did the messages have a red icon to the left and say "error"?

I would get your son his own system if you can because he will infect yours soon enough based on his downloads.

since you rely on your system for rd work, it is vital that your system be working properly as you stated.

Sorry it's taken so long to respond to this folks. Life and all that. So yesterday the machine shut off at least 4 times in the span of 30 minutes or so. Today after coming home from work my son reported the machine wouldn't power on at all. No matter how much we unplugged and plugged the power supply back in, it would not power on.

So I picked up a new power supply from Best Buy and installed it, but it still wouldn't come on. Unplugged all peripherals from the motherboard, BOOM! System powers on! Connected everything up again, NOTHING!

Turns out that I was using one of the SATA power cables from the old power supply for my HDD's just because the power connector configuration worked a little better with my drives. With the system powered on, as soon as I plugged in that old cable into the new power supply, the system would shut off.

So I connected the hard drives to the power supply with one of the new cables, and everything appears to be working normally. Seems very odd that a power supply peripheral cable could be causing the system to shut down. Anyone seen this before?

Ive seen it before yes
My old Antec True Power 550. It had 2x SATA power cables coming from the PSU, not many back then. Well, over time the pins started to push from out the back, Yellow, was the main culprit. I kept forcing it back in when connecting. This is when the SATA pins inside the connector came out and touched each other, but only when i connected the drive. I didnt realise until i got the torch out and looked closely at the pins inside. This connector got chopped off and replaced with a molex.

PatrickGSR94 said:

Sorry it's taken so long to respond to this folks. Life and all that. So yesterday the machine shut off at least 4 times in the span of 30 minutes or so. Today after coming home from work my son reported the machine wouldn't power on at all. No matter how much we unplugged and plugged the power supply back in, it would not power on.

So I picked up a new power supply from Best Buy and installed it, but it still wouldn't come on. Unplugged all peripherals from the motherboard, BOOM! System powers on! Connected everything up again, NOTHING!

Turns out that I was using one of the SATA power cables from the old power supply for my HDD's just because the power connector configuration worked a little better with my drives. With the system powered on, as soon as I plugged in that old cable into the new power supply, the system would shut off.

So I connected the hard drives to the power supply with one of the new cables, and everything appears to be working normally. Seems very odd that a power supply peripheral cable could be causing the system to shut down. Anyone seen this before?

If you are using a modular PSU then you have discovered that cable connections at the PSU end are not generally compatible between PSUs!

Perhaps, but in this case the problem was happening with the SATA cable that was originally supplied with the old PSU. I just didn’t see it until I tried using that same cable with the new PSU due to the connector configuration. The cable itself was the problem.