HP Envy 17 doesn't turn on after S.M.A.R.T. error

Bromeh

Honorable
Dec 6, 2012
27
0
10,580
This is going to be long so thanks to all the ones that keep with me on the subject.

I first got my HP Envy 17-j070ca a couple weeks ago and it was working fine. Since then, I decided to add memory (got the exact same specs ram, same size), then followed an SSD. I reinstalled Windows 8 and my drivers and everything worked like a charm. But then, I started doing some "hardcore" stuff like benchmarking the computer, playing games etc. I saw that my temps were too high (90c) so I decided to take the whole laptop apart and change the paste. I replaced the basic one with some Coolaboratory Liquid Ultra. Temps were a little better, but not a big change. I decided to leave it like that. And here comes the problem : I left the laptop on for about 5-6 days, coming back from school jumping on it doing my things and then going to sleep, without turning it off. On the 5th or 6th day, when I came back from school, I had a Windows error saying something like "there has been a weird problem and we don't know what it is, now scanning the hard drive" and it stayed at 0% for ever. Turned the computer off, thought it was only a little problem. Then, I start the computer up and I see a SMART error message saying that there is a problem with my hard drive and that I should change it ASAP. I just ignored it because I had an SSD installed and I was sur it wasn't the cause of this problem, maybe something else. Turned the computer on and off until I could boot in Windows. I was able to use it for a few seconds, enough to see my temps and they were at 65c, just booting. Then it did the error message again and said it was about to scan the computer but it stayed at 0% the whole time. Finally turned it off, but it wouldn't turn back on.

Now, I am stuck with a laptop with no warranty and I don't know what to do, I tried EVERYTHING. Tried removing the ram, using 1 stick, doesn't work. Changed the hard drive, nothing on that side. Removed the cmos battery since there is no erase cmos jumper, didn't help either. And finally, I removed the processor which I think is the cause of all this mess, but it didn't change a thing.

Help !?
 
Solution
If it's not turning on at all, could be the motherboard or the power circuit which may mean replacing the motherboard. You should have contacted HP if you noticed it was getting too hot for a warranty fix or at least check with them what the temperature should be.
 
The Coollaboratory liquid pro compound is conductive, meaning that if you got any of it on part of the motherboard, especially on electrical components and/or areas with an electrical path, it would have caused electrical damage to the system.

There's also always the potential for ESD damage if you serviced the system while not grounding yourself.
 

Bromeh

Honorable
Dec 6, 2012
27
0
10,580


It may be the problem, but is there a way to make sure it is the problem ? Because I read on many websites that people had kind of the same problem as me and the replaced the motherboard to no success.



I made sure I only applied it on the cpu and gpu so there are no worries on that side. Though, when I lifted up the little black sticker that covers some circuits on the cpu itself, I noticed a little bit of paste. But, I forgot to mention, that I accessed the BIOS before not being able to turn the laptop on and I could see my cpu listed. Also, the fact of booting without the cpu would make a difference doesn't it ? If the cpu is the broken part.
 


There is no way to fully rule something out when the system does not start. You can try a new keyboard or power supply, or try without a battery or with a new battery. Change the RAM and CPU. There could be a short in a component causing an issue, without swapping out parts for good ones one at a time, you won't find the cause. You can start by going cheapest to costliest part and hope one of the cheaper parts is the issue, or start with the most likely part which is the motherboard, although I have seen a few times where a bad keyboard caused issues.
 
Solution