Windows 10: BSOD's realted to clr.sys and ntdll.sys

Discus and support BSOD's realted to clr.sys and ntdll.sys in Windows 10 Drivers and Hardware to solve the problem; Hi. So about a week ago I updated my graphics driver and other drivers and also some games updated, notably valorant which its anticheat vanguard... Discussion in 'Windows 10 Drivers and Hardware' started by JamesEspinoza, Jul 16, 2020.

  1. BSOD's realted to clr.sys and ntdll.sys


    Hi.


    So about a week ago I updated my graphics driver and other drivers and also some games updated, ​

    notably valorant which its anticheat vanguard is known to cause issues so after a restart my system​

    was unstable and I got blue screened and whenever I stopped playing it again I was getting blue screened ​

    and after I uninstalled I randomly keep crashing and my system got more unstable. ​

    So then I reseted windows while keeping my files and I tried to test again with valorant and crashes ​

    happened again so I reinstalled windows again and im still crashing but less frequently so ​

    I suspect my ssd where windows is installed might be failing because some time when restarting ​

    from a crash windows couldn't find the bootable device or maybe some drivers.I'd also have done some memory test's and haven't found any errors except for ​

    Interface CRC error count = 3 with an attention status tested with hd tune pro so I still don't know the Issue​

    Some data:Crash dump files:https://drive.google.com/drive/folders/1aew-qvBEkFCwrwlmGXQHL0yEPpvahPRo?usp=sharing​

    System Information local


    Computer name: DESKTOP-5G8TMD0
    Windows version: Windows 10 , 10.0, build: 18363
    Windows dir: C:\WINDOWS
    Hardware: Alienware 17 R4, Alienware
    CPU: GenuineIntel IntelR CoreTM i7-6700HQ CPU @ 2.60GHz Intel8664, level: 6
    8 logical processors, active mask: 255
    RAM: 17044877312 bytes 15.9GB





    Crash Dump Analysis

    On Thu 7/16/2020 3:44:14 AM your computer crashed or a problem was reported
    crash dump file: C:\WINDOWS\Minidump\071620-13343-01.dmp
    This was probably caused by the following module: ntoskrnl.exe nt+0x1C23C0
    Bugcheck code: 0xEF 0xFFFFD60642CB6080, 0x0, 0x0, 0x0
    Error: CRITICAL_PROCESS_DIED
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a critical system process died.
    There is a possibility this problem was caused by a virus or other malware.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Thu 7/16/2020 3:44:14 AM your computer crashed or a problem was reported
    crash dump file: C:\WINDOWS\MEMORY.DMP
    This was probably caused by the following module: ntdll.sys ntdll!RtlLookupFunctionEntry+0x82
    Bugcheck code: 0xEF 0xFFFFD60642CB6080, 0x0, 0x0, 0x0
    Error: CRITICAL_PROCESS_DIED
    Bug check description: This indicates that a critical system process died.
    There is a possibility this problem was caused by a virus or other malware.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntdll.sys .
    Google query: ntdll.sys CRITICAL_PROCESS_DIED



    On Thu 7/16/2020 3:38:00 AM your computer crashed or a problem was reported
    crash dump file: C:\WINDOWS\Minidump\071620-15578-01.dmp
    This was probably caused by the following module: ntoskrnl.exe nt+0x1C23C0
    Bugcheck code: 0x5A 0x1, 0xFFFF87883FFC4110, 0xFFFF9C8956748290, 0xFFFFFFFFC000000E
    Error: CRITICAL_SERVICE_FAILED
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check appears very infrequently.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Tue 7/14/2020 12:28:55 AM your computer crashed or a problem was reported
    crash dump file: C:\Users\che_d\Downloads\MEMORY.DMP
    This was probably caused by the following module: clr.sys clr!TranslateSecurityAttributes+0x1F9910
    Bugcheck code: 0xEF 0xFFFFAE8AC2ED5280, 0x0, 0x0, 0x0
    Error: CRITICAL_PROCESS_DIED
    Bug check description: This indicates that a critical system process died.
    There is a possibility this problem was caused by a virus or other malware.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: clr.sys .
    Google query: clr.sys CRITICAL_PROCESS_DIED



    On Tue 7/14/2020 12:28:55 AM your computer crashed or a problem was reported
    crash dump file: C:\Users\che_d\Downloads\MINI-20200716T032424Z-001\MINI\071420-14703-01.dmp
    This was probably caused by the following module: ntoskrnl.exe nt+0x1C23A0
    Bugcheck code: 0xEF 0xFFFFAE8AC2ED5280, 0x0, 0x0, 0x0
    Error: CRITICAL_PROCESS_DIED
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a critical system process died.
    There is a possibility this problem was caused by a virus or other malware.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Mon 7/13/2020 8:18:37 PM your computer crashed or a problem was reported
    crash dump file: C:\Users\che_d\Downloads\MINI-20200716T032424Z-001\MINI\071320-19109-01.dmp
    This was probably caused by the following module: ntoskrnl.exe nt+0x1C23A0
    Bugcheck code: 0xEF 0xFFFFAF03741104C0, 0x0, 0x0, 0x0
    Error: CRITICAL_PROCESS_DIED
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a critical system process died.
    There is a possibility this problem was caused by a virus or other malware.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Mon 7/13/2020 7:00:44 AM your computer crashed or a problem was reported
    crash dump file: C:\Users\che_d\Downloads\MINI-20200716T032424Z-001\MINI\071320-15578-01.dmp
    This was probably caused by the following module: ntoskrnl.exe nt+0x1C23A0
    Bugcheck code: 0x154 0xFFFF8E0EDAEE2000, 0xFFFF88023E615F00, 0x2, 0x0
    Error: UNEXPECTED_STORE_EXCEPTION
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that the store component caught an unexpected exception.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Mon 7/13/2020 7:41:11 PM your computer crashed or a problem was reported
    crash dump file: C:\Users\che_d\Downloads\MINI-20200716T032424Z-001\MINI\071320-15046-01.dmp
    This was probably caused by the following module: ntoskrnl.exe nt+0x1C23A0
    Bugcheck code: 0xEF 0xFFFF930AE76EB080, 0x0, 0x0, 0x0
    Error: CRITICAL_PROCESS_DIED
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a critical system process died.
    There is a possibility this problem was caused by a virus or other malware.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




    :)
     
    JamesEspinoza, Jul 16, 2020
    #1
  2. Manoura Win User

    Computer crashed, related to ntdll.sys and ntoskrnl.exe

    My pc has been occasionally crashing(BSOD) when playing games. At first, the minidump logs said it was because of faulty RAM, so I ran the memory diagnostic tool and it said hardware problems were found. So I googled and found a post that said that when
    they updated their RAM, it didnt say hardware problems were found, and weirldy my preinstalled BIOS was a BIOS that the site of the mb's maker said it wasnt recommened for pinnacle ridge (aka my ridge), so i updated to an earlier version that didnt say that
    and when i ran the memory diagnostic tool it didnt find any problems. Now, 1 hour ago when my pc crashed and i looked at the logs, instead of saying something about ram it said, at the same time, ntdll.sys and ntoskrnl.exe failed. I'm willing to upload minidump
    and system log files. Sumit Dhiman, pls help me

    On Sun 01/03/2020 12:33:21 your computer crashed or a problem was reported

    crash dump file: C:\Windows\Minidump\030120-7812-01.dmp

    This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1510)

    Bugcheck code: 0xEF (0xFFFFA90438789340, 0x0, 0x0, 0x0)

    Error: CRITICAL_PROCESS_DIED

    file path: C:\Windows\system32\ntoskrnl.exe

    product: Microsoft® Windows® Operating System

    company: Microsoft Corporation

    description: NT Kernel & System

    Bug check description: This indicates that a critical system process died.

    There is a possibility this problem was caused by a virus or other malware.

    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    On Sun 01/03/2020 12:33:21 your computer crashed or a problem was reported

    crash dump file: C:\Windows\MEMORY.DMP

    This was probably caused by the following module: ntdll.sys (ntdll!NtTerminateProcess+0x14)

    Bugcheck code: 0xEF (0xFFFFA90438789340, 0x0, 0x0, 0x0)

    Error: CRITICAL_PROCESS_DIED

    Bug check description: This indicates that a critical system process died.

    There is a possibility this problem was caused by a virus or other malware.

    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntdll.sys .

    Google query: ntdll.sys CRITICAL_PROCESS_DIED
     
    Manoura, Jul 16, 2020
    #2
  3. WyndFyre Win User
    Blue Screen of Death by ntoskrnl.exe and ntdll.sys

    Hello, my computer crashes inconsistently whenever I play a game. Here is the WhoCrashed excerpt from my crash :

    On Sat 2/8/2020 12:20:16 AM your computer crashed or a problem was reported

    crash dump file: C:\Windows\Minidump\020820-8984-01.dmp

    This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)

    Bugcheck code: 0xEF (0xFFFFC086EC8DE300, 0x0, 0x0, 0x0)

    Error: CRITICAL_PROCESS_DIED

    file path: C:\Windows\system32\ntoskrnl.exe

    product: Microsoft® Windows® Operating System

    company: Microsoft Corporation

    description: NT Kernel & System

    Bug check description: This indicates that a critical system process died.

    There is a possibility this problem was caused by a virus or other malware.

    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    On Sat 2/8/2020 12:20:16 AM your computer crashed or a problem was reported

    crash dump file: C:\Windows\MEMORY.DMP

    This was probably caused by the following module: ntdll.sys (ntdll!ZwTerminateProcess+0x14)

    Bugcheck code: 0xEF (0xFFFFC086EC8DE300, 0x0, 0x0, 0x0)

    Error: CRITICAL_PROCESS_DIED

    Bug check description: This indicates that a critical system process died.

    There is a possibility this problem was caused by a virus or other malware.

    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntdll.sys .

    Google query: ntdll.sys CRITICAL_PROCESS_DIED
     
    WyndFyre, Jul 16, 2020
    #3
  4. BSOD's realted to clr.sys and ntdll.sys

    Blue screen ntdll.sys CRITICAL_PROCESS_DIED

    Hello everybody, sometimes when I use my computer I have a blue screen.


    BSOD's realted to clr.sys and ntdll.sys 4dcf4bf0-6dce-4556-b33c-d25a7fafa46a?upload=true.jpg


    It's a fake screenshot made by me on Photoshop because we can't take a screenshot on this but the bug with the BSOD's realted to clr.sys and ntdll.sys :( on the top is the same (on 6 lines) and the text and the QR code also.

    This blue screen also come when I shutdown my computer :/

    I think also I have a malware but I analyzed my PC with Windows Defender, Malwarebytes, ADWCleaner and RogueKiller.

    Here is a WhoCrash report

    --------------------------------------------------------------------------------

    System Information (local)

    --------------------------------------------------------------------------------

    Computer name: -PC-WIN10

    Windows version: Windows 10 , 10.0, build: 16299

    Windows dir: C:\WINDOWS

    Hardware: CX62 6QD, Micro-Star International Co., Ltd., MS-16J6

    CPU: GenuineIntel Intel(R) Core(TM) i3-6100H CPU @ 2.70GHz Intel586, level: 6

    4 logical processors, active mask: 15

    RAM: 4203593728 bytes total

    --------------------------------------------------------------------------------

    Crash Dump Analysis

    --------------------------------------------------------------------------------

    Crash dumps are enabled on your computer.

    Crash dump directories:

    C:\WINDOWS

    C:\WINDOWS\Minidump

    On Sun 08/04/2018 17:53:24 your computer crashed or a problem was reported

    crash dump file: C:\WINDOWS\MEMORY.DMP

    This was probably caused by the following module: ntdll.sys (ntdll+0xA0404)

    Bugcheck code: 0xEF (0xFFFF970306CE3580, 0x0, 0x0, 0x0)

    Error: CRITICAL_PROCESS_DIED

    Bug check description: This indicates that a critical system process died.

    There is a possibility this problem was caused by a virus or other malware.

    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntdll.sys .

    Google query: ntdll.sys CRITICAL_PROCESS_DIED

    The following dump files were found but could not be read. These files may be corrupt:

    C:\WINDOWS\Minidump\040818-28375-01.dmp

    --------------------------------------------------------------------------------

    Conclusion

    --------------------------------------------------------------------------------

    2 crash dumps have been found and analyzed. Only 1 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites.
    Click on the links below to search with Google for updates for these drivers:

    ntdll.sys

    If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often
    yields interesting results from discussions on the web by users who have been experiencing similar problems.

    Read the topic general suggestions for troubleshooting system crashes for more information.

    Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong
    to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you
    investigate this further.

    --------------------------------------------------------------------------------

    Thank you
     
    TheDevKiller, Jul 16, 2020
    #4
Thema:

BSOD's realted to clr.sys and ntdll.sys

Loading...
  1. BSOD's realted to clr.sys and ntdll.sys - Similar Threads - BSOD's realted clr

  2. BSOD L1C63x64.sys

    in Windows 10 BSOD Crashes and Debugging
    BSOD L1C63x64.sys: Heya guys, this is my first post here *Smile. I just had like 3 or 4 BSODs in these last two days, never had any. I just updated my Atheros 8151 PCI-e driver from Network adapter->properties->update driver. I'm not sure if it is the cause, so I used the tool and attached...
  3. BSOD L1C63x64.sys driver

    in Windows 10 BSOD Crashes and Debugging
    BSOD L1C63x64.sys driver: Hi, I am getting BSODs and the error message it gives is: Driver_IRQL_NOT_LESS_OR_EQUAL(L1C63x64.sys) I believe that is the Qualcomm Atheros Network driver, but mine is up to date to the last Windows8 compatible driver on the Atheros website. This leads me to believe...
  4. BSOD featuring dxgmms2.sys

    in Windows 10 BSOD Crashes and Debugging
    BSOD featuring dxgmms2.sys: Got another BSOD earlier tonight, this time with dxgmms2.sys cited onscreen. 85143
  5. BSOD blaming L1C63x64.sys

    in Windows 10 BSOD Crashes and Debugging
    BSOD blaming L1C63x64.sys: BSOD happened several times in this week after I updated my windows 10 into the latest version, especially when I was uploading or downloading something through utorrent via ipv6. Windows blame the LiC63x64.sys, and I have updated all my Atheros drivers but it still happen....
  6. BSOD blaming L1C63x64.sys

    in Windows 10 BSOD Crashes and Debugging
    BSOD blaming L1C63x64.sys: Like many others I am the victim of this, it happens more than once a day. It never happened on windows 8.1. At Toshiba's request, I have back-dated my driver to the one that Windows installs with windows 10. I am hoping this fixes the issue, if not, here's my dump 58971
  7. wdf01000.sys BSOD

    in Windows 10 BSOD Crashes and Debugging
    wdf01000.sys BSOD: Hey, this is more of a question. My keyboard has been malfunctioning due to liquid damage, so to disable it I installed an incompatible keyboard/touchpad driver intentionally. The day after, I've been getting wdf01000.sys BSOD errors during startup, which brings me to a...
  8. Frequent BSODs - L1C63x64.sys

    in Windows 10 BSOD Crashes and Debugging
    Frequent BSODs - L1C63x64.sys: Since upgrading to Windows 10 I am getting frequent BSODs with DRIVER_IRQL_NOT_LESS_OR_EQUAL in L1C634x64.sys especially when the network is loaded (heavy bit torrent activity) Googling has led me to believe that it is problems lies with my Atheros driver so I have updated...
  9. BSOD tdr_failure_igdkmd64.sys

    in Windows 10 BSOD Crashes and Debugging
    BSOD tdr_failure_igdkmd64.sys: I have been encountering this error frequently when running games, mostly World of Tanks and the World of Warships beta test. I ALWAYS get this error whenever I accidentally bump the windows key on my laptop in game. If I am at the port or garage screen with all my ships,...
  10. Frequent BSOD Wdf01000.sys

    in Windows 10 BSOD Crashes and Debugging
    Frequent BSOD Wdf01000.sys: I've been getting BSODs when leaving my computer idle. Not running anything intensive. From looking at the minidump file I can't find much other than it's probably because of the Wdf01000.sys driver. Hopefully you can get all of the information you need from the .zip file I...