Laptop won't boot

[AIZ-Mayune]

My acer aspire v5 laptop suddenly stopped booting. Black screen (sometimes it blinks), the fan starts spinning stops after a few seconds and the acer logo didn't appear.

Before this happened, it takes time for the acer logo to appear. It happened probably during the time I updated my touch pad, wifi/bluetooth, and audio drivers. A few days later I overused my laptop leaving it open for 2 or 3 days without rest? The not-booting started when I hibernated my laptop and turned it on. Then it persisted for after a few days.

I already removed and reinstalled the CMOS battery after 30 seconds, I already tried removing the HDD, I already tried removing the memory, I already tried removing the battery and connect it to a/c adapter, still nothing.

Here's the specs of my laptop:

AMD A10-5757M 2.5GHz
AMD RadeonHD 8750M
8GB Memory
1TB HDD
Windows 10 Home

 

[Laptop_Nerd]

Hi,

Here are some troubleshooting steps that may help in solving the issue.

- Do a hard reset first, remove the battery and AC adapter then press and hold the power button for 20 seconds then try to boot the laptop.
- Next is to test the AC adapter and see if it's supplying enough voltage or better yet try another AC adapter that has the same voltage.
- If there are lights on the laptop indicating that it's on connect and external monitor and see if you'll get any display from it and if you do press the Windows key + P at the same time and select Display Only then press Enter.
- If that will not solve the problem do reseat the RAM, remove them all for couple of seconds then put them back in making sure that they are seated properly into each slot.
- Lastly, try and connect an external monitor and see if you'll get a display from it or not because if you do that means it's the problem to the display.
- If all these will not work you may need to contact the manufacturer for a repair if it's still under the factory warranty.

 

[AIZ-Mayune]

I've tried most of them, and nothing happens.
I went to an acer service center and asked about my problem, and it turns out the motherboard was the problem.