Screen Stuck automatically of Nitro AN515-57 series without having a load on CPU or GPU

omdhengle
omdhengle Member Posts: 1 New User

Whenever i keep laptop at idle screen on , web surfing or any work screen gets stuck. Nothing works no keyboard, no cursor. its been more than 2 year since i am facing this issue

Answers

  • Selenophile14
    Selenophile14 Member, Ally Posts: 16

    Hello!!

    @omdhengle

    Tried leaving laptop overnight at both “automatic repair” and the “please wait” screen. Tried holding left alt and f10. Tried right alt and f10. Tried holding all f buttons lol. Nothing can budge it off the repair loop. Black screen with logo and doesnt have any other links or options available.

    bought it new in 21 with the extra care package. Problem started after some some sort of automatic update.

    runnings windows 10 pro 

    whats my options now?

    Do this, as this is how you Fix Automatic Repair Loop in Windows:

    Step 1: Start your PC normally. Once you see the spinning dots, hold the power button for at least 10 seconds to do a hard shutdown. Do this twice.
    Step 2: On the third start Windows will boot into the Recovery Environment and from there you can access several options like Safe Mode, Sysem Repair, etc.
    Please try each option one at a time, then see if Windows will boot then proceed to step 3.
    Step 3: Go to Troubleshoot - Advanced Option - System Restore

    • Check to see if you have a restore point you can go back to
    • If you do not have a Restore Point, go to Troubleshoot - Advanced Option - Startup Settings and click Restart

    Enter Safe Mode
    Once in Safe Mode, backup your data.
    Open Device Manager and check to make sure all your drivers are up to date then
    Reboot to see if Windows will start Normally.

    Btw and imo its best if you are prepared to backup your personal files is to start fresh and to do a "Clean Install" as your OS has things wrong within its drivers that cause this loop and its best to restart and do all the updates properly again so that you never get this again, as you must have problems within your OS.  

    Regards,

    Selenophile14