Ryzen 1700x Random Black Screen Crash

Feb 18, 2018
5
0
10
Ok I know there are a ton of posts about this but most of them say solved with no clear solution or outcome. I have tried everything I have seen so far in any of these posts so time for me to post one for mine. I cannot pin down a certain action or operation causing crash. Crashes doing everything and anything and no clear time frame. All system temps are under 40c. Tried cpu,gpu,ram benchmarks and no crashes. gaming - no crashes yet but have not had much seat time. just doing random operations (surfing web, playing with RGB lighting settings,at windows login screen,etc )

Just got this system up and running yesterday. First thing I did was update everything. Newest Bios, chipset direct from AMD, and all of the other drivers are most recent versions.

I have even uninstalled and fresh installed all drivers that i could. The black screens hard lock the pc and then I need to power cycle to reboot. Windows log shows nothing besides failure to shut down. This is a fresh install of windows 10 pro x64. I have tried overclocking ram to see if it was ram compatibility issue. and have not had any obvious change. The only thing that has seemed to do something was to leave stock ram speed but up voltage a bit. This took the crashes from within 2 hrs crash to no crash for over 12 hours of run time. it did crash finally around 14 hours. I then up the voltage just a tad more to recommended ram voltage on package which is 1.35v for trident z. and let it run over night. no crash till i touched it today then it crashed after a few mins.

Any ideas? Thanks in advance!!

System Specs: Everything is stock except i have boosted ram voltage but not speeds.
Ryzen 7 1700x
Asus Strix B350-F
Gskill Trident Z RGB 3200mhz running at stock 2133mhz voltage at package recommended 1.35v
Corsair RM750I PSU
GTX 970 100me GPU (this is only temporary)
NZXT Kraken AIO
Sandisk ultra 2 SSD 480GB
 
Solution

oriol.delavega

Prominent
Jan 31, 2018
62
0
660
I assume videocard worked correctly with your previous build.
Did you reinstall windows? A long shot, but perhaps something didn't correctly install the first time. More things you could try is disconnecting every other storage drives but for the OS one. And removing one stick of RAM at a time to see if any is faulty. Also testing the system with another PSU, if you have another one. If all this fails, you could remove the CPU, blow pins and socket with compressed air, and resettling it. If, in the end, that also fails, you could have a faulty motherboard or CPU.

 
Feb 18, 2018
5
0
10


Yes the gpu worked in the previous build, I have not tried a second fresh install of windows yet. might be worth a try. yes i can try a different psu. I have yet to do any hardware swaps since it seems to be a dare I say common issue and everyone that has tried doing hardware swaps have not worked and this issue seems to be more software and bios. I will definitely try the hardware if nothing else comes up. Ive been reading anything related to this topic and all of the people who have rma'd there parts still have the issue with the new ones. Heck one guy rma'd everything and swapped to confirmed working parts so not a single part was unchanged including ssd and same problem haha.
 

oriol.delavega

Prominent
Jan 31, 2018
62
0
660


You could also try Linux. This would rule out a soft error once and for all, if there is really one.
 
Solution
Feb 18, 2018
5
0
10


not a bad idea. we will see what the actual ower of the system wants to do im just building haha. he has it at the moment.
 
Oct 10, 2018
4
0
10
I have the exact same issue. Running a Ryzen 7 1700x with ASUS ROG Strix B350-F. I sent back the motherboard and got a replacement with no change. The CPU was sent to AMD and they said they couldn't reproduce the issue and that there was thermal paste on the pins and apparently cleaned it for me. When I got it back, there was more thermal paste on the pins than before I sent it (I checked if the problem was thermal paste on the pins before I sent it and didn't see any, but at least I know that they did check it). After removing the remaining paste, I tried it again and the problem still persists. I have tried removing each RAM stick individually and my GPU worked on my last rig (I don't have another one to try).
Hopefully this issue can be solved soon as I'm tempted to just buy a new CPU at this point.
 

cykamancer

Reputable
Apr 15, 2015
36
0
4,530


Hey did u find any solution? I'm having the same problem with my ryzen 1600 :(
 

cykamancer

Reputable
Apr 15, 2015
36
0
4,530


Hey did u find any solution? I'm having the same problem :(
 
Oct 10, 2018
4
0
10




Unfortunately not yet. I'm going to have to get back in touch with AMD but they're not being very helpful. It's almost like they refuse to believe that this issue exists. And it definitely does because mine crashed as I was typing up this response.
 

cykamancer

Reputable
Apr 15, 2015
36
0
4,530


actually last 2 week i did an experiment. i applied a mild overclock on my CPU and put a constant voltage( not Auto) in the BIOS. disabled cool'n quiet, c states in BIOS and it stopped crashing. 6 days ago i went back to BIOS defaults and just now it crashed after a long time. you should try what i said. if it works for u then we would know that is the cause. My guess is that the Auto values for voltage is wrong in bios. it undervolts the cpu causing it to crash. Happens mostly while idle/ low loads. Do let me know!
 
Oct 10, 2018
4
0
10


I have tried putting a voltage overclock (without increasing the frequency) thinking that the factory settings were unstable. Didn't see a change but I only tried a few voltages. If you're having some luck, I will try a much more detailed experiment and see if there is a stable "non-overclocked" voltage that people can use.
 

cykamancer

Reputable
Apr 15, 2015
36
0
4,530


Yup also be sure to disable AMD cool n quiet, global c state etc. Those will decrease the voltage too much automatically and starving the cpu of power causing it to crash. Good luck!
 
Oct 10, 2018
4
0
10


Will do. Thanks.