Ok, A long time intel user that has switched to AMD with Gigabyte Extreme X570 board with 5950X and 32g DDR3600 memory. all water cooled with a dual 480 rads dual pump system. also using a 8Pack 2000w PSU. Power is not an issue.
I have built PC's for many years since the old athlon days and P2 systems. My last system before the 5950x was a 9900k which sat at 5ghz all core for a year with out 1 error. I waited for the ryzan 5950x as it promised so much.
So i purchase the above and build my system, all i am waiting for is the 5950x on launch day. I manage to snag one and after flashing bios i install the 5950x and WAM my troubles begin. I have used every bios gigabyte have issued but none of them have cured the WHEA error's. Some bios have been better but never 100% stable. for 1 month plus i have tried to get the system stable and have spent many hours reading all the forums and posts on this issue to which i might add there are many.
I have tried 4 sets of memory, 2 stick 4 stick combo's and all this memory worked fine in an intel system. I even swapped out another 5950x from a friend which turned out worse than my first one on infinity fabric, Flck was worse. I have spent far to long on this system. It should be plug and play with out issue's. both CPU's should be able to run the same but this was not the case. One could reach DDR3600 speed the other could not. with out rebooting quite often on the exact same settings as the other 5950x. this alone proves to me its a silicone lottery to get a CPU to run at advertised speeds alone. they are obviously not being tested properly at there advertised speeds.
So i am at the crossroads that i will RMA my 5950x and M/B for a refund and go back to intel, yes it might be slower for encoding and work flow but at least it will be stable. Its a shame AMD cant offer any resolution's for this issue. either bad silicone which if thats the case to many CPU's have got through with out checking they actually run as advertised.
If its a chipset M/B issue then AMD should have the supplier's of M/B's sorted after 6 weeks. business user's cant wait for poor AMD support as AMD rely on board makers to provide the platforms for there CPU's and as a business user i cant put any more time into a Flaky unstable combination of M/B and CPU.
For AMD i feel its either time to be honest and say you have some bad silicone out there or FIX the issue with board makers as the problems are wide spread and any company looking to upgrade or replace computer systems that look into AMD ryzen as an option will come across all the issues people are having. Company's do not need unstable systems even if when working are faster.
So after a 6 week period of trying and spending many many hours i have to say good bye to AMD systems as far as my work place and home PC is concerned. the CPU's are just to inconsistent and have issue's that internet forums are full of.
So in the end its been an expensive waste of time and money on water blocks for AMD cpu's but i live and learn and i will now build me an intel system as i have done many times with out issue with WHEA error's.
I have asked about this and forwarded a link to this post to Gamers Nexus, OC3D, Hardware Canucks, TechPowerUp, AMD Ryzen, Gigabyte.
You never know, might get a reply.
Sad to hear about your experience that unfortunately goes to show how unreliable those are (and why amd don't seem to have any spares available anymore already ...)
Had a quite similar experience where I struggled with same issues (5950x on MSI motherboard) for a week before the cpu just flat lined and had to go through RMA .
Looks like these issues are indeed widespread on this line of CPU wich is very bad for a flagship, and never seen that many issues since my first PC build either and i've done quite a few ones on both Intel, AMD and even Cyrix since the days when 486 were considered powerful beasts ...
I wouldn't blame only AMD there tho, as considering the unusual quantity of orders TSMC got all of a sudden (Zen3, PS5/Xbox/ Professional line of Nvidia Ampere GPUs ...) , it seems very likely that they're the ones not fully testing/pushing faulty CPU to be able to deliver on promised numbers whilst possibly not having enough capacity/mastering over the 7nm process. Still, AMD should acknowledge the issue and setup a proper QA line before they send them out ...
But as someone pointed out in another thread, AMD will only look at it when it shows on their revenue, so all we can do is vote with our dollars and take our business to someone else it seems :\
I have sent many of the WHEA links to Steve Burke also. I really hope he looks into it. It is going to take a Steve or Linus to shed light on this issue I think.
It worked to get the Radeon Drivers improved.
The only way I see any AMD technical support folk on a thread is if someone starts fighting.
How about it Pokester.
Only joking ...
I think my fighting days are very much behind me. LOL
I'm just glad when I realize I am still breathing in the morning.
found several threads this December with others Users having the same errors after having BSODs using the 5950x processor.
Either it is a bad batch during the manufacturing process or there is a defect in engineering design causing the WHEA errors and BSODs.
Possibly it could be a conflict with another 3rd party software running in the background.
Try booting into a Clean Windows environment and see if the WHEA errors occurs. If it doesn't then you know it is a 3rd party software possibly running in the background causing conflict.
Basically booting into a Clean Windows desktop is disabling all 3rd party programs except Microsoft. Including its services.
I have done that. I got the BSOD and random reboot on a clean install prior to installing any drivers.
Something is definitely wrong with either the BIOS, Chipset Drivers, or the CPU itself. Its time to be vocal about this as more people are reporting their frustrations online.
At the tech website Sysnative.com one of the MS experts on BSOD mentioned that if you do clean install without installing any 3rd party drivers and the PC crashes it generally indicates a hardware issue.
I would RMA the processor and see if that fixes your problem since others with similar errors and BSODs all have different Computer setups except using AMD 5xxx series CPUs.
Either way Good luck.