Jump to content
HWBOT Community Forums


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by pepinorang

  1. Actually it is already there, but it seems I cannot get it working: OC MENU > BETA RUNNER > REAL THREAD Maybe you could try with an XP drive that is already ACPI?
  2. If I ask you screenshots and detailed info it is to help you and investigate your issue, otherwise I wouldn't even waste hours to answer you everyday! I'm not in charge of MSI forums and don't even have a member account there, it's FAE's work not mine, thus I don't know what is going there. Why buy anything new when you can RMA your parts easily? Your CPU probably has nothing to do in this neither, please stop over-exaggerating! Please show the post where I talked about IMC, there is NONE so please don't invent things, you misread and/or misunderstand! If that's your call, then why do you even come here to complain if you don't want my help?! You have prove NOTHING yet, no screens, no evidences, no detailed info about your setup, ABSOLUTELY NOTHING, despite me asking for it several times! In 1.51 auto rules for timings have been changed (as mentioned to GunnzAkimbo in this post http://forum.hwbot.org/showpost.php?p=445341&postcount=313) Some are probably loser for better compatibility, which would explain that a defective memory module can boot easier than with the previous version. Once again, BASELESS assumptions! This is the only mention about memory in the detailed change log (which you don't have access to): "Fix system OC fail issue when use Avexir DDR4-3000 CL17 8GB memory and XMP is Enabled." You mentioned your work as an engineer as your ONLY argument, as if YOU were the god here and that was explaining all, please don't try to reverse roles now! BTW, as an IBM engineer, maybe you can explain to me how a BIOS flash can kill only 1 memory module out of 4, I'm REALLY curious... Can you imagine how much motherboards MSI is selling? How much systems are built by System Intregrators with our boards? Just because you and another guy in some forums say that they have this issue without providing any detailed information on their setup nor any evidence on the issue means that this is a really caused by our BIOS update. If only you had provided what I have asked many times since the beginning, I could try to reproduce your issue but you never did, so tell me what I'm supposed to do?? Thanks for the link, however did you even read this thread? I did read all the 7 pages and there is only 1 guy in this thread (OP) with the issue you describe. Once again, the guy seems to have a limited technical knowledge, he oes not provide any detailed info on system specs, no screens, no evidence and all other posts are either replies to help him or other minor issues not related to yours which some are not even related to memory! P.S: I have spent 3h on your case this morning, so please next time you answer to me, cut the trolling/BS and do provide detailed information about your issue as I've asked you so many times that I can't even remember, so we can finally move forward and investigate your issue!
  3. Oh ok my bad, I was mistaking between the 5960 and the 5820. So indeed, it was CPU related, however why not RMA it to Intel? If as you say this was caused by a BETA BIOS update provided by FAE, why not ask MSI to replace it then? Could you send me the Support ticket number that was provided to you and the FAE contact you dealed with in MP? I'd like to investigate on that, thanks!
  4. What voltage mess are you talking about? Any proofs? (screenshot or video) I already explained in a previous post that the BIOS was removed because of Broadwell-E, you should ALL stop making baseless assumptions pulled out of thin air! It's your argumentation that is hilarious, no technical facts, no proofs? It's just possible because you are "engineer at IBM"? AWESOME! Re-read my post, I never talked about IMC but IC (aka memory chips), I though an "engineer at IBM" would know the difference. Show the threads, provide me proofs and technical facts, then I'll look into it... So far it's just a bunch of hearsay from users with limited technical knowledge that still assume they know it all.
  5. So the CPU wasn't damaged by the board if it was working fine other motherboards... If BIOS wasn't the cause, you probably had some issue with MB voltage controller, either corrupted firmware or defective IC.
  6. Seriously, you are just asking the same questions again and again in a different way. I already answered all with technical facts, one last time: 1. Please re-read previous post below, it has already answerer to your questions. All X99/Z170 motherboards behave the exact same way besides only MSI latest models have XMP LED. 2. That's up to you but it's not the way it's meant to be. 3. See 1. Or you can just leave your PSU ON like 99.9% of users out there... I already explained to you with technical facts from our engineers that it's not a bug, but you still prefer to assume you are right? OK...
  7. 1) You misread my explanation, Intel ME don't forget these configuration, that's the opposite. Because the saved configurations inside Intel ME might need to be updated, it double post to reset/update/save them. 2) You are not supposed to turn OFF your PSU each time your turn OFF your computer 3) Old ME versions didn't have this behavior but with newer Intel ME, ALL the X99/Z170 motherboards share this behavior. 4) See 1). Seems more like a BIOS issue... Anyway as said previously it's the BIOS/MB that controls the voltages (AUTO or manual), not the CPU. The full change log is always confidential, but for this one most change are related to Broadwell-E and bug fix. Here is what I can list: - Fix system OC fail issue when use Avexir DDR4-3000 CL17 8GB memory and XMP is Enabled. - Modify auto adjust DRAM timing related code. - Modify auto adjust CPU Base Clock related code when use over XMP 3300MHz memory for Haswell-E CPU. - Fix Intel SSD 750 S3 issue. LOL, all I can say is re-read my explanation... It's not possible and I already explained you why. Double flash is 200% useless unless Intel ME update went wrong or it has been corrupted with BCLK OC, in which case any BCLK change would fail or result in 100MHz. Since your memory hasn't been killed by "one of the bios updates after 1.1", which as I explained in a previous post with technical facts to someone else is IMPOSSIBLE; it's probably time to edit or delete your previous post, don't you think? Anyway, if I was you I would still try to run MEMTEST with all modules installed/detected at XMP, just to be sure as you may have one or more defective IC that cripple your kit. Higher capacity/frequency kits are more affected by this than others.
  8. First page updated with latest Softwares and BIOS. New XOC BIOS takes a lot more time than I expected as R&D is busy with next gen, but it will be ready around mid-may at very least. As I mentioned before, new XOC BIOS will be ACPI compatible, include 15 new memory presets for D-Die/E-Die/B-Die/MFR/AFR and fix ALL the bugs of HOT v2. In short, it' will be one to rule them all and I doubt another one will be needed until Kabylake or new competitive memory ICs are released. For Non-K OC, you can now use OFFICIAL/BETA BIOS, when Non-K CPU will be installed, BIOS will automatically switch to microcode and display an hidden menu named "Beta Runner". In this menu you have to enable the "NOC" option and your Non-K CPU will fly! BIOS screenshot, courtesy of Der8auer's MSI Z170 Non-K OC Guide:
  9. First page updated with latest BIOS & Software versions. :celebration: The TEST BIOS versions were requested by overclockers that work closely with us to test some OC features, ideas and/or remove some limitation, they were never meant to be released officially. After plenty of top scores were submitted with those BIOS, complains started to grow because 99% of the extreme overclockers here didn't have access to those "special" BIOS. Thus, we decided once again to show our support to the HWBOT XOC community and did "a favor" to them by sharing those TEST BIOS on the forum. Everything that was tested/unlocked in TC7/TC8 has been implemented into the OFFICIAL/BETA BIOS long time ago and bugs have been fixed as well. So in fact, that is the exact OPPOSITE of no vendor support! "Auto selection of voltages wasn't working anymore" What do you mean exactly, in details? Anyway, there is no such thing as an "auto voltage selection part" in any CPU. The auto voltages are controlled by the BIOS, not by any part of the CPU.
  10. So, I've got a chat with the R&D guys about this double post behavior, see below. 1) Action: Turn PSU OFF and discharge the MB, then turn PSU and MB ON. Behavior: POST will stop at code 33, shut down and reboot: Explanation: This is related to the XMP LED (on the lower right corner of OC Genie button), the BIOS need to shut down to initiate the BIOS code related to the XMP LED. 2) Action: Clear CMOS Behavior: MB will POST, then shut down before Windows loads and reboot Explanation: This is for Intel ME to save current PCI-E lane switching and related configurations to ensure all PCI-E devices work well. For e.g. without this mechanism, if all your PCI-E lanes are occupied and you clear CMOS + Remove some of the PCI-E devices, when you will turn ON the MB again the current PCI-E lane switching and related configurations will not be the same as the configurations saved in ME, which may cause issues with the PCI-E devices installed. 3) Action: Changing “the M.2 source link†between “auto†and ‘’PCH†in BIOS Behavior: MB will POST, then shut down before Windows loads and reboot Explanation: This is the same situation as 2. More generally, if there is any change related to PCI-E, the double post behavior will happen for Intel ME to save the new configuration.
  11. What do you mean by powered down and discharged? PSU switch off and no more juice in the motherboard? That actually might be similar for ME as well but I'm already checking this with R&D.
  12. Yes, as I said above the double post is normal after CLEAR CMOS. The board will POST once, then reboot right before loading OS and POST again without training the memory. This happens because after each CLEAR CMOS the Intel ME firmware included in BIOS also needs to be reset. That wasn't the case with old versions of Intel ME but it's been a long time already that it behave like this. However you said it's happening after turning of the PSU and that might be a bug, let me check this and get back to you asap!
  13. That's not the issue that you described in your previous post but anyway, it wouldn't happen if you strictly follow the correct flashing procedure. You can find an HOW-TO video on the first page along with MP/BETA BIOS versions (It's for Z87 but there is no major difference with X99): In fact this bug wasn't really a bad thing since it helped you and many others to achieve higher Ring frequency without any knowledge about required settings. The downside was that auto-rule was taking over manual settings of vRING and vRING OC1/2, which could be annoying if your CPU needed more or less volts than said auto-rule. However, the absence of this bug in MP/BETA BIOS wouldn't have been an issue for you if you did a little research about what voltages were required for Ring OC, which I posted along with max volts for 24/7 about 5 times in this thread now. But you are right, 5 times is probably not enough and I should probably post a full X99 OC guide on the front page. The Ring auto-rule bug was only present in the non-official XOC TEST BIOS TC7/TC8 which are about 1 year old now! Please, tell me what's not clear in this: ***WARNING : A TEST BIOS IS EXACTLY WHAT ITS NAME IMPLIES AND MIGHT CONTAIN SOME MINOR BUGS. HOWEVER THEY ARE OPERATIONAL AND MIGHT ALSO IMPROVE OC/COMPATIBILITY, SO USE THOSE BIOS AT YOUR OWN RISK, MSI CANNOT BE HELD RESPONSIBLE! FPT is required to flash Test BIOSes, you can download it from this thread: X99 BIOS, facts, stats and list of mainboards*** And I don't understand what you mean by "mature", at Computex 2015 we did about 10 GFP on this board with TC7 and BIOS only got better since then. There's no issue with the current MP/BETA BIOS and each new version improve memory compatibility as we keep validating new memory kits in QVL. I'm curious about "your first golden cpu that was crippled by our beta bios which you got directly from msi to fix a problem", please DO elaborate, I'm all ears... Glad it worked for you, as usual these settings are just a base and voltages need to be fine tuned depending on CPU quality. Yes, as I said above in TC7/TC8 the auto-rule table I posted before will apply no matter your manual settings, thus it will (almost) always manage to achieve good ring frequency.
  14. What you describe is a normal behavior after CLEAR CMOS, that is the Intel ME firmware that does this as it needs to be reset. However you seems to encounter this behavior at every boot after normal power off (which is not normal), is it correct?
  15. So you don't follow the correct flash procedure and encounter issues and that's the manufacturer's fault? I see... This has been discussed many, many, many times (last time 5 pages ago), I'm growing tired of people that don't make the effort of a little research in this thread! In TC8 (a TEST BIOS for XOC which as warned by the disclaimer on the main page, may contain bugs) the auto-rule is crippled and it will increase Ring voltages depending on ring ratio, despite of your manual settings. Which is why you could achieve 4.8GHz Ring with those settings, in reality Ring voltage with 48x ratio was 1.45v not 1.15v (which would never suffice to stabilize at that 4.8GHz). In newer BIOS versions, the ring auto-rule is working properly and you have to set some voltage manually, which you are doing totally wrong: - Ring 1.15v = It will never get you to 4.8GHz, check the Auto-Rule table below to give you an idea of what is needed. - Ring OC1 1.5v = This is not needed and might be dangerous for the CPU, 0.95v or AUTO is more than enough! - Ring OC2 1.5v = That is more like it but this might be too much on aircooling, as said several times in previous page, my recommendation is vRing 1.25v~1.3v and Ring OC2 1.4v~1.45v for 24/7
  16. You should not need to lose timings if the kit is on the QVL list. Setting proper SA/IO and in some case vDIMM should be sufficient to get memtest stable. Once again, what is a "double post cold boot issue" you never detailed it so I don't even understand what you mean with this... What I meant is that v1.3 had a bug with Broadwell-E not related to MSI, we fixed it and quickly released the better BIOS v1.4. For Official BIOS releases: http://www.msi.com For BETA/TEST OC BIOS: This thread (I'll update it later today). But once again Why update BIOS if your setup is working properly?! There is no valid reason to this, unless specified by MSI...
  17. I just tested X99A XPOWER AC/X99A GODLIKE GAMING/X99A GODLIKE GAMING CARBON in a row with latest BIOS versions available and G.SKILL TridentZ 3866, Corsair Vengeance 2666, Corsair Dominator Platinum 2800, HyperX Predator ES 3333, HyperX Predator ES 3466: XMP is working perfectly fine here. If I understand well your OC issue, it's that your memory isn't fully stable with XMP enabled and you randomly need to increase vDIMM to boot, correct? What are your memory model number, specs and nominal voltage? I can't understand why you are updating your BIOS if your setup was already working properly then?! Moreover, if new BIOS create issues on your setup why not go back to the previous version which apparently was fine for you? BIOS 1.3 was pulled out of the website for an issue which is not related to MSI and unless you have access to an early ES Broadwell-E CPU sample, it didn't even concern end-users. Please elaborate your "problems with the board are all over the place", each separately and clearly with as many details as possible on the issue, the whole setup and settings. This way I'll be able to help you properly because so far it's unclear to me. Who else has issues with the BIOS?? You are claiming that XMP is broken while davidm71_2 is unable to set a stable OC, how is that an issue?
  18. I need more info to be able to help you, could you provide the part/model number of your memory and your complete current OC settings? Are you also experiencing similar crashes in other games/softwares? I think you should see it the other way around: Be confident that we have been able to quickly fix an issue and release a better BIOS version shortly after it was noticed. What was (is?) your "double post cold boot issue" in the end? I remember that you have complained several times about it in previous posts, but you never detailed it clearly to me thus we couldn't even try to reproduce it! How can you claim this is true without any proof? Here is some technical fact for you: That is not even technically possible, as updating BIOS doesn't have any access to RAM, only to BIOS EPROM. The only possible way that a BIOS version could kill memory is if the JEDEC SPD auto-rule was broken and sets crazy high voltage, which is not (As mentioned above I just tested 5 kits with this BIOS and all are alive and working fine). In that very unlikely case, ALL memory modules would be affected and we would have noticed excessive voltage in validation process, before the BIOS would have even be released.
  19. None of the Official BIOS will lock your Non-K CPU, don't worry. When there is a Non-K CPU installed, BIOS will display an hidden option named "Beta Runner" in which you need to enable the option "NOC". If this does not happen it means the BIOS is not new enough and doesn't have the feature implemented. BIOS picture, courtesy of Der8auer's MSI Z170 Non-K OC Guide: http://overclocking.guide/updated-msi-z170-non-k-overclocking-guide-new-bios/
  20. If you are using AFR, it's probably Kingston own auto-rule. They have asked 1.8v max to not damage ICs.
  21. No it's not. I can make a table for ASUS/ASROCK/MSI if it's ok with Nick.
  • Create New...