Restart issues with a Ryzen 5 1600 build
Hey folks, hopefully I'm putting this in the right place, or at least STARTING in the right place. I am having very strange stability issues with a PC build, and at this point, the only components I've kept the same while troubleshooting are the Ryzen 5 1600 and the RAM (soon to be changed), so I'm putting it here.
Last year I built a Ryzen PC that has been seeing random restarts under all circumstances (gaming, on startup, at idle, on the desktop, on login, at any point after OS load) since November after running perfectly stable for at least 6 months. The original config follows:
ASRock AB350 Gaming K4
Ryzen 5 1600 (stock cooling)
16GB (2x8) DDR4-2666 Crucial Ballistix Tactical (On the AsRock QVL)
XFX Radeon RX480 GTR 8GB
Seasonic Focus+ Gold 750 PSU
500GB WD Blue SSD for Boot, various storage HDDs
Initially, there were no entries in the event log for these restarts, just the power-kernel notifications, and I discovered that the RAM was running at 2400 instead of 2666 following the ASRock 5.10 BIOS update (released 10/18/18). Ran Memtest for 2 hours after adjusting the timings, everything was fine. That seemed to make things more stable for a day, but then the restarts came back with one of two bugcheck errors: Either the Page Fault In NonPaged Area (rare, maybe 2 times), and the far more common Video TDR failure, specifically the atikmpag.sys driver. Uninstalled and re-installed the drivers, same problem. So I did a clean Windows install from a USB stick. The restart happened DURING THE INSTALL SETUP.
So I replaced the PSU, and went to an old Xion 700. The install continued apace and finished normally. Things again were fine for a few hours, then the restarts happened again with no event log entries. So, my guess was either the GPU or the mobo, and admittedly I didn't fully trust the ASRock from the start. So I bought an ASUS ROG STRIX B350-F, and an aftermarket Cooler Master just for fun. Did the new install, clean Windows setup ran just fine, and the restarts happened AGAIN a few hours in, again with no event log entries. So, I swapped out the GPU for a RX 560, and the PC ran perfectly for four days on both the Xion 700 and the Seasonic 750.
Thinking I had solved it, I bought a new GPU, the MSI RX580 Armor 8GB. Got the part last night, put it in, and the PC wouldn't boot at all with the new card. Not even a fan spin. So, I switched back to the Xion 700 PSU, and the PC booted only to have the no event log restarts happen again within minutes under load. Last night I ran Memtest on sequential, all tests for 13 hours, and no faults appeared. I currently have it running all tests round-robin at home right now. I have NO IDEA WHAT COULD BE WRONG, and its driving me insane, because I WORK in IT. I should be able to figure this out, but I can't. HELP! Also, I have ordered a new 8pin to GPU cable for the Seasonic PSU, to test if the cable is bad, and will be replacing the wall cable tonight. Currently my PC's configuration is as follows, which will boot but is not stable:
Ryzen 5 1600 (Cooler Master MA410P/AS5)
ASUS ROG STRIX B350-F
16GB (2x8) DDR4-2666 Crucial Ballistix Tactical (Not on ASUS QVL)
MSI Radeon RX580 Armor 8GB
Xion 700W PSU
500GB WD Blue SSD
I'm really out to sea here, so help a guy out, what did I miss? What step didn't I take while I was troubleshooting?
Have you tried running the system outside the case?
I'd tear it all down and see what happens.
If that's no good you can try pulling a stick of ram then try the other if that one fails.
If it's not the ram and you've tried different GPUs, PSUs and a motherboard I'd be suspicious of the CPU. Faulty CPUs aren't common but it's possible.
did you install windows 10? from a different iso file?
have you tried the latest updated iso? maybe the iso you're using is corrupted somehow
stress test the ram using the windows install usb
If it is the cpu this might help . . .
Your cpu might have Segfault(not related to the issue), too, if within week 25 2017.
YES, finally some good suggestions lol. Thanks you all. I'll check killryzen (the one time I didn't keep the CPU box), and try running it outside the case tonight. It could be something random like the case power cable having a short. Never thought of that.
I did use two different isos for my two Windows installs, both different 1803 USB sticks created off different clean Windows installs.
During the Windows install, you hit F10 to access the Command Prompt - You may also have the option to do a memtest from the installer
|All times are GMT -7. The time now is 06:29 AM.|
Powered by vBulletin® Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
User Alert System provided by Advanced User Tagging (Pro) - vBulletin Mods & Addons Copyright © 2019 DragonByte Technologies Ltd.
vBulletin Security provided by vBSecurity (Pro) - vBulletin Mods & Addons Copyright © 2019 DragonByte Technologies Ltd.
vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2019 DragonByte Technologies Ltd.