[SOLVED] New PC has had 88 BSODs in 11 months...~ntoskrnl.exe~ ?

[j_needs_BSOD_help]

Hello,

I built this computer back in October of 2020. I have had issues with BSOD since then, randomly. At first I was not concerned about the BSOD because this computer is my first build and I thought maybe some drivers needed updates, etc. The BSOD were rare, but as time has gone on the past 11 months, the BSOD are more frequent (literally multiple times a day with different codes) but still feel random. I have had 88+ "Critical" events (Kernel-Power ID 41 Task 63) over the 11 months according to the Event Viewer. I feel like it’s a driver problem and not hardware because the computer was literally just-put-together-brand-new when I began experiencing BSOD...but at this point with so many BSOD I have no idea.
The BSOD happens less during use of the computer but I can crash in the middle of gameplay or tasks, which is getting more frustrating. BSOD definitely happens more often when the computer has idled, which has made downloading any multi-gb files difficult because my internet isn’t the fastest.
I have read that ntoskrnl.exe gets blamed in BSOD but is not necessarily the culprit. I tried reading logs with WinDbg but I can only understand so much (there was only one log where I saw that TaskbarX caused one BSOD so I removed it). I want to add that I haven't done a good job of saving logs of my BSODs until recently, but I am uploading each .dmp after each BSOD now. In regards to the flash USB I’ll get my hands on one soon.

That being said, I have tried almost everything that I feel capable of and I’m at a loss, so here I am asking for help. I’ve tried to provide the most context possible with the following information.

TL;DR: 88+ Bluescreens over the past 11 months on my freshly built PC (October 2020). I really need help. Refer to the following for my specs and already attempted solutions.

Specs
Windows 10
MSI GeForce GTX 1660 Ti Ventus XS OC 6gb
Ryzen 5 3600 6 core 12 thread
GSkill Ripjaws V Series 16gb 3600 c18
SK hynix Gold S31 1tb ssd
Antec NeoECO Gold Zen Series Zen 500W 80 plus gold
MSI B450-A Pro Max

Attempted Solutions: BSODs still persist with each attempted fix
Windows Update successful, no issues
SFC successful, no issues
DISM successful, no issues
Chkdsk C:/f successful, no issues
Chkdsk C:/r ran, not sure how to check the log
Windows Memory Diagnostic
Uninstalled: Bluestacks, TaskbarX, MSI DragonCenter
Checked for driver updates on all sections of Device Manager
Updated Realtek audio driver
Many processors showing up on Device Manager. Is this suspicious? I have learned now that since my Ryzen has 12 threads there are supposed to be 12 processors listed!
Downloaded WinDbg to try to read my minidumps and find out the cause(s)...the only one I understood was that TaskbarX caused a BSOD at least once.
Downloaded DriverView
Downloaded BlueScreenView
Ran Driver Verifier but honestly I was confused about how it can help, after restarting my PC it BSOD in a loop 4-5 times until asking to pick a restore point.
Changed BIOS FCH Base Clock (MHz) from “[Auto]” to “[100.00]”
Changed BIOS XMP to “Disable”
Uninstalled and reinstalled Discord.exe after it caused one BSOD

Haven’t Attempted
Driver Verifier + WinDbg?
BIOS Update (I haven’t done this because I don’t have a flash drive USB)
Change BIOS voltage?
Registry Editor?
Do I have Faulty RAM?
Memtest86 (I haven’t done this because I don’t have a flash drive USB)
A driver (service) for this device has been disabled. An alternate driver may be providing this functionality. (Code 32)

Link to my .dmp files and more
https://drive.google.com/drive/folders/1icZoZSaXoe0hl0aNc1e49IOPGyIhisfL?usp=sharing

 

[Koekieezz]

I built this computer back in October of 2020. I have had issues with BSOD since then, randomly. At first I was not concerned about the BSOD because this computer is my first build and I thought maybe some drivers needed updates, etc. The BSOD were rare. As time has gone on the past 11 months, the BSOD seem more frequent but still random. Since then I have had 88 "Critical" events (Kernel-Power ID 41 Task 63) according to the Event Viewer. I feel like it’s a driver problem and not hardware because the computer was literally just-put-together-brand-new when I began experiencing BSOD.... but at this point I have no idea.

The BSOD rarely occurs during use of the computer but I have crashed in the middle of gameplay or tasks, which is frustrating. BSOD definitely happens more often when the computer has idled, which has made downloading any multi-gb files difficult. I have read that ntoskrnl.exe gets blamed in BSOD but is not necessarily the culprit. I tried reading logs with WinDbg but I can only understand so much (there was only one log where I saw that TaskbarX caused one BSOD). That being said, I have tried almost everything that I feel capable of and I’m at a loss, so here I am asking for help. I’ve tried to provide the most context possible with the following information.


Specs

Windows 10

MSI GeForce GTX 1660 Ti Ventus XS OC 6gb

Ryzen 5 3600 6 core 12 thread

GSkill Ripjaws V Series 16gb 3600 c18

SK hynix Gold S31 1tb ssd

Antec NeoECO Gold Zen Series Zen 500W 80 plus gold

MSI B450-A Pro Max


Attempted Solutions: BSODs still persist with each attempted fix

Windows Update successful, no issues

SFC successful, no issues

DISM successful, no issues

Chkdsk C:/f successful, no issues

Chkdsk C:/r ran, not sure how to check the log

Changed BIOS FCH Base Clock (MHz) from “[Auto]” to “[100.00]”

Windows Memory Diagnostic

Uninstalled: Bluestacks, TaskbarX, MSI DragonCenter

Checked for driver updates on all sections of Device Manager

Updated Realtek audio driver

Many processors showing up on Device Manager. Is this suspicious? I tried this solution and it didn’t work: https://superuser.com/questions/1389872/how-fix-driver-error-for-ryzen-processors-code-32

Downloaded WinDbg to try to read my minidumps and find out the cause(s)...the only one I understood was that TaskbarX caused a BSOD at least once.

Downloaded DriverView

Downloaded BlueScreenView

Ran Driver Verifier but honestly I was confused about how it can help, after restarting my PC it BSOD in a loop 4-5 times until asking to pick a restore point.


Haven’t Attempted

Driver Verifier + WinDbg?

BIOS Update (I haven’t done this because I don’t have a flash drive USB)

Change BIOS voltage?

Registry Editor?

Do I have Faulty RAM?

Memtest86 (I haven’t done this because I don’t have a flash drive USB)

Is my USB microphone a problem? Or any other USB devices?

Clean install of GPU?

Link to my .dmp files, .evtx files, screenshots
https://drive.google.com/drive/folders/1icZoZSaXoe0hl0aNc1e49IOPGyIhisfL?usp=sharing

try this step by step (read until end, you might need a usb drive and format it at fat32):

• Disconnect from internet
• Uninstall gpu driver DDU (clean and do not restart).
• Uninstall all the processors on device manager (should be 12 on yours, also when it asks for restart, click on no) like this:
  
  
• Restart the pc to bios, and update to the latest bios. Then go to bios again after update and load default or optimized settings, then save and exit.
  
  
• boot up to windows and install the latest AMD Chipset driver, reboot, go to power plan, choose amd ryzen balanced, and connect to internet.
  
  
• Install the latest nvidia driver.
  
  *do this all offline until reboot after installing chipset driver, also you may reboot to bios after all of this to set the XMP (and previous settings you did) and make sure ram is on slot 2 and 4 if you use 2 sticks. Download needed files (highlighted word) before doing step 1, do the step by orders.
  
  
• And check windows update (and optional updates) if there is any and install them (except chipset in optional update). Also enable Hardware Accelerated Graphics Scheduling (available on the latest win 10 update) in graphics settings like this and reboot:
  
  

Make sure the psu connected to the gpu is 1 pcie cable per 1 slot (use main cable, not the branches/split) like this:

 

[j_needs_BSOD_help]

Link to my .dmp files, .evtx files, screenshots
https://drive.google.com/drive/folders/1icZoZSaXoe0hl0aNc1e49IOPGyIhisfL?usp=sharing

Update
I want to add that I haven't done a good job of saving logs of my BSODs until recently, but I am uploading each .dmp after each BSOD now.
So I left my computer on overnight to try to get another BSOD and I did, so I uploaded that as well. I didn't expect to see Discord.exe on WinDbg... I'll try uninstalling and reinstalling Discord to fix drivers and see it causes another BSOD.

Microsoft (R) Windows Debugger Version 10.0.19041.685 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\092921-9609-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17763 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff8064b81c000 PsLoadedModuleList = 0xfffff8064bc334d0
Debug session time: Wed Sep 29 05:37:54.255 2021 (UTC - 7:00)
System Uptime: 1 days 0:40:54.828
Loading Kernel Symbols
...............................................................
................................................................
.............................................................
Loading User Symbols
Loading unloaded module list
........
For analysis of this file, run !analyze -v
5: kd> !analyze -v
***

• *
• Bugcheck Analysis *
• *

***

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8064b87b5d0, Address of the instruction which caused the bugcheck
Arg3: fffff181bd930a60, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 3

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-AF4C73Q

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 20

Key : Analysis.Memory.CommitPeak.Mb
Value: 81

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8064b87b5d0

BUGCHECK_P3: fffff181bd930a60

BUGCHECK_P4: 0

CONTEXT: fffff181bd930a60 -- (.cxr 0xfffff181bd930a60)
rax=0000000000000004 rbx=ffff8c80f5893180 rcx=0000000000000000
rdx=0000000000000000 rsi=ffffbb0cdb286080 rdi=000116108997af8b
rip=fffff8064b87b5d0 rsp=fffff181bd931450 rbp=fffff181bd9314f9
r8=0000000000000000 r9=0000000000000000 r10=00000000000007c0
r11=ffffbb0cddcd4e50 r12=ffffbb0cddaa6a88 r13=ffffbb0cddcd4e50
r14=ffffbb0cddaa6a80 r15=ffffbb0cdb2861c0
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!IopfCompleteRequest+0xd70:
fffff8064b87b5d0 f0480fbaaf1059000000 lock bts qword ptr [rdi+5910h],0 ds:002b:000116108998089b=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Discord.exe

STACK_TEXT:
fffff181bd931450 fffff8064c13e191 : ffff8c80f5893180 fffff18100000002 0000000000000000 0000000000000002 : nt!IopfCompleteRequest+0xd70
fffff181bd931560 fffff8064ba11357 : 0000000000000001 0000000000000000 ffffbb0cd9edee50 000000002842e700 : nt!IovCompleteRequest+0x1bd
fffff181bd931650 fffff808da7ade4c : ffffbb0cd9edee50 000000002842e700 fffff181bd931729 ffffbb0cdbb37080 : nt!IofCompleteRequest+0x196b27
fffff181bd931680 fffff8064b98c63a : ffffbb0cd9edee50 fffff8064c14a1e0 ffffbb0c00000000 ffffbb0c00000000 : Npfs!NpFsdWrite+0x8c
fffff181bd9316f0 fffff8064c13df49 : ffffbb0cd9edee50 ffffbb0ccd4398f0 0000000000000000 ffffbb0cded51520 : nt!IopfCallDriver+0x56
fffff181bd931730 fffff8064ba0f557 : ffffbb0ccd3eb8d0 0000000000000000 ffffbb0ccd3eb8d0 ffffbb0cdf544380 : nt!IovCallDriver+0x275
fffff181bd931770 fffff808d88d5d18 : 0000000000000000 fffff8064bb227c4 0000000000000000 fffff181bd931828 : nt!IofCallDriver+0x19c947
fffff181bd9317b0 fffff8064b98c63a : ffffbb0cd9edee50 fffff8064c14a1e0 ffffbb0c00000001 ffffbb0c00000000 : FLTMGR!FltpDispatch+0xe8
fffff181bd931810 fffff8064c13df49 : ffffbb0cd9edee50 ffffbb0ccd3eb8d0 00000000000001a8 fffff8064b854192 : nt!IopfCallDriver+0x56
fffff181bd931850 fffff8064ba0f557 : ffffbb0cd9edee50 ffffbb0cdb9d27f0 0000000000000000 ffffbb0cdf541870 : nt!IovCallDriver+0x275
fffff181bd931890 fffff8064bdfd1d1 : ffffbb0cd9edee50 0000000000000000 ffffbb0cd9edee50 fffff8064b9e5308 : nt!IofCallDriver+0x19c947
fffff181bd9318d0 fffff8064be49d4d : 0000000000000000 0000000000000000 fffff181bd931b80 fffff181bd931b80 : nt!IopSynchronousServiceTail+0x1b1
fffff181bd931980 fffff8064b9e5308 : 0000000000000400 0000000000000000 0000000000000001 0000000033974714 : nt!NtWriteFile+0x8bd
fffff181bd931a90 0000000077af1cbc : 0000000077af199a 0000002377b7158c 0000000000000023 0000000033b4d000 : nt!KiSystemServiceCopyEnd+0x28
000000001009eb98 0000000077af199a : 0000002377b7158c 0000000000000023 0000000033b4d000 000000001019fefc : 0x77af1cbc
000000001009eba0 0000002377b7158c : 0000000000000023 0000000033b4d000 000000001019fefc 000000001009ebe8 : 0x77af199a
000000001009eba8 0000000000000023 : 0000000033b4d000 000000001019fefc 000000001009ebe8 000000002842e700 : 0x0000002377b7158c 000000001009ebb0 0000000033b4d000 : 000000001019fefc 000000001009ebe8 000000002842e700 0000000000000098 : 0x23 000000001009ebb8 000000001019fefc : 000000001009ebe8 000000002842e700 0000000000000098 000000001019f478 : 0x33b4d000 000000001009ebc0 000000001009ebe8 : 000000002842e700 0000000000000098 000000001019f478 0000000000000000 : 0x1019fefc 000000001009ebc8 000000002842e700 : 0000000000000098 000000001019f478 0000000000000000 0000000033974714 : 0x1009ebe8 000000001009ebd0 0000000000000098 : 000000001019f478 0000000000000000 0000000033974714 0000000000000000 : 0x2842e700 000000001009ebd8 000000001019f478 : 0000000000000000 0000000033974714 0000000000000000 0000000033974714 : 0x98 000000001009ebe0 0000000000000000 : 0000000033974714 0000000000000000 0000000033974714 00000000`1019f1dc : 0x1019f478


SYMBOL_NAME: Npfs!NpFsdWrite+8c

MODULE_NAME: Npfs

IMAGE_NAME: Npfs.SYS

IMAGE_VERSION: 10.0.17763.831

STACK_COMMAND: .cxr 0xfffff181bd930a60 ; kb

BUCKET_ID_FUNC_OFFSET: 8c

FAILURE_BUCKET_ID: 0x3B_c0000005_VRF_Npfs!NpFsdWrite

OS_VERSION: 10.0.17763.1

BUILDLAB_STR: rs5_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {99b4c891-c1a8-e284-5714-192bf2d76ecf}

Followup: MachineOwner
---------

 

[j_needs_BSOD_help]

try this step by step (read until end, you might need a usb drive and format it at fat32):

• Disconnect from internet
• Uninstall gpu driver DDU (clean and do not restart).
• Uninstall all the processors on device manager (should be 12 on yours, also when it asks for restart, click on no) like this:
  
  
• Restart the pc to bios, and update to the latest bios. Then go to bios again after update and load default or optimized settings, then save and exit.
  
  
• boot up to windows and install the latest AMD Chipset driver, reboot, go to power plan, choose amd ryzen balanced, and connect to internet.
  
  
• Install the latest nvidia driver.
  
  *do this all offline until reboot after installing chipset driver, also you may reboot to bios after all of this to set the XMP (and previous settings you did) and make sure ram is on slot 2 and 4 if you use 2 sticks. Download needed files (highlighted word) before doing step 1, do the step by orders.
  
  
• And check windows update (and optional updates) if there is any and install them (except chipset in optional update). Also enable Hardware Accelerated Graphics Scheduling (available on the latest win 10 update) in graphics settings like this and reboot:
  
  

Make sure the psu connected to the gpu is 1 pcie cable per 1 slot (use main cable, not the branches/split) like this:

I'll let you know when I give these a try after I get my hands on a USB.

 

[Koekieezz]

I'll let you know when I give these a try after I get my hands on a USB.

hope all the best 😀

 

[j_needs_BSOD_help]

Update
I want to add that I haven't done a good job of saving logs of my BSODs until recently, but I am uploading each .dmp after each BSOD now.
So I left my computer on overnight to try to get another BSOD and I did, so I uploaded that as well. I didn't expect to see Discord.exe on WinDbg... I'll try uninstalling and reinstalling Discord to fix drivers and see it causes another BSOD.

Another BSOD. This time I can't understand much.
Once again uploaded .dmp to my shared files
https://drive.google.com/drive/folders/1icZoZSaXoe0hl0aNc1e49IOPGyIhisfL?usp=sharing


Microsoft (R) Windows Debugger Version 10.0.19041.685 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\092921-9640-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17763 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff8046a202000 PsLoadedModuleList = 0xfffff8046a6194d0
Debug session time: Wed Sep 29 10:23:05.442 2021 (UTC - 7:00)
System Uptime: 0 days 2:03:39.169
Loading Kernel Symbols
...............................................................
................................................................
...............................................................
Loading User Symbols
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
7: kd> !analyze -v
***

• *
• Bugcheck Analysis *
• *

***

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 000000000000003c, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8046a48adcc, address which referenced memory

Debugging Details:
------------------

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 2

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-AF4C73Q

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 12

Key : Analysis.Memory.CommitPeak.Mb
Value: 81

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: a

BUGCHECK_P1: 0

BUGCHECK_P2: ff

BUGCHECK_P3: 3c

BUGCHECK_P4: fffff8046a48adcc

READ_ADDRESS: fffff8046a600f08: Unable to get Flags value from nt!KdVersionBlock
GetUlongFromAddress: unable to read from fffff8046a6c5340
fffff8046a740390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8046a600f08: Unable to get Flags value from nt!KdVersionBlock
0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: ffff800ca75da100 -- (.trap 0xffff800ca75da100)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=0000000000000000 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl nz na pe nc
0000000000000000 ?? ??? Resetting default scope STACK_TEXT: ffffd4010d67d308 fffff8046a3cb8e9 : 000000000000000a 0000000000000000 00000000000000ff 000000000000003c : nt!KeBugCheckEx ffffd4010d67d310 fffff8046a3c7cd4 : ffff800cb3f441b0 fffff8046ab3e49c 0000000000000001 ffff9d7f60600000 : nt!KiBugCheckDispatch+0x69 ffffd4010d67d450 fffff8046a48adcc : 13f378716a3a4fa8 ffffd4010d67d5c8 00001858f33aff01 ffffad81d13aff00 : nt!KiPageFault+0x454 ffffd4010d67d5e0 fffff8046a3bc0b2 : 0000000000000001 ffffd4010d67d690 ffff800ca0cdfe00 0000000000000000 : nt!KzSetIrqlUnsafe+0x7c ffffd4010d67d610 fffff8046ac87bbf : fffff8046a388e3b 0000000000000000 ffff800ca75da100 ffffad81d1391180 : nt!KiInterruptDispatchNoLockNoEtw+0xe2 ffffd4010d67d7a8 fffff8046a388e3b : 0000000000000000 ffff800ca75da100 ffffad81d1391180 ffff800ca75da010 : hal!HalProcessorIdle+0xf ffffd4010d67d7b0 fffff8046a2c576b : 0000000000000000 0000000000989680 0000000000000000 000000000000007e : nt!PpmIdleDefaultExecute+0x1b ffffd4010d67d7e0 fffff8046a2c4f1f : 00000048023200e6 0000000000000004 0000000000000001 0000000000000000 : nt!PpmIdleExecuteTransition+0x6bb ffffd4010d67db00 fffff8046a3bdaac : ffffffff00000000 ffffad81d1391180 ffffad81d13a1300 ffff800cb06e3080 : nt!PoIdle+0x33f ffffd4010d67dc60 0000000000000000 : ffffd4010d67e000 ffffd4010d678000 0000000000000000 00000000`00000000 : nt!KiIdleLoop+0x2c


SYMBOL_NAME: nt!KzSetIrqlUnsafe+7c

IMAGE_NAME: Unknown_Image

IMAGE_VERSION: 10.0.17763.2213

STACK_COMMAND: .thread ; .cxr ; kb

MODULE_NAME: Unknown_Module

FAILURE_BUCKET_ID: RAISED_IRQL_USER_FAULT_AV

OS_VERSION: 10.0.17763.1

BUILDLAB_STR: rs5_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {1ae3b702-9567-a461-faae-d89b06459582}

Followup: MachineOwner
---------

 

[j_needs_BSOD_help]

Another BSOD. This time I can't understand much.
Once again uploaded .dmp to my shared files
https://drive.google.com/drive/folders/1icZoZSaXoe0hl0aNc1e49IOPGyIhisfL?usp=sharing

Update: Disabled XMP in my BIOS.
So from what was explained to me by someone on reddit, some of my BSOD errors are often related to RAM. They said, "Yes, this is the setting. If you ask why: The Ryzen 5 3600 is rated to work with 3200MHz RAM. It is possible that the system gets unstable with higher clocked RAM (XMP is a type of memory oc). Errors/BOSDs related to RAM are often "Page fault in nonpaged area" (afaik) and "Irql not less or equal". "
At this point, I'll wait and see if I continue to get RAM related BSOD errors and continue to upload the crash dumps if I do.