EVGA

BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.24)

Page: < 12345 > Showing page 2 of 5
Author
ZoranC
FTW Member
  • Total Posts : 1099
  • Reward points : 0
  • Joined: 2011/05/24 17:22:15
  • Status: offline
  • Ribbons : 16
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/05/11 10:37:23 (permalink)
EVGATech_LeeM
Let me check with the MB/BIOS team.



Thank you! :)
#31
dshelfoon
New Member
  • Total Posts : 11
  • Reward points : 0
  • Joined: 2005/11/01 18:13:50
  • Status: offline
  • Ribbons : 0
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/05/11 18:50:36 (permalink)
It also has active cooling so it is not an issue at all. I have two of these running in our development servers and they are perfect.  I also have the MSI variant which is quite frankly a bit bulky in comparison.
#32
ironage
New Member
  • Total Posts : 87
  • Reward points : 0
  • Joined: 2008/05/10 08:48:31
  • Status: offline
  • Ribbons : 1
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/05/20 03:43:05 (permalink)
Still no Update for Eleet-X to support per Core VCore ?!
#33
EVGA_Lee
Moderator
  • Total Posts : 4247
  • Reward points : 0
  • Joined: 2016/11/04 14:43:35
  • Location: Brea, CA
  • Status: offline
  • Ribbons : 14
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/05/20 09:14:33 (permalink)
ironage
Still no Update for Eleet-X to support per Core VCore ?!


At this point, I would not expect further updates to Eleet-X.  Our current plan is to first finalize support for ELEET X1 for the Z490 motherboards, then work on backwards compatibility with other chipsets.
#34
EVGA_Lee
Moderator
  • Total Posts : 4247
  • Reward points : 0
  • Joined: 2016/11/04 14:43:35
  • Location: Brea, CA
  • Status: offline
  • Ribbons : 14
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/05/20 10:15:28 (permalink)
ZoranC
EVGATech_LeeM
Let me check with the MB/BIOS team.



Thank you! :)


Sent you a PM with a beta BIOS to test.  Let me know how it works.
#35
ironage
New Member
  • Total Posts : 87
  • Reward points : 0
  • Joined: 2008/05/10 08:48:31
  • Status: offline
  • Ribbons : 1
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/05/20 16:04:11 (permalink)
thanks for your input about Eleet-X, is there a chance forme to get that beta Bios too for personal testing PLEASE ?
#36
zGunBLADEz
New Member
  • Total Posts : 58
  • Reward points : 0
  • Joined: 2014/11/26 07:05:08
  • Status: offline
  • Ribbons : 1
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/05/21 04:34:21 (permalink)
ironage
Still no Update for Eleet-X to support per Core VCore ?!


be glad they listened, bcuz it took them over 2 yrs for me to come here and request that same feature which was absent all that time on their bios since x299 launch to begin with which is one of the "features" this platform have ..


EVGATech_LeeM
ironage
Still no Update for Eleet-X to support per Core VCore ?!


At this point, I would not expect further updates to Eleet-X.  Our current plan is to first finalize support for ELEET X1 for the Z490 motherboards, then work on backwards compatibility with other chipsets.


huh??
really?
find funny that announcement. have something working  and prioritize something else before the fact
post edited by zGunBLADEz - 2020/05/21 04:41:31
#37
ZoranC
FTW Member
  • Total Posts : 1099
  • Reward points : 0
  • Joined: 2011/05/24 17:22:15
  • Status: offline
  • Ribbons : 16
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/05/21 20:09:54 (permalink)
EVGATech_LeeM
ZoranC
EVGATech_LeeM
Let me check with the MB/BIOS team.



Thank you! :)


Sent you a PM with a beta BIOS to test.  Let me know how it works.




Thank you, will do :)
#38
Damian Kenny
New Member
  • Total Posts : 2
  • Reward points : 0
  • Joined: 2010/11/18 21:45:26
  • Status: offline
  • Ribbons : 0
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/05/28 15:50:11 (permalink)
Any news on getting raid support for 2 x nvme's please?
Have tried all config's and can't get it to work.
 
Cheers
#39
EVGA_Lee
Moderator
  • Total Posts : 4247
  • Reward points : 0
  • Joined: 2016/11/04 14:43:35
  • Location: Brea, CA
  • Status: offline
  • Ribbons : 14
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/05/28 17:03:13 (permalink)
Damian Kenny
Any news on getting raid support for 2 x nvme's please?
Have tried all config's and can't get it to work.
 
Cheers


Which board, which CPU, which devices are connected in the PCIe slots, and which devices are plugged into the M.2/U.2 slots?
#40
Damian Kenny
New Member
  • Total Posts : 2
  • Reward points : 0
  • Joined: 2010/11/18 21:45:26
  • Status: offline
  • Ribbons : 0
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/05/28 17:36:46 (permalink)
X299FTWK, i910940X, 2 x M.2 Samsung 970's 2GB and 2 x rtx2080ti's oh and a m.2 Wi-Fi/Bluetooth card
Just wanted to raid 0 the 2 x 2gb sticks and have one large 4gb.
Cheers man.
post edited by Damian Kenny - 2020/05/28 21:50:45
#41
ZoranC
FTW Member
  • Total Posts : 1099
  • Reward points : 0
  • Joined: 2011/05/24 17:22:15
  • Status: offline
  • Ribbons : 16
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/05/28 18:29:11 (permalink)
Damian Kenny
Any news on getting raid support for 2 x nvme's please?

Just wanted to raid 0 the 2 x 2gb sticks and have one large 4gb.

 
If you don’t have to boot from RAID and are using Win10 you might want to take a look at Microsoft’s Storage Spaces. That is what I am experimenting with now and why I am excited about non-VROC 4x4 bifurcation in BIOS 1.23.
#42
Ki2Is
New Member
  • Total Posts : 22
  • Reward points : 0
  • Joined: 2020/01/03 02:44:00
  • Status: offline
  • Ribbons : 0
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/05/29 00:41:44 (permalink)
Hey, I have got a x299 FTW K and Bios v.1.23.
When running 4.5Ghz ADAPTIVE VCORE all core(NO BSOD), my BCLK stays at 100Mhz, but when switching to 4.8 4.8 4.7 4.8 4.6 4.6 4.7 4.7 4.7 4.7, BCLK goes up to 102.8Mhz and crashes while rendering.
I have looked already for the BCLK spread spectrum setting in the BIOS, but cannot find anything.
How can I disable that, to get the 100Mhz ?
#43
lmatyja
Superclocked Member
  • Total Posts : 180
  • Reward points : 0
  • Joined: 2017/10/14 08:45:06
  • Status: offline
  • Ribbons : 1
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/05/30 06:28:12 (permalink)
EVGATech_LeeM
Can u tell me what option is better for series 10xxx for voltage mod? override or adaptive? adaptive on stock for is 1.2V but for 4.8 adaptive normal is 1.3 ? for seris 7xxx is 1.2 and cant go lower where is problem ?
 
 
#44
FunktasticLucky
New Member
  • Total Posts : 46
  • Reward points : 0
  • Joined: 2010/11/23 04:16:16
  • Status: offline
  • Ribbons : 0
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/06/05 03:06:39 (permalink)
Just curious if anyone else has noticed a weird bug in per core overclocking?  I decided to try the new per core vcore and completely dial in my 10940X to get at least 5Ghz on a couple of cores at a minimum.  So I started with core 1 and set it to 4.9Ghz.  The other cores were set to 4.5Ghz while testing stability when I noticed that Core 1 won't actually boost to 4.9Ghz.  It stays at 4.5Ghz with the rest of the cores.
 
Now it gets weird.  I went in and set Core 2 to 4.9Ghz and core 1 to 4.5.  Fire up windows run Cinebench R20 and Core 2 boosts to 4.9Ghz immediately.  So I go back in and set core 1 to 4.9Ghz and run the test again.  Now core 1 and Core 2 both run at 4.9Ghz.  That's when I made this post.  It seems that you can NOT OC core 1 by itself.  Just throwing that out there.
#45
arestavo
CLASSIFIED ULTRA Member
  • Total Posts : 6916
  • Reward points : 0
  • Joined: 2008/02/06 06:58:57
  • Location: Through the Scary Door
  • Status: offline
  • Ribbons : 76
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/06/05 17:27:35 (permalink)
FunktasticLucky
Just curious if anyone else has noticed a weird bug in per core overclocking?  I decided to try the new per core vcore and completely dial in my 10940X to get at least 5Ghz on a couple of cores at a minimum.  So I started with core 1 and set it to 4.9Ghz.  The other cores were set to 4.5Ghz while testing stability when I noticed that Core 1 won't actually boost to 4.9Ghz.  It stays at 4.5Ghz with the rest of the cores.
 
Now it gets weird.  I went in and set Core 2 to 4.9Ghz and core 1 to 4.5.  Fire up windows run Cinebench R20 and Core 2 boosts to 4.9Ghz immediately.  So I go back in and set core 1 to 4.9Ghz and run the test again.  Now core 1 and Core 2 both run at 4.9Ghz.  That's when I made this post.  It seems that you can NOT OC core 1 by itself.  Just throwing that out there.



Yes, and with a 10940X. For me it was 4.9GHz on two cores, and the rest set to 4.5 - yet one core, I forget which, was stuck at 4.3. I gave up on per core overclocking.
 
Out of curiosity, do you also get varying levels instability when setting your mesh multi to anything other than auto?
#46
Merilwen
New Member
  • Total Posts : 35
  • Reward points : 0
  • Joined: 2012/06/27 14:32:32
  • Status: offline
  • Ribbons : 0
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/06/06 14:39:35 (permalink)
With v1.23 on the FTW K is anyone having problems with the BIOS not seeing a 64+ USB drive in Boot Override that was prepared using the Windows Media Creation Tool?  I've tried multiple known working drives (including the one I used to install Windows 10 1909) and I can't get it to show to install Windows.  But if I go into BIOS Update I can see the drives just fine.  I've also verified that the partition created is marked as an Active, Primary, Fat32 partition.  Granted the MCT only creates a 32gb partition (Fat32 max supported size) that shouldn't be an issue.
 
Any ideas?
 
Thanks
 
Edit:  I did try both USB 2.0 and 3.0 ports.  I seem to recall this was an issue I had on my old Z170 FTW until a more recent BIOS update allowed me to use a 64GB flash after the 16GB one I had prior ended up dying.
post edited by Merilwen - 2020/06/06 15:12:49
#47
lmatyja
Superclocked Member
  • Total Posts : 180
  • Reward points : 0
  • Joined: 2017/10/14 08:45:06
  • Status: offline
  • Ribbons : 1
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/06/09 08:32:54 (permalink)
could you add a ram option at 4100 MHz from the divider? not for bclk
#48
vertex72
New Member
  • Total Posts : 42
  • Reward points : 0
  • Joined: 2018/08/28 10:32:16
  • Status: offline
  • Ribbons : 0
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/06/15 00:57:35 (permalink)
there is some issus on evga x299 micro 2 bios, bios 1.16
bad cpu core per core voltage mapping,
 
with a i9 9820x
Core 1 bios = core 2 OS
Core 2 bios = core 3 OS
Core 3 bios = core 4 OS
Core 4 bios = core 5 OS
Core 5 bios = core 9 OS
Core 6 bios = core 6 OS
Core 7 bios = core 7 OS
Core 8 bios = core 8 OS
Core 9 bios = core 1 OS
Core 10 bios = core 10 OS
 
and E-leet is not compatible with this motherboard.
and Core 9 voltage (Core 5 in bios) can't be set after 1,05v, it's allways 1,198v 
 
 
#49
arestavo
CLASSIFIED ULTRA Member
  • Total Posts : 6916
  • Reward points : 0
  • Joined: 2008/02/06 06:58:57
  • Location: Through the Scary Door
  • Status: offline
  • Ribbons : 76
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/06/15 06:36:18 (permalink)
vertex72
there is some issus on evga x299 micro 2 bios, bios 1.16
bad cpu core per core voltage mapping,
 
with a i9 9820x
Core 1 bios = core 2 OS
Core 2 bios = core 3 OS
Core 3 bios = core 4 OS
Core 4 bios = core 5 OS
Core 5 bios = core 9 OS
Core 6 bios = core 6 OS
Core 7 bios = core 7 OS
Core 8 bios = core 8 OS
Core 9 bios = core 1 OS
Core 10 bios = core 10 OS
 
and E-leet is not compatible with this motherboard.
and Core 9 voltage (Core 5 in bios) can't be set after 1,05v, it's allways 1,198v 
 
 


Can't remember who it was that said this, but if you try and set a lower multiplier for per core than the stock turbo boost, the stock turbo boost voltage will be used with adaptive voltage settings set.

I had this problem with a 10940X and setting a multiplier lower than 48 for per core overclocking (turbo boost 3's boost is a 48 multiplier). I ended up using forced override voltage instead to use lower than 1.2V and have it actually use the voltage specified.
post edited by arestavo - 2020/06/15 06:39:10
#50
vertex72
New Member
  • Total Posts : 42
  • Reward points : 0
  • Joined: 2018/08/28 10:32:16
  • Status: offline
  • Ribbons : 0
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/06/15 08:18:06 (permalink)
my cpu is turbo max at 4,2ghz on 1-2 core (TB3) , all core at 4ghz, with my OC i can go to 4,5 to 4,9 ghz but I have 1 core who can't be set to a value other than 1,198v in bios( it's the hottest core)
 
I can do with max temp < 90°C (via xtu because core 1 set to my cpu a ratio limit all other core)
Core 1 - 4,7 - 1,24v 
Core 2 - 5,0 - 1,31v --> can't be set at this value via bios because core 1 limit other ratio to his value 
Core 3 - 4,5 - 1,15v 
Core 4 - 4,5 - 1,15v
Core 5 - 4,7 - 1,24v 
Core 6 - 4,9 - 1,28v --> can't be set at this value via bios because core 1 limit other ratio to his value 
Core 7 - 4,5 - 1,15v 
Core 8 - 4,7 - 1,24v
Core 9 - 4,4 - 1,1v --> can't be set at this value via bios because only 1,198v can be set (so 4,6ghz with 100°C instead of 88°C ...)
Core 10 - 4,7 - 1,24v
 
#51
Doscomp
New Member
  • Total Posts : 8
  • Reward points : 0
  • Joined: 2019/04/23 18:22:46
  • Status: offline
  • Ribbons : 0
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/06/18 08:20:30 (permalink)
Hi there today i updated my ftwk x299 with the new 1.23 bios but now the pc freezes at random, never had this for over 2 years with bios 1.17, any thoughts.
 
regards
#52
Jorgp2
New Member
  • Total Posts : 2
  • Reward points : 0
  • Joined: 2019/12/12 16:49:51
  • Status: offline
  • Ribbons : 0
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/06/19 16:33:38 (permalink)
arestavo
FunktasticLucky
Just curious if anyone else has noticed a weird bug in per core overclocking?  I decided to try the new per core vcore and completely dial in my 10940X to get at least 5Ghz on a couple of cores at a minimum.  So I started with core 1 and set it to 4.9Ghz.  The other cores were set to 4.5Ghz while testing stability when I noticed that Core 1 won't actually boost to 4.9Ghz.  It stays at 4.5Ghz with the rest of the cores.
 
Now it gets weird.  I went in and set Core 2 to 4.9Ghz and core 1 to 4.5.  Fire up windows run Cinebench R20 and Core 2 boosts to 4.9Ghz immediately.  So I go back in and set core 1 to 4.9Ghz and run the test again.  Now core 1 and Core 2 both run at 4.9Ghz.  That's when I made this post.  It seems that you can NOT OC core 1 by itself.  Just throwing that out there.



Yes, and with a 10940X. For me it was 4.9GHz on two cores, and the rest set to 4.5 - yet one core, I forget which, was stuck at 4.3. I gave up on per core overclocking.
 
Out of curiosity, do you also get varying levels instability when setting your mesh multi to anything other than auto?




I came here to see if anyone also had an issue with per core overclocking, just got the x299 dark again due to my x299 Taichi XE not supporting a negative voltage offset for per core overclocking but now per core overclocking doesn't seem to work at all.
 
Edit: Had to OC three cores
 
Edit: The feature is completely broken, changing a different core lowered the clockspeeds for every core
post edited by Jorgp2 - 2020/06/19 16:56:54
#53
lmatyja
Superclocked Member
  • Total Posts : 180
  • Reward points : 0
  • Joined: 2017/10/14 08:45:06
  • Status: offline
  • Ribbons : 1
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/06/20 00:47:08 (permalink)
I have the same problem, but it is also a problem in the cores, this is my 5 piece 10920x and each time one core is 0.050 / 0.070v higher than the other and he also causes that I can not use correctly per core voltage and the problem is also with per core multiplier, I can't give a single core a different number because it returns to 43 at allI have the same problem, but it is also a problem in the cores, this is my 5 piece 10920x and each time one core is 0.050 / 0.070v higher than the other and he also causes that I can not use correctly per core voltage and the problem is also with per core multiplier, I can't give a single core a different number because it returns to 43 at all, and no one answers it, no one knows what to do about it.
post edited by lmatyja - 2020/06/20 00:54:14
#54
lmatyja
Superclocked Member
  • Total Posts : 180
  • Reward points : 0
  • Joined: 2017/10/14 08:45:06
  • Status: offline
  • Ribbons : 1
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/06/21 03:18:43 (permalink)
Oki and why adaptive ignor my value ? if i give another voltage, he work like OC robot give same voltage ?????
#55
Jorgp2
New Member
  • Total Posts : 2
  • Reward points : 0
  • Joined: 2019/12/12 16:49:51
  • Status: offline
  • Ribbons : 0
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/06/24 07:21:05 (permalink)
Any idea what going on with the per core oc?
#56
ironage
New Member
  • Total Posts : 87
  • Reward points : 0
  • Joined: 2008/05/10 08:48:31
  • Status: offline
  • Ribbons : 1
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/06/28 05:44:59 (permalink)
I have got the exact same problem with my 10900X and Per Core Voltage, all Cores running 43x, when i have set 45x in the bios. (non-AVX Full Load)
Frankly said i am getting fed up with the bugged EVGA UEFI Bios.
post edited by ironage - 2020/07/01 06:28:24
#57
wimpievanzyl
New Member
  • Total Posts : 21
  • Reward points : 0
  • Joined: 2019/07/01 05:06:46
  • Status: offline
  • Ribbons : 0
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/07/05 06:36:18 (permalink)
Hi can anyone tell me if there is a XOC BIOS available that are compatible with the 10980xe? The two XOC bioses on the xdevs site throughs the df post code when flashed to any of the BIOS chips. Any help will be greatly appreciated 
#58
rjohnson11
EVGA Forum Moderator
  • Total Posts : 102313
  • Reward points : 0
  • Joined: 2004/10/05 12:44:35
  • Location: Netherlands
  • Status: offline
  • Ribbons : 84
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/07/05 06:56:36 (permalink)
Your post was stuck in the spam filter so sorry for the delay

AMD Ryzen 9 7950X,  Corsair Mp700 Pro M.2, 64GB Corsair Dominator Titanium DDR5  X670E Steel Legend, MSI RTX 4090 Associate Code: H5U80QBH6BH0AXF. I am NOT an employee of EVGA

#59
ZoranC
FTW Member
  • Total Posts : 1099
  • Reward points : 0
  • Joined: 2011/05/24 17:22:15
  • Status: offline
  • Ribbons : 16
Re: BIOS Updates for X299 Dark (1.23) / FTW K (1.23) / Micro ATX 2 (1.16) / Micro ATX (1.2 2020/07/08 22:33:49 (permalink)
Size of drives with 4Kn sectors is reported incorrectly. Below screenshot is 16TB drive reported as 2TB in size. This indicates size is calculated as number of LBAs * sector size but sector size is assumed / hardcoded as 512 bytes.
 
I understand why fixing this wouldn’t be highest priority but 4Kn drives have been around for years so I can’t see why it would be left as still incorrect (not to mention that implies part of code hasn’t been revisited for years).
 
Also, I feel size should be reported in number of LBAs rather than GB figure because first one is exact while other one is not exact (it is approximate / “rounded”). As side benefit programmer wouldn’t have to deal with cluster size anymore.
 

#60
Page: < 12345 > Showing page 2 of 5
Jump to:
  • Back to Mobile