![]() So if you have more than 1 rank in channel and run it on higher frequency (aka more than Zen 3 specced 3200) it becomes much taxing on memory controller. And with more things to pay attention for, less attention averaged you can pay to one rank. Why it matters? Because memory controller can ask only 1 side of 1 stick at once, so they need to switch "attention". Simply speaking it means how many sides on RAM stick is populated, 1 or 2. Memory rank is related to RAM sticks themselves. If it have 4 slots, then it is 1-1 2-2 if looking right on it, and usually marked as A2 A1 B2 B1 in motherboard instruction if it is 2 slots, then each one have own channel. It related to different slots on motherboard. Ryzen Zen 2 and Zen 3 memory controller have tougher time dealing with anything except 2x1R from getgo if you are not lucky, so with 2x2R or higher there may be hard times booting into system on RAM clocks higher than 3200 (and for 4x2R it may be even lower) without turning on 2T or GDM (in order of increasing stability 2T -> GDM)Īlso, don't mix up RAM being dual-channel and being dual-ranked.Ģ channels mean that CPU memory controller is basically split by half, and each half works independently to reduce data latency and starvation by being able to alternate channels. While 2x2R have higher chance to get issues from getgo, but easier to work with in terms of overclocking. 4x1R usually have harder time clocking higher or getting tighter timings, because almost every mobo on market use daisy-chain RAM setup. In order of increasing potential stability issuesīut between 2x2R and 4x1R there are different issues. You can use 2x 1R sticks (usually 2x4 or 2x8), 2x2R (can be either 2x8 or 2x16 as you have, or, maybe even 2x32 ), 4x1R (4x8 sticks) and 4x2R (4x16 or 4x32 sticks). I had it on "Auto" so I changed to 1t because of two RAM sticks." "I checked in BIOS to see what I had in DRAM Controller Configuration in AMD CBS and AMD Overclocking - 1t or 2t. Maybe you had 3600 1T with quad rank setup. Nah, just boot in system with original setup (XMP and auto) and send Zentimings output as you did before with 2133 default. I heard that this crash can happen because of CPU idle voltage. Same with VSoc and Differential field changed to +.006 volts. Look - I set VCore to Normal and set voltage in the Differential field to +.006 volts. I found the last solution I never tried before so I did that. power supply iddle control -> typical current idleĤ. PSS support/AMD Cool n Quiet -> disabled I disabled "fast startup", reinstalled GPU drivers, updated every single driver. I tried checking health of all components that can be tested and I never get even a single problem or damage.Ģ. It can handle stress-tests from various programs easily, nothing bad happening when doing that. My PC, except this one issue, is working fine, with good temperatures, no overheating. Let me tell you ALL I tried and all I know.ġ. I tried almost everything, almost every method with no effect. It mostly depends on how advanced is specific game (for example, Dirt Rally 2.0 is crashing often than Dying Light). Sometimes I can have "safe" month or two, sometimes I get couple of crashes in one day. ![]() Here is the full spec:ĪMD Ryzen 5 3600X 6-Core Processor (12 CPUs), ~3.8GHzĢx GOODRAM 16GB (1x16GB) 3600MHz CL17 IRDM PRĬrashes happen only in games and they are pure random. Some infos about my setup, the rest is in the log down below.I have this, as I saw, common problem with WHEA logger 18 crash on my PC. ![]() I think have updated all plugins and the log analyzer of OBS gives neither critical messages nor warnings. But that hasn't really been a problem so far. Yes, I have many scenes that are also nested, with many browser sources. I only got this problem with OBS 28, before that it never happened. I get sound problems in individual sources (it sounds stuttery, like the sound can't be processed fast enough) and after a few more minutes OBS sometimes crashes. Which is really weird, since I'm coding over the GPU. But after about 10 minutes of streaming, the CPU utilization goes up to 35% and sometimes 40%. About 6% CPU utilization without stream, about 11% with stream. When I start OBS, the CPU and GPU utilization values are completely within limits.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |