Note on archived topics.
10-17-2016 01:21 PM - edited 10-17-2016 01:22 PM
I have a HP Pavilion g7-2361eb Azerty, and I also used to have another HP Laptop that I got from work.
I no longer have the one from work, but I still had the charger for it.
Now my cleaning lady decided to put all the chargers and everything she could find together, and I no longer know which charger I should use on the Pavilion g7.
These are the 2 chargers.
And I also found this info on my laptop:
I was told that I couldn't just use whichever chargers, because one is 19.5V and the other 19V, and the A-values are also different...
But then when I look at that picture on the laptop, it seems to say it has a range?
Thanks a lot for any support, because I cannot use my laptop, and I am too afraid to damage it if I pick the wrong charger.
10-17-2016 07:08 PM - edited 10-17-2016 07:12 PM
Either charger should work fine. One may be 65 watt and the other 90 watt. Most HP laptops can use either. Charger for my HP says 19.5~~4.62a.
Just an FYI. Your model is on the list of possible battery recall. You might want to check it:
**Click Accept as Solution on a Reply that solves your issue**
***Click the Thumbs-Up button as a way to say Thanks!***
10-24-2016 03:37 PM
Thank you for that information.
I used one of the chargers to boot the PC, and thought I would just do a restore and remove all data to start out fresh...
Around 47% of process, it stopped. And since then, if I try to boot it, it just shows the HP logo, goes black, HP logo, goes black and turns off...
I tried running a system test, and there as well it just turned off after some time... a couple of tests that did finished had passed...
Any idea what I can do here, please?
10-27-2016 02:05 AM
As running the complete tests always got stuck, I decided to give the components separately a try.
When trying the memory/processor one, I let it run for like 4-6 hours, and it was still only at 1%...
So it must have gotten stuck also there.
The moments before I did this **bleep** system restore this laptop was working perfectly... and now it's a big mess.