ACER Aspire desktop - 4 beeps on SHUTDOWN now won't boot
On power up, the power light blinks for awhile before lighting steady. But NO beeps during power up. I've tried re-seating RAM with no success... any ideas?
Answers
-
- Remove all external devices including mouse dongle.
- Unplug charger and disconnect battery from mainboard. Replace bottom cover.
- Plug charger back in. Turn it on.
- If still nothing, reconnect battery. and remove RAM sodimm. Replace bottom cover or RAM door.
- Turn it on and immediately tap F2 to try to enter BIOS menu.
- If still no success, replace RAM sodimm and disconnect HDD or SSD. Replace bottom cover or HDD door.
- Turn it on and immediately tap F2 to try to enter BIOS menu.
Report back.
Jack E/NJ
0 -
"disconnect battery" - I have a desktop, not a laptop. Are you referring to the CMOS battery?
0 -
"disconnect battery" - I have a desktop, not a laptop. Are you referring to the CMOS battery?
0 -
Sorry, what's the full desktop model number? For example TC-885? Meanwhile, can you access BIOS menu on startup by tapping ESC or DEL immediately after turning machine on?
Jack E/NJ
0 -
I don't know the model number off the top of my head. The PC is in my car, ready to be looked at for repair, so I don't have any way to try ESC or DEL. I won't be able to until Monday.
0 -
OK. I'll stand by.
Jack E/NJ
0 -
I'll try the ESC or DEL immediately after power on, this evening. But I had an IT friend of mine take a look at it over the weekend, and 99.9% sure the motherboard was bricked due to a corrupt driver update. He disconnected everything but the CPU but couldn't even get it to boot to BIOS.
0 -
The only kind of update that has a high risk of bricking is BIOS firmware. Rarely a device driver. What's the full desktop model number anyway? For example TC-885?
Jack E/NJ
0 -
I ran Auslogics "driver updater" just before it happened. That's the only cause I can think of. Will get you the model number asap.
0 -
It's am Acer TC-120 desktop
0 -
Updater should've been OK unless you downloaded it from a dicey site. Why & what were you trying to update?
Jack E/NJ
0 -
Got it straight from Auslogic. The utility indicated that some drivers were old... really old. I was just trying to get things updated.
0 -
Yes. But why? Driver updates are primarily meant to fix problems. So what problems were the 'really old' drivers causing?
Jack E/NJ
0 -
And 'really old' drivers are 'really old' because they were working correctly. :) Updates typically are either to fix a problem or to add support for newer hardware within the same driver package...
Click on "Like" if you find my answer useful or click on "Yes" if it answers your question.0 -
I wad hoping for the "performance boost" promised by Auslogics. Lesson learned, I suppose.
0 -
Only a BIOS firmware update has a significant risk of bricking the mainboard. Do you know what updates it was proposing to apply? Did the machine react badly before while loading the updater, during the update process or after the update process completed?
Jack E/NJ
0 -
I don't remember exactly which updates. However it "bricked " AFTER I ran the utility. I have since bought a new motherboard and am back up and running
1 -
>>>I have since bought a new motherboard and am back up and running>>>
Well, that's one sure-fire way of solving the problem. 🙂 Thanks for reporting back.
Jack E/NJ
0 -
I'm 99.9% sure the old motherboard was bricked. My IT buddy disconnected everything but the CPU and it wouldn't even boot to BIOS.
0 -
I doubt the updater was responsible. But a strange coincidence. Unless it tried to apply errant BIOS firmware.
Jack E/NJ
0
