Jump to content
HWBOT Community Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

14 Good

About Falkentyne

  • Rank
    kitchen robot


  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The problem here is that some people are posting load voltages during CB R15/R20, while others are posting BIOS set voltages. We need consistency. If people are going to do that, at least do what Nik did above me and show your idle and load voltages so we have something to go on. There is a MASSIVE Difference if you get 1.28v at load during CBR20 @ 5.3 ghz and then claim that's your BIOS voltage.... A Bios voltage of 1.30v at 1.3 ghz is going to droop down to about 1.2v at load with an aggressive LLC...I don't even think a super golden chip can handle that unless it's below ambient.
  2. Interesting. So the worse bin (higher VID, lower SP) chip scaled better on LN2 (less vcore on LN2) than the lower VID chip? Do most chips follow something close to his?
  3. All these are @ load voltages measured and not bios set voltages, right?
  4. Thank you, Spalve. 1.34v is measured load voltage or voltage set in BIOS?
  5. Hi, I have a request for you guys, the Bios team, and Hicookie. It is rather important! Right now, access to the Intersil VR ISL69269 doesn't have read access. Martin (HWinfo64) looked at the debug dump and could not find an accessible VRM. If this VRM is accessible, accurate voltage, current and power monitoring through VR VOUT, IOUT, and POUT can be added into HWinfo (and also into System Information Viewer, "SIV", the third party program), just like in Gigabyte's Z390 boards. Can you guys make a BIOS update for the Aorus Master, Extreme, and other 69269 boards, so we can get proper, accurate power monitoring by unlocking read access to the VRM? The competitors (Asus, MSI) have access to "Die-sense" voltage readouts via their Bios, so it would really awesome if you guys could re-enable access to the VRM. Thank you! (I'm using both a Z490 Master and M12E)
  6. For 24/7 use on ambient cooling, you want to stay in the voltage range based on this curve: 1520mv - (2.1 mOhm * IOUT) IOUT <=138A If you're using fixed voltage in BIOS + Loadline calibration, then you need to first know your current draw. Once you find that, plug your current draw into the top formula where IOUT is a variable and you will get your absolute max safe vcore. Then you can calculate what bios voltage you should be running to stay below that max safe voltage point like this: Bios set voltage - (LLC mOhms * IOUT)=load voltage. LLC mOhms is based on a starting value of 2.1 multiplied by a percentage, with lower numbers meaning less vdroop. Intel spec is 2.1 mOhms of vdroop (1.6 mOhms for 9900k/9700k) So 50% reduced vdroop is 1.05 mOhms. This is Level 5 LLC on Asus boards and LLC=Turbo on Gigabyte and 50% reduced vdroop on eVGA. If your motherboard supports current monitoring via Asus EC or VRM monitoring by VR VOUT, then you can get Current from HWinfo64 easily. And you can use VR VOUT for accurate load voltage and cross reference it with the top formula. That's all there is to it. You get difficulties on boards that do not have "Die-sense" vcore readings and no amps (current) monitoring. That i can't help with. Asus recommends about 1.35v Bios set with LLC6 or 1.40v Bios set with LLC5 on their boards.
  7. What's your opinion about the changes to the 12 Apex vs the 11 Apex visually or build quality? Are the VRM phases the same, besides increase in power stages to 70A?
  8. Eurocom hasn't been a Prema partner for a long time now.
  9. Glad you recovered your board. Enjoy.
  10. Ok, I know that you can SHORT pins 6 and 7 (with a mini screwdriver) on the primary BIOS (the pins across from the pin marked as 1 with the marking) to force the board to boot from the backup BIOS instead. Try this first and see if it works. If it doesn't, then try shorting pins 6 and 7 on the backup BIOS. One of these should make the board boot. I think the problem is that if you only crossflash ONCE, there are some bugs that C_N found out over on xtremesystems, and a few others found out too; namely, that PLL Overvoltage doesn't work, and the board doesn't seem to save voltages properly (or maybe initialize them) until it is powered off. You have to reflash a second time (a non modded BIOS? Not sure if you need a non modded BIOS or not, but it's safest NOT to flash the modded BIOS a second time) for this to work properly. If you used a modded BIOS to do the crossflash, and then flashed THAT code to the backup with alt-f12, I could see how this could kill the board. Also keep in mind that the B2 UD5 has a hardware flaw with LLC that is not bios correctable--it was corrected with the B3 board only.
  11. Wait, are you sure? LLC1 on the B2 bios would overvolt by 0.05V+ over 1.4v, and LLC2 would overvolt by 0.15v and crash the system. This was fixed on F1 BIOS on the B3 board...so the B2 board crossflashed with F3g doesn't overvolt with LLC1 anymore?
  12. Big question is Does that mod for B2->B3 fix LLC1 on UD5? Wonder why no B2 version fix ever came out...when F1 version of B3 was dated OLDER than the latest B2 beta? Was LLC1 overshooting on B2 a BIOS problem or was it hardware?
  13. He didn't test the B3 bios with the B2 board, though. The above poster has a B3 board.
  14. Hi, CPU-Z 1.57 is reading the Vcore as VTT on my gigabyte B3 stepping P67a-UD5. Is anyone else having similar problems with B3 boards? It read correctly on B2. Does anyone have access to contacting the author about this problem?
  • Create New...