Having a bunch of random BSOD (most caused by ntsokrnl.exe)

Everything points to the Intel(R) Dual Band Wireless-AC 8260 adapter as the cause of several of the 7/13 dumps.

Install the Intel® Driver & Support Assistant (Intel® DSA)

The Intel® Driver & Support Assistant keeps your system up-to-date by providing tailored support and hassle-free updates for most of your Intel hardware. View a list of driver & software exclusions.

Note: This application is supported on Microsoft Windows 7, Windows 8, Windows 8.1, and Windows® 10 using Chrome, Firefox, or Edge* (version 44.17763/18.17763 or newer) browsers.

Code:

3: kd> lmvm Netwtw06
Browse full module list
start             end                 module name
fffff800`66760000 fffff800`6700d000   Netwtw06   (pdb symbols)          d:\symbols\Netwtw06.pdb\089306B7F4A8405A8F7204E32E8E8D221\Netwtw06.pdb
    Loaded symbol image file: Netwtw06.sys
    Mapped memory image file: d:\symbols\Netwtw06.sys\5B8FE9F98ad000\Netwtw06.sys
    Image path: \SystemRoot\System32\drivers\Netwtw06.sys
    Image name: Netwtw06.sys
    Browse all global symbols  functions  data
    Timestamp:        Wed Sep  5 10:36:41 2018 (5B8FE9F9)
    CheckSum:         0087527E
    ImageSize:        008AD000
    File version:     20.70.3.3
    Product version:  1.0.1.0
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.6 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    Information from resource tables:
        CompanyName:      Intel Corporation
        ProductName:      Intel® Wireless WiFi Link Adapter
        InternalName:     .sys
        OriginalFilename: .sys
        FileVersion:      20.70.3.3
        FileDescription:  Intel® Wireless WiFi Link Driver
        LegalCopyright:   Copyright © Intel Corporation 2011
        Comments:         NDIS650_MINIPORT

The latest dump was a ...

Code:

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffb60a38377000, memory referenced.
Arg2: 0000000000000011, value 0 = read operation, 1 = write operation.
Arg3: fffff80345225d10, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

It indicates bindflt.sys is the probable cause which is unlikely as this is a OS driver.

Here is a good article on ways to fix this: Page Fault in Nonpaged Area BSOD Error on Windows 10 Solved
Work through steps 1 through 5 and see if that resolves the problem.

An earlier dump indicates wuauclt.exe as the probable cause.

wuauclt.exe is a legitimate process file popularly known as Windows Automatic Updates. It is associated with Windows Operating System developed by Microsoft Corporation. ... Malware programmers create files with virus scripts and name them after wuauclt.exe with an intention to spread virus on the internet.

Please run full scans with your Anti-virus software and Malwarebytes Antimalware.

No, I don't see a Clean Install making any difference.

07/20 07:21 dump is a

Code:

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffffffffffff8b, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80632210906, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

• Bug check 0x50 can occur after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
• Another possible cause is the installation of a faulty system service or faulty driver code.
• Antivirus software can also trigger this error, as can a corrupted NTFS volume.

The 10;27 dump shows

*** WARNING: Unable to verify timestamp for MbamChameleon.sys

I suggest uninstalling Malwarebytes for awhile to see if that makes any difference.

Just because your ram tested with 0 errors does not mean it is good. As I'v mentioned many times before. the best memor7y diagnostic going is the Operating System. I agree it is "probably" not your ram but if you could replace it that would be a good ting to do.

Yes, I believe it's a hardware problem but have no idea at this point what hardware.
We'll see what uninstalling MBAM does.

If it fails again then:

===================================================
Follow this tutorial to stress test your CPU:
If you have a Intel CPU then test it with the Intel Processor Diagnostic Tool.

Prime95 - Stress Test Your CPU - Windows 10 Forums

OCCT: OCBASE / OCCT

For both the above, read the instructions carefully and watch your system when testing.
If it starts spitting out problems and you can't shut it down - simply turn the system off/unplug it from the wall

For Intel CPUs (32 and 64 bit): Intel® Processor Diagnostic Tool

The purpose of the Intel® Processor Diagnostic Tool is to verify the functionality of an Intel® microprocessor. The diagnostic tool checks for brand identification, verifies the processor operating frequency, tests specific processor features, and performs a stress test on the processor.

===================================================
Follow this tutorials to stress test your GPU:
FurMark - GPU Stress Test - Windows 10 Forums

If you have a AMD APU instead of a discreet GPU, try UNIGINE 3D Benchmark..

Read the instructions carefully and watch your system when testing.
If it starts spitting out problems and you can't shut it down - simply turn the system off/unplug it from the wall

You have had a total of 32 BSODs in two days:

Code:

Bluescreen: P1: 0X0000001e 7/21/2020 03:31 PM P1: 0X0000001e 7/21/2020 3:30 PM
Bluescreen: P1: 0X00000050 7/21/2020 03:27 PM P1: 0X00000050 7/21/2020 03:27 PM
Bluescreen: P1: 0X0000001e 7/21/2020 02:07 PM P1: 0X0000001e 7/21/2020 02:06 PM
Bluescreen: P1: 0X0000001e 7/21/2020 02:06 PM P1: 0X0000003b 7/21/2020 01:58 PM
Bluescreen: P1: 0X0000003b 7/21/2020 00:57 PM P1: 0X000000d1 7/21/2020 03:23 AM
Bluescreen: P1: 0X000000d1 7/21/2020 03:23 AM P1: 0X00000050 7/21/2020 03:15 AM
Bluescreen: P1: 0X00000050 7/21/2020 03:14 AM P1: 0X0000000a 7/21/2020 12:33 AM
Bluescreen: P1: 0X0000000a 7/21/2020 12:32 AM P1: 0X0000000a 7/21/2020 12:32 AM
Bluescreen: P1: 0X0000003b 7/21/2020 12:25 AM P1: 0X0000000a 7/21/2020 12:25 AM
Bluescreen: P1: 0X0000003b 7/21/2020 12:25 AM P1: 0X0000001e 7/21/2020 12:17 AM
Bluescreen: P1: 0X0000001e 7/21/2020 12:16 AM P1: 0X0000001e 7/21/2020 12:16 AM
Bluescreen: P1: 0X0000007f 7/21/2020 12:02 AM P1: 0X0000007f 7/21/2020 12:02 AM

Code:

Bluescreen: P1: 0X00000050 7/20/2020 11:53 PM P1: 0X00000050 7/20/2020 11:45 PM
Bluescreen: P1: 0X0000001e 7/20/2020 11:39 PM P1: 0X00000001 7/20/2020 11:38 PM
Bluescreen: P1: 0X0000001e 7/20/2020 11:38 PM P1: 0X00000001 7/20/2020 11:38 PM
Bluescreen: P1: 0X0000001e 7/20/2020 11:38 PM P1: 0X00000001 7/20/2020 11:31 PM

Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA
The PAGE_FAULT_IN_NONPAGED_AREA bug check has a value of 0x00000050. This indicates that invalid system memory has been referenced. Typically the memory address is wrong or the memory address is pointing at freed memory.

Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED
The KMODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000001E. This indicates that a kernel-mode program generated an exception which the error handler did not catch.

Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION
The SYSTEM_SERVICE_EXCEPTION bug check has a value of 0x0000003B. This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
The DRIVER_IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x000000D1. This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL
The IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x0000000A. This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at an invalid address while at a raised interrupt request level (IRQL). This is typically either a bad pointer or a pageability problem.

Bug Check 0x7F: UNEXPECTED_KERNEL_MODE_TRAP
The UNEXPECTED_KERNEL_MODE_TRAP bug check has a value of 0x0000007F. This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.

---

Looks like quite a few BSODs did not generate dumps or the dumps were deleted. I see many of these:

Code:

7/21/2020 12:16 AM
Windows Error Reporting
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0
Problem signature:
P1: 124
P2: 0
P3: ffff8306f8007030
P4: bea00000
P5: 108
P6: 10_0_19041
P7: 0_0
P8: 768_1
P9: 
P10: 
Attached files:
\\?\C:\Windows\LiveKernelReports\WHEA\WHEA-20200720-1708.dmp
\\?\C:\Windows\TEMP\WER-22828-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER64E4.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER64E5.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6503.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6514.tmp.txt
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_10e7a59561ef47cce8a69f26934b38431f1023_00000000_cab_807a5916-9bf3-4da9-b87d-f4c91b575c09
Analysis symbol: 
Rechecking for solution: 0
Report Id: 807a5916-9bf3-4da9-b87d-f4c91b575c09
Report Status: 4
Hashed bucket: 
Cab Guid: 0

WHEA 124 is normally a CPU failure but can sometimes be caused by a defective driver, so lets enable Driver Verifier to see if that shows us anything. If not then I'm leaning toward a defective CPU, even though it passes the tests you've run.

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