Ext7+ BIOS v2.60 or v3.00 & 4 Sticks kit = Code 00 |
Post Reply |
Author | |
bezel
Newbie Joined: 25 Nov 2015 Status: Offline Points: 13 |
Post Options
Thanks(0)
Posted: 17 Apr 2016 at 9:01pm |
Hi.
My PC: CPU:6700K MB: Extreme 7+ RAM: 16GB (4x4) GSkill Ripjaws 4 2800MHz Cooling: Corsair H110i GTX GPU: Zotac 980Ti AMP Extreme PSU: Corsair AX 850W SYS: WIN 10 Home After the release of UEFI v3.00 I've decided to update my 2.50 version using Instant Flash method. The update process went fine to the point were You press enter to restart the PC. Unfortunately PC restarted couple of times and got stuck on Dr.Debug code 00. I switched to backup bios B (v2.50) and did a copy to A and it works fine. After that I tried v2.60 but that also ended with Dr.Debug code 00. Tried couple of times ,cleared CMOS via battery and button but with no luck. One time I saw code 00 change to 19 just for a second and that got me thinking maybe its something with memory. So I've took out three memory modules and it boots just fine! 1 stick = Ok 2 sticks in dual channel = Ok 3 sticks in different slots = Ok 4 sticks in different slots = NOT WORKING! So my point is that my memory ,(four sticks kit F4-2800C16Q-16GRK) which works fine with v2.50 and on earlier UEFI versions ,stopped working in v2.60 and v3.00. The F4-2800C16Q-16GRK kit was and still is on Memory Support List ,supporting both dual channel and four sticks. For now I will stay with v2.50 and in the near future I'll grab 2x8GB kit that I hope will work with v3.00. Just wanted to add this for those who might have this problem. PS. Sorry for bad English but it is not my first language. Edited by bezel - 18 Apr 2016 at 1:13am |
|
DooRules
Newbie Joined: 05 Nov 2015 Location: Newfoundland Status: Offline Points: 122 |
Post Options
Thanks(0)
|
I use bios 2.31 on my Extreme 7+. I have found all other bios's to be problematic in one form or another. No issues at all with 2.31, funny thing is i don't even see it listed for download anymore.
|
|
bezel
Newbie Joined: 25 Nov 2015 Status: Offline Points: 13 |
Post Options
Thanks(0)
|
Yeah for my build 2.50 is the best at the moment although sometimes it still can freeze while browsing UEFI
Generally for me the Skylake platform is the worst. I have never had so many problems with my previous builds |
|
Xaltar
Moderator Group Joined: 16 May 2015 Location: Europe Status: Offline Points: 25073 |
Post Options
Thanks(0)
|
It's nice to see someone placing the blame where it belongs for a change A lot of people come here blaming ASRock for problems without first checking if the problem is common across all manufacturers. I have had a few issues with my Skylake 6600k build but have been lucky enough to avoid most of the more irritating ones (sleep and memory issues) due to my usage particulars. I leave my PC running 24/7, it never goes into sleep mode and I am only using a single 8gb RAM kit (2x4gb) so don't have to worry about upping VCCIO and VCCSA voltages or playing about with manual timings etc. On the up side, intel is working on sorting out their issues and when they do this will filter down to motherboard manufacturers and we should eventually see a stable, reliable Skylake platform emerge. I wasn't paying much attention to things when Haswell dropped but looking over old posts and release reviews I see nothing as bad as I have seen with Skylake. I do believe that Skylake is a step in a good direction though, many of the features added (returned in point of fact) to Skylake will be a solid platform to build from with future generations of CPU. I love the independent BCLK being returned as well as taking unnecessary features off the CPU die and putting them back in the chipset where they belong.
|
|
|
|
bezel
Newbie Joined: 25 Nov 2015 Status: Offline Points: 13 |
Post Options
Thanks(0)
|
@Xaltar
I saw plenty topics on many different forums about problems with Skylake. It does not matter who is the motherboard manufacturer. They all have similar stability issues and one thing in common ,the Z170 chipset. Now ASRock and others are trying to fix what Intel broke. "we should eventually see a stable, reliable Skylake platform emerge" I really hope so I like those low CPU temps and high OC potential Edited by bezel - 18 Apr 2016 at 7:36am |
|
parsec
Moderator Group Joined: 04 May 2015 Location: USA Status: Offline Points: 4996 |
Post Options
Thanks(0)
|
Hmm, let's think about this...
The G.SKILL F4-2800C16Q-16GRK Ripjaws 4 memory, that is included in the Z170 Extreme7+ Memory Support List, is not listed by G.SKILL for use with any Z170 boards. Only X99 boards are included: http://gskill.com/en/product/f4-2800c16q-16grk But, we know that all four DIMMs of this memory did work fine with an earlier UEFI version. This memory uses Samsung memory chips, which are usually better than other kinds. It seems there are some differences between memory that works with the X99 and Z170 platforms. The 3.00 UEFI is said to include improvements with DRAM compatibility. Apparently those changes were not "liked" by the Ripjaws 4 memory. Or the improvements need some... improvement. One thing I always do (unless I forget) is before I apply a UEFI/BIOS update, I'll load a UEFI profile with stock CPU and memory speeds. I hope this will result in less of a "shock" to the memory and system, which normally will change to stock/Auto memory settings after a UEFI/BIOS update. My update to 3.00 went fine. It even preserved my setting of RAID in the Storage Configuration screen, which I believe was true for 2.50 too. I've noticed that higher speed memory and/or greater amounts of memory in Skylake systems tends to need more VCCSA and VCCIO. The XMP values for VCCSA and VCCIO voltages for my G.SKILL Trident Z 3200 memory are very high, 1.250V and 1.150V respectively. I can reduce both of them to 1.150V and 1.100V at 3200 without any problems, and have gone lower but did not test that enough. This is only with an 8GB kit, 4GB x 2. Something I have noticed in previous UEFI versions, is a difference between the DRAM, VCCSA, and VCCIO voltage settings, and the resulting actual value. For example, given settings of: DRAM voltage at 1.35V, VCCSA voltage at 1.250V, VCCIO voltage at 1.150V. The resulting actual voltages are: DRAM of 1.376V, VCCSA of 1.280V, VCCIO of 1.176V. I'm reading the resulting actual voltages in the UEFI, H/W Monitoring screen, and in Windows with HWiNFO64. The UEFI H/W Monitoring screen and HWiNFO64 values are identical for all three values. Finally my point: I wonder if the XMP values for VCCSA and VCCIO for the Ripjaws 4 memory are lower than those used for newer memory used with Skylake, like Ripjaws 5 and Trident Z. I know the VCCSA and VCCIO voltages on my X99 board system are much lower, with different memory. The Dr Debug POST code of 00 normally means a dead CPU, or no power to the CPU, not a memory problem. Personally, my Z170 EX7+ PC goes into and out of Sleep fine, I use it all the time now that I must wait for NVMe SSDs to POST... yes they are slow to POST. If you like a slow, long POST, get an X99 system and put NVMe SSDs in it. UEFI 2.31 was a Beta version, that was migrated to a regular release with other changes, 2.50 I believe. ASRock does not release endless Beta UEFI versions, and does not keep them available for download forever, like another mobo manufacture I'm aware of. One comment about the Skylake platform being less stable, or having more issues than other platforms in the past. Did we use Windows 10 on those other platforms? |
|
Post Reply | |
Tweet
|
Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |