Ryzen Owners Zen Garden

[8BitZ80]

I've given up trying to get rid of WHEA errors. It seems like they will pop up every five days or so regardless of BIOS settings. Stock, undervolt, flashing different BIOS versions, it doesn't matter. At least they only happen on resume from sleep and don't seem to affect the system reliability.

 

[tabascosauz]

I've given up trying to get rid of WHEA errors. It seems like they will pop up every five days or so regardless of BIOS settings. Stock, undervolt, flashing different BIOS versions, it doesn't matter. At least they only happen on resume from sleep and don't seem to affect the system reliability.

Are they still the Bus/Interconnect ones? Can't solve those by changing core overclocks, only Cache Hierarchy and a rare one I can't remember are on the cores part. Have you tried cutting down on unnecessary VSOC as well as VDDG CCD and VDDP? Starting to feel that it's a good rule to live by that unless you're aiming at 4000+ or are randomly rebooting, lower VSOC is almost always better. Less is more and all that jazz

 

[8BitZ80]

Are they still the Bus/Interconnect ones? Can't solve those by changing core overclocks, only Cache Hierarchy and a rare one I can't remember are on the cores part. Have you tried cutting down on unnecessary VSOC as well as VDDG CCD and VDDP? Starting to feel that it's a good rule to live by that unless you're aiming at 4000+ or are randomly rebooting, lower VSOC is almost always better. Less is more and all that jazz

It doesn't say, but they don't seem to be core-specific WHEA errors. The SoC voltage according to hwinfo is set at 1.1V, not sure if that's high or low though.

 

[Octopuss]

I've given up trying to get rid of WHEA errors. It seems like they will pop up every five days or so regardless of BIOS settings. Stock, undervolt, flashing different BIOS versions, it doesn't matter. At least they only happen on resume from sleep and don't seem to affect the system reliability.

You should RMA the CPU and/or the board. Unless there are none on default settings of course.
WHEA errors are serious shit.

 

[Mussels]

I've given up trying to get rid of WHEA errors. It seems like they will pop up every five days or so regardless of BIOS settings. Stock, undervolt, flashing different BIOS versions, it doesn't matter. At least they only happen on resume from sleep and don't seem to affect the system reliability.

resume from sleep i would treat as a bug and not a stability issue - cant affect gaming or benching performance if it only occurs waking from sleep

 

[8BitZ80]

resume from sleep i would treat as a bug and not a stability issue - cant affect gaming or benching performance if it only occurs waking from sleep

One thing I did notice is that, at least for the last two WHEA errors I had, they were both reported as the user "LOCAL SERVICE". They happened at different times but both had the same process ID. I checked Task Manager and none of the entries matched that ID number, but that's probably because the system has been restarted since those errors were posted.

Not much to go by but I might try to watch the error logs and catch a WHEA after it happens to see what the associated process is.

You should RMA the CPU and/or the board. Unless there are none on default settings of course.
WHEA errors are serious shit.

I get what you mean but doing an RMA would be such a pain in the ass. If there were unfixable crashing issues I would probably do it though.

 

[PaulieG]

I would test cores individually, because all core boost is always lower than single, thus possibly "hiding" instability with at higher frequencies.

Usually a single core instability will show itself in everyday activities. Once I'm multicore stable, I'll just go about daily tasks with youtube running endlessly for 24 hours. If there are no odd windows errors or reboots then I doubt there is any single core instability after passing a solid multicore stability test.

 

[kapone32]

What the UA batch numbers for these two 3700X's?

Let's face it, 3000 was basically a beta test for AMD's chiplet design (of which Ryzen 5000 is the finished product), and AMD treated its product and us buyers as such. It wouldn't be surprising to start seeing more stability issues with time, from some of the initial lower binned CPUs / harder-worked CPUs. 3600 and 3700X got the worse end of the stick - there were some really bad 3600s and 3700Xs in Q2 2019 and Q3 2019 production - like, 4.0 @ 1.3V bad.

AMD definitely pushed more Vcore through the 3000 chips than 5000. Probably in a bid to try to get the lower quality silicon as close to the "rated boost" as they could get, to avoid a class action lawsuit. I got used to seeing peak Vcore at up to 1.55V every other day on my 3700X for a meagre 4.28GHz effective, no PBO no offset no nothing just bone stock - and the same on 4 different motherboards, no less. The 5900X now peaks at about 1.49-1.5V @ 4.85-4.9GHz effective, stock.



The I/O die says hi and would like to remind that it too is a piece of silicon with finite lifespan in all seriousness, the entirety of my old chip was a [barely] living testament to "if it ain't broke, don't fix it" - read: don't overclock a turd .

So I learned my lesson and not fixing what's not broke is what I'm doing now

You mean the 3300X right?

 

[freeagent]

I don't know.. it does what it is supposed to, 4650 all core @ stock, no PBO. I can add 200MHz with PBO.. its good enough for now.. I'm not really interested in hitting 5ghz on one core or anything like that.

I've given up trying to get rid of WHEA errors. It seems like they will pop up every five days or so regardless of BIOS settings. Stock, undervolt, flashing different BIOS versions, it doesn't matter. At least they only happen on resume from sleep and don't seem to affect the system reliability.

Does that happen under 2000 FCLK?

 

[windwhirl]

AMD Finds a Fix for Ryzen's USB Problems, BIOS Patch Coming in Early April

Plugging in the fix

www.tomshardware.com

If anyone suffered from those issues, a fix may be coming soon-ish.

 

[8BitZ80]

Does that happen under 2000 FCLK?

I just run the standard 3600/1800, it was running 3800/1900 just fine but I went back to standard settings to see where these errors (which haven't gone away) are coming from.

 

[freeagent]

This CPU doesn't like my 4 sticks past 1833 or so.. Sometimes I can fluke it and get it to run 1866 or 1900 but more often than not 1833 is my cap with these 4 sticks. A real bummer since my 3600XT handles them no problem up to 1900/1900. So it spits errors at 1800 for you? If I run my subs too tight at known good speeds and voltages I can get it to error, maybe something in the memory dept is too tight? I suck at subs so I cant really offer any advice there. I see some peoples screen shots and mine would just crash lol.

 

[phanbuey]

are you sure the mobo just doesnt like fastboot? Try disabling that and see if you still get them... I've seen quite a few rigs, intel and AMD throw cache errors on wake / cold fastboot start because of it.

 

[tabascosauz]

You mean the 3300X right?

? Where'd you get 3300X from lol

 

[Mussels]

? Where'd you get 3300X from lol

it was the first single CCX chip, not the 5800x

 

[tabascosauz]

it was the first single CCX chip, not the 5800x

I'm a little confused, I don't think I ever mentioned either the 3300X or 5800X in that post. Probably a misquote somewhere.

It doesn't say, but they don't seem to be core-specific WHEA errors. The SoC voltage according to hwinfo is set at 1.1V, not sure if that's high or low though.

Post up a Zentimings screenie, let's see those minor voltages.

 

[Mussels]

i vaguely remember a comment the single CCX chip being a beta test

i dont care enough to see if it was this thread or not, i just think i understood what he meant

 

[ViperXTR]

AGESA 1.2.0.2 coming to fix the USB issue
https://www.reddit.com/r/Amd/comments/m2wqkf

Sorry, but your post seems to match the mood of your avatar pic >_>
Jokes aside, i have yet to experience these WHEA issues but i see many others experience it as well, for 5600X and 5800X, maybe bad combo of cpu, board and memory perhaps (i also use the exact same 32GB brand speed model and frequency and CL)

 

[Alyjen]

Any of you experienced sound issues? Last week my old but faithfull Sound Blaster Z started acting strange, after 1-2h of Warzone (which is crashing normal computers and for me it haven't crashed once) sound suddenly become distorted, lots of crackling for louder sounds, not so bad for other sounds , simple game restarted fixed the issue.

I did all the usual drivers & other updates, got new Creative Control app (which is pretty nice) and also did some reading one pcie gen4 impact on USB not also other pcie devices like sound cards. Yesterday I had 2h session without any errors. Additionally I ran stress test on CPU & GPU at the same time for an hour and played music in the background, also no issues, no whea errors everything was fine... so yea I wonder if it's AMD or Creative or just bad Warzone update.

 

[freeagent]

No issues here, just using onboard sound right now though.. I got 10 years out of my Auzentech Prelude, which uses creative hardware. Just stopped working after it crashed my computer.. it could be on its way out.. or it could just be the update..

 

[Alyjen]

Yea I don't really want to use onboard, not that I could spot the difference but I use stereo speakers & headset and with Sound Blaster I can switch via them with software I seems small but it's super important feature. Same goes for some usb DACs, it's hard to run speakers & headset & mic at the same time.

 

[freeagent]

Yea I don't really want to use onboard, not that I could spot the difference but I use stereo speakers & headset and with Sound Blaster I can switch via them with software I seems small but it's super important feature. Same goes for some usb DACs, it's hard to run speakers & headset & mic at the same time.

Oh yeah you can do that too. I have headphones and desktop speakers hooked up through the onboard, and then I have my GTX 980 connected to my AVR for a much larger sound

 

[Alyjen]

oh AVR I have in another room now, but this sound very promising in case my SBZ goes down

 

[windwhirl]

I use stereo speakers & headset and with Sound Blaster I can switch via them with software

You can do that with Realtek onboard audio. You just have to configure it to duplicate the audio stream on both outputs (front and rear jacks in my case), IIRC, and then in the volume tray icon you get the choice to swap between headphones and speakers.

 

[Alyjen]

You can do that with Realtek onboard audio. You just have to configure it to duplicate the audio stream on both outputs (front and rear jacks in my case), IIRC, and then in the volume tray icon you get the choice to swap between headphones and speakers.

Thanks! I'll check it. I got used to this way of working when my PC was under TV connected to AVR & headset and if I wanted to switch from AVR to headphones I'd have to get up and walk few steps to plug them in, then I discovered that my Sound Blaster can do it