Jump to content
HWBOT Community Forums

NoMS

Members
 View Profile  See their activity

  • Posts

    470

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Posts posted by NoMS

    ASUS ROG MAXIMUS Z690 APEX | APEX 14

    in Alder Lake (Z690) & Raptor Lake (Z790) OC

    Posted

    3 hours ago, marco.is.not.80 said:

    I'm still confused. One BIOS can't be flashed back. I get that. The other BIOS would have the NON-K OC BIOS installed. You can't just flip the switch  to choose the BIOS that works and go from there?

    Sorry - I think I'm missing something here - educate me.

    You can, but if the NON-K OC BIOS get broken for some reason and you need USB Bios Flashback to fix it, it will refuse to flash the older BIOS if you already flashed the another chip with the newer one.

    • Like 3

    ASUS ROG MAXIMUS Z690 APEX | APEX 14

    in Alder Lake (Z690) & Raptor Lake (Z790) OC

    Posted · Edited by NoMS

    On 1/24/2023 at 6:38 AM, marco.is.not.80 said:

    Guys, isn't this why we have dual bioses? Flash the latest one to one bios and keep the old bios on the 2nd one. What's the problem?

    The problem is if you got some issue while using the older bios, something like the board getting stucked at post code '28' even after clearcmos and you need to use USB Bios Flashback, you are out of luck since it only works with a newer bios version.

    This happened to me and now Non-K OC is gone. :/

    • Like 1

    NoMS - K6-2 450MHz @ 720MHz - 5min 9sec 374ms SuperPi - 1M

    in Result Discussions

    Posted · Edited by NoMS

    45 minutes ago, Antinomy said:

    Should be fixed since 1.86. I've reported it on 1.85. Try versions from 1.86 to current and let me know. If you don't have them, I can send you.

    Downloaded all of them since 1.86 from here, is there any other version you want me to try?
    1.86 is broken here and all the other versions looks the same, attached is one video showing the issue with 1.86 and a report.txt from 1.98 which you can also spot the issue.

    Here is a validation with 1.98, apart from the fact that the image looks correct, the 5.6MHz on memory clock is very wrong.

    Also I don't know if it helps but my board is a P5A rev 1.03.

    TOCP-2B025FEAE8.txt

    NoMS - K6-2 450MHz @ 720MHz - 5min 9sec 374ms SuperPi - 1M

    in Result Discussions

    Posted · Edited by NoMS

    2 hours ago, Antinomy said:

    What clock detection issues, clock jumping? Which version where you using? We've fixed this with Franck Delattre about 2-3 years ago specifically for P5A. Versions 1.9x should be fine.

    Yes, clock jumping. 1.03.0 Vintage Edition is broken as you can see in the video i posted on this thread, tbh, even the old 1.47 I used sometimes got issues with this, it's only a bit more manageable than newer versions. ?

    If I remember well from my previous testing, same issue as 1.03.0 on CPU-Z 1.98. Any ideas to fix that?

×
×
  • Create New...