My Ryzen 1700x PC won't shut down, not in BIOS or Win10 or Linux

[neosapien]

I upgraded my PC with Ryzen components on June 17th, and everything was working fine until this last Monday or Tuesday, when I found that my PC would no longer sleep or hibernate. It would try to go into sleep or hibernate mode, and then half a second after turning out its lights and going to sleep, it would turn itself right back on again. I then found that the exact same thing was happening with Shut Down.

I googled, and tried as many suggestions I could find. Disable Wake on...well, everything, really. Disable Fast Startup in Windows 10 Power control panel. Enable ErP in BIOS (S4 and S5). Update BIOS. Clear CMOS. Reset to default BIOS settings.

I became curious to see if this was a Windows 10 issue or a hardware issue, so I tried to see if it was possible to shut down the PC in the BIOS or in a Linux installation I have on a bootable flash drive. Lo and behold, same exact issue, system doesn't care who's asking it to shut down in what state, it won't shut down (if I'm in the BIOS and I just push the power off button, the system again tries to shut down, and then starts itself right back up again, same behavior if I tell it to shut down through Win10 or Linux). I disconnected every USB device but the keyboard and mouse, even tried disconnecting the LAN cable from the router. I've disconnected and reconnected the 2-pin power switch from the motherboard, thinking maybe it wasn't connected securely.

If I press and hold down the power button, that will turn the system off, but then it won't power back on again until I reset the power supply by turning it off and then on again at the on/off switch. My system just really, really doesn't want to be shut down, for some reason. Or sleep, or hibernate.

Here are pictures of it - who knows, maybe someone will see something wrong with my wiring or something. Inside my PC | Wiring hidden behind right case panel.

CPU: AMD Ryzen 7 1700X (Summit Ridge, ZP-B1)
3400 MHz (34.00x100.0) @ 3492 MHz (35.00x99.8)
Motherboard: ASUS PRIME X370-PRO (latest BIOS)
Chipset: AMD X370 (Promontory)
Memory: 16384 MBytes @ 1197 MHz, 16-16-16-39
- 8192 MB PC19200 DDR4 SDRAM - G Skill F4-2400C16-8GFT
- 8192 MB PC19200 DDR4 SDRAM - G Skill F4-2400C16-8GFT
Graphics: MSI GTX 970 (MS-V316)
NVIDIA GeForce GTX 970, 4096 MB GDDR5 SDRAM
Drive: WDC WD7500AACS-00D6B1, 732.6 GB, Serial ATA 3Gb/s
Drive: Samsung SSD 850 EVO 1TB, 976.8 GB, Serial ATA 6Gb/s @ 6Gb/s
Drive: WDC WD10EADS-00L5B1, 976.8 GB, Serial ATA 3Gb/s
Drive: WDC WD2001FASS-00W2B0, 1953.5 GB, Serial ATA 3Gb/s
Drive: HL-DT-ST BD-RE WH10LS30, BD-R
Sound: Asus Xonar DSX
Network: Intel I211AT Copper (Pearsonville) Network Adapter
OS: Microsoft Windows 10 Education (x64) Build 15063.483 (RS2)
Case: Cooler Master HAF 932
PSU: Corsair HX520W

 

[daveybrat]

My guess would be the 10 year old power supply you kept while upgrading most of the other parts. I would suggest replacing that first.

 

[neosapien]

My guess would be the 10 year old power supply you kept while upgrading most of the other parts. I would suggest replacing that first.

No joy. I went out and bought an EVGA Supernova 650 G2. Error persists.
Tried disconnecting everything in the system that I could - every USB device but keyboard and mouse, the PCI-E sound card, every SATA device, every fan except the CPU HSF. Error still persists.

 

[R0H1T]

Are all the drivers, especially graphics, properly installed? Also there's this setting in the BIOS ~ system state after power failure ~ what's that set to?

 

[neosapien]

Are all the drivers, especially graphics, properly installed? Also there's this setting in the BIOS ~ system state after power failure ~ what's that set to?

Windows Update is fully updated, Nvidia Geforce drivers are fully updated, AMD Chipset drivers are fully updated.

In BIOS:
In Boot Menu, Fast Boot is Enabled. Next Boot after AC Power Loss is set to Normal Boot.
In Advanced Menu, under APM Configuration, ErP Ready is set to Enable(S4+S5). Restore AC Power Loss is set to Power off. Power On By PCI-E / Ring / RTC are all set to Disabled.

 

[R0H1T]

Sounds like a board issue to me then, you could try one last thing ~ reset BIOS & disconnect all non essential devices, including ethernet cable & boot drive, then try booting into Linux (using that flash drive) & see if it;s possible to shutdown, sleep or hibernate.

If it's still not doing any of the three then you'd have to RMA the board. Some other Ryzen owners (with the same board?) can probably chime in to share their thoughts.

 

[Iron Woode]

before you RMA the board try an earlier BIOS rather than the newest one. See if the problem persists.

 

[Pick2]

Have you tried disconnecting the "power on" switch - the two wires you posted you reseated in your OP. Then try shutdown from windows or wherever and see if that changes anything.

 

[neosapien]

Sounds like a board issue to me then, you could try one last thing ~ reset BIOS & disconnect all non essential devices, including ethernet cable & boot drive, then try booting into Linux (using that flash drive) & see if it;s possible to shutdown, sleep or hibernate.

If it's still not doing any of the three then you'd have to RMA the board. Some other Ryzen owners (with the same board?) can probably chime in to share their thoughts.

Okay, I spent a while testing. Here's the results:

Unplugged peripherals - sound card, all SATA drives, fan controller, mouse, LAN cable disconnected

In Linux LXLE 64-bit
Sleep Attempt 1 - Plug in mouse, open shut down menu, unplug mouse, select suspend. System suspends successfully, does not power back up.
Sleep Attempt 2 - Plug in mouse, open shut down menu, select suspend. System fails to suspend successfully, powers itself back up.
Sleep Attempt 3 - Plug in mouse, open shut down menu, unplug mouse, select suspend. System suspends successfully, does not power back up.
Sleep Attempt 4 - Plug in mouse, open shut down menu, select suspend. System fails to suspend successfully, powers itself back up.
Hibernate Attempt 1 - Plug in mouse, open shut down menu, unplug mouse, select hibernate. System fails to begin shut down process, unknown error, unlike in Sleep Attempts #2 & 4. Screen becomes blurry and pixelated, but does not begin to shut down at all.
Hibernate Attempt 2 - Plug in mouse, open shut down menu, select hibernate. System fails to begin shut down process, unknown error, same as with hibernate attempt #1.
Shut Down Attempt 1 - Plug in mouse, open shut down menu, unplug mouse, select shut down. System fails to shut down successfully, powers back up.
Shut Down Attempt 2 - Plug in mouse, open shut down menu, select shut down. System fails to shut down successfully, powers itself back up.
Shut Down Attempt 3 - Plug in mouse, open shut down menu, unplug mouse, select shut down. System fails to shut down successfully, powers back up.
Shut Down Attempt 4 - Plug in mouse, open shut down menu, unplug mouse, select shut down. System fails to shut down successfully, powers back up.
Shut Down Attempt 5 - Do not plug in mouse. Press power button on case. System shuts down successfully.
Shut Down Attempt 6 - Do not plug in mouse. Press power button on case. System fails to shut down successfully, powers back up.
Shut Down Attempt 7 - Do not plug in mouse. Press power button on case. System fails to shut down successfully, powers back up.
Shut Down Attempt 8 - Do not plug in mouse. Press power button on case. System fails to shut down successfully, powers back up.

In Win10 - Plug SSD back in, boot into Win10 login screen
Sleep Attempt 1 - Mouse unplugged. System fails to sleep properly, powers back up.
Sleep Attempt 2 - Mouse unplugged. System fails to sleep properly, powers back up.
Sleep Attempt 3 - Mouse unplugged. System fails to sleep properly, powers back up.
Sleep Attempt 4 - Mouse unplugged. System fails to sleep properly, powers back up.
Sleep Attempt 5 - Mouse unplugged. System fails to sleep properly, powers back up.
Hibernate Attempt 1 - Mouse unplugged. System fails to hibernate properly, powers back up.
Hibernate Attempt 2 - Mouse unplugged. System fails to hibernate properly, powers back up.
Hibernate Attempt 3 - Mouse unplugged. System fails to hibernate properly, powers back up.
Hibernate Attempt 4 - Mouse unplugged. System fails to hibernate properly, powers back up.
Hibernate Attempt 5 - Mouse unplugged. System fails to hibernate properly, powers back up.
Shut Down Attempt 1 - Mouse unplugged. System shuts down successfully, does not boot back up.
Shut Down Attempt 2 - Mouse unplugged. System fails to shut down properly, powers itself back up.
Shut Down Attempt 3 - Mouse unplugged. System fails to shut down properly, powers itself back up.
Shut Down Attempt 4 - Mouse unplugged. System fails to shut down properly, powers itself back up.
Shut Down Attempt 5 - Mouse unplugged. System fails to shut down properly, powers itself back up.

 

[neosapien]

before you RMA the board try an earlier BIOS rather than the newest one. See if the problem persists.

Okay, I tried. No joy.

Reflash BIOS:
0805 - Current version
0612 - Version I was running when I initially started having these problems. I upgraded to 0805 to try and stop them.
0604 - Error message from Asus EZ Flash 3 Utility v03.00 - "Selected file is not a proper BIOS!"
0511 - Error message from Asus EZ Flash 3 Utility v03.00 - "Selected file is not a proper BIOS!"
0504 - Error message from Asus EZ Flash 3 Utility v03.00 - "Selected file is not a proper BIOS!"
0502 - Error message from Asus EZ Flash 3 Utility v03.00 - "Selected file is not a proper BIOS!"
Reflashing back to 0612.

In Win10 - Plug SSD back in, boot into Win10 login screen (BIOS 0612)
Sleep Attempt 1 - Mouse unplugged. System fails to sleep properly, powers back up.
Sleep Attempt 2 - Mouse unplugged. System fails to sleep properly, powers back up.
Sleep Attempt 3 - Mouse unplugged. System fails to sleep properly, powers back up.
Sleep Attempt 4 - Mouse unplugged. System fails to sleep properly, powers back up.
Sleep Attempt 5 - Mouse unplugged. System fails to sleep properly, powers back up.
Hibernate Attempt 1 - Mouse unplugged. System fails to hibernate properly, powers back up.
Hibernate Attempt 2 - Mouse unplugged. System fails to hibernate properly, powers back up.
Hibernate Attempt 3 - Mouse unplugged. System fails to hibernate properly, powers back up.
Hibernate Attempt 4 - Mouse unplugged. System fails to hibernate properly, powers back up.
Hibernate Attempt 5 - Mouse unplugged. System fails to hibernate properly, powers back up.
Shut Down Attempt 1 - Mouse unplugged. System successfully shuts down, does not boot back up.
Shut Down Attempt 2 - Mouse unplugged. System successfully shuts down, does not boot back up.
Shut Down Attempt 3 - Mouse unplugged. System fails to shut down properly, powers itself back up.
Shut Down Attempt 4 - Mouse unplugged. System fails to shut down properly, powers itself back up.
Shut Down Attempt 5 - Mouse unplugged. System fails to shut down properly, powers itself back up.

 

[neosapien]

Have you tried disconnecting the "power on" switch - the two wires you posted you reseated in your OP. Then try shutdown from windows or wherever and see if that changes anything.

Do you mean that I should turn on the PC with the 2-pin power switch cable connected to the motherboard front panel connector, but then while the PC is turned on, I should disconnect that 2-pin cable, then see if I can successfully sleep/hibernate/shut down the system? I only ask to confirm because it's a matter of unplugging a cable from the motherboard while the system is running.

 

[R0H1T]

What port did you plug the mouse in, totally random or just the same port (or 2) every time? Looks like your USB port could be damaged, do you have access to PS/2 mouse & port for your mobo or another USB mouse?

 

[neosapien]

What port did you plug the mouse in, totally random or just the same port (or 2) every time? Looks like your USB port could be damaged, do you have access to PS/2 mouse & port for your mobo or another USB mouse?

Prior to running my most recent LXLE tests, I had the mouse plugged into one of the motherboard's rear panel USB 3.0 (or I guess they're called USB 3.1 5gbps now) ports. When I decided to do the Linux tests, I unplugged the mouse from the rear panel port and brought it over to the case's front panel ports, which are USB 2.0 and connected to a header on the motherboard.

I have access to an old MS USB mouse, as well as a USB to PS/2 adapter.

But if it was an issue where the USB port that the mouse was connected to was damaged, then surely the system would have functioned normally when I was attempting to sleep/hibernate/shut down the system while the mouse was unplugged?

 

[R0H1T]

Prior to running my most recent LXLE tests, I had the mouse plugged into one of the motherboard's rear panel USB 3.0 (or I guess they're called USB 3.1 5gbps now) ports. When I decided to do the Linux tests, I unplugged the mouse from the rear panel port and brought it over to the case's front panel ports, which are USB 2.0 and connected to a header on the motherboard.

I have access to an old MS USB mouse, as well as a USB to PS/2 adapter.

But if it was an issue where the USB port that the mouse was connected to was damaged, then surely the system would have functioned normally when I was attempting to sleep/hibernate/shut down the system while the mouse was unplugged?

That's not always the case, I have a USB port at the back damaged, I have disabled it in BIOS. A damaged USB port could work at times & still post other problems, I say this because 4 times you unplugged (or didn;t plug) the mouse in, you could shut the system down. So it's likely a port or the mouse, troubleshooting is a real PITA, but that's the only conclusion I can come up with after the last set of tests.

 

[neosapien]

That's not always the case, I have a USB port at the back damaged, I have disabled it in BIOS. A damaged USB port could work at times & still post other problems, I say this because 4 times you unplugged (or didn;t plug) the mouse in, you could shut the system down. So it's likely a port or the mouse, troubleshooting is a real PITA, but that's the only conclusion I can come up with after the last set of tests.

So maybe the surest way to test is to unplug the mouse entirely, plug a keyboard into the PS/2 port, so that no devices are using any USB ports at all, then boot into the Windows 10 login screen and see if I can sleep/hibernate/shut down.

 

[R0H1T]

Yes, also it'd be worthwhile to check if the same USB port or ports are causing the issue when you plug the mouse in.

 

[DAPUNISHER]

At some point in a troubleshoot, you have to call it, and cut your losses. I.E. time, effort, loss productivity or gaming. I would send that board back. Mark it somewhere very subtle, so you can be certain you do not get the same one back. I have had it happen. If the new one exhibits the same symptoms, you know the culprit is another component.

 

[Iron Woode]

So maybe the surest way to test is to unplug the mouse entirely, plug a keyboard into the PS/2 port, so that no devices are using any USB ports at all, then boot into the Windows 10 login screen and see if I can sleep/hibernate/shut down.

sounds like a good idea, but more than likely it's the board.

a lot of people are complaining about that board, especially ones with a sticker showing 502.

Time to RMA the board.

 

[EXCellR8]

did you try command prompt? more specifically shutdown /s /f /t 0

one of my ITX boards would shut down but then automatically power itself back on like some stubborn phantom board.

 

[neosapien]

I called Asus to tell them about my motherboard issues. They suggested RMAing the motherboard, but said that they didn't have any stock to do an Advanced RMA (and would not substitute it for a similar Asus AM4 motherboard), so I would have to send the motherboard back first, and be without it for weeks. I told them that's not really acceptable to me, I can't go without a motherboard for that length of time. They gave me a case number and told me to call them back at a later date to see if they have more stock available to do the Advanced RMA.

 

[Iron Woode]

I called Asus to tell them about my motherboard issues. They suggested RMAing the motherboard, but said that they didn't have any stock to do an Advanced RMA (and would not substitute it for a similar Asus AM4 motherboard), so I would have to send the motherboard back first, and be without it for weeks. I told them that's not really acceptable to me, I can't go without a motherboard for that length of time. They gave me a case number and told me to call them back at a later date to see if they have more stock available to do the Advanced RMA.

these things do happen.

I had a similar issue with Asus when I RMA'd my H81M-E board. So I had to use my old socket 775 system instead. The good news was that I received my new board 6 days later.

 

[Elixer]

I called Asus to tell them about my motherboard issues. They suggested RMAing the motherboard, but said that they didn't have any stock to do an Advanced RMA (and would not substitute it for a similar Asus AM4 motherboard), so I would have to send the motherboard back first, and be without it for weeks. I told them that's not really acceptable to me, I can't go without a motherboard for that length of time. They gave me a case number and told me to call them back at a later date to see if they have more stock available to do the Advanced RMA.

Damn, that blows, but, is expected, mobo's have been selling pretty fast.

Have you tried to take the mobo out of the case, and stick it on the cardboard box, and see if it shuts down correctly then? Sometimes it shorts out on the case, and it causes really odd issues.

 

[DAPUNISHER]

Damn, that blows, but, is expected, mobo's have been selling pretty fast.

Have you tried to take the mobo out of the case, and stick it on the cardboard box, and see if it shuts down correctly then? Sometimes it shorts out on the case, and it causes really odd issues.

The general consensus from reading around, is that Asus's CS is trash now. Not surprised they kicked the can down the road. Asus reps, potentially reading these threads, are welcome to prove me wrong by escalating his case, and getting him a new board. wink wink nudge nudge

 

[bigboxes]

Not cool Asus. Not cool at all. Customer service should be a top priority, not an afterthought.

 

[EXCellR8]

On one hand they could have replaced it with something else I suppose but on the other it's not like they can serve every single consumer in a timely manner that aligns with your expectations. I'd say if they are at least offering that it's better than nothing. Not trying to defend them, as I've had some crap support too, but if supply is low and there's many people wanting to RMA there's not really a ton they can do but tell you to be patient.

You could always buy a cheaper board in the interim and sell it off later... hope you get it sorted though