-
×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
- STOP in PsMain Error code: 0x5001579

Create an account on the HP Community to personalize your profile and ask a question
02-29-2016 03:23 AM
When i turn on notebook the screen display "STOP in PsMain Error code: 0x5001579" on o blue backgroud. As you see on a picture. How can I solve this problem ?
03-01-2016 12:30 AM - edited 03-01-2016 12:31 AM
Hello,
Thank you for posting in the HP Support Forum.
You are using business class computer and this error occured because of failed component in CheckPoint (Pointsec) full disk encryption
It seems your computer is a business one and its HDD has been encrypted with Checkpoint software.
If this is the case, please contact your company's local helpdesk and ask the encryption support or security team to step in. They will use one of the many methods to fix the problem.
*** HP employee *** I express personal opinion only *** Joined the Community in 2013
04-01-2016 08:46 AM
Interesting... I have one laptop with the same model that just got this problem today 1st of April!!!
This could be some updates deployed???
Unfortunately seems we have to format again the computer and lose all the data on it 😞
04-01-2016 08:55 AM
Hello @RSousa
There is not much that can be done at the moment - usually data can be recovered using DMU tool
>> http://dl3.checkpoint.com/paid/d1/CP_2.0_FDE_Dynamic_Mount_Utility_AdminGuide.pdf?HashKey=1459529699...
Please, note that this is Checkpoint FDE / Pointsec / problem - this is not related to HP.
Please, get in touch with your company helpdesk OR contact Checkpoint support team for assistance.
Thank you for your understanding !
*** HP employee *** I express personal opinion only *** Joined the Community in 2013
09-30-2016 11:30 AM
I have found this error occurs at power up when I have inadvertently plugged in my USB cable I utilize to charge my phone. The order of which it bootstraps in the BIOS is having it look at external ports, thus looking for that script from my plugged in phone, ostensively. If I don't have my phone plugged in, it powers up and accesses the internal script like it should.
Amending the order in which is looks for the Checkpoint script in the BIOS via F10 is one way to avoid this error - or just remembering not to have anything plugged into USB ports at power up.