Joined
·
5,972 Posts
Did he get lucky though?Yea you got lucky. It all comes down to do you wanna roll the dice on a 4-500 dollar purchase
Did he get lucky though?Yea you got lucky. It all comes down to do you wanna roll the dice on a 4-500 dollar purchase
Two ryzen 5000 CPUs no whea errors and I guarantee you gtz overclocked his memory and fclk. He's in the x299 thread overclocking multiple 7000x CPUs and memory lol.Did he get lucky though?
I really truly think it is an issue with motherboards and not CPUs. This is just regarding the WHEA issues, I never experienced the USB disconnect issues.Well I spent all day yesterday tweaking the system, and I can say system is error free. The biggest culprit was my BCLK clock (even though it was only 100, but more on that later).
This should apply to all Gigabyte boards, even though I was not crashing by buddy with the same board (his is the WiFi version) and CPU was.
Like I mentioned above, I always set my BCLK clock manually to 100. But whenever you set it manually the option for Spread Spectrum disappears, according to Gigabyte it should automatically disable. Well turns out it does not, if I leave BCLK on auto and then disable spread spectrum this resolved 40 percent of my issues. This was not found out until the very end when I just started messing with BIOS settings to see what worked (thank god for save profiles). I think modern platforms have spoiled us, because everything just runs smoother. It's not like the good ole 775 days where you had memory holes and needed certain straps to be stable. Or my old P5n-SLI board being quirky as hell with my Q6600 that I had to resort to a special BIOS just to run stable at the 333 strap (1333FSB/667DDR2). So in essence we have become lazy because boom we either just adjust the multi and voltage or enable PBO. I think that's why I enjoy RAM overclocking and tweaking as well.
Since I did not figure out the above I was pulling my hairs out to get zero errors. First issue I tackled was the SOC volts, this board with XMP enabled defaults to .995. It was never an issue because it never crashed. With my original settings (listed in the original post), I would get 230 errors with the following tests. Start up, play doom eternal for 10min, loop CB20 for 10mins, and then 10 more minutes of general usage. 230 errors and I stopped it at that, if I would have kept it open it would be higher because it would error in idling. With 1.15 SOC volts my errors dropped to 130 errors with the test mentioned above. I upped the SOC voltage pass 1.2 but gave me the same errors so I worked back down to 1.145 and that resulted in the same errors as a voltage of 1.25. I adjusted VDDP to .920 and VDDIO and VDDG to .945 (this setting voltage moved automatically). With final voltages tuned I got 90 errors.
90 errors, this is where I was pulling my hair. Started tweaking memory at this points but this resulted in more errors, with me tuned DJR running 3800CL16 I got less errors than with running stock XMP at 3600. What I find weird is 3800CL16 (IF ran 1:1 in all test) ran better and less errors than 3533-3733 and gave me the same errors running 3266-3466. At 3200 all errors disappeared, but I should have paid better attention, at 3200 even though I had BCLK at 100 it was 100. Every other strap was 99.6-99.9, this should have been a dead giveaway spread spectrum was doing its thing. Memory speeds 2400-2933 gave me same amount of errors. 2133-2400 error free and again bclk stuck 100. It was here that I finally decided to look into the BCLK jumping around even though it was set to 100 and spread spectrum should have been disabled.
With BCLK left on auto and spread spectrum disabled left me with a BCLK at 100. With this little change and 3800/1900, 10 WHEA errors. Now 10 errors I was excited, so know all I did was disable PBO and my lovely +150mhz and boom zero errors!!! Even with PBO disabled I still get my 4600 all cores and 4.85 single core boosts, so I am still happy. According to AMD and Gigabyte AGESA 1.1.8.0 and beyond should fix that (hopefully 4000/2000IF).
Just want to remind everybody, even though I had a crap ton of WHEA errors I was still apparently stable.
There are constant restocks at B&H or you are lucky and hit some of the super deals. I have an deal to sell my 5800X at cost it takes to buy an 5600x in CanadaWell if your fear of an issue is that great. It might be best not to buy. Simply because if you end up being that 1 or 2% you will not be happy. Personally if I could actually find a 5800X at retail... it would be mine.
Get into the StockDrops discord and sign up for 5800X. They helped me get mine + 3 months of xbox game pass for $480 (ANTonline).Well if your fear of an issue is that great. It might be best not to buy. Simply because if you end up being that 1 or 2% you will not be happy. Personally if I could actually find a 5800X at retail... it would be mine.
The one I sold with no errors was 2044 aswell.Don't buy online, head to the shops and find an early manufacturing code.
Mine is 2040SUS and runs like a champ, 2000 and 2033 IF stable and WHEA free.
If you check the online reviews you will notice all reviewers are using 2036SUS chips so I figured AMD would send them handpicked chips and looked for something similar.
I've also tested a 2044SUS which has no WHEA issues.
My friend has a 2046SUS with no errors.The one I sold with no errors was 2044 aswell.
this isn't like a permanent thing or 2..this depends on silicon quality and how stable you can clock higher on IF Clocks and Memory clock..I haven't got 1 since owning and recently upgrading from a 5800x to a 5900x..my 5900x is in fact better in terms of silicon quality as I can tune down the previous voltages the 5800x was using..and no WHEA logger errors on event viewer..No one can really answer that as there are thousands with the whea errors and fclk issues. And that's only reported problems. Not the ones that are just flat out returning units
Interesting. I can only run my intel ddr4 4000 bdie samsung at 3733 stable. Its really unstable though still need to spend more time tweaking itMost definitely not worth the upgrade.
I've got all of the 5000 series chips and I haven't seen any issues at all, but I am primarily using them for extreme overclocking and not much 'daily' type of usage. As for fabric, out of the 7 chip's I've tested, only one of them will not do 1900. Most of them will do above 1900 and up to 2100, but there are major issues such as performance degradation above 1900. If you keep FCLK between 1800-1900, then I can say with some confidence you wont experience issues.
I wouldn't upgrade, it's just not worth it unless you are doing extensive CPU heavy workloads like 3D rendering or parametric modeling for your job.
If you're increasing voltages, try lowering. Especially SOC and VDDx. I was very unstable at 1.1 SOC. 1.050 SOC cleaned it all up.Interesting. I can only run my intel ddr4 4000 bdie samsung at 3733 stable. Its really unstable though still need to spend more time tweaking it
Thanks. Got to tinker some more.If you're increasing voltages, try lowering. Especially SOC and VDDx. I was very unstable at 1.1 SOC. 1.050 SOC cleaned it all up.
Have you been able to test this CPU in a different motherboard to see if the WHEA free frequency range stays the same and if it stays WHEA free ??Don't buy online, head to the shops and find an early manufacturing code.
Mine is 2040SUS and runs like a champ, 2000 and 2033 IF stable and WHEA free.
If you check the online reviews you will notice all reviewers are using 2036SUS chips so I figured AMD would send them handpicked chips and looked for something similar.
I've also tested a 2044SUS which has no WHEA issues.
Not tested my 5800X on any other board.Have you been able to test this CPU in a different motherboard to see if the WHEA free frequency range stays the same and if it stays WHEA free ??
As I am thinking this issue is cause by boarderline "sync" issues between specific CPU and motherboard combo.
When I say combo, I dont mean the actually motherboard model, CPU model, but the specific motherboard/CPU combo.
Seeing Cidious has already posted info where same CPU works differently on different motherboard etc.
Really, really hoping they manage to tie this issue down so we at least get CPUs that produce consistent results.
I.e. my current CPU WHEA posting range changes day by day!
Sometime 2033/2066 post fine, sometimes 2033 goes funky, at the same time when 2033 goes funky a previous unpostable FCLK frequency, 1966, is able to post !!
Thats why I think there is a sync issue somewhere ....
Pure conjecture. You have no reason to even comment as you just are parroting what you have "heard". A few people have memory related issues and suddenly the cpu is no good? Come on.Care to explain the stock whea errors? In all reality it's bad CPUs+ bad bios firmware implication on amds part.
I have zero idea when it's gonna be fixed as I personally down own a ryzen system just going off of what I read.
Rofl so the huge thread on here is bs?Pure conjecture. You have no reason to even comment as you just are parroting what you have "heard". A few people have memory related issues and suddenly the cpu is no good? Come on.