On previos boards I had there was a way to force it into "limp" mode by removing all memory dimms but 1, leaving one dimm in slot 2. not sure if this board has this feature but I am looking it up.
 
EDIT: Try only populating slot 3, maybe even try 1 slot at a time, its worth a shot.

I have updated to this bios from 1.09 a few weeks ago and have not yet had a single problem.
 
I can still OC my 6700k and 3000c15 memory to the same specs as i have had it at for over a year now.
 

 
 

upgraded my z170ftw and now i have d3 and 4 beeps than 98. System won't start. what should i do?
why you remove dual bios from ftw?
 
Update: i reflash GD25Q128CSIG via SPI programmer (used 1E177201.bin file). Now all working good!
Evga support said that BIOS chips is out of stock. All peoples who wait new chips: you can flash it yourself. It is very simply )))
 
arduino code:
#include "SPIFlash.h"
#include <SPI.h>
#include <avr/wdt.h>
SPIFlash flash(2, 0);
byte buf[1024];
void setup() {
  Serial.begin(115200);
  while (!Serial);
  if (flash.initialize())
    Serial.println("Init OK!");
  else
    Serial.println("Init FAIL!");
}
 
void loop() {
  char cmd;
  if (!Serial.available()) return;
  cmd = Serial.read();
  if (cmd == 't') {
    Serial.print("COM ok\n");
    return;
  }
  if (cmd == 'i')
  {
    Serial.print("DeviceID: ");
    Serial.print(flash.readDeviceId(), HEX);
    Serial.print('\n');
    return;
  }
  if (cmd == 'a')
  {
    flash.chipErase();
    while (flash.busy());
    Serial.print("OK");
    Serial.print('\n');
    return;
  }
  if (cmd == 'e')
  {
    long  sector = Serial.parseInt();
    Serial.read();
    flash.blockErase4K(sector);
    Serial.print("OK");
    Serial.print(sector);
    Serial.print('\n');
    return;
  }
  if (cmd == 'w')
  {
    long addr = Serial.parseInt();
    Serial.read();
    for (int bufsz = 0; bufsz < 128; bufsz++)
    {
      while (Serial.available() == 0);
      buf[bufsz] = Serial.read();
    }
    flash.writeBytes(addr, buf, 128);
    Serial.print("OK");
    Serial.print(addr);
    Serial.print('\n');
    return;
  }
  if (cmd == 'r') {
    long addr = Serial.parseInt();
    Serial.read();
    for (int i = 0; i < 4; i++)
    {
      flash.readBytes(addr + (i * 1024) + 0, buf, 1024);
      for (int j = 0; j < 1024; j++)
        Serial.write(buf[j]);
    }
    return;
  }
}
 
Software to flash http://skproj.ru/wp-conte...2/SpiEepromFlasher.zip

lowe0
I'm curious: is there a known issue w/ this BIOS?  The chip EVGA sent me (thanks!) has 2.00 beta on it, and I'm hesitant to flash it to 2.01 to get off of the beta.

I use it two days. There are no any problems with 2.01. CPU (7700k) and memory overclock is stable.
But flashing under Win10 was fault and i reflashed BIOS chip by extenal programmer.

Based on my experience so far, I would say don't update unless you have a dual bios board.
Until this update, I've never once had an issue with a bios flash and have done a lot of them over the past 20 years.

Surprisingly, I received a new BIOS chip today even though support insisted they were out of stock.  Seems like there must be a communication disconnect at eVGA tech support.  Anyway, all is well with the replacement chip.  It says the BIOS is version 2.00.  No way I am going to update to 2.01 and risk bricking another chip.  I'm thinking about upgrading to a dual bios board to avoid future issues like this.  It might need to be a different manufacturer though considering the only available eVGA board with dual BIOS is the $300 Classified.

I'm getting an A2 code and a CMOS checksum error.

Just adding my name to the hat of 2.01 "0d" error code. I had just received a bios chip with 2.01 in order to be able to boot kaby lake. Booted fine but after a cmos clear was unable to boot. "0d" error code kept showing up. Contacted EVGA support and they will be sending my another bios chip.

guys i Tried flashing the bios, on a z170 FTW, after some error that i did not document, the bat file closed and now, on restart i am getting F2, F9 error, How do i flash a new version of BIOS? 

loveha
People should stay away from this BIOS. Gives nothing but issues.

Just to update my situation. I've received a second Bios chip with 2.01. This time i carefully picked my bios settings and made sure to not clear cmos. So far so good. But I am afraid that if I clear CMOS i'll get the "0d" error code again.

Hi. Im having a massive problem. I was updating via windows from 1.05 to 2.01, and when the system rebooted.. all i get is error/post code 98. And the system will no longer even reach BIOS. I have tried unplugging and reseating everything along with CMOS and nothing. Please, any help would be much much appreciated, thank you, Ollie f

bildier

lowe0
I'm curious: is there a known issue w/ this BIOS?  The chip EVGA sent me (thanks!) has 2.00 beta on it, and I'm hesitant to flash it to 2.01 to get off of the beta.

I use it two days. There are no any problems with 2.01. CPU (7700k) and memory overclock is stable.
But flashing under Win10 was fault and i reflashed BIOS chip by extenal programmer.

What tools do you have/need to reprogram it? 

My Dartk Mode dosen't work anymore on my Z170 Stinger after BIOS Update...

bought G3900 Skylake, updated BIOS from 1.09 via USB flash to 2.01 - now kabylake G4560 is running well.
 
uff  - error code 62 gone... :-)

Flashed using the live update thing and now my system won't post and it gets stuck at 18 on the debug then restarts. I thought updating my bios would improve my nvme performance(950 pro was at half the speed). One thing to note is that I have a es 2.8ghz CPU and I believe this bios might have dropped support or it's just bad and might be the explanation for my poor nvme performance. Maybe I need a new bios chip? Or maybe I need to pick up a kaby lake?