Jump to content
HWBOT Community Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

12 Good

About dreamcat4

  • Rank
    maintenance bot

Recent Profile Visitors

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

  1. 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).
  2. 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: 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
  3. 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.
  4. 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?
  5. 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.
  6. 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.
  7. Hey guys. The excellent @dsanke has already made a 1704 mod bios since 2 weeks ago. We just didn't know about this thread. Let me see if I can make attachment to upload it to my message here... - Port from M10A - AURA/RGB Fixed - SLI Fixed - iGPU vBIOS Replaced to M9A - Dell SLIC 2.4 - Dell Windows Server 2016 Data Center Key - ME - uCode : 506E0(0x18),506E1(0x2A),506E2(0x2E),506E3(0xC6),506E8(0x34),906E9(0x8E),906EA(0x9A),906EB(0x9A),906EC(0x9E) - GBE : I219-LM - Model : MAXIMUS IX APEX dsanke: Author: @dsanke Motherboard: ASUS ROG MAXIMUS IX APEX Based on:ASUS ROG MAXIMUS X APEX 1704 ME: Microcodes: 506E0(0x18),506E1(0x2A),506E2(0x2E),506E3(0xC6),506E8(0x34),906E9(0x8E),906EA(0x9A),906EB(0x9A),906EC(0x9E). Note: Flash via SPI Programmer. Support All LGA1151 CPU except Xeon and Skylake ES. AURA/SLI Fixed. Ethernet adapter changed to I219-LM. Added DELL SLIC 2.4 and Windows Server 2016 Datacenter key. Edit model back to M9A. $ md5sum ROG-MAXIMUS-IX-APEX-ASUS-1704.7z ROG-MAXIMUS-IX-APEX-ASUS-1704/ROG-MAXIMUS-IX-APEX-ASUS-1704.bin 4806e282c2f813822ab7d8be981a715e ROG-MAXIMUS-IX-APEX-ASUS-1704.7z b792b3dc333ff6920afbf5e89d9ae5ff ROG-MAXIMUS-IX-APEX-ASUS-1704/ROG-MAXIMUS-IX-APEX-ASUS-1704.bin Is ok, right? 😋 ROG-MAXIMUS-IX-APEX-ASUS-1704.7z
  8. We really Splave to ask Nick for us again. He was going to already. Anyhow - that's how it got Nick's attention last time. Looking back though, the only noteworth improvement seems to be... this ? > Core selection fixed 1/2/3/4/5/6 all available now instead of 1/2/3/6 Then I think I can live with that. Unless it was being able to set specific per-core multipliers. Rather than enable / disable cores completely. Or perhaps there were also other kinds of improvements on the mOCF side? Then I am not aware of them.
  9. Well you say that, but mine was only $50 USD including shipping. (2nd hand, ebay). Because one of it's pci-e slots had been ripped off by accident. Everything else works just fine though 😋 Tee hee
  10. Yes - please see if you can remink him about it, the next time an opportunity comes up. Quite a few of us have the full ATX version here
  11. Ah yes! But is that also fixed on the full ATX version BIOS? We still have the same version from April. No further updates since that time. https://community.hwbot.org/topic/175489-asrock-z170-mocf-lives-on-coffee-lake-mods/?do=findComment&comment=496834 Kind Regards (full ATX version owner)
  12. Then it's not missing the SKT_OCC, which means it is not your problem.
  13. Hey there. Photos show other way you can connect the SKT_OCC pins of the socket together: Either way does same thing, it tells the board that there is a coffee lake CPU inserted into the socket. (because that function moved in coffee lake to a different pinout location)
  14. Thanks Nick! Outstanding stuff. We are very grateful. I will also let my friend know online, who has same board. We were planning to make a mod BIOS ourselves but you saved us the work. BTW (and this is important) there have also been found a number of boards which did not change very much from Z270 to Z370. The design is much the same, including the VRMs and layout etc. These boards have been backwards flashed with Z370 BIOS succesfully. This then lets support FULL overclocking features and controls for hex core. Since we noticed that you may have skipped / passed on updating super carrier / i7 professional / oc formula in z370. The any Z390 board with similar IR35201 and other design is going to be helpful as a backwards flash candidate. This may not be possible for such board as Z170 OCF here. But there is still others like Z270 supercarrier and it seems IR35201 is still used. Of course you may need to change board design in future successor products for many other reasons and purpose. So not to worry about Just wanted to say / mention..
  15. +1 But I can see why splave is only interested in bothering with the Micro ATX version though... because as an overclocker, the 2 dimm slots is much better. Wheras the regular ATX board was known to be somewhat problematic in regards to the memory. Still, I don't happen to own the M-ATX version. Just the full atx myself. No idea where else / proper channels to ask about this since it is an unofficial mod BIOS. Will be getting a hardware flasher soon.