• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Ryzen 5000 crashes - anyone getting them?

I’ve seen zero faults with 5000 series CPUs and I come into contact with a lot more than most people and in many configurations.

@Journey Are you seeing many problems with Ryzen systems?

A lot of reports on the MSI and AMD forums, Reddit and some other Forums. Different RAM brands, number os sticks etc.

Here it's one trying to centralise the discussion:
https://www.reddit.com/r/AMDHelp/comments/kfyst7/random_bsods_with_amd_5000_series_processor/

He links to 18 threads about the same issue there too.
 
Last edited:
A lot of reports on the MSI and AMD forums, Reddit and some other Forums. Different RAM brands, number os sticks etc.

I’d just start randomly returning parts. Start with the CPU if you think its faulty. I’m 99% sure the CPU isn’t the issue, but you seem reluctant to find out.
 
A lot of reports on the MSI and AMD forums, Reddit and some other Forums. Different RAM brands, number os sticks etc.

Here it's one trying to centralise the discussion:
https://www.reddit.com/r/AMDHelp/comments/kfyst7/random_bsods_with_amd_5000_series_processor/

He links to 18 threads about the same issue there too.

Pretty sure it's power delivery related, since mine has had a BIOS update the issue has gone entirely, however the voltages are behaving differently as reported by HWINFO. It would jump to 1.225v ish under boost conditions, now it seems to happily be hitting 1.31v. Idle is now just shy of 1.0v, before it was around 0.9v, even dipping to the high 0.8's.
 
Pretty sure it's power delivery related, since mine has had a BIOS update the issue has gone entirely, however the voltages are behaving differently as reported by HWINFO. It would jump to 1.225v ish under boost conditions, now it seems to happily be hitting 1.31v. Idle is now just shy of 1.0v, before it was around 0.9v, even dipping to the high 0.8's.

Did you just updated the BIOS or did you do something else too? Are you using an MSI motherboard too? I have started with BIOS 7C84v14 (my pendrive was with the file ready waiting before the new version came out) and then flashed to the latest 7C84v15 after encountering the issues.
 
A lot of reports on the MSI and AMD forums, Reddit and some other Forums. Different RAM brands, number os sticks etc.

Here it's one trying to centralise the discussion:
https://www.reddit.com/r/AMDHelp/comments/kfyst7/random_bsods_with_amd_5000_series_processor/

He links to 18 threads about the same issue there too.

18 threads?

@Grim5 - more evidence for you of this worrying trend.

I hope all these issues with Ryzen 5000 get cleared up for the owners ASAP, it's simply not acceptable this long after release.
 
18 threads?

@Grim5 - more evidence for you of this worrying trend.

I hope all these issues with Ryzen 5000 get cleared up for the owners ASAP, it's simply not acceptable this long after release.
More trolling dave why oh why have you just quoted someones post you must spend all your time looking for faults on amd processors no input into help these people with the problems just your usual excuse to have a go at amd its rather boring mate as posted earlier some of the issues are software related not all of them though
 
If that was the issue, shouldn't resetting CMOS and using two sticks without enabling XMP work? I still get the same errors. Can't WHEA errors happen just because of the CPU? Why people having the same issue are reporting they fixed the issue by replacing just the chip, then?
No one is telling not to do anything. Everyone is making suggestion. At the end of the day you are the person sitting there with the hardware and you along are able to diagnose this effectively.

most WHEA issue is vcore isn’t set right via earlier bios release (AGESA 1.0.8.0 to 1.1.9). With AGESA 1.2 it is all sorted. Then any remaining WHEA is overclocking or ram setup issues.

if you feel RMA cpu is the way to go then do it. You don’t need to ask internet for permission and certainly don’t get all passive aggressive over people that is helping you. That is one sure way to make your way onto ignore list and you better start another account in the future as people won’t be so helpful again.

over and out.
 
More trolling dave why oh why have you just quoted someones post you must spend all your time looking for faults on amd processors no input into help these people with the problems just your usual excuse to have a go at amd its rather boring mate as posted earlier some of the issues are software related not all of them though

Ignore function is handy for pish spouters :)
 
No one is telling not to do anything. Everyone is making suggestion. At the end of the day you are the person sitting there with the hardware and you along are able to diagnose this effectively.

most WHEA issue is vcore isn’t set right via earlier bios release (AGESA 1.0.8.0 to 1.1.9). With AGESA 1.2 it is all sorted. Then any remaining WHEA is overclocking or ram setup issues.

if you feel RMA cpu is the way to go then do it. You don’t need to ask internet for permission and certainly don’t get all passive aggressive over people that is helping you. That is one sure way to make your way onto ignore list and you better start another account in the future as people won’t be so helpful again.

over and out.

Those were genuine questions, not passive-aggressive. You see, what I have been trying to say is that I didn't overclock anything and the issues are there no matter if I have all the mem sticks, two sticks, XMP disabled or enabled.

The RAM is on the QVL of the motherboard so it should work properly when you update BIOS/reset cmos without enabling changing anything and with XMP disabled.
It's not that I don't want to believe all the experience everyone else has/had, it's just that I did test/re-sitted/removed/added sticks and the issues were still there.

Maybe a lot of the times RAM is to blame, but testing different combinations is not working. Maybe a lot of the times the CPU is working 100%, but the issues me and other users are experiencing is pointing to another direction. Maybe the next MSI BIOS update can sort it out, I don't know.

But anyway, thanks everyone for helping out.
 
18 threads?

@Grim5 - more evidence for you of this worrying trend.

I hope all these issues with Ryzen 5000 get cleared up for the owners ASAP, it's simply not acceptable this long after release.


Oh I don't care haha - all Ryzen CPUs has been stable for me, it's the Intel 860 and 4790k that gave me crashes
 
5600x here with dirt cheap 4x8gb HyperX RGB memory.

I had a one issue with my hard drives not working or being detected at all, following a BIOS update. I re-seated the CPU, made sure the motherboard and CPU weren't contaminated with anything (like excess thermal paste) put it back together and it's not crashed yet. Been running it through the wringer with Prime95, Cyberpunk and it hasn't crashed yet :)
 
Seems they are failing more than you think :eek:

AMD Ryzen 5000 processor failures: are they really that bad?


https://www.techradar.com/news/amd-ryzen-5000-processor-failures-are-they-really-that-bad


ya'll keep linking to an Intel shillbot twitter account which has already had its tweets deleted

yeah ryzen 5000 has a 20% defective rate cause some random on twitter said so :p:p:p

seriously, use some critical thinking people - hardware unboxed already went and talked to multiple REAL PC STORES who said the defective rate was under 2%

Case closed, next topic!
 
ya'll linking to an Intel shillbot twitter account which has had its tweets deleted

yeah ryzen 5000 has a 20% defective rate cause some random on twitter said so :p:p:p

seriously, use some critical thinking people - hardware unboxed already went and talked to REAL PC STORES who said the defective rate was under 2%

Case closed, next topic!

It’s this guy. Lovely site, just fishing for private data.
https://www.powergpu.com/
 
not surprised it got deleted probably got death threats off all the AMD zealots :p Look how quick the AMD defence force assembled here :eek:

:D But seriously, not sure why everyone is getting upset. The truth will come out regardless, but if everyone wants to row about it then fair play. The OP only asked a reasonable question then things just went backwards, as usual.
 
Back
Top Bottom