Question Constant BSODS I've tried everything I can think of

Oct 2, 2020
5
0
10
0
Recently my computer began bluescreening at seemingly random times and I can't pin down what might be causing the issue. What is more interesting is that it's much less likely to blue screen when I'm doing any sort of hardware intensive task. For instance, I could play a game or work within video production software for hours with it being much less likely to bluescreen than when I'm just doing something like browsing the internet. I'm running out of ideas. Here's a list of things I've attempted and had no success either replicating the BSOD or repairing it.

-Reimaged my machine
-Ran SFC and CHKDSK
-Updated and reinstalled most drivers
-Stress tested my gpu and cpu. Was unable to cause a crash.
-Ran memory diagnostics and Memtest86. No errors.
-Reseated all hardware I could.
-Reset bios to defaults.
-Removed any unnecessary peripherals and hardware.
-Ran stability tests on my ssd.
-Ran driver verifier without a crash.

Below is a link to the dump files. If anyone could help me further troubleshoot this issue I would greatly appreciate it. Thanks!

Dump Files:
https://1drv.ms/u/s!AsT_IYB1I7f4hAlFX8ie0IROxque?e=wn5GMX

System Info:
https://1drv.ms/t/s!AsT_IYB1I7f4hAp36FYkgflAks83?e=QePyVf
 
Oct 2, 2020
5
0
10
0
The links look like spam.

What errors are you getting reported?
They're just links to dump files I've shared. I figured the dump files might give some more helpful info. Let me copy a couple.

IRQL_NOT_LESS_OR_EQUAL
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x8279)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8065FCC425D)

IRQL_NOT_LESS_OR_EQUAL
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8065FCC425D)

KMODE_EXCEPTION_NOT_HANDLED
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8045D2C3F90, 0x0, 0xFFFFFFFFFFFFFFFF)

DPC_WATCHDOG_VIOLATION
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80720EFA320)
 
Last edited:
Oct 2, 2020
5
0
10
0
They asked for my Google login.

Did you do a google search on any of these?

eg IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe gives https://answers.microsoft.com/en-us/windows/forum/windows_10-performance-winpc/bsod-irqlnotlessorequal-caused-by-ntoskrnlexe/993e0654-fcbf-439c-8ac9-d9056d38de17?auth=1

PS - I think Google wants me to agree to new conditions and that's why they keep popping up.
Weird, they're just shared onedrive files. I wouldn't think you'd have to sign in or anything. Yeah I've done some searching around which is how I found some of the things I attempted earlier. No luck still.
 
Oct 2, 2020
5
0
10
0
Most fixes I've looked at relate to memory problems.
Is your ram a kit?
Is your ram kit listed on your motherboard memory QVL?
Do you still get problems if you do not OC (including XMP) your ram?
Maybe downlaod onto a usb and run memtest - https://www.memtest86.com/
Yeah it's a 16gb two stick kit. I've ran memtest86 on them 3 or 4 times now without errors. They're on the QVL list and the problem still persists even without XMP/DOCP settings enabled.
 
Oct 2, 2020
5
0
10
0
Here's another chunk of the most recent BSODs if this might clue someone in.

On Sun 10/4/2020 12:27:38 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100420-6421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0xFC (0xFFFF83017B9CE6A0, 0x8A0000040C4009E3, 0xFFFFF8015546B2A0, 0x3)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
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 an attempt was made to execute non-executable memory.
This may be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. Memory corruption can also occur because of overheating (thermal issue). 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 10/4/2020 12:27:38 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0x33EF6)
Bugcheck code: 0xFC (0xFFFF83017B9CE6A0, 0x8A0000040C4009E3, 0xFFFFF8015546B2A0, 0x3)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This may be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. Memory corruption can also occur because of overheating (thermal issue). 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 10/4/2020 12:23:58 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100420-6468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0x139 (0x3, 0xFFFFEC0BDAB21240, 0xFFFFEC0BDAB21198, 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 10/4/2020 12:21:56 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100420-6234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0x1 (0x7FF8032F4BE4, 0x0, 0xFFFF0000, 0xFFFFA201D8F3AB80)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
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.
 

ASK THE COMMUNITY