BSOD POWER_STATE failure

Page 1 of 2 12 LastLast

  1. Posts : 47
    windows 10
       #1

    BSOD POWER_STATE failure


    Windows 10: 1909 18363.900
    Dell Inspirion 7375 laptop
    Ryzen 2500u

    Today, out of the blues, I have got BSOD POWER_STATE_Failure, there were two BSOD within 24 minutes interval. I have looked up the on the event . I found little odd because frequent bsod I haven't received for awhile especially this one



    6/18/2020 2:2013
    EventID 41
    Version 6
    Level 1
    Task 63


    BugcheckCode 159
    BugcheckParameter1 0x3
    BugcheckParameter2 0x0
    BugcheckParameter3 0x0
    BugcheckParameter4 0x0
    SleepInProgress 4


    PowerButtonTimestamp 0
    BootAppStatus 0
    Checkpoint 11
    ConnectedStandbyInProgress false
    SystemSleepTransitionsToOn 2
    CsEntryScenarioInstanceId 0
    BugcheckInfoFromEFI true
    CheckpointStatus 0




    Date: 6/18/2020 12:54 PM
    Event ID: 41
    Task Category: (63)
    Level: Critical
    Keywords: (70368744177664),(2)
    User: SYSTEM


    EventID41

    Level1
    Task63
    Keywords 0x8000400000000002
    EventRecordID 83954
    ProcessID Core ="4" ThreadID="8"
    >

    BugcheckCode 159
    BugcheckParameter1 0x3
    BugcheckParameter2 0xffffb70f19168b60
    BugcheckParameter3 0xffffd9855e0538b0
    BugcheckParameter4" 0xffffb70f1996e9a0
    SleepInProgress" 0

    PowerButtonTimestamp 0
    BootAppStatus 0
    Checkpoint 41
    ConnectedStandbyInProgress false
    SystemSleepTransitionsToOn 13
    CsEntryScenarioInstanceId 0
    BugcheckInfoFromEFI false
    CheckpointStatus 0



    I am unable to find what the reason could be , I have taken look around to see what the problem with this related to. I ruled out display adapter or heat issue, the driver has been stable for the graphic and I have monitoring CPU temp with HWinfo
    Attachment 283997
      My Computer


  2. Posts : 13,960
    Windows 10 Pro X64 21H1 19043.1503
       #2

    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.
      My Computers


  3. Posts : 47
    windows 10
    Thread Starter
       #3

    Thanks for feedback, I ran the diagnosis on pc. As you had mentioned about testing the ssd, I ran crystaldiskinfo---- Health status states its good, I have also looked into the wear count, here is an screenshotAttachment 284025
      My Computer


  4. Posts : 13,960
    Windows 10 Pro X64 21H1 19043.1503
       #4

    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   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   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
      My Computers


  5. Posts : 47
    windows 10
    Thread Starter
       #5

    I have tested memory with MemTest, doing 4+4 pattern, The result shows passed, no error on multiple run of the test.

    Attachment 284123

    - - - Updated - - -

    As per the instruction on activating Verifier, with set of steps, restarted the computer, BSOD appeared, same message appeared on both occasion "Driver_Verifier_detected_Violation", This triggered to run E-PSA dells diagnosis , then it prompt with windows 10 automatic repair which I was able to boot into safe mode and disable it in order to get back to windows.
    Afterward, I ran V2 logger, Attachment 284132

    - - - Updated - - -

    Ztruker said:
    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.
    Btw I didn't find DMP file in Windows
      My Computer


  6. Posts : 13,960
    Windows 10 Pro X64 21H1 19043.1503
       #6

    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.
      My Computers


  7. Posts : 47
    windows 10
    Thread Starter
       #7

    Thanks, Is this the culprit of BSOD, of this particular one_Driver Verifier ? I understand with the help of verifier, it pinpoint to one of the driver that was causing bsod, where the rest of the driver hasn't been evaluated or runned

    For this particular driver zemana , . How would I go about with this, since, it is uninstalled. Should I just delete from the path location or registry? I want to trace all the zemana application files that has been left behind.
      My Computer


  8. Posts : 13,960
    Windows 10 Pro X64 21H1 19043.1503
       #8

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


  9. Posts : 47
    windows 10
    Thread Starter
       #9

    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
    Last edited by mik07; 21 Jun 2020 at 16:17.
      My Computer


  10. Posts : 5,185
    64bit Win 10 Pro ver 21H2
       #10

    Your most recent dump implicates the AMD i2C driver. You would need to update your motherboard drivers.

    Code:
    6: kd> !irp ffffbf01afe1a9a0
    Irp is active with 6 stacks 4 is current (= 0xffffbf01afe1ab48)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
         cmd  flg cl Device   File     Completion-Context
     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
    >[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
                0 e1 ffffbf01af524930 00000000 00000000-00000000    pending
               \Driver\ACPI
                Args: 00000000 00000001 00000001 00000000
     [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
                0 e1 ffffbf01af9e9d90 00000000 fffff80130771150-ffffbf01afbf11e8 Success Error Cancel pending
               \Driver\amdi2c    nt!PopRequestCompletion
                Args: 00000000 00000001 00000001 00000000
     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-ffffbf01afbf11e8    
    
                Args: 00000000 00000000 00000000 00000000
    
    
    6: kd> lmvm amdi2c
    Browse full module list
    start             end                 module name
    fffff801`3d940000 fffff801`3d952000   amdi2c   # (pdb symbols)          c:\symcache\amdi2c.pdb\B8BF2954D5C44713AA12AE3485CF81AC1\amdi2c.pdb
        Loaded symbol image file: amdi2c.sys
        Mapped memory image file: c:\symcache\amdi2c.sys\5C91C83D12000\amdi2c.sys
        Image path: amdi2c.sys
        Image name: amdi2c.sys
        Browse all global symbolsfunctionsdata
        Timestamp:        Wed Mar 20 04:57:33 2019 (5C91C83D)
        CheckSum:         00017BF5
        ImageSize:        00012000
        File version:     1.2.0.99
        Product version:  1.2.0.99
        File flags:       8 (Mask 3F) Private
        File OS:          40004 NT Win32
        File type:        3.7 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        Information from resource tables:
            CompanyName:      Advanced Micro Devices, Inc
            ProductName:      AMD I2C Controller Driver
            InternalName:     amdi2c.sys
            OriginalFilename: amdi2c.sys
            ProductVersion:   1.2.0.99
            FileVersion:      1.2.0.99
            FileDescription:  AMD I2C Controller Driver
            LegalCopyright:   Copyright  2014-2019 Advanced Micro Devices, Inc
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 12:39.
Find Us




Windows 10 Forums