I received the unit inoperative. At the time of my original post, I had tried all the known remedy to bring the DC53427HYE out of what I thought was hibernation mode. Since there was no POST (unable to wake from hibernation) I had no clue what BIOS version was installed. There was no drive, no memory, and no wireless connected. I had installed a blank Micron 256GB mSata drive, 16Gb Hynix 1.35v 204 pin SODIMM ram to test. When powered up with correct power supply there was nothing to indicate it had power until I gave the power button one short press. The blue light came on then when off for about 5 second, then illuminated again, then repeat the same cycle. I was able to long depress the power button to return the unit to no blue light. Once the unit was disassembled, and powered on by the correct power supply I noted that there was a green light illumination on the back side of the motherboard. There was no cooling fan operation at this point. Subtracting memory, swapping memory, Shorting CMOS jumper, removing the clean mSata drive, removing the CMOS battery all had no effect. Not as a single operation or combined operation of removing or swapping hardware.
The actual fix was to re-flow the CPU and chip set on the motherboard. There was no visible damage to the motherboard under a microscope. The only conclusion I could make was an apparent broken or cold solder contact. Heating the back side, opposite side of motherboard from the physical chips did the trick. Unconventionally this was done with the heat sink still attached binding the cpu to the opposite side of the motherboard. A solder reflow heat gun was used along with three thermal probes to establish uniform heating.
Once the board was allowed to naturally cool to ambient temperature, it was repopulated with drive, memory, and wireless. Power was applied and the unit started normally to visual BIOS. The unit was next fully assembled and tested again by loading Microsoft Windows 8.1 Professional. Everything loaded, works normally and allows me to write this reply from the very same unit.
I knew this problem was rather unique as I have not seen one other occurrence as I have described. The repair was beyond orthodox, and very likely one that would render the unit beyond repairable, but I was at the point where a failed attempt would be better than no attempt to repair.I am quite happy with the end result.
N. Scott Pearson
Read the post carefully son, the method used to repair the non-functioning board is NOT only unorthodox, it very well can destroy an otherwise good board. I was not working with a good board.
Not many DIY repair folk have access to a digital microscope or a test bench equipped to handle circuit analysis. The solution I chose was not random. The solution was carefully controlled.
Again, this was a unique solution to a rare yet specific fault.
FYI... This single DC53427HYE works flawlessly to this day and does pass very stringent testing.
Oh, I understood the description just fine; I was making a joke.
I actually don't consider it unorthodox either. Working at Intel for many years (though as a S/W engineer - and now retired), I had plenty of opportunities to watch this being done. Every time FAB A samples of a new product came in from the factory, some level of repair or rework usually proved necessary...