ASRock.com Homepage
Forum Home Forum Home > Technical Support > Intel Motherboards
  New Posts New Posts RSS Feed - Z170 ProM4s build help
  FAQ FAQ  Forum Search Search  Events   Register Register  Login Login

Z170 ProM4s build help

 Post Reply Post Reply Page  <12
Author
Message
culdog1 View Drop Down
Newbie
Newbie


Joined: 02 May 2016
Status: Offline
Points: 9
Post Options Post Options   Thanks (0) Thanks(0)   Quote culdog1 Quote  Post ReplyReply Direct Link To This Post Posted: 10 May 2016 at 3:24am
Thanks Parsec for your input, i will try to work my way through your suggestions tonight if I'm able. I do know the bios is the latest 2.23, I flashed it earlier in this process. And I'll create an UEFI profile. Thanks
Back to Top
culdog1 View Drop Down
Newbie
Newbie


Joined: 02 May 2016
Status: Offline
Points: 9
Post Options Post Options   Thanks (0) Thanks(0)   Quote culdog1 Quote  Post ReplyReply Direct Link To This Post Posted: 10 May 2016 at 3:33am
Excuse me bios is version 2.60 sorry

Back to Top
parsec View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 04 May 2015
Location: USA
Status: Offline
Points: 4996
Post Options Post Options   Thanks (0) Thanks(0)   Quote parsec Quote  Post ReplyReply Direct Link To This Post Posted: 11 May 2016 at 12:50am
For what its worth, I connected two SATA drives to my Z170 Extreme7+ board, with a Samsung 950 Pro as the OS drive, and a Samsung SM951 (AHCI version) M.2 SSD in the board too.



Both SATA drives are recognized, and the PC boots. The two SATA drives are SSDs, which should make no difference IMO, unless the HDDs you two are using are old or you are using IDE to SATA adapters for the HDDs.

Notice in the Device Manager screenshot all four SSDs are listed. I also expanded the IDE ATA/ATAPI controllers and Storage Controllers entries. That's just to show that the controllers for the various drives are active and using a driver. You should be seeing at least some of those entries in your Device Manager list, depending upon the various storage drivers you are using.
Back to Top
culdog1 View Drop Down
Newbie
Newbie


Joined: 02 May 2016
Status: Offline
Points: 9
Post Options Post Options   Thanks (0) Thanks(0)   Quote culdog1 Quote  Post ReplyReply Direct Link To This Post Posted: 11 May 2016 at 8:12am
I'm giving up on this board. I will start an RMA with ASRock. Thanks for all the input from all. Wish me luck on the next try
Back to Top
invasmani View Drop Down
Newbie
Newbie


Joined: 28 Apr 2016
Status: Offline
Points: 3
Post Options Post Options   Thanks (0) Thanks(0)   Quote invasmani Quote  Post ReplyReply Direct Link To This Post Posted: 13 May 2016 at 5:11am
Originally posted by Xaltar Xaltar wrote:

Are you using a new SATA cable with the drives or an old one from a previous build? The reason I ask is because using a SATA 1 cable on any of my systems causes a post failure. Make sure you use new SATA 3 cables. 

Aside from that I am afraid I can't really suggest anything other than perhaps removing the M.2 drive and trying to power the system with only a SATA drive connected to see of the issue still occurs. 
I'd also advice checking system agent voltage if that's set too low for a given CPU clock frequency/BCLK frequency not sure which is the cause it can fail to post or cause post failure messages to do with the boot drive being inaccessible.

Generally speaking I've found SA needs to be 1.05v minimum or higher in typically up to around 1.15v to avoid such issues. I have no idea in the case of M.2 drives though that might require even higher SA in conjunction with other SATA drives is my initial suspicion based on what I've seen at least.

I'd try raising SA to 1.25v and seeing if it helps and from there lowering it to the point where the boot drive inaccessible errors begin to occur and raise it up anywhere from 0.05v to 0.15v above that.
Back to Top
parsec View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 04 May 2015
Location: USA
Status: Offline
Points: 4996
Post Options Post Options   Thanks (0) Thanks(0)   Quote parsec Quote  Post ReplyReply Direct Link To This Post Posted: 13 May 2016 at 1:35pm
Originally posted by invasmani invasmani wrote:

I'd also advice checking system agent voltage if that's set too low for a given CPU clock frequency/BCLK frequency not sure which is the cause it can fail to post or cause post failure messages to do with the boot drive being inaccessible.

Generally speaking I've found SA needs to be 1.05v minimum or higher in typically up to around 1.15v to avoid such issues. I have no idea in the case of M.2 drives though that might require even higher SA in conjunction with other SATA drives is my initial suspicion based on what I've seen at least.

I'd try raising SA to 1.25v and seeing if it helps and from there lowering it to the point where the boot drive inaccessible errors begin to occur and raise it up anywhere from 0.05v to 0.15v above that.


System Agent voltage (VCCSA) being to low causing POST failures and drive recognition issues?

I'm glad you brought this up, since it might be a factor in this issue, but possibly not directly for the reason you explained. Your idea is definitely worth testing IMO.

I wonder what the default/Auto setting in the Z170M Pro4S' UEFI for VCCSA voltage provides.

I've never had the problem with my drives that the others in this thread have, with the Auto VCCSA setting in the UEFI resulting in 1.072V for VCCSA. I had three M.2 SSDs in my Z170 Extreme7+ board with that VCCSA voltage.

VCCSA is related to memory stability in Skylake systems. We have seen some strange issues that were fixed by changing to memory with better compatibility. Is this another example of that?

Increasing VCCSA is done when over clocking memory, and the XMP profiles of high speed DDR4 memory (3000+) set VCCSA and VCCIO voltages to values significantly higher than the defaults. My G.SKILL DDR4 3200 memory's XMP profile set VCCSA to 1.250V, and VCCIO to 1.150V. I found that those rather high voltages could be reduced significantly, without loss of memory stability or boot problems, with the memory at its highest rated speed. But that depends upon the model of memory being used, and some DDR4 memory designed for X99 systems does not always work well with Skylake systems.

If anyone tries to increase the VCCSA voltage to the value suggested above, you might find the voltage value suddenly changing to a red colored font. That is normally done when a voltage setting value is above the range suggested by Intel. The voltages in red are not automatically dangerous, but there are limits to any voltage, beyond which damage can occur.

That is what I meant by increasing VCCSA not directly being a fix for this issue. That is, increasing VCCSA does not directly benefit the M.2 and SATA IO system itself (part of the Z170 PCH), but fixing any memory stability problems on these boards has also cured other strange problems like this one.

Another hint about this is, I reduced the PCH +1.0 voltage from the Auto setting, which was 1.016V by default. I wanted to see if that would affect the PCH temperature, and it did. The PCH voltage is the main voltage for the Z170 PCH chipset, which provides all the M.2 and Intel SATA ports. The default PCH +1.0 voltage would be another worth checking on the Z170M Pro4S.

Skylake is a rather different system from Intel compared to their recent past. The voltage regulators (FIVR) on the CPU die itself, found in Haswell and Broadwell processors, is no longer used in Skylake. Skylake also is the first non-HEDT platform to use DDR4 memory, and is the first Intel system to use PCIe 3.0 lanes in the PCH/Chipset, for use with the PCIe (M.2) and SATA storage interfaces. AHCI and NVMe use system memory to store and communicate IO requests to disk drives. Put this all together, and we can see the potential for new issues like this one.
Back to Top
culdog1 View Drop Down
Newbie
Newbie


Joined: 02 May 2016
Status: Offline
Points: 9
Post Options Post Options   Thanks (0) Thanks(0)   Quote culdog1 Quote  Post ReplyReply Direct Link To This Post Posted: 13 May 2016 at 8:56pm
I may have found the possible culprit in my setup. My brother has an asrock z97 that I borrowed, so disconnect all his stuff except EVGA 110 750 power supply, put my 950 in and boot up no problem. Shut down, connect WD green 350 sata boots and windows sees the WD. This power supply uses modular cables just like mine a Corsair ax750. So i swap out power supply and boot with 950 only it boots, shut down add WD no boot no post nothing. I tried connecting DVD burner same result. I tried every cable that came with the corsair nothing. put the evga back in and try every cable and they all work. I think my power supply maybe has a short in it when i connect a modular cable something causes no power. Now I'm about to head over to corsair forums and see what they've got. I'll keep everyone updated
Back to Top
Xaltar View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 16 May 2015
Location: Europe
Status: Offline
Points: 22943
Post Options Post Options   Thanks (0) Thanks(0)   Quote Xaltar Quote  Post ReplyReply Direct Link To This Post Posted: 13 May 2016 at 9:42pm
The one time I don't suggest trying another PSU......

Good luck Thumbs Up
Back to Top
 Post Reply Post Reply Page  <12
  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.141 seconds.