Driver Power State Failure on restart, shutdown, sleep

Okay will do. I did perform a repair install as mentioned on my OP before I sought help on here. In fact I did it twice and it didn't fix the issue. But as of now the problem is resolved, but I hate not knowing what the problem was in case it does come back. Would you like me to mark this has solved or wait some time in case celebration is premature?

Had you considered troubleshooting the log corruptions of/in the event viewer:

Code:

Event[5150]:
  Log Name: System
  Source: Microsoft-Windows-Eventlog
  Date: 2020-01-24T14:25:06.672
  Event ID: 106
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Service availability
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: CTEZ-PC
  Description: 
Corruption was detected in the log for the Security channel and some data was erased.

Code:

Event[3300]:
  Log Name: System
  Source: Microsoft-Windows-Eventlog
  Date: 2020-01-21T17:47:18.405
  Event ID: 106
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Service availability
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: CTEZ-PC
  Description: 
Corruption was detected in the log for the Microsoft-Windows-Winlogon/Operational channel and some data was erased.

Code:

Event[2396]:
  Log Name: System
  Source: Microsoft-Windows-Eventlog
  Date: 2020-01-21T09:52:37.501
  Event ID: 106
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Service availability
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: CTEZ-PC
  Description: 
Corruption was detected in the log for the Microsoft-Windows-Wcmsvc/Operational channel and some data was erased.

Code:

Event[2390]:
  Log Name: System
  Source: Microsoft-Windows-Eventlog
  Date: 2020-01-21T09:52:34.979
  Event ID: 106
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Service availability
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: CTEZ-PC
  Description: 
Corruption was detected in the log for the Microsoft-Windows-Storage-Storport/Operational channel and some data was erased.

Code:

Event[2299]:
  Log Name: System
  Source: Microsoft-Windows-Eventlog
  Date: 2020-01-21T09:33:40.843
  Event ID: 106
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Service availability
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: CTEZ-PC
  Description: 
Corruption was detected in the log for the Microsoft-Windows-PushNotification-Platform/Operational channel and some data was erased.

I hadn't. I wasn't even aware of these logs. Do those events tell you anything specific to look at or look for?

Make a new restore point:
Create System Restore Point in Windows 10

Make a backup image using Macrium and save the image to another disk drive:
Macrium Software | Your Image is Everything
Backup and Restore with Macrium Reflect


These are trial and error troubleshooting steps:
https://support.microsoft.com/en-us/...ewer-log-files

After lurking this thread since the beginning, I thought I would add my solution just in case it helps anyone having the Driver Power State Failure BSOD.
First of all, I had tried every other solution, including Resetting the PC.
The only thing that seems to have worked (for 5 days so far) was disabling all the Graphics card start-ups (Scheduled Tasks and Windows Services) with Ccleaner.
It didn't cause any problems with the GPU, it functions the same as before.
It seems to have worked for me so I thought I would add it to the list of possible fixes.

what you mean by graphic card startups? can you explain, i have the same problem

GRH said:

After lurking this thread since the beginning, I thought I would add my solution just in case it helps anyone having the Driver Power State Failure BSOD.
First of all, I had tried every other solution, including Resetting the PC.
The only thing that seems to have worked (for 5 days so far) was disabling all the Graphics card start-ups (Scheduled Tasks and Windows Services) with Ccleaner.
It didn't cause any problems with the GPU, it functions the same as before.
It seems to have worked for me so I thought I would add it to the list of possible fixes.