Author: marioava1108Subject: FATAL1TY Z170 GAMING-ITX/AC wont post
Posted: 02 Nov 2016 at 11:37pm
![Originally posted by parsec]( "Originally posted by parsec") parsec wrote:
![Originally posted by marioava1108]( "Originally posted by marioava1108") marioava1108 wrote:
After disconnecting the SSDs and going down to one 8gb memory it finally posted. |
I doubt the SSDs were the cause of the failure to POST. My guess is the memory was the cause.
Have you tested both DIMMs individually, to make sure both work? Also check both DIMM slots, to be sure both work, in case you have a bad board.
Another cause of the memory failure could be bent pins in the CPU socket.
Are you sure your memory is the G.SKILL F4-2400C15D-16GVR? Your listing in the first post show "Z170/X99", while G.SKILL only shows Z170 boards as compatible. Or was that line pulled from PC Parts Picker?
I would connect the SSDs again with the one DIMM installed, and see if you can POST into the UEFI.
Were you really going to have two drives connected when you installed Windows? Not a good idea unless both SSDs will always be in that PC.
While I agree a newer UEFI version is a good idea, I'm not sure the latest 7.10 version is a good idea. Any of the ASRock Z170 board's 7.xx UEFI versions add compatibility for the upcoming Intel Kaby Lake processors. Some users have reported less than ideal results with those versions. My Z170 board seems unaffected, and I don't know either way about your board. But why chance it at this point since the 7.10 UEFI does nothing for you that the 2.30 version already does.
Your memory should default to 2133 in the UEFI, do you see it at that speed?
|
The SSDs already had W10 installed from my old machine. I pulled the part name for the memory from the Amazon listing. I tested both DIMMS and they appear to be working just fine. I installed my other HDDs and everything seems stable. I'm guessing that I may have not had the memory all the way in the slots? Thanks for the heads up on the 7.10 UEFI, I'll avoid that for now since I don't need it.
parsec wrote: