Resolve Acer ATC 605 desktop forever reboot loop (before POST) issue

Long Story Short
Problem: Acer ATC-605 desktop (ATC-605-UR13) in forever reboot before POST.
Cause: Malfunction 300W power supply unit (My best guess: Not enough power during bootup)
Solution: Replace the 300W power Supply unit with another 380W power supply unit

Long Story
It's a love and hate to Acer computer. The love is the price really reasonable. And the hardware quality would make you hate Acer never want to buy from the brand again.

I bought a refurbished "Acer ATC-605-UR13 (i.e. Aspire TC 605) Core i5-4440 10GB 1TB WiFi HD 4600 DVDRW Windows 8.1 Desktop" in 2014. In the very beginning, I found it rebooted by itself once in a while. Later after upgrading it to Windows 10, it worked sometimes and did not boot up most of the time. When it was unable to boot up, the screen is blank, no beep code, no POST (Power on self Test) screen. The CPU FAN spinned one time in 3-5 seconds. Then, the computer turned off itself and rebooted itself and started the reboot cycle again. This is a very frustrated experience. 

Since I'm living a busy life and I have other notebook to use, I leave it on the corner of the desk until recently. I was thinking that I'm lacking a reliable desktop to store family photos/videos. I pulled the Acer desktop out and see if the booted problem can be fixed. 

The reason I wanted to fix it is: the CPU i5-4440 is amazing fast (6398 passmark score which it is faster than a lot of low-end i7 CPUs, per reference in cpubenchmark.net). It has plenty of ram 10GB !!!!!!!. It can be upgraded and running to Windows 10 with no issue at all when it is booted up.

I'm not a hardware person. What I can do it is to observe the obvious symptoms and trying to narrow down to it. I tried below list of things:

- Upgrade the firmware to the latest one and reboot- Remove all ram and reboot- Replace the power supply and reboot- Unplug all the harddisk and cd-rom and reboot- Unplug ram and reboot- Remove secure boot from BIOS- Disable UEFI from BIOS- Clear the CMOS using battery removal or jumper- Disable most of the thing not needed from bios. - Reinstall the Windows 10 (from Reset command)- Google the sympotms and tried out all the solutions from the Web.

All of the above never can get ride of the reboot loop problem. Last thing I tried is to use the POST Diagnostic card to see the code where the boot up process stopped before the POST. The POST Diagnostic card is in progress of delivery from Ebay. Before it arrived, I found that when I removed the harddisk and DVD-ROM connection and after the CMOS is cleared. Sometimes the system can be rebooted up and can be used until the PC is shutdown. And the reboot problem come back again in next reboot. 

When looking from the web solutions, I noticed that the i5-4440 CPU consumed 82W power. And the default power supply got 300W power. 1/3 of power already going to the CPU. And sometimes, when the harddisk and DVD-ROM were disconnected (power and signal cable), the PC can be booted after POST. I was thinking two issues. Could it be a short circult protection from the power supply. Or simply not enough power during the PC boot up process. So, this Sat. morning, I went to Frys to buy a 380Watt power supply ($12.99 after rebated) and give it a shot. Volla, this is the first time in the last months the PC can be booted up with no problem. The 380W PSU resolved the problem YAY. 

I don't know the real cause yet. I have a friend who works as architect to design PSU. I'll certainly go to him and consult him why. 

A solution to Project Fi activation error code B010

Background:

(In case you want to know the solution right away, you can skip the Background to read the solution  section down below)

I'm a Project Fi user for couples months. I enjoy so much the service, the freedom to use or not to use the data and it costs me $23 each month include everything (fee and tax) because of the unused data refund. With the recent $199 Nexus 5x deal, I bought a Nexus 5x phone for my another family member to transfer the phone number to Project Fi to save more money.

I got the phone with a new SIM Card and trying to activated with a new google account. During activation, I got the error code B010. I call the Project Fi support from the activation App page. For 45 minutes, we tried different things to trying to resolve the activation issues, but nothing worked

Then, the Fi support said the SIM card was associated with the Google account where the phone and SIM card is purchased that it cannot be activated under to another Google account unless the association is broken. The funny thing is: even on their end, they does not have method, in a more software term "interface", to remove the association. We kind of stuck there.

The Fi support suggested to activate the new phone and new SIM with "phone purchased" Google Account that the SIM card is associated as one Google account can associate more than one line and phone.  I followed to activate the phone to the "phone purchased" Google Account.  Somehow, the new phone and new SIM is taking over my own phone instead of my family member phone number. i.e. In one option, I choose to use Primary number because it warns me the other option won't receive call and text which is useless.

Finally, the Fi support suggested to email me a link to purchase a new SIM card (free of charge) that this SIM card does not associate with any account.

So, now, the new Phone and new SIM got my old number. My old 'SMART' phone and old SIM became a DUMB WIFI device cannot make a call. Before getting the NEW SIM card, I put back the just activated SIM card on my old phone. I discover below solution doesn't need an extra new SIM card.

Problem:

New Phone and New SIM purchased from a Google account would fail with code B010 while activating the Project Fi with another Google account.

Root Cause:
New SIM order from 'A' Google account is associated with the 'A' Google account which is not able to activate to 'B' Google account in Project Fi unless the association is broken.

Brief Solution:

1. Activate the new SIM and new phone with the Google account that purchased the SIM and Phone
2. Activate the new SIM with the old Phone with the old phone existing Google account.
3. Old SIM is now made inactive.
4. Activate the Old SIM + New Phone with any Google account you want.

It's like swapping the two values of A and B with a temporary variable X.

X=A

A=B

B=X

Details solution steps:
1. Associate the new phone and new SIM card with the "phone purchase" Google account by activated the new phone and new SIM card with the "phone purchase" Google account.
2. Pull out the just activated SIM card and put it inside the old Phone and do the activation with the "purchase" Google account. --->; Yay, I got my old phone number back on my old Nexus 5x phone with the "new" SIM.
3. Somehow, step 2 did the trick to break the old SIM card association with the old Google account.
4. Put the old SIM card (i.e. the SIM card just got pull out replaced by the new SIM for my Old Nexus 5x) inside the new Nexus 5x phone and do all the activation with the NEW Google account.
5. Unexpectedly smooth within 5 minutes, the New Phone is activated with the old SIM card and with the NEW Google account. (The activation asks me the a new phone number and it's carrier transfer information).

The magic is to activate the new SIM (Step 1) with the new phone. Then, deactivated the old SIM (Step 2) by activate the new SIM again with the old phone. Somehow the old SIM is made "inactive" in Project Fi page status. Then, the old SIM is free to use to activate on another Google account (Step 4 and 5).

In case you have interest, you read below detail background.

Conclusion:
Kudo should be given to Project Fi support. The support I talked to is very sincere and patience clarifying a lot of questions I asked. Though the support did not directly point me to the solution, The support trying as much help as possible. Without the support willingness to help, I will never try "Step 1". And I learned that It's not the phone associated with the Google account. It's only the SIM card associated with the Google account. And this association cannot be broken by a interface from Project Fi support (as least the one I called doesn't has interface to do so). Maybe future, the Project Fi team can add this feature to their support interface. Before that, please try my discovery and let me know if it works for your in comments. :)

Side node: Thanks to Roger Hu posting the root cause of B010 http://hustoknow.blogspot.com/2016/03/project-fi-and-b010-error-codes.html, Somehow the Project Fi support is unable to transfer the Asset Id from one account to another. I'm glad I don't need 3 weeks to resolve this issue. :)