BSOD POWER_STATE failure

The dump doesn't show anything of use. The system even log on the other hand shows you have a problem with your hard drive which looks to be a SK hynix SC311 SATA 256GB.

There are 22 of these entries in the system log split between \Device\Harddisk1\DR1 and \Device\Harddisk1\DR2.

Code:

Event[8227]:
  Log Name: System
  Source: disk
  Date: 2020-06-17T17:10:12.385
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: lam
  Description: 
An error was detected on device \Device\Harddisk2\DR2 during a paging operation.

Code:

Event[8639]:
  Log Name: System
  Source: disk
  Date: 2020-06-18T13:29:14.592
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: lam
  Description: 
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

Tests the SSD and see if it shows any problems but even if it doesn't I would look at replacing is as soon as you can.

Diagnostics Test
HDD TEST

Run HDTune to

• check the health,
• scan for errors, not quick scan but full scan
• run a benchmark.

Run CrystalDiskInfo Portable and CrystalDiskMark Portable to

• Check health of drive
• Check performance of drive

Run SeaGate SeaTools for Windows (test ALL hard drives - HDD/SSD/USB/etc)

You can also try the various options available with chkdsk, especially chkdsk /r /f.

That looks okay, give SeaTools a try.

Would also be good to test RAM and if that looks okay then run Driver Verifer to check for bad drivers:

===================================================
Up through DDR3, follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums
DDR4, follow this tutorial: MemTest86 v8.1 Free Memory Testing Tool Review

Both of these are diagnostic tools designed to test Random Access Memory (RAM) for faults. They will verify that:

• RAM will accept and keep random patterns of data sent to it
• There are no errors when different parts of memory try to interact
• There are no conflicts between memory addresses

They run from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

   Warning

MemTest86+ and Memtest86 need to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM. The new version of Memtest86 only allows 4 passes for the free version so run it twice, back to back.

If you are asked to run MemTest86+ or Memtest86 by a Ten Forums member make sure you run the full 8 (or 4+4) passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

   Note

Both of these diagnostics has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ or 4+4 passes of Memtest86 is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run it overnight, starting just before you go to bed and leave it overnight.

Take a picture when done and post in the forum please.

Run Driver Verifier

Driver Verifier-- tracking down a mis-behaving driver.

Following the instructions in the above link will check for problems in all non-Microsoft drivers.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.

To check if verifier is active, open a Command Prompt and enter:

verifier /query

If not active it will respond with

No drivers are currently verified.

If you have questions, see this additional tutorial which may help to clear things up.

Enable and Disable Driver Verifier in Windows 10

The 6/19 dump is a Driver Verifier triggered dump which is what we are looking for. It shows

Code:

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)

Unable to load image zamguard64.sys

FAULTING_IP: 
zamguard64+228
fffff80f`82da0228 2e686f6f6b00    push    6B6F6Fh

FOLLOWUP_IP: 
zamguard64+228
fffff80f`82da0228 2e686f6f6b00    push    6B6F6Fh

FAULT_INSTR_CODE:  6f6f682e
SYMBOL_NAME:  zamguard64+228
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: zamguard64
IMAGE_NAME:  zamguard64.sys
FAILURE_BUCKET_ID:  0xc4_2003_zamguard64!unknown_function
BUCKET_ID:  0xc4_2003_zamguard64!unknown_function

7: kd> lmvm zamguard64
Browse full module list
start             end                 module name
fffff80f`82da0000 fffff80f`82e22000   zamguard64   (no symbols)           
    Loaded symbol image file: zamguard64.sys
    Image path: zamguard64.sys
    Image name: zamguard64.sys
    Browse all global symbols  functions  data
    Timestamp:        Wed Aug 17 13:06:53 2016 (57B499AD)
    CheckSum:         000415E8
    ImageSize:        00082000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

zamguard64.sys

Name	zamguard64.sys
Info	Zemana ZAM AntiMalware driver
Source	Zemana Anti Malware: Best Premium & Free Malware Removal Software

You have ZAM_Guard ZAM Guard Driver ZAM Guard Driver Kernel System Running OK TRUE FALSE 0 143,360 0 8/17/2016 1:06:53 PM \??\C:\WINDOWS\System32\drivers\zamguard64.sys 8,192

Uninstall it once you can figure out what it's part of.

You could try reinstalling it then use Geek Uninstaller (free) to remove it, see if that gets rid of all the leftovers.

There was another instance of BSOD POWER_STATE failure, trying to figure out.
Btw, I have found a solution to wiping the driver, there was an thread on uninstalling the particular software and left over stuff.

I would like to know if there are more in dump-file than this specific one, Or Should I keep running Verifer to see what it leads to

- - - Updated - - -

I have attached the recent mini-dump -- the recent one,Attachment 284555