-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Notebooks
- Notebook Boot and Lockup
- Re: CMOS Reset (502) black screen

Create an account on the HP Community to personalize your profile and ask a question
07-19-2022 04:32 PM - edited 07-19-2022 04:39 PM
@Francesca5 wrote:Hello @ub6424 !
As I promised, here it's a photo of my laptop. I removed the battery and I confirm there's no sign of CR2032 battery, so I suppose that @WyreNut is right , The main battery provides the voltage for the internal clock.
Thank you for the picture
I checked the service manual again, it seems that there is indeed no CR2032 battery installed.
Clone your current hard drive and put in a SSD drive:
https://www.amazon.com/SAMSUNG-500GB-Internal-MZ-77E500B-AM/dp/B08QBMD6P4
07-19-2022 05:05 PM
I already have a SSD where the SO has been installed and I don't feel my laptop is slow even storing some documents on HDD.
I'm asking because I'm not able to understand if this upgrade from HDD to a SSD will permanently resolve this CMOS Reset black screen.
07-21-2022 05:28 AM - edited 07-21-2022 05:34 AM
Hi everybody, noted that there isn't any CR2032 battery, that the internal clock is powered by main laptop battery and that I didn't receive any answer from support in 2 days, I say that my problem is solved by replacing old battery of my laptop, so no CMOS Reset (502) black screen has been displayed anymore.. Additionally in my case there was no need to switch from a HDD to a SSD like suggested before.
However due to the battery replacement I have another issue that it's not linked to this thread, so this topic can be closed.
07-21-2022 08:36 AM
@Francesca5 wrote:I'm asking because I'm not able to understand if this upgrade from HDD to a SSD will permanently resolve this CMOS Reset black screen.
It was only a hint. Of course, this had nothing to do with the current CMOS problem.
Good luck
- « Previous
- Next »