BSOD and I think Defender is the problem. Can someone confirm?

Page 5 of 6 FirstFirst ... 3456 LastLast

  1. Posts : 545
    seL4
       #41

    nags,

    What was happening before the blue screen? Did you just wake up your computer, or had it been idle for a bit of time?

    Could you also please send us the output of the following command from a PowerShell prompt:

    Code:
    Get-Disk | Select FriendlyName, Model, BusType, FirmwareVersion, IsBoot | Format-List
      My Computer


  2. Posts : 28
    Windows 10 Pro
    Thread Starter
       #42

    This time, I was not on the computer when it crashed. I had the computer running the whole time when it crashed.

    But, there have been instances when it crashed while I am working. Here is the output of the command.

    PS C:\Users\Nagarjunam> Get-Disk | Select FriendlyName, Model, BusType, FirmwareVersion, IsBoot | Format-List


    FriendlyName : LITEONIT LMT-256M3M
    Model : LITEONIT LMT-256M3M
    BusType : SATA
    FirmwareVersion : VZDB
    IsBoot : True
      My Computer


  3. Posts : 545
    seL4
       #43

    The crash dumps from the BSODs describe similar exceptions (errors):

    Code:
    ExceptionAddress: fffff8006f8ea700 (nt!RtlDecompressBufferXpressLz+0x0000000000000060)
    ExceptionCode: c0000006 (In-page I/O error)  
    ExceptionFlags: 00000000
    NumberParameters: 3  
    Parameter[0]: 0000000000000000   
    Parameter[1]: 0000000023308810   
    Parameter[2]: 00000000c0000483Inpage operation failed at 0000000023308810, due to I/O error 00000000c0000483

    You are also continuing to get event log entries that suggest issues with your disk, such as:

    Code:
    Event[11863]:
      Log Name: System
      Source: Disk
      Date: 2017-08-24T10:49:03.338
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Nags-XPS
      Description: The IO operation at logical block address 0x24353e8 for Disk 0 (PDO name: \Device\0000003a) failed due to a hardware error.
    Given that your SSD has passed several tests, it appears that most of the time your disk is functioning properly. However it looks like in certain circumstances something is causing I/O operations to fail entirely, as if your disk is dying or freezing up. This leads me to believe there is something more subtle going on than just disk failure, as generally we would be seeing problems during the disk tests.

    From the information you just gave me about your disk, it looks like you are running a version of disk firmware that does have problems with causing the disk to freeze. Dell has released a newer version of firmware for your disk (VZDC, A02).

    Here is a link to the firmware updater: LiteOn IT LMT-256M3M Solid State Drive Firmware Update Driver Details | Dell US

    Notice that in the change log, Dell mentions the following:
    Code:
    - Fixed issue where SSD freezes for 30s when waking up from LPM
    Note: LPM = Link Power management, this is how Windows/firmware govern power to connected devices in order to conserve energy.

    I would also suggest that you disable link power management for your disk, at least temporarily.

    To do this, go to "Power Options" in the Control Panel, select "High Performance" as your power plan. Then follow this guide on disabling AHCI power management.
      My Computer


  4. Posts : 28
    Windows 10 Pro
    Thread Starter
       #44

    I have been running Dell Update, but it never recommended this updated driver. I went ahead an updated the driver. I also changed the power management to "High Performance".

    If it crashes again, I will disable AHCI power management.
      My Computer


  5. Posts : 545
    seL4
       #45

    Has your computer bugchecked since updating your SSD's firmware?
      My Computer


  6. Posts : 41,462
    windows 10 professional version 1607 build 14393.969 64 bit
       #46

    1) Uninstall and reinstall: Cisco AnyConnect Secure Mobility Client
    2) Post an updated zip: BSOD - Posting Instructions - Windows 10 Forums



    Code:
    7/13/2017 8:00 PM    Application Error    Faulting application name: vpnagent.exe, version: 3.1.14018.0, time stamp: 0x56d417e2
    Faulting module name: vpnagentutilities.dll, version: 3.1.14018.0, time stamp: 0x56d416ff
    Exception code: 0xc0000005
    Fault offset: 0x00033fc5
    Faulting process id: 0x7f0
    Faulting application start time: 0x01d2fbf9b9dce3a0
    Faulting application path: C:\Program Files (x86)\Cisco\Cisco AnyConnect Secure Mobility Client\vpnagent.exe
    Faulting module path: C:\Program Files (x86)\Cisco\Cisco AnyConnect Secure Mobility Client\vpnagentutilities.dll
    Report Id: 29327e7c-f975-462d-a63b-2349c7c8aef4
    Faulting package full name: 
    Faulting package-relative application ID:7/13/2017 4:19 PM    Application Error    Faulting application name: vpnui.exe, version: 3.1.14018.0, time stamp: 0x56d419eb
    Faulting module name: combase.dll, version: 10.0.15063.296, time stamp: 0x9847392f
    Exception code: 0xc0000005
    Fault offset: 0x000c5a9f
    Faulting process id: 0x2bb4
    Faulting application start time: 0x01d2fb53341e46b8
    Faulting application path: C:\Program Files (x86)\Cisco\Cisco AnyConnect Secure Mobility Client\vpnui.exe
    Faulting module path: C:\WINDOWS\System32\combase.dll
    Report Id: 25cc5933-1938-4171-b1c6-7a25ae75fa72
    Faulting package full name: 
    Faulting package-relative application ID:8/17/2017 2:04 PM    Application Error    Faulting application name: vpnui.exe, version: 3.1.14018.0, time stamp: 0x56d419eb
    Faulting module name: combase.dll, version: 10.0.15063.447, time stamp: 0x8543d53c
    Exception code: 0xc0000005
    Fault offset: 0x000c5a9f
    Faulting process id: 0x26f0
    Faulting application start time: 0x01d317611626de71
    Faulting application path: C:\Program Files (x86)\Cisco\Cisco AnyConnect Secure Mobility Client\vpnui.exe
    Faulting module path: C:\WINDOWS\System32\combase.dll
    Report Id: c4dd10ee-449e-4052-a722-a762bff383cd
    Faulting package full name: 
    Faulting package-relative application ID:8/9/2017 4:08 PM    Application Error    Faulting application name: vpnui.exe, version: 3.1.14018.0, time stamp: 0x56d419eb
    Faulting module name: combase.dll, version: 10.0.15063.447, time stamp: 0x8543d53c
    Exception code: 0xc0000005
    Fault offset: 0x000c5a9f
    Faulting process id: 0x2980
    Faulting application start time: 0x01d3107575c2465a
    Faulting application path: C:\Program Files (x86)\Cisco\Cisco AnyConnect Secure Mobility Client\vpnui.exe
    Faulting module path: C:\WINDOWS\System32\combase.dll
    Report Id: 2c55c64a-d9aa-4ae1-9108-c7f5712e4c3d
    Faulting package full name: 
    Faulting package-relative application ID:
      My Computer


  7. Posts : 28
    Windows 10 Pro
    Thread Starter
       #47

    Spectrum said:
    Has your computer bugchecked since updating your SSD's firmware?
    I did a bugcheck again with HDTune. No errors found.
      My Computer


  8. Posts : 28
    Windows 10 Pro
    Thread Starter
       #48

    My computer has not crashed yet after updating the SSD firmware. I will reinstall Cisco AnyConnect, if it crashes one more time.
      My Computer


  9. Posts : 41,462
    windows 10 professional version 1607 build 14393.969 64 bit
       #49
      My Computer


  10. Posts : 28
    Windows 10 Pro
    Thread Starter
       #50

    Hello @zbook,

    I am all set with this. Looks like this was an issue with Windows 10 itself. After installing all the updates,the number of BSOD's have reduced. Now they are almost once in couple of months, which i am ok to deal with.

    Thank you all the other too who tried to help me.
      My Computer


 

  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 17:43.
Find Us




Windows 10 Forums