ASRock.com Homepage
Forum Home Forum Home > Technical Support > AMD Motherboards
  New Posts New Posts RSS Feed - Asrock 970M Pro3 - 16GB 1600MHZ RAM Problem
  FAQ FAQ  Forum Search Search  Events   Register Register  Login Login

Asrock 970M Pro3 - 16GB 1600MHZ RAM Problem

 Post Reply Post Reply
Author
Message
Paul_MCFC View Drop Down
Newbie
Newbie


Joined: 15 Dec 2016
Status: Offline
Points: 8
Post Options Post Options   Thanks (0) Thanks(0)   Quote Paul_MCFC Quote  Post ReplyReply Direct Link To This Post Topic: Asrock 970M Pro3 - 16GB 1600MHZ RAM Problem
    Posted: 15 Dec 2016 at 7:52am
I have 4x 4GB  1600mhz Corsair Vengance Low Profile RAM installed on Asrock 970M Pro3. If I change the frequency of RAM in BIOS to 1600 I get a lot of issues, SATA devices disappear and I can't boot into windows. If I set it back to 1333mhz everything seems to be fine.

Please any ideas am I doing something wrong, and just to confirm board supports 4x4gb 1600 ram and it should work?

thank you Smile
Back to Top
PetrolHead View Drop Down
Groupie
Groupie


Joined: 07 Oct 2015
Status: Offline
Points: 403
Post Options Post Options   Thanks (0) Thanks(0)   Quote PetrolHead Quote  Post ReplyReply Direct Link To This Post Posted: 16 Dec 2016 at 2:48am
Depending on your CPU, the 1600 MHz setting on four sticks of RAM is either a small overclock (OC), a moderate OC or a considerable OC. This is because the internal memory controller (IMC) of the CPU is put under more stress the more sticks of RAM you have (and the more slots the motherboard has).

If the exact model of your RAM is officially supported by ASRock for this motherboard, then you might need to increase RAM voltage or CPU-NB (the IMC) voltage and/or speed. So:

1. Check if your RAM is lister on the memory support list (http://www.asrock.com/mb/AMD/970M%20Pro3/?cat=Memory)
2. Check your BIOS setting for RAM voltage, RAM settings, CPU-NB voltage and CPU-NB speed.
3. Report back with your findings.

Also, tell us what CPU you're using.
Ryzen 5 1500X, ASRock AB350M Pro4, 2x8 GB G.Skill Trident Z 3466CL16, Sapphire Pulse RX Vega56 8G HBM2, Corsair RM550x, Samsung 960 EVO SSD (NVMe) 250GB, Samsung 850 EVO SSD 500 GB, Windows 10 64-bit
Back to Top
wardog View Drop Down
Moderator Group
Moderator Group


Joined: 15 Jul 2015
Status: Offline
Points: 6447
Post Options Post Options   Thanks (0) Thanks(0)   Quote wardog Quote  Post ReplyReply Direct Link To This Post Posted: 16 Dec 2016 at 9:29pm
I'd like to know specifically what's the P/N of your Vengence 16GB(4x4GB) matched Kit ?
Back to Top
Paul_MCFC View Drop Down
Newbie
Newbie


Joined: 15 Dec 2016
Status: Offline
Points: 8
Post Options Post Options   Thanks (0) Thanks(0)   Quote Paul_MCFC Quote  Post ReplyReply Direct Link To This Post Posted: 21 Dec 2016 at 12:10am
I don't know exactly what the issue was with 4 x 4gb ram had two matching pairs in alternate dimm slots tested with memtest too. Anyways I got 2 x HyperX Savage 16GB 2X8GB Dual Channel DDR3 1866MHz and all seems to be stable .... thanks
Back to Top
wardog View Drop Down
Moderator Group
Moderator Group


Joined: 15 Jul 2015
Status: Offline
Points: 6447
Post Options Post Options   Thanks (0) Thanks(0)   Quote wardog Quote  Post ReplyReply Direct Link To This Post Posted: 21 Dec 2016 at 1:41am
Originally posted by Paul_MCFC Paul_MCFC wrote:

I don't know exactly what the issue was with 4 x 4gb ram had two matching pairs in alternate dimm slots tested with memtest too. Anyways I got 2 x HyperX Savage 16GB 2X8GB Dual Channel DDR3 1866MHz and all seems to be stable .... thanks


Using two unmatched 8GB(2x4) will most times create issues depending on if the manufacturer switched actual chips on the DIMM stick itself. That in turn will cause what you saw.

The chances of the above are only exacerbated by each kits stick S/Ns that are wide apart.


Edited by wardog - 21 Dec 2016 at 1:47am
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.04
Copyright ©2001-2021 Web Wiz Ltd.

This page was generated in 0.173 seconds.