As usual this is a self inflicted problem and definitely NOT an AMD problem. Running junk-ware from MB and other vendors will ultimately be bad news and running multiple ones even more sever problems. In the case of Ryzen, users should ONLY run Ryzen Master. Enjoy, John.
It's an AMD problem because the only commonality I've seen across every online post that suffers this exact problem is an AMD processor. Also, Ryzen Master is irrelevant, because if you'll check the links I included, Ryzen Master (and AMD Overdrive for that matter) was one of the triggers for the crash, and the problem affects FX and Phenom processors too, at least. You seem to have a history of insisting users use Ryzen Master or screenshot Ryzen Master before helping them. At least read the featured links before wrongly assuming the problem is self-inflicted – the ROG post and others confirm it to be an AMD CPU temp sensor issue, and Intel doesn't seem to behave this way.
I've been running MSI Afterburner and ASUS AI Suite constantly without any issue since the last crashes. Only when I launched a third CPU temp monitoring program like HWiNFO, Speccy or CoreTemp did the computer blackscreen after a few minutes.
Before asking a question the forum headers asks you to provide your system information. I don't really have enough information to offer a suggestion so please give the following information as required to post:
When posting a new question, please provide as much detail as possible describing your issue making sure to include the relevant hardware and software configuration.
That being said what you describe sounds more like a power issue and likely affecting GPU not CPU. Once we have specs we can give a better idea of what to try.
As already mentioned AMD does not suggest the use of 3rd party tweaking software such as Afterburner. You can get yourself quickly into an unstable setup doing so.
If you have an AMD GPU you need nothing more than Wattman in the drivers. For your CPU you should use nothing more than Ryzen Master.
This is not a question, as referenced in the guidelines Read This First . The post makes it pretty clear what it is, a central topic to centralise discussion about this particular issue. If you read the post and the external links, you'd see that it's confirmed to be a CPU issue, not a graphics card issue (I even included a "Cause" section if you read the post), and by extension it seems that all CPUs reported to be affected by this specific issue are AMD CPUs. I've already solved my problem. This is to help other people who may have been racking their brains for months like I was with the same problem.
-sum1-, I do not in any way believe this is an AMD issue. It is simple misuse of poor quality utilities. As pokester said and I have told many users, all that is needed is Ryzen Master. Enjoy, John.
Well this is for questions for people needing help from other users. You are breaking forum rules then by not posting in general discussion. Your discussion doesn't belong here at all then.I was only trying to get enough information to try to help you. Nobody can possibly see anything as you didn't give information just a bunch of general comments. I can see that you are pretty rude to people trying to help you. Glad you fixed your issue. Since you still have not really explained your issue with comments spread across literally generations of hardware or what fixed it, I am not sure how your intent is to inform or help the community. Have no fear i am quite sure I nor anyone else will attempt to help you again. I am sure one of the AMD mods will be happy to put your post where it belongs. amdmatt ray_m
Why you would recommend a overclocking tool to pinpoint a systemwide shutdown, is over my head. And why you would consider it less junkwarish, than all the other "junkwares" coming from the manufacturers of specific hardware, even more.
Delving through two threads, it is quite obvious, that AMD does not want you to monitor their hardware...and that is the source of the problem.
pokester I don't find anything rude about his replies and I don't know how he can be more clear about what he was attempting to do. Clearly, he is the one trying to help. I have been searching and searching while testing and testing finding no straight answers over the internet. What I did find was A LOT of people are having this problem with slightly different specs (different mb types, different RAM types, different generation AMD processors) but all are AMD, with no central place out there to DISCUSS the issue. So yes, I get what sum1 was trying to do here.
Anyway, here is my situation. I changed my i7-7700 cpu on a ASUS prime b250-c motherboard with 16gb hyper X 2400m RAM to AMD 2700x on a ASUS prime x470 pro motherboard. At first i just used the hyper x RAM for couple weeks until I had money to purchase an AMD optimized 3200m RAM having no problems (even used AI suite to OC to 4150 mhz on cpu and still having the monitoring software used on my old intel cpu and board). In the meantime, I went to pc-parts picker and plugged in my build parts to find compatible RAM. I found the Corsair Vengeance LPX 3200M specifically saying AMD optimized right here on the box as opposed to the other suggested compatible RAM not even saying AMD optimized. So for obvious reasons , I went with that. It was only after I installed this RAM that I began experiencing this exact random blackscreen issue described here. I firmly believe the RAM change is just a coincidence and surely could not be the issue, but I just reinstalled the old hyper X 2400m RAM today and my system already feels more stable. Is this all in my head? It just doesn't make sense.
I think the Memory Controller on Ryzen 2000 series and below are "sub optimal"
See: Asus ROG Crosshair Hero VII, Ryzen 2700x, Corsair Vengeance RGB (Pro) 3200 4x16GB Memtest86 failures...
That link may be of help.
You should have saved yourself a massive headache and just gone for a Ryzen 3000 series processor.
Another thing to improve stability is remove the AMD GPU and drivers and install an Nvidia GPU.
More background to the above link: