A few days ago or maybe weeks ago, I posted on this forum on the unusual behaviour of my pc when I would start it. It would take long for the keyboard and mouse to be detected and then a slow startup. Btw this didn't happen before and I have SSDs only on my pc. I factory resetted my pc the other day as I got my GTX 1050 Ti, then found out that it was faulty/broken. There were artefacts on the screen and drivers couldn't be downloaded. As I have a Ryzen 3 2200G APU, I downloaded the Drivers for it again, as I have to wait for another GPU to come at a good price, and I need to download the drivers for my APU as I play at Custom Resolution in CSGO. After I downloaded the drivers for my APU and restarted it, the screen was flickering on and off in the lock screen, and I finally logged in and turned my PC Hz from 144Hz to 60Hz, and for anyone wondering I have a ASUS PRIME A320M-K MOBO with CV650 PSU. Before downloading the drivers, I could turn my pc at 144Hz with no issues basically, but after drivers downloaded, I started noticing some issues. Of course, next time I can boot my pc at 60Hz, but that's not why I am here for.
I think that AMD Drivers are having problems recognizing, or maybe loading whatever they are used for. In my opinion, when I turn my pc on, I think that it takes some time for the APU to be recognized, and then after that the keyboard/mouse is turned on and gives display to the monitor.
List of problems I have been having/noticed: Screen flickering, PC is on but then monitor doesn't display so you have to hard reset your pc, long time for the pc to load/turn on, sometimes pc is turned on but no display to monitor so have to hard reset and try again.
List of what I have tried: Making sure all power connectors, cables etc are in together, moved my RGB fans lighting node to a separate SATA Connector (that time was thinking maybe there's some voltage problems with the fans interfering with the SSDs required ones idk really lol), took USB connector out and then put it back in, made sure loose wires were not touching the MOBO etc.
PC Build: ASUS PRIME A320M-K, Corsair CV650, UpHere 3 RGB fans (6-pin to Lighting Node which connects to SATA Connector), 1 3-pin RGB Back Fan, Ryzen 3 2200G, 120GB WD Green (I believe is the name for it) SSD, 480GB PNY SSD, 2x 8GB 2400Mhz RAM.
Conclusion: I have had this pc for over 2 years and never had this problem, day one the PC would turn on in seconds, maybe less than 10 secs. I think the new AMD Drivers update are causing this issue, and this must be known to them, and any other people looking for help with problems similar to this. Please comment if you have similar problems below, or maybe what you did that may have fixed such issues for you.
I think that AMD Drivers are having problems recognizing, or maybe loading whatever they are used for. In my opinion, when I turn my pc on, I think that it takes some time for the APU to be recognized, and then after that the keyboard/mouse is turned on and gives display to the monitor.
List of problems I have been having/noticed: Screen flickering, PC is on but then monitor doesn't display so you have to hard reset your pc, long time for the pc to load/turn on, sometimes pc is turned on but no display to monitor so have to hard reset and try again.
List of what I have tried: Making sure all power connectors, cables etc are in together, moved my RGB fans lighting node to a separate SATA Connector (that time was thinking maybe there's some voltage problems with the fans interfering with the SSDs required ones idk really lol), took USB connector out and then put it back in, made sure loose wires were not touching the MOBO etc.
PC Build: ASUS PRIME A320M-K, Corsair CV650, UpHere 3 RGB fans (6-pin to Lighting Node which connects to SATA Connector), 1 3-pin RGB Back Fan, Ryzen 3 2200G, 120GB WD Green (I believe is the name for it) SSD, 480GB PNY SSD, 2x 8GB 2400Mhz RAM.
Conclusion: I have had this pc for over 2 years and never had this problem, day one the PC would turn on in seconds, maybe less than 10 secs. I think the new AMD Drivers update are causing this issue, and this must be known to them, and any other people looking for help with problems similar to this. Please comment if you have similar problems below, or maybe what you did that may have fixed such issues for you.