Jump to content
HWBOT Community Forums

dreamcat4

Members
  • Content Count

    24
  • Joined

  • Last visited

Community Reputation

18 Good

About dreamcat4

  • Rank
    maintenance bot

Recent Profile Visitors

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

  1. Hello. During my BIOS mod today, I have had the opportunity to confirm that it is using 4x phase doublers. They are 4x IR3599s on the main Vcore, as you can see with the photos attached. The silkscreen says PU10x0, and there are no markings for 3 of them. However the 4th one PU1040 does carry a clear marking. And the package size and type matches the only package that the IR3599 comes in, the locations are where you would expect them to be etc. There is no possible way that this board does not use IR3599s. Without any doubt.
  2. correct. ...still waiting for somebody to confirm whether this board is a doubled or a true 8 phase. Actually I can inspect mine today. So just wondering what I should be looking out for? There was some other way were were going to verify this. Ah: "What would be nice then is to try to CONFIRM that the other 2 phases for the igpu are coming from a completely different VRM controller (than the main vcore one). Because if the vcore is a true 8 phases, and it is an Asus rebrand of an IR35201.... then there should be 0 phases left on it for the igpu vrm --> needs a seperate controller."
  3. Please tell us if you can what else was changed. It would be nice to hear about these other differences. It may be helpful to know about when running the new 10's BIOS on the 9.
  4. Yeah man. This has also confused me too for a very long time indeed! According to the german vrms list here https://www.hardwareluxx.de/community/f12/lga-1151-mainboard-vrm-liste-1175784.html It says that it should have 4x IR3599 "Doppler" (="Doubler" in english) But here is the part Buildzoid's video where he comes to the same initial conclusion as yourself: What would be nice then is to try to CONFIRM that the other 2 phases for the igpu are coming from a completely different VRM controller (than the main vcore one). Because if the vcore is a true 8 phases, and it is an Asus rebrand of an IR35201.... then there should be 0 phases left on it for the igpu vrm --> needs a seperate controller. Hopefully you can take another look! Many thanks because so many people keep saying it's just a doubled 4 phase and I truly don't know still. Would try to look myself but it's my main system here. So unfortunately cannot dismantle / examine.
  5. [NOTE] New 2003 mod bios file is attached at the very bottom of this same post. Please download / save for later. However before flashing / updating, please read through very carefully and fully all of the post here, for the changelog information. Since this new BIOS includes new update(s) from Intel !!! And personally, as for myself I don't actually know what they actually are yet... Hello again. Well it seems yesterday @dsanke has released new BIOS updates for some of these ASUS boards. Including this one. He did not include his normal summary information this time. But instead put: dsanke Changes the same as before. So therefore the only difference between this 2003 revision and the previous 1901 BIOS should be whatever the manufacturer, ASUS has added. And remembering that this is actually a modded the Apex 10 bios. So that actually made me curious enough to bother checking what might be in it. Also because the version number seems like it is significantly higher now. The original files are available from here: https://www.asus.com/Motherboards/ROG-MAXIMUS-X-APEX/HelpDesk_Download/ Unfortunately (unlike in their previous updates), ASUS did not tell us what was changed in this latest update. Wheras the previous 2 updates from ASUS did at least include some partial information, for what was improved: Here I am just copying from a previous information which was included with the earlier '1901' BIOS. Assuming that nothing @dsanke has done has changed: Author: @dsanke Motherboard: ASUS ROG MAXIMUS IX APEX Based on:ASUS ROG MAXIMUS X APEX 2003 ME: 11.7.0.1229 Microcodes: The same as original M10A BIOS. Note: Flash via SPI Programmer. Support All LGA1151 CPU except Xeon and Skylake ES. AURA/SLI Fixed. ==== $ md5sum * 4904b53e1dceb1ac217e590bd43c7d69 ROG-MAXIMUS-IX-APEX-ASUS-2003.7z 9baf6299714bff49eb766bf48e7177bd ROG-MAXIMUS-IX-APEX-ASUS-2003.bin Anyhow, coming back to the missing changelog from ASUS... @dsanke also updated these 2 other ASUS boards. All together. And for *those other 2 boards*, they *do* include information in their changelog entries. And the other '2003' bios (for the Maximus 10 Hero) shares the same exact upload date. As the apex. https://www.asus.com/us/Motherboards/ROG-MAXIMUS-X-HERO/HelpDesk_Download/ So perhaps it was just an innocent error / forgot. Since the similar Hero board does explain it's changelog: But it also shares exactly also the 2 previous changelog entries. So this really does strongly suggest that ASUS does try very hard to keep these 2 boards in-step / always together. So then, the 2003 update includes 4 new changes. Vs the 1901, which was purely for compatibility with new intel processor SKUs. The ASUS changes are: * "Improve System Performance." * "Updated ME FW." * "Updated Intel commit for security." * "Updated RAID driver." Whatever that means. @dsanke mod bios for Apex 9 attached. Please discuss, it should be possible to find information elsewhere (from other sources) for what the middle 2 are all about. Kind Regards. Just a quick note: FWIW It almost seems as-if the increment of the minor version number reflects the number of different and unique feature (or bugfix) changes. That have been made since the last update. For this update, if we ignore and discount the "Improve System Performance" at the top. And assume that point 1 references the points 2 & 4 being the things that are 'improving' the performance. Then that leaves us with 3 different / unique changes in the clangelog here... And the last 2 digits are '03'. Wheras in the previous BIOS update, it was '01' and there was only 1 unique change. And then the 1st 2 digits counting and incrementing the major BIOS version (18, 19, 20). So therefore 2003 = "the 20th BIOS update, and it includes 3 new changes". Would appear to be the ASUS naming scheme is here. And for all of their other motherboards (and other types of devices too!). Unless I am mistaken about that. Anyhow thanks to @dsanke for continuing to update this BIOS. Keeping it current with the latest. Although he still seems to be unable to register an account at this forum, for whatever technical reason(s) he cannot be here. ROG-MAXIMUS-IX-APEX-ASUS-2003.7z
  6. Oh. Well you can check if the pinout is correct by using a multimeter, and probing the resistance between each pin and the corresponding pin on the SPI chip. I am not sure how the jumper to select the A or B bios. But maybe it just affects only 1 of those pins, like the !CS (spi chip select). Which is shown here to be pin #1 on the SPI chip, and pin 5 on the header. Also check it with the multimeter.
  7. That isn't actually what 'degraded' is supposed to mean. It's supposed to mean something other than comparing 2 entirely different motherboard. Which are never going to yield the same performance (despite both of them being very decent overclocking boards). Also I am just wondering what part of the motherboard exactly do you believe has degraded? The smoothing caps on the DDR4 memory channels? That would be rather premature given the typical ratings of those components. Assuming they are at least 2v rated caps and you have not been running a very high voltage of 2v on your ram. Or perhaps the socket contacts have gotten dirty? (because it can happen fairly easily, and they can be just as easily cleaned, and then the performance restored). Same for the DDR4 memory slot. Debris can easily get into that. This kinds of statements about degraded motherboards puzzles me when there is not really 'much else' in the pathway directly between the ram and the cpu itself. Much less anything that can actually wear out, or 'degrade', in some non-reversable fashion as you both seem to be attributing the matter to here. I'm not trying to argue that your ram speeds have not become less. Because certainly you seem to both be thinking that. Just that maybe there is some alternative explanation, that isn't really the motherboard's itself fault (as much as any other model). And can be gotten back somehow.
  8. The bios modder Dsanke has also made an 0901 now. Here it is: 4:22 PM] dsanke: Author: @dsanke Motherboard: ASUS ROG MAXIMUS IX APEX Based on:ASUS ROG MAXIMUS X APEX 1901 ME: 11.7.0.1229 Microcodes: The same as original M10A BIOS. Note: Flash via SPI Programmer. Support All LGA1151 CPU except Xeon and Skylake ES. AURA/SLI Fixed. $ md5sum *1901* 9ff2714a4b6ab8aedb5c877ff0eef8c3 ROG-MAXIMUS-IX-APEX-ASUS-1901.rar d72335f098f3654945e9502664090057 ROG-MAXIMUS-IX-APEX-ASUS-1901.rom ROG-MAXIMUS-IX-APEX-ASUS-1901.rar
  9. Just literally whatever was changed in the 10 apex. So for that, you need to consult the official apex 10 (z370) '1801' changelog / release notes. Which is being provided by ASUS, (not us).
  10. Well I never posted any BIOS made by elmor. But heres the latest one from Dsanke. See attachment. Dec 19 2018 [12:47 PM] dsanke: Author: @dsanke Motherboard: ASUS ROG MAXIMUS IX APEX Based on: ASUS ROG MAXIMUS X APEX 1801 ME: 11.7.0.1229 Microcodes: 506E0(0x18),506E1(0x2A),506E2(0x2E),506E3(0x74),506E8(0x34),906E9(0x5E),906EA(0x6A),906EB(0x5E),906EC(0x84). Note: Flash via SPI Programmer. Support All LGA1151 CPU except Xeon and Skylake ES. AURA/SLI Fixed. $ md5sum ROG-MAXIMUS-IX-APEX-ASUS-1801.7z ROG-MAXIMUS-IX-APEX-ASUS-1801/ROG-MAXIMUS-IX-APEX-ASUS-1801.bin 0c6637e1ea85f94f72dadd57c5c141b5 ROG-MAXIMUS-IX-APEX-ASUS-1801.7z 968d92d84f2869f69ca759c2452937b4 ROG-MAXIMUS-IX-APEX-ASUS-1801/ROG-MAXIMUS-IX-APEX-ASUS-1801.bin ROG-MAXIMUS-IX-APEX-ASUS-1801.7z
  11. Well I wasnt even trying to do that in the first place. My message was not intended for any such overclockers. It was intended for all the regular folk who own these publicly available OC Formula overclocking motherboards, who come here and keep asking about which pads to short / isolate. Why isolate them? And you know, 'why bother' or 'oh it's too hard and difficult to do that bit' etc. Well the only reason I bothered to comment about it in the first place was because you can't replace an LGA socket very easily.. And we are also talking about how hard to get hold of the MOCF specifically, these days. It's a pretty rare board now.
  12. This ^^. Dont avoid / take unecessary risks. Once a tiny piece of metal (LGA pin head) falls into the plastic holes, you cannot know anymore if it's shorting something out doen under there.. and there is not [really] any obvious or sure-fire way to dislodge / get it back out again. Not really worth the risk, is it?
  13. Hi there. Any of you here have flashed your apex 9 onto z370 bios already? I have a small request: Can you please run for me (as root user) the following script, under linux? ls-iommu.sh https://gist.github.com/jabbas/a8785710a5e8655045fc0be67385e887 If you are on windows, then please boot of a linux live USB. Which can be burned from ISO disk image file on windows using the program rufus. For example ubuntu https://www.ubuntu.com/download/desktop This is to check / see the IOMMU groups. For virtualization passthough under linux. Thank you.
  14. Nope... I'm not familiar with any of those things which you are talking about. But if you tested it, and actually found any specific features are missing, please provide links, to where they are properly explained. Then maybe @danske can be made aware and possibly integrate them into a future release. You're going to have to actually test his BIOS first though. Certainly I have no problems with that on my own board. But I'm kindda busy right now. And might not actually get around to it for quite a while myself. [edit] but for windows xp compatibility aspect - that is not really any problem of the bios modding. The bios is based on M10A (z370) which is why it does not work. You would need to look for other types of solutions for win xp. @dsanke is not going to be providing any kind of a fix for that.
×
×
  • Create New...