Acer Predator (Vega 56+Ryzen 2) Helios 500

Discussion in 'Acer' started by ThatOldGuy, Jun 3, 2018.

Tags:
  1. Deks

    Deks Notebook Prophet

    Reputations:
    1,163
    Messages:
    4,905
    Likes Received:
    1,951
    Trophy Points:
    231
    I had the latest chipset drivers installed before the bios. As for gpu drivers, those were the 19.5.2 drivers from AMD website.
    But, both the chipset and gpu drivers are independent of the bios. So I don't understand what could have messed up the BIOS update
     
    hmscott likes this.
  2. Megol

    Megol Notebook Evangelist

    Reputations:
    111
    Messages:
    564
    Likes Received:
    76
    Trophy Points:
    41
    Wait that shouldn't be possible, wasn't the original 256GB an NVMe drive?
    No that shouldn't matter at all. Hope you get it back quickly.
     
    hmscott likes this.
  3. Deks

    Deks Notebook Prophet

    Reputations:
    1,163
    Messages:
    4,905
    Likes Received:
    1,951
    Trophy Points:
    231
    I don't know whether the original 256GB SSD was NVMe or not. Sufficed to say, I put my 500GB SSD into the first slot, and moved the 256GB into the second slot (because the laptop kept booting Windows automatically off the first slot and there was no way to change it permanently inside the BIOS - every time a restart of the machine occurred, the laptop would automatically switch the boot to slot 1).

    Anyway, the 256GB SSD (original) is in the second slot and is detected by Windows and works... and my 500GB SSD is in slot 1.

    I think both are NVMe... so the SSD would probably work in slot 2 even if the slot was not NVMe (not too sure about those standards though).

    I also spoke with PC Specialist today and asked them to try and notify the engineers to install the latest 1.09 bios ig they can as others managed to do so, but if they cannot, they should install the version 1.08 at least as the 1.06 is too old and doesn't have security/stability patches of newer versions. - the guy said he will pass it on to them.

    Oh and I asked them if possible to not touch the HDD.
    I don't mind if they need to reset Windows (on the SSD), but that the HDD has nothing to do with it and as such shouldn't be touched or deleted, because even if there was a fault with it, wiping the data off it wouldn't do any good anyway (With which the guy agreed - but did say they cannot technically guarantee that).
     
    Megol and hmscott like this.
  4. SMGJohn

    SMGJohn Notebook Evangelist

    Reputations:
    121
    Messages:
    535
    Likes Received:
    300
    Trophy Points:
    76
    Always take out harddrives etc that the OS does not occupy and always expect them to reinstall the machine when you send stuff like that in for repair.
    Even if you tell them it usually does not prevent them doing it.
    Really annoying but just how it is in my long experience dealing with laptop services.

    Sent fra min SM-G970F via Tapatalk
     
    Megol likes this.
  5. Deks

    Deks Notebook Prophet

    Reputations:
    1,163
    Messages:
    4,905
    Likes Received:
    1,951
    Trophy Points:
    231
    Probably should have taken out the HDD... but I was exhausted/tired by that point and what's done is done... but most of it I have backed up anyway (or at least the stuff I REALLY need - everything else is minor and I can download from the Internet again - such as few programs).

    Reinstall/reset of the machine (from SSD) is fine... I told them they don't have to touch the HDD as the OS is not on it.
    I don't understand OEM fascination with doing that.
    It's utterly pointless and doesn't do ANYTHING to solve a potential mechanical problem (if there is one to begin with) which is something I told them.

    And besides, if they have time to do that, you'd think they would try to reflash the latest bios themselves, and if that doesn't work, then test to see why isn't it allowing them to do that and address that problem... or at the very least flash the immediate version before that (which ran fine).
     
    Megol and SMGJohn like this.
  6. xdyphx

    xdyphx Notebook Enthusiast

    Reputations:
    0
    Messages:
    35
    Likes Received:
    27
    Trophy Points:
    26
    17.12.png

    17.12 have something related to chipset driver inside

    19.5.2.png
    19.5.2
     
    hmscott likes this.
  7. Deks

    Deks Notebook Prophet

    Reputations:
    1,163
    Messages:
    4,905
    Likes Received:
    1,951
    Trophy Points:
    231
    And?
    I did have Acer's original drivers installed, but I express updated them t 19.5.2 in order to preserve Freesync functionality.
    If 17.12 had something to do with the chipset, it could have been Freesync related.... because if you just end up installing 19.5.2 drivers themselves, you lose Freesync.

    Anyway, I don't think this would have messed up the BIOS as chipset drivers are OS level, and they don't interact with the BIOS itself.... not to the level where they would corrupt the BIOS.
     
  8. xdyphx

    xdyphx Notebook Enthusiast

    Reputations:
    0
    Messages:
    35
    Likes Received:
    27
    Trophy Points:
    26
    Wierd because i put 1tb nvme inside, 32gb ram and even 2700x and i installed my bios without problems and i do everthing on full oced machine (ram timings, cpu, gpu and hbm2 ram timings).
     
    Last edited: Oct 3, 2019
  9. Uckaynotebook

    Uckaynotebook Notebook Enthusiast

    Reputations:
    0
    Messages:
    22
    Likes Received:
    13
    Trophy Points:
    6
    xdyphx likes this.
  10. win32asmguy

    win32asmguy Moderator Moderator

    Reputations:
    856
    Messages:
    2,449
    Likes Received:
    1,203
    Trophy Points:
    181
    I tried the new driver, installed on top of 19.9.2 which worked fine other than the sleep / resume screen static issue is still present. The "Radeon Image Sharpening" option is available in the display settings.

    The 1.09 bios update worked fine for me, but after spending some time reading the Acer community forums it seems like very many models (not just ours) have a chance of bricking during an update. My only thought is maybe the Insyde bios update util has some strange bug related to the ITE update util (for the embedded controller) which can randomly cause the update to fail.
     
    Deks and Megol like this.
Loading...

Share This Page