Solved My new AMD Ryzen 3900x system keeps turning itself back on after full shutdown

  • Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Welcome to our Community
Wanting to join the rest of our members? Feel free to sign up today.
Sign up
Not open for further replies.

John Lockwood

PCHF Member
PCHF Member
Jun 11, 2017
Hello all,

I am having an odd issue with my new motherboard/system. I just swapped out my Threadripper 1950x and Gigabyet x399 Aorus Gaming 7 motherboard for a Ryzen 3900x and Gigabyte x570 Xtreme. So far, I have no issues with the performance. I have not done any overclocking, and everything has been stable.

Here is my full parts list vis PC Part Picker:

I have installed the latest Bios version; F10 from Gigabyte's website. I also have downloaded the latest chipset drivers and individual drivers for all the components that are Windows 10 1909 supported, as I am running Windows 10 Pro version 1909.

One 3 known occasions now, my system has powered itself back from a full shutdown state. I powered it down before heading out for a bit. and when I came home it was powered on. When I logged into my main user account, task manager said system up time was 4 hours and some change, which meant it kicked on shortly after I had powered it down.

Last night I had done a full shut down, and while working on another build for a friend, my system powered itself back on. This time I actually saw it do it. At this point, I started researching what could been causing it. Here are some steps I have taken to try to prevent it from doing it.

In BIOS, I double checked to make sure fast boot was off, which it has been since I installed the BIOS. I turned off 'Wake Up On LAN" after the first time it turned itself back on, but the issue continues. Since it turned back on last night, I have gone into Windows Power Settings and changed the following under the Sleep tree:
-Sleep After: Never
-Hibernate: Never
-Allow Wake Times: Never

I also went into device manager and turned off 'Allow this device to wake PC" under the mouse and keyboard settings. After I made this changes, I clicked on the start icon, and click 'Shut down". It shut all the way down, and I tapped on my keyboard and mouse a little bit to make sure they where not going to trigger a boot up. It stayed powered down, and I left the room. Later on when I came back to the PC, and it was booted up again and task manager said it was up almost 4 hours, which means the system stayed shut down for about an hour and a half, if that, before it booted back up.

Does anyone have anything else I could try? I would just keep the kill switch off for now, but I really don't want to do that. I know the Ryzen 3900x and x570 is still relatively new and there is not a lot about this board online yet. I have not attempted to contact Gigabyte yet.. That's my next step on Monday when they have support lines open.

I have stopped my PC from randomly booting up now. I am not sure which of my connected devices was causing it, but after talking to Gigabyte support, they suggested that I enable the ErP setting in the bios. This has seemed to solve the issue, as my pc has been shut down 3 times since then without any boot ups, including an over night shut down.


PCHF Administrator
Security Team
PCHF Donator
Malware Teacher
Jul 19, 2016
Please do not bump threads, it will only stop you getting help.

All our helpers are volunteers who have a life away from the forum. You will be helped asap, although seeing you are getting help elsewhere?????
Last edited:


Autonomous Admin
Support Team
Sep 9, 2016
The OP has been able to resolve the issue by working with Gigabyte Tech Support, solution added to OP.
Not open for further replies.