Print Page | Close Window

Ryzen board, no post

Printed From: ASRock.com
Category: Technical Support
Forum Name: AMD Motherboards
Forum Description: Question about ASRock AMD motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=4589
Printed Date: 22 Dec 2024 at 2:58pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com


Topic: Ryzen board, no post
Posted By: patchfile
Subject: Ryzen board, no post
Date Posted: 12 Mar 2017 at 3:41am
" rel="nofollow - So the wife and I ordered parts from Newegg to build 2 Ryzen computers. We only use Asrock motherboards and Newegg would only let us preorder one of each board so we had to get different boards. Not a big deal, I got the Killer/ac and she got the PRO4.

My parts all got here first and I am up and running with no major issues for the last few days. The PRO4 showed up yesterday and I put her computer together but it would not post.

I spent all day on it. I tried different PSU's, GPU's, RAM. Put My CPU on her board and her CPU on my board, both worked fine on the Killer/ac but nothing worked on the PRO4. At one point I dug out an old motherboard speaker and plugged it in to hear the error codes and was met with silence. I even took everything off the board except the CPU and heatsink and still got no error beeps. Oh well, has to be a bad board, so I got an RMA number and shipped it back to Newegg.

Fast forward to this morning and I get a call from my Brother-in-law who also ordered the same parts as me to build his new gaming rig. He also has the Killer/ac, and he is having the exact same issue as the PRO4, no post, no error beeps, nothing.

I have been doing this for a long time, I built my first computer in 1993 and I build 3 or 4 computers a year for people who depend on me for tech support and gaming information. Having two boards from the same manufacturer both refuse to post or give an error code seems like too much of a coincidence.  

I am wondering if there is some trick to these new Ryzen boards that I am missing. Did we just get super unlucky with two DOA boards? Or am I missing something?

I appreciate any information you can share.



Replies:
Posted By: mgrandy@hotmail.co.u
Date Posted: 12 Mar 2017 at 4:10am
buy a pci diagnostic card £5 it will tell you all. it will post error code. check error code manual hope it dont say no-CPU or the like and then contact the required vendor.


if it dont post boards dead,if it do you get a code to give a bit more info. these check variable amounts of stuff before post if your having issues. 

pros easy to use
        takes mins

cons usually results end up followed by tears in most cases 



-------------
fx 9370 asrock, fatal1ty 970 performance 3.1, NZXT phantom f-atx, AeroCool Integrator 850W, Corsair Hydro Series H100


Posted By: patchfile
Date Posted: 12 Mar 2017 at 4:56am
I will definitely pick one of these up.

But I am still interested if others have seen issues like these on the new Ryzen boards. 


Posted By: Playtoreview
Date Posted: 12 Mar 2017 at 1:51pm
Just registered to post that I am having the same issues. No post. No display. Tried everything. Don't think these boards were ready for a retail release.

Might try to flash it with a bootable USB drive but frustrating and time wasting.


Posted By: patchfile
Date Posted: 12 Mar 2017 at 3:16pm
Thank you for taking the time to join and reply. 

Both boards on my end have been sent back to Newegg for replacement. Good luck flashing yours, let us know if it works.


Posted By: Xaltar
Date Posted: 12 Mar 2017 at 3:32pm
I am afraid I can't help much here as I am still waiting to set up my own Ryzen system. From everything I have read about the webz though it seems RAM is a common issue. If the BIOS revision on the effected boards is an early or prerelease version the board may not be compatible with the RAM being used, even if the same RAM works on another board. It should be easy enough to check the sticker on the RAM for it's version number. Sadly this does not help at all as the only thing you can do is try different RAM until one works then flash the BIOS. It is much simpler and less stressful to just RMA and get a working replacement at this point.

Ryzen launched very suddenly and we have already seen a lot of issues from all board partners regarding compatibility and bugs. Those buying into Ryzen now sadly have to pay the "Early Adopters Tax". EAT, because it eats away at your nerves and often wallet LOL EAT is nothing new but seldom has there been such a new platform on so many levels. New socket, CPU architecture, PCH and all that brings with it. It is certainly an exciting time but early adopters need to be prepared for these kinds of issues.


-------------


Posted By: formula383
Date Posted: 12 Mar 2017 at 4:39pm
" rel="nofollow - Just thought i would add i have a asrock x370 killer sli/ac board and it worked fine out of the box and died only a few hours after use. might be just a corrupt bios idk but looks like i have to rma board as the bios chip looks like it is not removable?? :(


Posted By: Xaltar
Date Posted: 12 Mar 2017 at 4:48pm
No one is using socketed BIOS ROMs anymore, sadly it seems they are no longer being made and existing stocks are insufficient for the demand..... 

-------------


Posted By: patchfile
Date Posted: 13 Mar 2017 at 12:55pm
That really sucks about your Killer/ac. I hope your RMA goes quickly.


Posted By: patchfile
Date Posted: 13 Mar 2017 at 1:00pm
Originally posted by Xaltar Xaltar wrote:

I am afraid I can't help much here as I am still waiting to set up my own Ryzen system. From everything I have read about the webz though it seems RAM is a common issue. If the BIOS revision on the effected boards is an early or prerelease version the board may not be compatible with the RAM being used, even if the same RAM works on another board. It should be easy enough to check the sticker on the RAM for it's version number. Sadly this does not help at all as the only thing you can do is try different RAM until one works then flash the BIOS. It is much simpler and less stressful to just RMA and get a working replacement at this point.

Ryzen launched very suddenly and we have already seen a lot of issues from all board partners regarding compatibility and bugs. Those buying into Ryzen now sadly have to pay the "Early Adopters Tax". EAT, because it eats away at your nerves and often wallet LOL EAT is nothing new but seldom has there been such a new platform on so many levels. New socket, CPU architecture, PCH and all that brings with it. It is certainly an exciting time but early adopters need to be prepared for these kinds of issues.

It has always been my policy to never buy a new platform. It needs to be 6 months old or more so that I avoid the early adopter tax. But this time around it all fell in to place that I either bought Ryzen early, or risk not having the money in a few months. So we bit this time. I really feel sorry for those building their first computer, or the less than tech savvy who just want the latest and greatest.

It is my hope that this thread can be a place for people to learn and hopefully one of us will find a solution.


Posted By: Xaltar
Date Posted: 13 Mar 2017 at 1:10pm
I am the opposite, I love early adoption. For me half the fun is finding fixes and workarounds but I have not been able to get my hands on a Ryzen setup yet Wink 

-------------


Posted By: RyzenWindows7
Date Posted: 14 Mar 2017 at 12:44am
Just registered to post on behalf of my system builder friend. After trying all day yesterday, he got his X370 Killer SLI/ac to post. What he did is :
Shut computer off
Cleared CMOS
took battery out
Left battery out for about 10 seconds
Put battery back in
Turn computer back on 

Still got a black screen, but while thinking it posted about 40 + seconds later

Hopefully this will help

Still has to get USB and SATA DVD player to get recognized

If there's interest reply too this and will keep people informed, will probably be able to have an update today.

By the way he as well as I who also got this board are looking to run Windows 7.


Posted By: RyzenWindows7
Date Posted: 14 Mar 2017 at 12:48am
Booting windows 7 on a sata 6 SSD OCZ windows boots up in less than 12 seconds


Posted By: Xaltar
Date Posted: 14 Mar 2017 at 1:05am
Awesome stuff mate, thanks for sharing your findings Thumbs Up

-------------


Posted By: RyzenWindows7
Date Posted: 14 Mar 2017 at 1:33am
great, thanks,  should have more info today on usb and other drivers


Posted By: patchfile
Date Posted: 14 Mar 2017 at 12:32pm
Originally posted by RyzenWindows7 RyzenWindows7 wrote:

Just registered to post on behalf of my system builder friend. After trying all day yesterday, he got his X370 Killer SLI/ac to post. What he did is :
Shut computer off
Cleared CMOS
took battery out
Left battery out for about 10 seconds
Put battery back in
Turn computer back on 

Still got a black screen, but while thinking it posted about 40 + seconds later

Hopefully this will help

Still has to get USB and SATA DVD player to get recognized

If there's interest reply too this and will keep people informed, will probably be able to have an update today.

By the way he as well as I who also got this board are looking to run Windows 7.

Outstanding. This is exactly what I was hoping for. 


Posted By: wardog
Date Posted: 14 Mar 2017 at 1:34pm
" rel="nofollow - patch, I'm curious. What memory do you have?


Too, if everyone currently here and in the future coming here would please list out your system components.


Posted By: RyzenWindows7
Date Posted: 14 Mar 2017 at 9:36pm
I am at work right now but later so post detail list of all components in the working windows 7 system with Ryzen everything works including all usb posts. Only thing not working is SATA dvd, usb DVD does work. So far very happy, my build will be next I have different components as well


Posted By: patchfile
Date Posted: 15 Mar 2017 at 5:47am
Originally posted by wardog wardog wrote:

" rel="nofollow - patch, I'm curious. What memory do you have?


Too, if everyone currently here and in the future coming here would please list out your system components.

We have G.Skill Ripjaws 2400 (F4-2400C15D-16GVR) 8GB x2
and
Patriot Viper 2133 (PVE48G213C4GY) 8GB x1
 

I was writing out all of the hardware that I have tested in the last week when I realized I did not put the other RAM in my computer, so I shut it all down and tried the Patriot RAM on the Killer/ac. Did not post. But, when I put the G.Skill back in, it booted up just fine.

Just so there is no confusion; I reset the Bios to factory settings before I did this.

The G.skill RAM worked out of the box on my Killer/ac. The Patriot was first tested on the PRO4 that had all of these problems.

The PRO4 was stripped down and rebuilt with all of the components from my computer but never posted. This included a Bios reset before putting the G.Skill RAM on it.

I find it odd that the PRO4 did it's no post thing, and continued to not post no matter what I did. But when I put the Patriot RAM on the Killer/ac it did not post, then putting the G.Skill back in allowed it to work as normal.

Why didn't the PRO4 post with the G.Skill? I am really wishing I had not RMA'd the PRO4. 

But it is looking like the Patriot RAM may be the culprit.


Posted By: wardog
Date Posted: 15 Mar 2017 at 10:49am
" rel="nofollow - Thanks. Interesting.

One thing I notice concerning Ryzen memory is that other than the seemingly req'd CR of 1, CAS, RAS to CAS, and RAS Precharge are all represented by the same cycle/latency.

That G.Skill F4-2400C15D-16GVR kit of yours, while not Ryzen "certified' by G.Skill,, does meet this assumption(exempting the CR2):
F4-2400C15D-16GVR
15  CAS
15 RAS to CAS
15 RAS Precharge
35
2 CR/N/T


Do the G.Skill operate while/with a Command Rate of 1 being forced in the BIOS?



Odd too. That Patriot PVE48G213C4GY stick is 14-14-14-(I can't locate just what CR they are) is assumed to meet Ryzen "specs' but that doesn't necessarily rule out any incompatibility chip wise.

Did you move this one Patriot stick across all 4 slots and still not work/boot?







Posted By: patchfile
Date Posted: 16 Mar 2017 at 4:56pm
Originally posted by wardog wardog wrote:

" rel="nofollow - Thanks. Interesting.

One thing I notice concerning Ryzen memory is that other than the seemingly req'd CR of 1, CAS, RAS to CAS, and RAS Precharge are all represented by the same cycle/latency.

That G.Skill F4-2400C15D-16GVR kit of yours, while not Ryzen "certified' by G.Skill,, does meet this assumption(exempting the CR2):
F4-2400C15D-16GVR
15  CAS
15 RAS to CAS
15 RAS Precharge
35
2 CR/N/T


Do the G.Skill operate while/with a Command Rate of 1 being forced in the BIOS?



Odd too. That Patriot PVE48G213C4GY stick is 14-14-14-(I can't locate just what CR they are) is assumed to meet Ryzen "specs' but that doesn't necessarily rule out any incompatibility chip wise.

Did you move this one Patriot stick across all 4 slots and still not work/boot?

I did try the Patriot in all 4 RAM slots of both boards. I will dig in to the Bios and try CR 1 in the morning.


Posted By: parsec
Date Posted: 16 Mar 2017 at 5:53pm
Originally posted by patchfile patchfile wrote:

" rel="nofollow - So the wife and I ordered parts from Newegg to build 2 Ryzen computers. We only use Asrock motherboards and Newegg would only let us preorder one of each board so we had to get different boards. Not a big deal, I got the Killer/ac and she got the PRO4.

My parts all got here first and I am up and running with no major issues for the last few days. The PRO4 showed up yesterday and I put her computer together but it would not post.

I spent all day on it. I tried different PSU's, GPU's, RAM. Put My CPU on her board and her CPU on my board, both worked fine on the Killer/ac but nothing worked on the PRO4. At one point I dug out an old motherboard speaker and plugged it in to hear the error codes and was met with silence. I even took everything off the board except the CPU and heatsink and still got no error beeps. Oh well, has to be a bad board, so I got an RMA number and shipped it back to Newegg.

Fast forward to this morning and I get a call from my Brother-in-law who also ordered the same parts as me to build his new gaming rig. He also has the Killer/ac, and he is having the exact same issue as the PRO4, no post, no error beeps, nothing.

I have been doing this for a long time, I built my first computer in 1993 and I build 3 or 4 computers a year for people who depend on me for tech support and gaming information. Having two boards from the same manufacturer both refuse to post or give an error code seems like too much of a coincidence.  

I am wondering if there is some trick to these new Ryzen boards that I am missing. Did we just get super unlucky with two DOA boards? Or am I missing something?

I appreciate any information you can share.


Unfortunately, the default setting for the Boot Beep option in the UEFI/BIOS, Boot screen, is Disabled.

So until you can get into the UEFI/BIOS and enable that option, you won't get any beeps from the POST beep speaker. Confused  That is the default setting of the Boot Beep option of every ASRock board's UEFI/BIOS I have used.

That is a choice I don't understand, since having the POST beep speaker enabled when a board is used for the first time would be the most useful. We then have situations like this where the user reacts in the only way they find logical. I want to be clear that I don't blame you in any way.

Memory compatibility as a function of UEFI/BIOS support, which seems to be the case between the two boards (assuming nothing else is wrong, such as bent pins in the CPU socket with Intel systems, that does not apply here) remains a mystery to me. It is also something the user can do nothing about to fix on their own, short of a UEFI/BIOS update. That is, if they are able to do that.

We have struggled with DDR4 memory compatibility with the three earlier DDR4 compatible systems, Intel's X99, and their 100 and 200 series chipset boards. Ryzen systems have initially seemed to be even worse regarding DDR4 memory compatibility. That may really be caused by the existing base of DDR4 products being solely designed for Intel systems. Plus Ryzen is so new, we are still learning its memory compatibility requirements.

The bottom line regarding DDR4 memory is, we must be certain it is compatible with the system we have. When things like this happen, how do we expect users to react?




-------------
http://valid.x86.fr/48rujh" rel="nofollow">


Posted By: silent
Date Posted: 16 Mar 2017 at 11:48pm
Created account to add my problems to the list. First the specs:
AMD Ryzen 7 1800x
Asrock 370 Killer SLI/ac
32GB dominator plat straight off the list at asrock
Dual Geforce GTX 1080's
Creative labs sound card
Water cooling by EK waterblocks
Lamptron fan controller
SATA Blu-Ray
3 - 1TB ssd
EVGA g2 1000w power supply

Problem...everything is installed, but nothing runs. Push power button and the only thing that comes up is a "breathing" red LED surrounding the south bridge. Very frustrated...a lot of money in this system. I tried the clear CMOS, remove battery, etc...didn't work. I've let it sit for an hour hoping the power fairy would fly by. I can't figure out if it's the Pwr Sply or the board.


Posted By: Xaltar
Date Posted: 17 Mar 2017 at 12:00am
Welcome to the Ryzen thread Wink

First up I would strip that thing down and just install 1 gpu, 1 stick of RAM and the CPU. No drives or add in devices. Then before you put power to the PSU clear CMOS. 

That is a hell of a lot of components that could be interfering with post so lets get that down to the bare minimum.

That is going to be a beastly system Thumbs Up


-------------


Posted By: silent
Date Posted: 17 Mar 2017 at 12:10am
OK, 1 RAM stick in A2 in, 1 GPU in, no fans, no SC, no SSDs, nada. Push power and it blinks 5 times then starts breathing. 


Posted By: silent
Date Posted: 17 Mar 2017 at 12:11am
" rel="nofollow - Couls it be the PSU? It came from my old system AMD 990FX Fatality board. I'm lost..and I'm a retired Information technology guru :)


Posted By: Xaltar
Date Posted: 17 Mar 2017 at 12:16am
What is the PSU model and how old is it?

When in doubt, swap it out Tongue

It may also be worth pulling the CMOS battery for 20 mins or so with the system powered off.

Man, I don't miss my days in IT, more headaches than it's worth Ouch Now I scratch the IT itch as a hobby, much more enjoyable. 


-------------


Posted By: silent
Date Posted: 17 Mar 2017 at 12:20am
Bought the pwr sply 2/11/16. It is the EVGA Supernova 1000 G2 gold. With all the stuff I had hooked up, could I have overloaded the psu. I did a v & w count and thought I was safe. 


Posted By: wardog
Date Posted: 17 Mar 2017 at 1:18am
This may or may not apply, depending on from whom or where you purchased the Supernova 1000 G2.

http://www.evga.com/articles/00803/" rel="nofollow - http://www.evga.com/articles/00803/


I post this as I can envision someone offloading a faulty one in a For Sale thread or on an auction site.

Heck, they may or may not have known, only that it, the PSU, was the fault of THEIR issue too.














Posted By: twf85
Date Posted: 17 Mar 2017 at 4:47am
Just wanted to chime in and make sure people who are failing to POST have also unplugged all headers: HD Audio, USB 2.0/3.0.. anything not critical for system function.

I had an issue with a front panel USB3.0/memory card add-in that was giving me hell. I overlooked it as a possible source of the problem, and it took hours of beating my head against the wall before I finally stripped out everything. Booted fine after that.


-------------
https://valid.x86.fr/qc9lr0" rel="nofollow">


Posted By: patchfile
Date Posted: 17 Mar 2017 at 7:56am
Originally posted by twf85 twf85 wrote:

Just wanted to chime in and make sure people who are failing to POST have also unplugged all headers: HD Audio, USB 2.0/3.0.. anything not critical for system function.

I had an issue with a front panel USB3.0/memory card add-in that was giving me hell. I overlooked it as a possible source of the problem, and it took hours of beating my head against the wall before I finally stripped out everything. Booted fine after that.

This is a very good point. 

I did remove all headers and used a flat head screwdriver to short the power button connector to power the motherboard on. I do NOT recommend this method, it is dangerous for your motherboard and components. You can permanently damage them if you are not extremely careful.


Posted By: patchfile
Date Posted: 17 Mar 2017 at 8:02am
Originally posted by silent silent wrote:

Created account to add my problems to the list. First the specs:
AMD Ryzen 7 1800x
Asrock 370 Killer SLI/ac
32GB dominator plat straight off the list at asrock
Dual Geforce GTX 1080's
Creative labs sound card
Water cooling by EK waterblocks
Lamptron fan controller
SATA Blu-Ray
3 - 1TB ssd
EVGA g2 1000w power supply

Problem...everything is installed, but nothing runs. Push power button and the only thing that comes up is a "breathing" red LED surrounding the south bridge. Very frustrated...a lot of money in this system. I tried the clear CMOS, remove battery, etc...didn't work. I've let it sit for an hour hoping the power fairy would fly by. I can't figure out if it's the Pwr Sply or the board.

Mine powered up. All the fans came on, the HDD's spun up and even the DVD player made that clicking noise. Just nothing was making it to the monitor.

Your issue sounds like a PSU problem. As others have already mentioned. 



Posted By: wardog
Date Posted: 17 Mar 2017 at 8:02am
Originally posted by twf85 twf85 wrote:

I had an issue with a front panel USB3.0/memory card add-in that was giving me hell.


Most definitely.

These can halt a computer in it's tracks. Pains in the azz they are.


Posted By: patchfile
Date Posted: 17 Mar 2017 at 8:04am
Originally posted by wardog wardog wrote:

Originally posted by twf85 twf85 wrote:

I had an issue with a front panel USB3.0/memory card add-in that was giving me hell.


Most definitely.

These can halt a computer in it's tracks. Pains in the azz they are.

Years ago I did warranty work on an HP desktop that would not power on if the keyboard was plugged in. Any keyboard, I tried several. Was something wrong with the PS/2 port I guess.


Posted By: silent
Date Posted: 17 Mar 2017 at 10:15pm
" rel="nofollow - OK, 1 stick of RAM, 1 GPU, 1 CPU power, 1 Fan attached, 1 pump attached. New power supply borrowed from a friend, Rosewill 1000. Does same thing. No post,nothing but 5 flasshes of the red led then it breathes- let sit fro 30 min.  Does that mean it has to be the board?


Posted By: parsec
Date Posted: 17 Mar 2017 at 11:26pm
Originally posted by silent silent wrote:

" rel="nofollow - OK, 1 stick of RAM, 1 GPU, 1 CPU power, 1 Fan attached, 1 pump attached. New power supply borrowed from a friend, Rosewill 1000. Does same thing. No post,nothing but 5 flasshes of the red led then it breathes- let sit fro 30 min.  Does that mean it has to be the board?


Sorry but must check the basics. Is the 4/8 pin CPU power cable connected to the board? At the top, left hand side of the board? Essential or the CPU will not operate. Is that the "1 CPU power"?

What LED is flashing five times? Where on the board? Is that the chipset heatsink flashing and then breathing? If so, that means nothing.

We are not at the board being bad yet IMO. Since you changed your hardware quite a bit, have you cleared the UEFI/BIOS with the board's jumper yet? Please do that.

Is your memory the CMD32GX4M4B3000C15 model? Or the 2800 or 2666 kits? What memory slot are you using? Use an A2 or B2 slot with one DIMM.


-------------
http://valid.x86.fr/48rujh" rel="nofollow">


Posted By: silent
Date Posted: 18 Mar 2017 at 12:00am
Yes, correct CPU power attached. Top left corner of MB.
The southbridge LED blinks 5 times then goes into the "breathing" LED style option
Cleared the CMOS so many times it's shiny
removed battery for 10 min
Memory is CMD32GX4m4a2666c15 - 1 stick in A2



Posted By: silent
Date Posted: 18 Mar 2017 at 12:51am
Fixed it! Bad ground in the backplate....


Posted By: twf85
Date Posted: 18 Mar 2017 at 7:36am
Originally posted by silent silent wrote:

Fixed it! Bad ground in the backplate....

Woot! Good job!


-------------
https://valid.x86.fr/qc9lr0" rel="nofollow">


Posted By: patchfile
Date Posted: 18 Mar 2017 at 10:34pm
Originally posted by silent silent wrote:

Fixed it! Bad ground in the backplate....

Glad you found the issue.


Posted By: silent
Date Posted: 19 Mar 2017 at 12:23am
I accidentally found it. I had both sides off the  case, and accidentally touched the backplate..and it turned on. So, I turned it off and straightened the rubber gasket..and voila' it worked. Thanks for all your input tho... :) 


Posted By: patchfile
Date Posted: 01 Apr 2017 at 6:55am
Problem finally solved. I have been testing the Patriot RAM with every BIOS version, including the Beta versions.

As of 3/31/2017, using the Flash BIOS over network option in the Tools section of the BIOS, I was able to update to BIOS version 2.00 on the X370 Killer/ac and BIOS version 2.20 on the B350 Fatal1ty K4. Now the Patriot Viper 2133 (PVE48G213C4GY) 8GB works on both motherboards.

I manually set the RAM speed and timings before shutting it down, then installed the Patriot RAM. The boot cycle restarted to black screen 3 times, I assume it was trying to find an XMP profile for the new RAM. After those 3 restarts it loaded up just fine. I was able to see the RAM in the BIOS and it is working so far in Windows 10.

I had faith in ASRock, I knew they would get this problem solved eventually.



Posted By: Trender
Date Posted: 01 Apr 2017 at 7:18am
Mine couldn't post it was just new and what it fixed it was moving the jumpers and so clearing the cmos


Posted By: parsec
Date Posted: 01 Apr 2017 at 10:05am
Originally posted by patchfile patchfile wrote:

Problem finally solved. I have been testing the Patriot RAM with every BIOS version, including the Beta versions.

As of 3/31/2017, using the Flash BIOS over network option in the Tools section of the BIOS, I was able to update to BIOS version 2.00 on the X370 Killer/ac and BIOS version 2.20 on the B350 Fatal1ty K4. Now the Patriot Viper 2133 (PVE48G213C4GY) 8GB works on both motherboards.

I manually set the RAM speed and timings before shutting it down, then installed the Patriot RAM. The boot cycle restarted to black screen 3 times, I assume it was trying to find an XMP profile for the new RAM. After those 3 restarts it loaded up just fine. I was able to see the RAM in the BIOS and it is working so far in Windows 10.

I had faith in ASRock, I knew they would get this problem solved eventually.



Your Patriot Viper memory, model number PVE48G213C4GY, which we can check in the link below, is to quote, "Built for the latest Intel platforms...":

https://patriotmemory.com/product/viper-elite-series-ddr4-8gb-2133mhz-gray-2/" rel="nofollow - https://patriotmemory.com/product/viper-elite-series-ddr4-8gb-2133mhz-gray-2/

Your memory works as you know, but the latest information regarding using DDR4 memory designed for Intel systems is, the XMP profiles will not work for the Ryzen memory controller. That is really not surprising, as they are different systems, and the XMP data is configured for Intel systems.

You said you set the memory timings and speed manually, which is what you must do when the XMP data is not applicable to the system you are using with your memory. You guessed the three restarts (POST was run three times, for memory training, or trying different timings) was to find an XMP profile.

Did you check what the memory timings were set to now that the memory is working? Is it what you set it to manually? Of course at a speed of 1866 or 2133, the usual stock/default speed of DDR4 memory, the standard JEDEC SPD data would be used, not an XMP profile. Or was an XMP profile available for 2133? That is not clear on the Patriot page about this memory.

The standard SPD data could work at 2133. Other models of this memory at speeds up to 3200 would have an XMP profile, but again the XMP profiles of memory designed for Intel systems are not compatible with Ryzen systems.

Run CPU-Z and click the Memory tab to see the current timings being used. Click the SPD tab to check the JEDEC SPD data, and the XMP profile data.

The problem ASRock solved was working around, at least for this model of memory, the timing data designed for Intel systems.


-------------
http://valid.x86.fr/48rujh" rel="nofollow">


Posted By: patchfile
Date Posted: 02 Apr 2017 at 6:13pm
Originally posted by parsec parsec wrote:

Originally posted by patchfile patchfile wrote:

Problem finally solved. I have been testing the Patriot RAM with every BIOS version, including the Beta versions.

As of 3/31/2017, using the Flash BIOS over network option in the Tools section of the BIOS, I was able to update to BIOS version 2.00 on the X370 Killer/ac and BIOS version 2.20 on the B350 Fatal1ty K4. Now the Patriot Viper 2133 (PVE48G213C4GY) 8GB works on both motherboards.

I manually set the RAM speed and timings before shutting it down, then installed the Patriot RAM. The boot cycle restarted to black screen 3 times, I assume it was trying to find an XMP profile for the new RAM. After those 3 restarts it loaded up just fine. I was able to see the RAM in the BIOS and it is working so far in Windows 10.

I had faith in ASRock, I knew they would get this problem solved eventually.



Your Patriot Viper memory, model number PVE48G213C4GY, which we can check in the link below, is to quote, "Built for the latest Intel platforms...":

https://patriotmemory.com/product/viper-elite-series-ddr4-8gb-2133mhz-gray-2/" rel="nofollow - https://patriotmemory.com/product/viper-elite-series-ddr4-8gb-2133mhz-gray-2/

Your memory works as you know, but the latest information regarding using DDR4 memory designed for Intel systems is, the XMP profiles will not work for the Ryzen memory controller. That is really not surprising, as they are different systems, and the XMP data is configured for Intel systems.

You said you set the memory timings and speed manually, which is what you must do when the XMP data is not applicable to the system you are using with your memory. You guessed the three restarts (POST was run three times, for memory training, or trying different timings) was to find an XMP profile.

Did you check what the memory timings were set to now that the memory is working? Is it what you set it to manually? Of course at a speed of 1866 or 2133, the usual stock/default speed of DDR4 memory, the standard JEDEC SPD data would be used, not an XMP profile. Or was an XMP profile available for 2133? That is not clear on the Patriot page about this memory.

The standard SPD data could work at 2133. Other models of this memory at speeds up to 3200 would have an XMP profile, but again the XMP profiles of memory designed for Intel systems are not compatible with Ryzen systems.

Run CPU-Z and click the Memory tab to see the current timings being used. Click the SPD tab to check the JEDEC SPD data, and the XMP profile data.

The problem ASRock solved was working around, at least for this model of memory, the timing data designed for Intel systems.

I feel like I was just put on trial by you, not sure why, but I will try to answer.

I ordered the CPU's, motherboards and RAM before there was a QVL list on the ASRock website. I took a shot in the dark for my preorders. I kept the RAM because I believed ASRock would release a BIOS that would eventually work, and I did not want to pay a restocking fee. 

Yes, I set the memory timings and speed manually, it is an old habit. I don't really know why it powered on to a black screen three times before it finally posted. But when I checked the memory settings after the 3rd boot, my timings and speed setting were unchanged, but there was an available XMP profile for the Patriot RAM. I know this because the G.Skill RAM timings and speed are different than the Patriot, and the XMP profile was showing the Patriot settings; 14-14-14-32 @2133

I explained what I did, step by step, in case someone wanted to duplicate it. I was not trying to be authoritative, just thorough. I have never worked with XMP profiles before, I assumed it was the way memory was identified by the BIOS now days. I can see I was wrong. 

CPU-Z screens you asked for http://imgur.com/dVxsxdZ



You seem intent on pointing out my poor choice of RAM, but as I said, none of this information was available on February 22nd when I ordered it. 



Print Page | Close Window

Forum Software by Web Wiz Forums® version 12.04 - http://www.webwizforums.com
Copyright ©2001-2021 Web Wiz Ltd. - https://www.webwiz.net