Yes, I think I said that above. So faster memory is much more linear in resultant speed and performance for Ryzen/TR/EYPC than Intel BY DESIGN.
Yes, I think I said that above. So faster memory is much more linear in resultant speed and performance for Ryzen/TR/EYPC than Intel BY DESIGN.Inter ccx speed is tied to memory speed.
My U14S mounting kit arrived on Wednesday. I spent yesterday and this morning tinkering with my overclock now that I have proper cooling.
It pains me to say that the VRMs and the heatsinks on the Strix B350-F are complete and utter dog****. Even with an open case and a fan blowing on them directly they are getting overwhelmed by the 1700 at 1.35v. It's a shame because other than that the board is really nice for the price. I imagine this motherboard would be just fine with a Ryzen 3 or 5 but I'm not comfortable pushing my CPU any further.
I ordered an X370 Taichi and a 960 Evo to go with it earlier this afternoon.
Taichi is nicer anyway. B350, while they do overclock they are budget boards. What did you expect? You can't expect a 16 Phase VRM on a budget chipset, and a miracle to go along with it.
1.Update AGESA to 1.0.0.6b. No memory ABL(AGESA Boot Loader) or training changes.
2.Add setup options to select SMART fan temperature source. Change default to monitor external CPU temperature.
PS1. Windows update is available for version P3.00 or later.
Many people have had great success overclocking on B350 based boards; I'm simply sharing my experience with one particular board. As I said in my previous post everything else about the Strix B350-F is great, which is why I picked it. My "mistake" was when I decided at the last minute to go with a 1700 instead of the 1600 as I originally intended. That combination wouldn't of been an issue. Lesson learned.
Yes, the higher-end boards (like the Taichi, hence my reason for choosing it now) have much better components. Obviously. You making ridiculous strawman claims on my behalf is just nonsense, however.
Larry, are you over your medical issues ? or do I have to ban you until you see a doctor ?AGESA 1.0.0.6b? Does that fix the AoTS bug that someone on here was having? Would be nice to find out.
Do you have more information on that? Because I looked around the web and the most I found was with a single user (maybe one other person) hitting up a bunch of forums with the issue. I think that guy thought it was or self came to the solution that it was related to the Linux seg fault crash bug (which no Agesa is going to fix apparently). But honestly I don't know if it is a real problem. Like I said all results came back to the same guy.AGESA 1.0.0.6b? Does that fix the AoTS bug that someone on here was having? Would be nice to find out.
Taichi is nicer anyway. B350, while they do overclock they are budget boards. What did you expect? You can't expect a 16 Phase VRM on a budget chipset, and a miracle to go along with it.
Do you have more information on that? Because I looked around the web and the most I found was with a single user (maybe one other person) hitting up a bunch of forums with the issue. I think that guy thought it was or self came to the solution that it was related to the Linux seg fault crash bug (which no Agesa is going to fix apparently). But honestly I don't know if it is a real problem. Like I said all results came back to the same guy.
The segfault problem is not specific to Linux as it is a hardware flaw. It has been observed under the BSD's and Windows.I think I read post of that guy on reddit. He also said that Shadow of Mordor can crash because segfault bug because in that game is high cpu usage. Is segfault bug only on Linux or it is also on Windows?
The segfault problem is not specific to Linux as it is a hardware flaw. It has been observed under the BSD's and Windows.
As of the last I heard the only well-known method of triggering the flaw under Windows was to run the same sort of compiles that readily trigger the flaw under Linux -- by using the WSL. Note that there is no Linux code in the WSL; it is Windows code.
There may yet be other apps/workloads that are found to trigger this flaw in the future.
I don't know about that. But that one guy is the only really confirmed person to run into it. It's not Linux only but it was the most reliable test. This guy got it to do the same thing on two of his systems when as far as I can tell out of a dozen forums only one person suggested they might have the same issue. So I don't know if it's really worth worrying about either.I think I read post of that guy on reddit. He also said that Shadow of Mordor can crash because segfault bug because in that game is high cpu usage. Is segfault bug only on Linux or it is also on Windows?
Correct it's not a bug that will crash on high workloads or anything else. While there are ways to make the CPU fault in Windows, I think the Linux test was the only one that could be considered an actual workload for the CPU.So no need to RMA the CPU if I only use Windows (I use it for gaming, music, movies, audio/video rendering, web design)?
You know, I wonder if the appcrashes I saw in reliability monitor, for BOINC task applications, were because of this bug? (As they would cause high CPU usage.)I think I read post of that guy on reddit. He also said that Shadow of Mordor can crash because segfault bug because in that game is high cpu usage. Is segfault bug only on Linux or it is also on Windows?
Again, this is a hardware problem. If a new version of some program triggers this problem it won't matter what OS you are running.So no need to RMA the CPU if I only use Windows (I use it for gaming, music, movies, audio/video rendering, web design)?
Again, this is a hardware problem. If a new version of some program triggers this problem it won't matter what OS you are running.
I run Linux and can reproduce the problem several times per hour by compiling the Linux kernel using all 12 threads. After disabling ASLR I have not been able to trigger the problem again after about 10 hours of the tests that previously caused it.
My advice would be to RMA it if you don't want to live with the risk of being unable to RMA it later.
As for me, I'm in the (presumed) same position as you; I see no glitches, code failures, or crashes. My system is rock solid and nothing fails. However, I know that that might change tomorrow with some new program, release, or just a change in my workload. I don't care. I have spare machines capable of doing everything I need -- and I intend to replace this chip when the first substantial upgrade comes out anyway.
My guess would be that the worst case scenario for you is the very low probility of a short downtime or process interruption and maybe even the price of a new chip. That risk-adjusted price is low enough for me to ignore -- and probably for you too.
Judging my the patterns of known examples, I'd *guess* that you'd be most likely to see an application crash. In theory, of course, it could be *any* program -- even the OS -- but that seems highly unlikely since applications generate the vast majority of the load.OK thank you. One more question: If by any chance I run at that error on Windows, how will I know it, will it cause system to crash, freeze, restart or something?
Just build a asus b350m-k with a 1600x for one of the kids.
With new bios from august the corsair lpx 3000 2x8 booted at xmp settings 2933. All fine.
I would say those asus b350 is 100% ready now.
Use my 1700 stock cooler. Goes fine for gaming at stock freq.
Fantatic cheap and powerfull cpu for 144 1440 gaming in games like overwatch and bf1 using a rx56.
Pubg runs like crap. If anyone knows how to fix that let me know.
How did you get it to sit on AM4 socket? DId you have to make your own mounting bracket?For those of you who might remember this cooler from 2007, my Scythe Ninja Plus is currently happily cooling a 1600X, ten years after the revision was launched.