BSOD: DRIVER_POWER_STATE_FAILURE

I need a solution

seems that Symantec encryption 10.4.2 mp3 is causing bsod. actually I think its been happening in windows 10 for about a year. introduced with 1803/1809 carried over into 1903. so it may have started with earlier version not just mp3. pgpwded.sys seems to be the culprit. anyone else experiencing?

Windows failed to resume from hibernate with error status 0xC0000001.

Microsoft-Windows-Kernel-Boot

Keywords (8796093022208)

FailureStatus: 3221225473

FailureMsg: A fatal error occurred processing the restoration data

The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009f (0x0000000000000003, 0xffff800efe7ea060, 0xfffffe01efc8f7b0, 0xffff800f0ccee6e0). A dump was saved in: C:WINDOWSMEMORY.DMP. Report Id: 2830e9ce-7a77-4bad-85b4-1983571d377a.

The previous system shutdown at 1:43:24 AM on ‎10/‎18/‎2019 was unexpected. <- Interesting, that is probably the time I hibernated before shutting down to go to sleep…and this error showed up in the log after the boot failure 8 hours later marked 9:41:21AM…

10/18/2019 9:41:08 AM The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. <- That is when the fault happened.

Session “ReadyBoot” stopped due to the following error: 0xC0000188 <- Does ReadyBoot have anything to do with Fast Start? I am going to try to disable Fast Start and see if that makes any difference…

0

Related:

The computer has rebooted from a bugcheck. The bugcheck was: %1. A dump was saved in: %2.

Details
Product: Windows Operating System
Event ID: 1001
Source: Save Dump
Version: 5.2
Symbolic Name: EVENT_BUGCHECK_SAVED
Message: The computer has rebooted from a bugcheck. The bugcheck was:
%1.
A dump was saved in: %2.
   
Explanation

The computer has restarted from a bugcheck. The event log contains details about the cause of the bugcheck.

   
User Action

If an error report was generated for this error, you might be able to obtain more information about the error by sending the report to Microsoft for analysis.

What to expect

Microsoft actively analyzes all error reports and prioritizes them based on the number of customers affected by the error signature contained in the report. When a report is submitted, Microsoft will try to determine the cause of the error, categorize it according to the type of issue encountered, and send you relevant information when such information is available. However, because error reports do not always contain enough information to positively identify the source of the issue, Microsoft may might need to collect a number of similar reports from other customers before a pattern is discovered. Although Microsoft might not be able to provide a solution for your particular error at this time, all information submitted is used to further improve the quality and reliability of our products.

Related: