So this is a pretty strange situation. And my root question to you experts is:
Is this really a memory OC issue or something else?
Let me preface this explanation with the fact that I am not much of an over-clocker. I've built quite a few systems, but never delved into the dark world of OC and while I understand basic/intermediate hardware specs, the minutiae of RAM timings and all the various tweakable OC BIOS settings eludes me.
I didn't plan to get into OC with this new build I am doing. I purchased the following:
- AMD Ryzen 3 2200G
- ASRock AB350 Pro4 ATX mobo
- G.SKILL F4-2666C15D-8GVR (DDR4 2666\Timing 15-15-15-35\CAS Latency 15\Voltage 1.2V)
What I didn't know (didn't even know to check) is that the RAM apparently has an SPD speed of 2133MHz and a "tested" speed of 2666 (this spec wasn't advertised on Newegg).
I'm not sure yet if this is true of ALL DDR4 ram? But it seems pretty disingenuous to advertise it at just a "tested" speed if those speed profiles won't definitively work on a system.
All that aside (though feel free to enlighten me more here if you see fit), here is the issue:
I loaded Windows 2016 Server (all tests I mention were also done with Windows 10 x64) and everything works fine for basic OS setup. Install some updates, tweak a few OS parameters, etc... just testing out the build. I realize then that the RAM speeds are showing as 2133 in CPU-Z and in my BIOS. I do a little research and find my BIOS XMP profile settings and change it to the one profile and the 2666 speed. I boot up again and all looks good. BIOS, CPU-Z and windows wmic commands all show the speed at 2666.
I then realize I don't have the Ryzen Vega display driver installed, so I install it (I've tried numerous versions from AMD and ASRock).
Screen goes black. Monitor still gets signal, but OS is apparently crashed (can tell this from no remote access/ping).
After messing around I have definitively determined that this only happens when my RAM is set about 2400.
2133 works. 2400 works. 2666 no go.
If I try a new OS load with RAM set to 2666 then I get the black screen crash during driver install I mention. If I do the configuration with RAM set to 2133 then everything works, but when I switch back to 2666 I get the Windows logon screen for about 2-3 seconds on boot and then it crashes black again in the same way.
What gets me (again - admittedly not a lot of OC experience) is why would setting the RAM to 2666 affect the system in this very strangely specific way?
I should also mention I ran 4 passes (default) of the Passmark memtest86 app against my system running at 2666 and there were absolutely no errors.
I can also seemingly run Windows without any issue (did not do any extensive stress testing).
The issue only happens when I try to install/load the Ryzen Display driver.
I've been posting around trying to explain the situation and ask questions appropriate to the forum I'm in.
I'm really at a loss.
People have been telling me:
- Forget the XMP profile and do all the settings yourself: I've tried some basic things I could gleam from comments, but I really am at a loss as to how to manually tweak all the settings myself. The few things I have done (voltage, some basic timings) don't seem to make a difference.
- The CPU may be bad: I suppose this is possible, but why would it work fine at 2133.
I've gone ahead and ordered a replacement Ryzen as well as Different RAM that is actually listed on the QVL (PV48G300C6K).
The ASRock QVL is horrible as they don't list a lot of RAM that is available and it seems full of errors/inconsistencies (like they say they only test 2 sticks from what looks like a 4 stick set, etc). Plus from a lot of what I read (and past experience) almost any RAM will work as long as it falls within spec.
Anyway - that's my story. Hopefully one of these new components fixes the issue - but I'd still like to understand what is going on.
I suppose it could be the MoBo as well - but I've already RMA'd it twice in the first week and hoping I don't need to do that all again.
Any thoughts/ideas?
Thanks
Is this really a memory OC issue or something else?
Let me preface this explanation with the fact that I am not much of an over-clocker. I've built quite a few systems, but never delved into the dark world of OC and while I understand basic/intermediate hardware specs, the minutiae of RAM timings and all the various tweakable OC BIOS settings eludes me.
I didn't plan to get into OC with this new build I am doing. I purchased the following:
- AMD Ryzen 3 2200G
- ASRock AB350 Pro4 ATX mobo
- G.SKILL F4-2666C15D-8GVR (DDR4 2666\Timing 15-15-15-35\CAS Latency 15\Voltage 1.2V)
What I didn't know (didn't even know to check) is that the RAM apparently has an SPD speed of 2133MHz and a "tested" speed of 2666 (this spec wasn't advertised on Newegg).
I'm not sure yet if this is true of ALL DDR4 ram? But it seems pretty disingenuous to advertise it at just a "tested" speed if those speed profiles won't definitively work on a system.
All that aside (though feel free to enlighten me more here if you see fit), here is the issue:
I loaded Windows 2016 Server (all tests I mention were also done with Windows 10 x64) and everything works fine for basic OS setup. Install some updates, tweak a few OS parameters, etc... just testing out the build. I realize then that the RAM speeds are showing as 2133 in CPU-Z and in my BIOS. I do a little research and find my BIOS XMP profile settings and change it to the one profile and the 2666 speed. I boot up again and all looks good. BIOS, CPU-Z and windows wmic commands all show the speed at 2666.
I then realize I don't have the Ryzen Vega display driver installed, so I install it (I've tried numerous versions from AMD and ASRock).
Screen goes black. Monitor still gets signal, but OS is apparently crashed (can tell this from no remote access/ping).
After messing around I have definitively determined that this only happens when my RAM is set about 2400.
2133 works. 2400 works. 2666 no go.
If I try a new OS load with RAM set to 2666 then I get the black screen crash during driver install I mention. If I do the configuration with RAM set to 2133 then everything works, but when I switch back to 2666 I get the Windows logon screen for about 2-3 seconds on boot and then it crashes black again in the same way.
What gets me (again - admittedly not a lot of OC experience) is why would setting the RAM to 2666 affect the system in this very strangely specific way?
I should also mention I ran 4 passes (default) of the Passmark memtest86 app against my system running at 2666 and there were absolutely no errors.
I can also seemingly run Windows without any issue (did not do any extensive stress testing).
The issue only happens when I try to install/load the Ryzen Display driver.
I've been posting around trying to explain the situation and ask questions appropriate to the forum I'm in.
I'm really at a loss.
People have been telling me:
- Forget the XMP profile and do all the settings yourself: I've tried some basic things I could gleam from comments, but I really am at a loss as to how to manually tweak all the settings myself. The few things I have done (voltage, some basic timings) don't seem to make a difference.
- The CPU may be bad: I suppose this is possible, but why would it work fine at 2133.
I've gone ahead and ordered a replacement Ryzen as well as Different RAM that is actually listed on the QVL (PV48G300C6K).
The ASRock QVL is horrible as they don't list a lot of RAM that is available and it seems full of errors/inconsistencies (like they say they only test 2 sticks from what looks like a 4 stick set, etc). Plus from a lot of what I read (and past experience) almost any RAM will work as long as it falls within spec.
Anyway - that's my story. Hopefully one of these new components fixes the issue - but I'd still like to understand what is going on.
I suppose it could be the MoBo as well - but I've already RMA'd it twice in the first week and hoping I don't need to do that all again.
Any thoughts/ideas?
Thanks