PH315-52-78VL Restart issues (Helios 300)

alcer350
alcer350 Member Posts: 4 New User
edited November 2023 in 2020 Archives
Hi guys, just got a new Predator Helios 300 PH315-52-78VL that only seems to have an issue when I tell it to "Restart" from Windows 10. It will go to the restarting screen then after that the screen stays black, keyboard stays lit up for a while then turns off. Nothing else happens until I hold the power button to force shut down. "Shut down" works fine from Windows 10 desktop but not "Restart". This is a problem because I am trying to update the BIOS but since it needs to restart the computer it can't. I uninstalled the 1660 TI graphics driver and installed the ones from Acer support page. This did not work. When I get back to my hotel room (working away from home) I will try to uninstall the Intel display drivers and install from Acer as well but was wondering what else to check? I checked the ram cards making sure they are seated properly as well.

Best Answer

  • Balatekie
    Balatekie ACE Posts: 1,353 Pioneer
    Answer ✓
    alcer350 said:
    Well not sure what happened but after I installed the second drive back in the laptop and try to restart the laptop it works now...hopefully it stays that way. I was able to update the bios also.
    Great! I am glad that you finally got it to work. :)
     :) If you think I've answered your question, please hit the Accept Answer:)

Answers

  • Balatekie
    Balatekie ACE Posts: 1,353 Pioneer
    Hi!!

    @alcer350

    Perform clean boot

    When your device starts normally, Windows 10 loads many services, drivers, and applications, which remain running in the background, if one or more them is causing issues, it's possible that you will come across a black screen.

    Using a clean boot allows you to instruct Windows 10 to start only with a minimal set of services, drivers, and apps, which can help you to figure out if something running in the background is the cause of the screen going completely black.

    A clean boot is similar to safe mode, but it allows you to re-enable one service or software at a time, which can help to pinpoint the problem more accurately.

    To perform a clean boot, use these steps:

    1. Open Start.
    2. Search for msconfig, click the System Configuration result to open the experience.
    3. Click the Services tab.
    4. Check the Hide all Microsoft services option.
    5. Click the Disable all button.

    6. Click the Apply button.
    7. Click the Startup tab.
    8. Click the Open Task Manager option.
    9. Click the Startup tab.
    10. Select each application, and click the Disable button in the bottom-right corner.

    11. Close Task Manager.
    12. Click the OK button in the "System Configuration" experience.
    13. Restart your computer.

    While this process won't fix the problem, it'll give you an idea of where to start looking to resolve the issue.

     :) If you think I've answered your question, please hit the Accept Answer:)

  • alcer350
    alcer350 Member Posts: 4 New User
    edited July 2019
    Balatekie said:
    Hi!!

    @alcer350

    Perform clean boot

    When your device starts normally, Windows 10 loads many services, drivers, and applications, which remain running in the background, if one or more them is causing issues, it's possible that you will come across a black screen.

    Using a clean boot allows you to instruct Windows 10 to start only with a minimal set of services, drivers, and apps, which can help you to figure out if something running in the background is the cause of the screen going completely black.

    A clean boot is similar to safe mode, but it allows you to re-enable one service or software at a time, which can help to pinpoint the problem more accurately.

    To perform a clean boot, use these steps:

    1. Open Start.
    2. Search for msconfig, click the System Configuration result to open the experience.
    3. Click the Services tab.
    4. Check the Hide all Microsoft services option.
    5. Click the Disable all button.

    6. Click the Apply button.
    7. Click the Startup tab.
    8. Click the Open Task Manager option.
    9. Click the Startup tab.
    10. Select each application, and click the Disable button in the bottom-right corner.

    11. Close Task Manager.
    12. Click the OK button in the "System Configuration" experience.
    13. Restart your computer.

    While this process won't fix the problem, it'll give you an idea of where to start looking to resolve the issue.

    Thanks!! I figured out what was causing it. The second M2 ssd drive that I installed that has all my Steam games on it for some reason would not let the laptop boot from the C drive OS. How can I make sure it always boot the C drive even when restarting it?
  • alcer350
    alcer350 Member Posts: 4 New User
    Well not sure what happened but after I installed the second drive back in the laptop and try to restart the laptop it works now...hopefully it stays that way. I was able to update the bios also.
  • Balatekie
    Balatekie ACE Posts: 1,353 Pioneer
    Answer ✓
    alcer350 said:
    Well not sure what happened but after I installed the second drive back in the laptop and try to restart the laptop it works now...hopefully it stays that way. I was able to update the bios also.
    Great! I am glad that you finally got it to work. :)
     :) If you think I've answered your question, please hit the Accept Answer:)

  • prajin1
    prajin1 Member Posts: 3 New User
    @alcer350 Hey there, could you please let me know how did you solve the issue? I just bought my laptop yesterday and I am having exactly the same problem. I have installed a single ssd. Thank You. 
  • alcer350
    alcer350 Member Posts: 4 New User
    prajin1 said:
    @alcer350 Hey there, could you please let me know how did you solve the issue? I just bought my laptop yesterday and I am having exactly the same problem. I have installed a single ssd. Thank You. 
    All I did was remove the extra ssd, turned it on making sure restart works, then turned it off and plugged the extra ssd back in. After that the issue never came back. Still hasn't to this day.