mikearmstrong
Beta member
- Messages
- 4
- Location
- UK
Hi, I have an Acer Travelmate p253 laptop running Windows 10 that has all of a sudden bricked on me. It was working absolutely fine until the other day when I went to do something on it and it was being really slow, would not open programs, wouldn't even open the start menu. I had to hard reset (holding down the power button) and when it booted back up I had to do a disk check. I did this and it was seemingly fine for the few hours after that I used it.
I then went on it the next day and it was being extremely sluggish again. I tried to restart it but it got stuck on the restart screen for an extremely long time and again, I had to hard reset. Since then I have not been able to get on my laptop at all. It gets to the Acer screen but cannot get past there. I can get into BIOS and the boot-loader-menu but that's about it. It simply tries to come on for a long time but comes up with a crash report and restarts before doing this again then attempts an automatic repair. It then seemingly goes to the automatic repair screen but I am met with a blank screen and nothing happens.
After looking online, I found that I can put the Windows 10 recovery files onto a USB drive, boot from that and then access the safe-mode, troubleshooting and repairs. So I made one of these drives, told the computer to boot from it and to no surprise of mine, it didn't help my cause whatsoever. I am pretty certain that it is booting from the device as I have set it as the first boot device and it goes to a different Acer screen before doing a similar thing to the automatic repair and taking me to a blank screen.
So currently I am struggling to work out what I can do. I can't access automatic repair, I can't boot to the files that allow me to repair my system otherwise, I can't even do a factory reset. So if someone has any idea of what to do, that would be very much appreciated.
Extra information:
-I did a Windows 10 update on the day this all happened so the issue could be a corrupted Windows, although the laptop worked fine for hours after before having any issues
-My laptop was idle when all of this occurred, it had been sitting on the desktop with no applications running for quite a while before this happened.
-After the disk check that I had to do, it was running fine for the rest of the night (from what I remember).
I then went on it the next day and it was being extremely sluggish again. I tried to restart it but it got stuck on the restart screen for an extremely long time and again, I had to hard reset. Since then I have not been able to get on my laptop at all. It gets to the Acer screen but cannot get past there. I can get into BIOS and the boot-loader-menu but that's about it. It simply tries to come on for a long time but comes up with a crash report and restarts before doing this again then attempts an automatic repair. It then seemingly goes to the automatic repair screen but I am met with a blank screen and nothing happens.
After looking online, I found that I can put the Windows 10 recovery files onto a USB drive, boot from that and then access the safe-mode, troubleshooting and repairs. So I made one of these drives, told the computer to boot from it and to no surprise of mine, it didn't help my cause whatsoever. I am pretty certain that it is booting from the device as I have set it as the first boot device and it goes to a different Acer screen before doing a similar thing to the automatic repair and taking me to a blank screen.
So currently I am struggling to work out what I can do. I can't access automatic repair, I can't boot to the files that allow me to repair my system otherwise, I can't even do a factory reset. So if someone has any idea of what to do, that would be very much appreciated.
Extra information:
-I did a Windows 10 update on the day this all happened so the issue could be a corrupted Windows, although the laptop worked fine for hours after before having any issues
-My laptop was idle when all of this occurred, it had been sitting on the desktop with no applications running for quite a while before this happened.
-After the disk check that I had to do, it was running fine for the rest of the night (from what I remember).