Új hozzászólás Aktív témák

• #8661 ricsip addikt ricsip #8660

  Új Válasz 2025-09-19 11:54:41 #8661

  Új hozzászólás

  Összes hozzászólása itt Válaszok az összes hozzászólására itt Válaszok erre a hozzászólásra

  Privát üzenet küldése

  

  ricsip

  addikt

  válasz ricsip #8660 üzenetére

  Na csak jól elbeszélgetek itt magammal...

  Gyanúsan Secure Boot + AMD GPU inkompatibilitásról lehet szó. Az F38-as BIOS-al jött be ez a hírek szerint, ezen a lapon esélyesen F37 volt legutóljára felrakva, mielőtt meghülyült az egész az F40H-ra update-től.

  ----

  its likely because of the black screen soft bricking issue which was in the beta and not fixed in the stable leading to influx of complaints

  somebody else example: https://www.overclock.net/threads/gi.../post-29310257

  and my own experience below

  if you dont set a bios password and dont disable full screen logo show, ie most people, you should be fine, i also wonder if the issue only affects amd GPUs but i dont know

  Originally posted by amEliza View Post
  a warning: this latest beta has some impactful bugs, likely other boards with "logofail" fix too.

  when i disable the option "Full Screen LOGO Show" i get no display output until in uefi or in windows, i would suggest keeping it enabled, and especially set it to enabled before you update to this uefi version.

  clearing cmos jumper didn't clear the setting for me, so it can seem like a bricked mobo, but you can still type bios password blindly and hit enter to reach uefi.

  recovery flash from usb using qflashplus mobo button will work and will clear the setting and restore display output. --> hát mondjuk nekem ez nem működött

  also a similar bug is that even with the above logo setting enabled, when a bios password is set, the bios password entry screen is now blank except for a console curser at the top left, but again password can still be entered blindly.
  personal opinion, i was shocked to see this build moved from beta to stable with the issue still present

  ----

  For a long time the steps of toggling standard to custom, custom back to standard accepting defaults, and enabling secure boot, has overcome the default of enabled not active (Setup mode displayed instead of User mode)

  There is the reset keys option but over time there are often posts about bricked m/b after messing with keys settings

  But I have seen posts recently suggesting this doesn't work any more with recent beta BIOS versions - suggesting there is now a BIOS keys issue

  But BIOS with small letters are beta and for old designs like B550 and X570 that are working fine why risk it?

  There is the theory that Windows can load microcode updates for these reported vulnerabilities as well as BIOS updates - even if theyre possible to happen

  There is also still confusion with people thinking secure boot enabled is needed for W11 - but it is called for by some games

Új hozzászólás Aktív témák