Windows 10 Blue Screens and Event Viewer Errors

Page 1 of 4 123 ... LastLast

  1. Posts : 16
    Windows 10
       #1

    Windows 10 Blue Screens and Event Viewer Errors


    Hello I am new
    So short version of the story...I will try to keep it as short as I can. For a few(3 maybe) months I have bee haveing issues with Windows 10 2004 (Build 19041.508). Probably microsoft suppport knows me well at this point, tried community forum also and now I am here.
    I was on version 1909, errors and freezings started happening becaues of an update, then I did clean reinstall. Then again an update massed up a week or 2 later and I had to do reistall. I had to contact tech support and it was painfull process and wasn't helpful at all. Anyway recently errors and freezings started happening again and I was convinced by win tech support that I should upgrade from 1909 to 2004 and everything will fix itself. Well no...So now I have even more errors.
    I don't really want to reisntall again and rather fix the errors, because at this point reistalling feels like just waste of time. I tried researching the errors and looked at forums for solutions and nothing worked so far.

    Warnings: DistributedCOM event 10016(apparently this one is normal), ESENT event 642

    Errors: DistributedCOM event-10010, AppModel-Runtime event 65, AppPopup event-56 ACPI 15

    Blue screen codes: DRIVER_IRQL_NOT_LESS_OR_EQUAL, SYSTEM_SERVICE_EXEPTION, KERNEL_SECURITY_CHECK_FAILURE, KMODE_EXEPTION_NOT_HANDELED (recently after freezing PC just restarts without bluescreen but in the same way as if blue screen happened)

    What I have tried: 3 clean reistalls so far, Virus scan with Defender(clear), Virus scan with Malwerebytes(caused blue screen), DISM(all types), SFC(all good), Memory scan(all good), SSD Health check(healthy), drives updateing especially nvidia one(did clean install because upgraded from quadro p4000 to gtx 1080ti which was faulty and then rtx 2080s), unistalling win updates, and probably something else that I can't remmember right now.

    Please help, any advice, any help will be appreciated. Any questions, please ask, because I might have forgotten to include something important. Also sorry for spelling mistakes, English's not my firts language.

    - - - Updated - - -

    OK so just a few minutes after this post blue screen with KERNEL_SECURITY_CHECK_FAILURE happened.
      My Computer


  2. Posts : 1,862
    Windows 10 Pro 2004 20H1
       #2

    Welcome.

    Follow these instructions that are posted at the top of the forum -

    BSOD - Posting Instructions
      My Computer


  3. Posts : 16
    Windows 10
    Thread Starter
       #3

    OldNavyGuy said:
    Welcome.

    Follow these instructions that are posted at the top of the forum -

    BSOD - Posting Instructions
    Thanks for replying. In the zip file, after I ran the Log Collector, I found files with IP addreses and windows keyID numbers which I am not sure it's good to share. Not sure if this is inforamtion someone could use in malicious ways. Can I delete the files which describe my hardwere in detail? Do you need all these files in order to help me or only specific ones? Thanks.
      My Computer


  4. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #4

    Please just upload the zip file. There is nothing in there that can be used maliciously. It has been uploaded thousands of times. Some of what is there will not be needed but it's better if we have all of it to look at.

    If you're not comfortable doing so then you're not going to get much help here, sorry. We need the data to be able to help.
      My Computers


  5. Posts : 16
    Windows 10
    Thread Starter
       #5

    Here's the zip archive. I am not trying to offend or to be rude, I am sure everybody knows that we have to be carefull with the information we put on the internet. Anyway, I hope you can find what's causing the issues since the tech people of Microsoft coudn't. Thanks.
      My Computer


  6. Posts : 1,862
    Windows 10 Pro 2004 20H1
       #6

    There is no personally identifiable information in the log files collected.
      My Computer


  7. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #7

    6 Bluescreen entries detected ...
    3 Unique Bug Check codes: 139 001 01e

    P1: 0X0000001E 22/09/2020 00:16
    P1: 0X00000001 02/10/2020 21:52
    P1: 0X00000139 06/10/2020 00:33

    Suggest you run

    Tuneup.bat - Click here to go to the BSOD batch repository to download and run this batch file. Capture the output as directed and add to a post here.
    Need to see what SFC and DISM do as far as repairing system files.

    After running the batch file, if you get another BSOD the system should not automatically restart. Take a picture of the BSOD screen and post here then reboot, not before.

    After that I'll need you to run Driver Verifier for up to 48 hours and then memtest86 for 8 passes, which consists of two runs of 4 passes each. You have 48GB of RAM so this is going to take along time. What you may want to do is remove either 16GB or 32GB of ram and test the remaining. Swap installed and removed RAM 16GB at a time.

    Any failure, even one, means one of the two installed 8GB modules is defective so you need to remove one and test. If it failes htat is the bad one. If not remove it and install the other 8GB module and test.

    Repeat until all rem is tested. Quite possible/likely all your ram is good but still needs to be tested to verify.

    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.

    Follow instructions here to decide which drivers you want to test. 3-5 is a good start. Add 3-5 more every two hours until all are selected or you get a BSOD.

    Enable and Disable Driver Verifier in Windows 10

    Familiarize yourself with how to get out of Driver verifier from the above link and from the first link.

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


  8. Posts : 16
    Windows 10
    Thread Starter
       #8

    Ok thanks. Will be back soon after I do the tests.
      My Computer


  9. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #9

    Run Tuneup.bat first and post the output here.
      My Computers


  10. Posts : 16
    Windows 10
    Thread Starter
       #10

    I downloaded the Tuneup.bat and ran it from the File Explorer Downloads folder. It ran around half a minute maybe a minute and it gave me a blue screen with SYSTEM_THREAD_EXEPTION_NOT_HANDELED and what failed: dxgmms2.sys (is that telling something because usually spits ony the misterious code with the capital letters) Then after it restarted I immediately ran the Log Collector(which I am attaching). Then I ran the Tuneup again an it went smoothly this time.

    Code:
    ###########################################################
    # The following commands will be run in sequence.         #
    # The first 5 will take quite a while to run, be patient. #
    ###########################################################
    
    sfc /scannow
    dism /online /cleanup-image /scanhealth
    dism /online /cleanup-image /restorehealth
    sfc /scannow
    
    chkdsk /scan
    
    wmic recoveros get autoreboot
    wmic recoveros set autoreboot = false
    wmic recoveros get autoreboot
    wmic recoveros get DebugInfoType
    wmic recoveros set DebugInfoType = 7
    wmic recoveros get DebugInfoType
    
    wmic pagefile list /format:list
    wmic Computersystem where name="DESKTOP-975KCGB" get AutomaticManagedPagefile
    wmic Computersystem where name="DESKTOP-975KCGB" set AutomaticManagedPagefile=True
    wmic Computersystem where name="DESKTOP-975KCGB" get AutomaticManagedPagefile
    
    bcdedit /enum {badmemory}
    
    
    C:\WINDOWS\system32>sfc /scannow
    
    Beginning system scan.  This process will take some time.
    
    Beginning verification phase of system scan.
    Verification 100% complete.
    
    Windows Resource Protection did not find any integrity violations.
    
    C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.329
    
    Image Version: 10.0.19041.508
    
    [==========================100.0%==========================] No component store corruption detected.
    The operation completed successfully.
    
    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.329
    
    Image Version: 10.0.19041.508
    
    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.
    
    C:\WINDOWS\system32>sfc /scannow
    
    Beginning system scan.  This process will take some time.
    
    Beginning verification phase of system scan.
    Verification 100% complete.
    
    Windows Resource Protection did not find any integrity violations.
    
    C:\WINDOWS\system32>chkdsk /scan
    The type of the file system is NTFS.
    
    Stage 1: Examining basic file system structure ...
      789248 file records processed.
    File verification completed.
     Phase duration (File record verification): 5.92 seconds.
      7865 large file records processed.
     Phase duration (Orphan file record recovery): 0.00 milliseconds.
      0 bad file records processed.
     Phase duration (Bad file record checking): 1.44 milliseconds.
    
    Stage 2: Examining file name linkage ...
      224 reparse records processed.
      936856 index entries processed.
    Index verification completed.
     Phase duration (Index verification): 13.62 seconds.
      0 unindexed files scanned.
     Phase duration (Orphan reconnection): 590.65 milliseconds.
      0 unindexed files recovered to lost and found.
     Phase duration (Orphan recovery to lost and found): 1.63 milliseconds.
      224 reparse records processed.
     Phase duration (Reparse point and Object ID verification): 4.22 milliseconds.
    
    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
     Phase duration (Security descriptor verification): 47.68 milliseconds.
      73805 data files processed.
     Phase duration (Data attribute verification): 0.42 milliseconds.
    CHKDSK is verifying Usn Journal...
      40349624 USN bytes processed.
    Usn Journal verification completed.
     Phase duration (USN journal verification): 269.68 milliseconds.
    
    Windows has scanned the file system and found no problems.
    No further action is required.
    
     233768959 KB total disk space.
     123733384 KB in 353909 files.
        205572 KB in 73806 indexes.
             0 KB in bad sectors.
        908403 KB in use by the system.
         65536 KB occupied by the log file.
     108921600 KB available on disk.
    
          4096 bytes in each allocation unit.
      58442239 total allocation units on disk.
      27230400 allocation units available on disk.
    Total duration: 20.47 seconds (20478 ms).
    
    C:\WINDOWS\system32>wmic recoveros get autoreboot
    AutoReboot
    TRUE
    
    
    C:\WINDOWS\system32>wmic recoveros set autoreboot = false
    Updating property(s) of '\\DESKTOP-975KCGB\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'
    Property(s) update successful.
    
    C:\WINDOWS\system32>wmic recoveros get autoreboot
    AutoReboot
    FALSE
    
    
    C:\WINDOWS\system32>wmic recoveros get DebugInfoType
    DebugInfoType
    7
    
    
    C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
    Updating property(s) of '\\DESKTOP-975KCGB\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'
    Property(s) update successful.
    
    C:\WINDOWS\system32>wmic recoveros get DebugInfoType
    DebugInfoType
    7
    
    
    C:\WINDOWS\system32>wmic pagefile list /format:list
    
    
    AllocatedBaseSize=7168
    CurrentUsage=0
    Description=C:\pagefile.sys
    InstallDate=20200627185653.841684+060
    Name=C:\pagefile.sys
    PeakUsage=0
    Status=
    TempPageFile=FALSE
    
    
    
    
    C:\WINDOWS\system32>wmic Computersystem where name="DESKTOP-975KCGB" get AutomaticManagedPagefile
    AutomaticManagedPagefile
    TRUE
    
    
    C:\WINDOWS\system32>wmic Computersystem where name="DESKTOP-975KCGB" set AutomaticManagedPagefile=True
    Updating property(s) of '\\DESKTOP-975KCGB\ROOT\CIMV2:Win32_ComputerSystem.Name="DESKTOP-975KCGB"'
    Property(s) update successful.
    
    C:\WINDOWS\system32>wmic Computersystem where name="DESKTOP-975KCGB" get AutomaticManagedPagefile
    AutomaticManagedPagefile
    TRUE
    
    
    C:\WINDOWS\system32>bcdedit /enum {badmemory}
    
    RAM Defects
    -----------
    identifier              {badmemory}
      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:09.
Find Us




Windows 10 Forums