Acer Nitro 5 AN515-58 When fast boot is turn on and laptop is turning on there is bug

Sinfolke
Sinfolke Member Posts: 14

Tinkerer

edited December 2 in Nitro Gaming

I haven't yet found a way to report a bios bug to Acer directly. Previous post is here: https://community.acer.com/en/discussion/comment/1301076

When fast boot is turn on and laptop is turning on (not rebooted), there is bug that the keyboard shows reload animation 3 times. Sometimes screen also turn on and off.

I think moderators could report or to show where i could.

BIOS version: 2.14
OS: no matter

[Edited the thread to add issue detail]

Answers

  • Puraw
    Puraw ACE, Member Posts: 14,047 Trailblazer

    This model is from 2022 so you should have Windows11 23H2, update Windows build 4391 (Oct. 22). Disable Fast Startup and Hibernate as these options interfere with Modern Standby in Windows11: in "Change what closing the lid does" and "Change settings currently unavailable" then reset the Power Plan in: "Edit Power Plan".

  • Sinfolke
    Sinfolke Member Posts: 14

    Tinkerer

    I use linux mint and have no Windows at all. On the version 2.09 there was no such thing and fast boot worked well. After the bios update the bug happens independently of OS. It occurred on windows, linux, or in dual boot.

  • Sinfolke
    Sinfolke Member Posts: 14

    Tinkerer

    edited November 13

    @Puraw (mention because forgot to do so)
    Also it seems does not occur after wake up from sleep mode

  • JackE
    JackE ACE Posts: 45,081 Trailblazer

    > >On the version 2.09 there was no such thing and fast boot worked well.> >

    What problem were you trying to fix by changing from v2.09? BIOS updates are often meant to fix problems that might arise in some but not necessarily all machines due to unannounced production changes. Accordingly, unless there is a critical reason for doing so, BIOS updates should not be applied to a functional machine.

    Jack E/NJ

  • Sinfolke
    Sinfolke Member Posts: 14

    Tinkerer

    edited November 27

    @JackE There was no a reason and it worked properly with version it had but i just though it'd be nice to update onto latest version. If i knew it could cause bugs i wouldn't perform an update. Now i'm even ready to perform a roll back but as I read it can be done with risk of breaking.

    I see there is new update 2.16 which i maybe will try but idk whether it will fix the problem

  • JackE
    JackE ACE Posts: 45,081 Trailblazer

    If it were mine, I'd try the new update first. Rollbacks are riskier.

    Jack E/NJ

  • Sinfolke
    Sinfolke Member Posts: 14

    Tinkerer

    @Puraw @jackE Update to 2.16 did not solve the problem

  • JackE
    JackE ACE Posts: 45,081 Trailblazer

    > >I use linux mint and have no Windows at all. > > bug happens independently of OS. It occurred on windows, linux, or in dual boot> >

    If you have no Windows at all, then how do you know it happens on Windows? And how did you install the 2.16 update Windows EXE executable with no Windows at all. WINE cannot be used for running Windows BIOS EXE executables without risking a BIOS firmware corruption.

    Jack E/NJ

  • Sinfolke
    Sinfolke Member Posts: 14

    Tinkerer

    edited December 2

    @JackE I've made a 27 gb separate drive and installed win11 tiny there. It even have around 8-10 gb free space. Update done from there. The bug occurs even if i select windows boot manager as a booting drive in bios

    I just use it without fast boot but hope this discussion could help them solve it in further updates

  • JackE
    JackE ACE Posts: 45,081 Trailblazer

    > > @JackE There was no a reason and it worked properly with version it had but i just though it'd be nice to update onto latest version.

    If it was my machine, I would just use it as-is without fast boot at this point. This issue seems relatively minor. But the risk of bricking the machine or introducing more serious problems is too great, by trying to go back to v2.09.

    Updates often are meant to fix problems for later production models caused by earlier BIOS versions. So if a particular production release doesn't seem to have problems, it's probably best to leave well enough alone. BIOS firmware updates are much riskier than operating system software driver updates. Thus they should be considered irreversible and only done as a last resort to try to fix serious problems.

    Jack E/NJ

  • yused
    yused Member Posts: 1 New User

    hello i had the same problem did you solve it? if you did, can you share your solution?
    also i did something and looks like it worked, but not sure if its just coincidence or not. Try setting what power button and closing laptop lid does in windows settings and change it back to normal

  • Sinfolke
    Sinfolke Member Posts: 14

    Tinkerer

    edited December 15

    @yused The fix is turn off fast boot in bios settings. Your advise for sad not helped

  • Sinfolke
    Sinfolke Member Posts: 14

    Tinkerer

    edited December 17

    @yused Another fix without turning off fast boot is add supervisor password. I actually done a roll back to 2.09 and issue still was there. Helped to add password in bios. Without password bug occurs

  • JackE
    JackE ACE Posts: 45,081 Trailblazer

    > >I actually done a roll back to 2.09 and issue still was there. Helped to add password in bios. Without password bug occurs> >

    As mentioned earlier, if it was mine I'd try to avoid the temptation of taking chances like this of flashing & re-flashing the BIOS chip unless there is a very good reason for doing so. Just because driver software or bios firmware might have a newer date is certainly NOT a good reason. Updates are often designed to fix problems in later production releases, not your own earlier release, that might arise due to announced hardware changes that may occur without notice.

    Jack E/NJ