Page 41 of 103 FirstFirst ... 31 39 40 41 42 43 51 91 ... LastLast
Results 401 to 410 of 1030
  1. #401
    ROG Guru: Blue Belt Array gupsterg PC Specs
    gupsterg PC Specs
    MotherboardAsus Maximus VII Ranger
    Processori5 4690K
    Memory (part number)HyperX Savage 2400MHz 16GB
    Graphics Card #1Sapphire R9 Fury X (1145/545 Custom ROM)
    MonitorAsus MG279Q
    Storage #1Samsung 840 Evo 250GB
    Storage #2HGST 2TB
    CPU CoolerThermalRight Archon SB-E X2
    CaseSilverstone Temjin 06
    Power SupplyCooler Master V850
    Headset/Speakers HyperX Cloud
    OS Win 7 Pro x64 / Win 10 Pro x64
    gupsterg's Avatar
    Join Date
    Feb 2015
    Reputation
    102
    Posts
    982

    Quote Originally Posted by thedotlair View Post
    Reading between the lines, this is more about Asus actually releasing OFFICIAL BIOSes rather than Dropbox links for their supported platforms, like other manufacturers are. Remove MSI out of the loop (due to their faux par with the BIOS RAM sizes), both Gigabyte and ASRock have been regularly releasing updates via official channels, Asus haven't - they're not even in the same category and their support email is woeful.

    And before I get shouted at by some members on here, ROG Forums are not an official release method and we shouldn't have to rely on one individual (Shim) to get releases to us.
    ASUS do tend to be slower to release an official" UEFI update, so I agree with that. Do they quash more bugs per release? this is debatable IMO. So I do believe they need to "step up their game".
    Intel Defector AMD Rebel

    TR 1950X - Custom WC - Asus Zenith Extreme Alpha - G.Skill Trident Z 3400MHz C14 QC - RX VEGA 64
    R5 3600 - Custom WC - Asus Crosshair VII Hero Wifi - G.Skill Ripjaws V 3800MHz C16 - Sapphire HD 5850 Toxic

    24/7 OC: i5 4690K @ 4.9GHz CPU@1.255v 4.4GHz Cache@1.10v - Archon SB-E X2 - Asus Maximus VII Ranger
    Sapphire Fury X (1145/545 ~17.7K GS 3DM FS)

  2. #402
    New ROGer Array
    Join Date
    Jul 2019
    Reputation
    13
    Posts
    35

    Quote Originally Posted by gupsterg View Post
    ASUS do tend to be slower to release an official" UEFI update, so I agree with that. Do they quash more bugs per release? this is debatable IMO. So I do believe they need to "step up their game".
    Maybe we'd know how many bugs they fixed in every release if they'd devote more than a handful of words to describing the changes. I mean, look at the C7H changelogs:

    0601:
    1. Update SMU Firmware to version 43.18.0
    2. Update RAID driver to version 9.2.0.41.
    3. Update Asus Grid notification behavior
    Above average because it gives some specific version numbers. What "notification behavior" changed? Have fun finding out!

    0702:
    Update Agesa Code to 1.0.0.2c.
    Update compatibility protocol for 3rd party hardware monitoring software.
    Fixed miscellaneous issues with fan calibration/options.
    Wow, another version number. albeit from AMD. Then two useful sounding but vaguely described fixes or updates.

    0804:
    1. Improve system stability
    2. Improve Secure Erase function on NVMe devices
    3. Update LPPT firmware
    Ahhh "improve system stability", you have to get used to that phrase reading Asus BIOS changelogs! Is it ever actually true? Who knows, because we never get to find out what was changed.

    1002:
    (literally nothing)
    Maybe they just forgot to do the usual excellent job this time around?

    1103:
    1. Update AMD AGESA version to 1.0.0.6
    2. Improve system stability
    Lucky AMD provide version numbers or we wouldn't even get those I'm sure. And oh look it's the mysterious "Improve system stability" again!

    1201:
    Improve system performance.
    Add CPU PCIe Lanes Unlocked item in BIOS when plugging in AMD Athlon 2XX series processors.
    A rare gem here as we actually get a pretty specific and clear description of a BIOS change. But it's paired with the counterpart of "Improve system stability", the equally vague "Improve system performance".

    2008:
    Update AGESA 0070 for the upcoming processors and improve CPU compatibility.
    Not actually that bad I suppose, assuming there were no other changes in this version... but why not link to a list of compatible CPUs? (my guess: they probably didn't have an up to date one on their website, given how long it took to add the Zen 2s to the official compatibility list)

    2103:
    "1. Update AM4 ComboPI 0.0.7.2
    2. Improved Memory Stability"
    Another AMD-provided version number and yet another very vague improvement claimed (I like how this was posted with the quotes, really gives it that "copied and pasted from someone's email" feeling).

    2203:
    Enhanced security
    That's it. 2 words. If you were fixing a security problem, you'd think providing a tiny bit more information might just possibly be somewhat useful...?

    2304:
    1. Update AM4 ComboPI 0.0.7.2A for next-gen processors and to improve CPU compatibility
    2. Fixed an issue with Precision Boost values
    3. Improved memory compatibility
    4. Enhance system security
    This one is practically novel-length by normal standards! Let's see, another AMD-provided update first (never described in the same format: "AGESA Code", "AMD AGESA version", "AGESA", "AM4 ComboPI". I'm sure most people will know they all refer to the same thing, but not everyone will, and it neatly demonstrates they're not following any standard process for writing these things). Then fixing "an issue" (what issue exactly? not for us to know apparently), the standard vague improvement claimed, and another security issue apparently fixed with no further information deemed necessary.

    2406:
    1. Improve system stability.
    Anyone seeing the pattern yet?

    2501:
    Fix an issue where the mouse will sometimes freeze in the UEFI.
    Update multi-language string.
    Fix an issue with the Safe Boot button.
    Don't really have an issue with the language part, that's a minor change. The mouse is still broken in 2501 isn't it? But at least it's a specific testable change, so I'll give them that. And then "fixing an issue", again without telling us what the issue was.

    Reading all of that should really make you angry at Asus. I know there are a lot of you here that enjoy spending time tweaking every possible thing in your systems - don't you feel it would be helpful to have as much information as possible about something as fundamental to it as the BIOS is? To have more confidence that problems you've reported are being addressed? Instead it's like they're deliberately trying to provide the absolute minimum amount of information.

    I will admit that other manufacturers often aren't much better at this, but why should that stop Asus from leading the way? They're the biggest mobo manufacturer by quite some distance aren't they? Seems like it'd be a good marketing point for attracting enthusiasts to the brand. I imagine it might even compensate for slow BIOS updates if the eventual releases were very likely to be stable and perform well and be accompanied by detailed changelogs. Conversely, they are really not doing themselves any favours by combining slow and often buggy releases with minimal changelogs.

  3. #403
    ROG Guru: White Belt Array bigtop1967 PC Specs
    bigtop1967 PC Specs
    MotherboardCrosshair VII Hero
    ProcessorRyzen 1700X
    Memory (part number)G.Skill F4-4266C19D-16GTZR
    Graphics Card #1XFX Raadeon RX 580 8GB Black Edition
    Monitor2 x Acer CB241HQK
    Storage #1Samsung SM961 NVME
    Storage #22 x SanDisk Ultra II
    CPU CoolerCoolMaster Masterliquid 240
    CaseAero 500
    Power SupplyCorsair RM850
    Mouse Microsoft Mobile Wireless 4000
    OS Windows 10 Pro
    Network RouterASUS
    bigtop1967's Avatar
    Join Date
    Jul 2016
    Reputation
    11
    Posts
    93

    Quote Originally Posted by KsgKsg View Post
    I have installed palit game rock 1080ti.
    I look at pci-e mode in BIOS-TOOLS, additionally in GPU-Z.
    NVME is installed in the lower slot.
    BIOS ver. 2501

    I want to say that with a 2600x processor the video card starts at 16x, but does not start at 3700x.
    Wow - so it says x8 in the bios as well?

    When you changed the bios setting in Onboard Devices menu to [disabled (x8 mode)] it still said x8 in the bios when you saved and rebooted??

    Code:
    M.2_2 PCIe Bandwidth Configuration [Disabled(X8 mode)]
    PCIEX16/X8_1 Mode [GEN 3]
    PCIEX8/X4_2 Mode [Auto]
    PCIEX4_3 Mode [Auto]
    M.2_1 Link Mode [GEN 3]
    M.2_2 Link Mode [Auto]
    It's a shame you don't have another 3xxx cpu so you could rule out hardware/firmware. The fact thge card works (even at x8) means the cards are fine, so I get why you think it must be CPU.

    I'll ask over on OCN for you - someone might know
    Last edited by bigtop1967; 08-14-2019 at 12:06 PM.
    Ryzen 9 3900X | Current Bios - 2801 | Crosshair VII Hero | 16GB Patriot Steel 4400CL19 @ 3733CL16 | ADATA SX8200NP 480GB | Fractal Design S36 AIO

    About me: I am dyslexic and DO occasionally miss things!

    There are 10 types of people, those who understand binary, and those that don't.
    F people in 10 don't understand hexadecimal

  4. #404
    ROG Guru: Blue Belt Array gupsterg PC Specs
    gupsterg PC Specs
    MotherboardAsus Maximus VII Ranger
    Processori5 4690K
    Memory (part number)HyperX Savage 2400MHz 16GB
    Graphics Card #1Sapphire R9 Fury X (1145/545 Custom ROM)
    MonitorAsus MG279Q
    Storage #1Samsung 840 Evo 250GB
    Storage #2HGST 2TB
    CPU CoolerThermalRight Archon SB-E X2
    CaseSilverstone Temjin 06
    Power SupplyCooler Master V850
    Headset/Speakers HyperX Cloud
    OS Win 7 Pro x64 / Win 10 Pro x64
    gupsterg's Avatar
    Join Date
    Feb 2015
    Reputation
    102
    Posts
    982

    @adr82

    Valid point, I too would prefer a more enhanced changelog and agree other vendors are not much better, but a vendor can choose to be better.

    My mouse in UEFI did come back in UEFI 2501, "SAFEBOOT" button does not work as intended, nor does holding down power button make board enter "SAFEMODE". These two do function as they should in UEFI 0068 posted here.

    The issue I and noted another owner on OCN with UEFI 0068, chipset voltage can be ~1.35V on very first boot (link). Once set manually as 1.05V it will be that, you can use "SAFEBOOT" & "SAFEMODE" and you won't see ~1.35V chipset voltage, but if you do CMOS CLEAR you will.

    UEFI 2602 is the only UEFI so far for Matisse that has functioning "recovery", ie if I do a bad OC profile board will Q-Code: F9 (like when 1xxx/2xxx CPU was used on prior UEFIs) and it will retry to train up again, if it can't it will resets settings, recover automatically.
    Last edited by gupsterg; 08-14-2019 at 10:10 AM.
    Intel Defector AMD Rebel

    TR 1950X - Custom WC - Asus Zenith Extreme Alpha - G.Skill Trident Z 3400MHz C14 QC - RX VEGA 64
    R5 3600 - Custom WC - Asus Crosshair VII Hero Wifi - G.Skill Ripjaws V 3800MHz C16 - Sapphire HD 5850 Toxic

    24/7 OC: i5 4690K @ 4.9GHz CPU@1.255v 4.4GHz Cache@1.10v - Archon SB-E X2 - Asus Maximus VII Ranger
    Sapphire Fury X (1145/545 ~17.7K GS 3DM FS)

  5. #405
    ROG Guru: White Belt Array bigtop1967 PC Specs
    bigtop1967 PC Specs
    MotherboardCrosshair VII Hero
    ProcessorRyzen 1700X
    Memory (part number)G.Skill F4-4266C19D-16GTZR
    Graphics Card #1XFX Raadeon RX 580 8GB Black Edition
    Monitor2 x Acer CB241HQK
    Storage #1Samsung SM961 NVME
    Storage #22 x SanDisk Ultra II
    CPU CoolerCoolMaster Masterliquid 240
    CaseAero 500
    Power SupplyCorsair RM850
    Mouse Microsoft Mobile Wireless 4000
    OS Windows 10 Pro
    Network RouterASUS
    bigtop1967's Avatar
    Join Date
    Jul 2016
    Reputation
    11
    Posts
    93

    Quote Originally Posted by gupsterg View Post
    ASUS do tend to be slower to release an official" UEFI update, so I agree with that. Do they quash more bugs per release? this is debatable IMO. So I do believe they need to "step up their game".
    I agree - they've launched so many products in the last 3 years it looks like they're having trouble keeping up with updates. It's becoming like waiting for phone updates. Of course they now have to keep nearly all AM4 boards 'up to date' . Until this fiasco which (on this occasion) is mainly AMD, things were 'ok' - but since AMD threw many spanners in the works, I believe it's shown up some weakness at ASUS

    Things have changed - they need to step up - they can't just release all these products and not update them. It's not acceptable any more. If they want to launch all these products then they must make sure the resources are there to support them on the same level as any other product.

    What annoys me is that AMD launched early and failed to provide vendors with proper firmware for that launch. AGESA 1002 is fairly stable, but then to churn out 3 versions of 1003, all with bugs shows they just weren't (aren't) ready.

    I do expect a better bios from ASUS, which is what I used to get - you can't just forget older products - some of us only got our CH7s recently - I don't even see why newer devices should have priority. Perhaps, like phone vendors, motherboard vendors will have to give their products a guaranteed 3 years of updates (for example)?
    Ryzen 9 3900X | Current Bios - 2801 | Crosshair VII Hero | 16GB Patriot Steel 4400CL19 @ 3733CL16 | ADATA SX8200NP 480GB | Fractal Design S36 AIO

    About me: I am dyslexic and DO occasionally miss things!

    There are 10 types of people, those who understand binary, and those that don't.
    F people in 10 don't understand hexadecimal

  6. #406
    ROG Guru: White Belt Array bigtop1967 PC Specs
    bigtop1967 PC Specs
    MotherboardCrosshair VII Hero
    ProcessorRyzen 1700X
    Memory (part number)G.Skill F4-4266C19D-16GTZR
    Graphics Card #1XFX Raadeon RX 580 8GB Black Edition
    Monitor2 x Acer CB241HQK
    Storage #1Samsung SM961 NVME
    Storage #22 x SanDisk Ultra II
    CPU CoolerCoolMaster Masterliquid 240
    CaseAero 500
    Power SupplyCorsair RM850
    Mouse Microsoft Mobile Wireless 4000
    OS Windows 10 Pro
    Network RouterASUS
    bigtop1967's Avatar
    Join Date
    Jul 2016
    Reputation
    11
    Posts
    93

    I've noticed on 2602 that if I get a blue screen and hit the reset button, it sometimes doesn't reboot - it just goes to code 0D and I have to press it again. I'll sometimes do this from the desktop (when nothing is running!) as this also avoids training, but often get the code 0D there as well.

    Also, if I do a restart from windows, it still takes ages to shut down, and when it does reboot, it usually retrains memory so is quite slow.
    Ryzen 9 3900X | Current Bios - 2801 | Crosshair VII Hero | 16GB Patriot Steel 4400CL19 @ 3733CL16 | ADATA SX8200NP 480GB | Fractal Design S36 AIO

    About me: I am dyslexic and DO occasionally miss things!

    There are 10 types of people, those who understand binary, and those that don't.
    F people in 10 don't understand hexadecimal

  7. #407

  8. #408
    ROG Enthusiast Array
    Join Date
    Oct 2017
    Reputation
    10
    Posts
    33

    Thanks!!!

  9. #409
    ROG Guru: Blue Belt Array gupsterg PC Specs
    gupsterg PC Specs
    MotherboardAsus Maximus VII Ranger
    Processori5 4690K
    Memory (part number)HyperX Savage 2400MHz 16GB
    Graphics Card #1Sapphire R9 Fury X (1145/545 Custom ROM)
    MonitorAsus MG279Q
    Storage #1Samsung 840 Evo 250GB
    Storage #2HGST 2TB
    CPU CoolerThermalRight Archon SB-E X2
    CaseSilverstone Temjin 06
    Power SupplyCooler Master V850
    Headset/Speakers HyperX Cloud
    OS Win 7 Pro x64 / Win 10 Pro x64
    gupsterg's Avatar
    Join Date
    Feb 2015
    Reputation
    102
    Posts
    982

    Quote Originally Posted by Shamino View Post
    Non fully validated ABB versions of 370/470 if you wish to try
    Thank you & appreciated Peter .

    UEFI 2602 has 2 new settings in PMU menu (max values that can be entered shown).

    Click image for larger version. 

Name:	PMU Menu 1.0.0.3AB.jpg 
Views:	0 
Size:	136.9 KB 
ID:	81374

    R5 3600 (Batch: BF 1922SUT)
    ASUS ROG Crosshair VII Hero Wifi (UEFI 2602, AGESA ComboPi-AM4 1.0.0.3AB)
    F4-3200C14Q-32GVK

    CPU Stock

    RAM/IF: 3800MHz/1900MHz

    SOC: 1.093V VDDG: 1.025V CLDO_VDDP: 0.901V VDDP: 1.05V
    VBOOT: 1.4V VDIMM: 1.4V VTTDDR: 0.7V
    ProcODT: 34.3, RTT/CAD Bus drive strength/timings [Auto]

    Changed only MR6VrefDQ Control in PMU Training menu.

    1h, 2h, 10h, 24h, 36h, 48h, 56h all result in Q-Code: F9, 3x board would try to POST, each time it would fail, settings would reset and board would then POST.

    Meddling with MR6VrefDQ has not proved what is default, reading info (shown below) this value may change per calibration.

    Meddling with MR6VrefDQ clearly destroyed POST ability of profile.

    I believe this setting is altering this:-

    Click image for larger version. 

Name:	DDR4 SDRAM info 2.jpg 
Views:	0 
Size:	165.6 KB 
ID:	81375

    Is above info correct for MR6VrefDQ?

    Any info you can share on CPU Vref Training Seed?
    Last edited by gupsterg; 08-14-2019 at 01:20 PM.
    Intel Defector AMD Rebel

    TR 1950X - Custom WC - Asus Zenith Extreme Alpha - G.Skill Trident Z 3400MHz C14 QC - RX VEGA 64
    R5 3600 - Custom WC - Asus Crosshair VII Hero Wifi - G.Skill Ripjaws V 3800MHz C16 - Sapphire HD 5850 Toxic

    24/7 OC: i5 4690K @ 4.9GHz CPU@1.255v 4.4GHz Cache@1.10v - Archon SB-E X2 - Asus Maximus VII Ranger
    Sapphire Fury X (1145/545 ~17.7K GS 3DM FS)

  10. #410
    New ROGer Array
    Join Date
    Aug 2019
    Reputation
    10
    Posts
    1


Page 41 of 103 FirstFirst ... 31 39 40 41 42 43 51 91 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •