Windows 10: Newly build pc april 2020 keeps getting bsod's Ntoskrnl.exe, ntdll.sys,win32kfull.sys

Hi All,


I build a new pc couple of months ago but i keep getting bsod at random times which is getting pretty frustrating. Sometimes the computer just semi-freezes where i can move the mouse and move the windows but things like the searchbar aren't working anymore. I cannot start any app until i restart my system.


My system is up to date, drivers are all downloaded from the websites Gigabyte, Nvidia, etc.

PC specs:
Gigabyte Aorus x570 Elite

Amd Ryzen 7 3700x

G skill 2x8gb ddr4 3600mhz cl16 ram

Gigabyte RTX 2080 SUPER videocard

Cooler Master MWE Gold 750 Full Modular PSU

WD Blue SSD SN550 1Tb NVMe OS installed here

Seagate BarraCuda 6TB 5400rpm HDD drive

NZXT Kraken X63, 280mm


What i have tried:

Clean install windows 2 times

Ran chkdsk

Ran DISM

Reverted the latest windows update.

Disabled all the RGB lighting programs to see if one of those were causing the random BSOD's.

BIOS back to default settings no xmp preset for RAM

Reseated the RAM sticks

Multiple Memory stresstests --> no BSOD

Multiple CPU stresstests --> no BSOD

Multiple GPU stresstests --> no BSOD


I have multiple DUMP files and WhoCrashed shows me it is caused by Ntoskrnl.exe, ntdll.sy or win32kfull.sys.
BSOD errors: CRITICAL_PROCESS_DIED, KERNEL_SECURITY_CHECK, DPC_WATCHDOG_VIOLATION, SYSTEM_SERVICE_EXCEPTION.

The BSOD's seem to occur randomly but mostly when im gaming rocket league, among us, gears 5, no mans sky.

Im in need of help!


https://we.tl/t-z1fKr5Ods4 <-- link to DUMP files.


---

whocrashed

----


On Thu 01/10/2020 20:32:02 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100120-7265-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F3EA0
Bugcheck code: 0xEF 0xFFFFDB01873DB080, 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 01/10/2020 20:32:02 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 0xFFFFDB01873DB080, 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 Sun 13/09/2020 21:10:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\091320-6859-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F3EA0
Bugcheck code: 0x139 0x3, 0xFFFFCC83B13A73E0, 0xFFFFCC83B13A7338, 0x0
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 23/08/2020 11:35:29 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\082320-6187-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3DDF40
Bugcheck code: 0x139 0x1D, 0xFFFFD68B8E711260, 0xFFFFD68B8E7111B8, 0x0
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 16/08/2020 20:53:31 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081620-6296-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3DDF40
Bugcheck code: 0x133 0x0, 0x501, 0x500, 0xFFFFF8070D0FA320
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs thermal issue.
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 08/08/2020 22:31:31 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\080820-7500-01.dmp
This was probably caused by the following module: win32kfull.sys 0xFFFFC889650A9E8C
Bugcheck code: 0x3B 0xC0000005, 0xFFFFC889650A9E8C, 0xFFFF81811EB32910, 0x0
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.






Conclusion



6 crash dumps have been found and analyzed. 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.


:)

 

QCAMAIN1.SYS CAUSING BSOD

This was probably caused by the following module:
qcamain1.sys (Qcamain10x64+0x108678)

Bugcheck code: 0x1D3 (0x333, 0x0, 0x0, 0x0)

Error: CUSTOM_ERROR

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: qcamain1.sys .

Google query: qcamain1.sys CUSTOM_ERROR

Using WhoCrashed I found this thread: QCAMAIN1.SYS CAUSING BSOD (Code 37 Error) however without
solution, locked.

I did get BSOD almost everytime I moved the laptop.

This worked for me:

unscrew wifi module, push a little into the socket. Screw in. DONE

 

BSOD - driver_irql_not_less_or_equal (l1c63x64.sys)

Hi Seung,

Sorry for the inconvenience caused by BSOD - driver_irql_not_less_or_equal (l1c63x64.sys).

Please let us know the make/model of your computer.

The L1C63x64.sys is the Atheros LAN driver and I would suggest to uninstall and reinstall the Atheros LAN driver but install the latest Atheros LAN driver by visiting the manufacture's website and avoid using any LAN driver available though Windows Update.

However the problem could also be with any VPN software and other software so make sure you have the latest version of each of these software.

If the errors continue uninstall the VPN software and check if the issue persist.

Hope this helps. Get back to us for further queries for BSOD - driver_irql_not_less_or_equal (l1c63x64.sys). We are happy to help!

 

Ntoskrnl BSOD

• Update your Realtek audio driver.
• Update your computer.
• Disable overclocking settings.
• Turn off BlueStacks/ another Android emulator.
• Clean your registry.
• Check your disk for errors.
• Fix bad memory issues.
• Remove faulty sticks of RAM.
• I hope these methods help you!
• Regards,
• Lewis
  
  * Added by Moderator: Information from
  https://windowsreport.com/windows-8-bsod-ntoskrnl-exe/
  
  * Moderator note: Advice given on this page might or might not be safe and/or effective but there are programs usually classified as PUP's (Potentially Unwanted Programs) being pushed that should not be downloaded or installed.