Question Almost monthly bluescreen

[JunkSniperJoe]

For a while now, I've been having random Windows 10 bluescreens about once a month. They seem to happen during/after watching a YouTube video or doing something with Netflix. I've uninstalled my graphics drivers with DDU and reinstalled many times; however, the issue still persist. Memtest86 shows that my RAM is fine. My BIOS is up to date as well.

minidump zip file link

Specs:

CPU: AMD Ryzen 5 5600X 3.7 GHz 6-Core Processor
CPU Cooler: ARCTIC Liquid Freezer II 360 56.3 CFM Liquid CPU Cooler
Motherboard: Asus TUF GAMING X570-PRO (WI-FI) ATX AM4 Motherboard
Memory: Corsair Vengeance RGB Pro 32 GB (4 x 8 GB) DDR4-3600 CL18 Memory
Storage: Samsung 970 Evo Plus 500 GB M.2-2280 NVME Solid State Drive
Storage: Samsung 980 Pro 1 TB M.2-2280 NVME Solid State Drive
Video Card: MSI GeForce RTX 3080 10GB 10 GB GAMING X TRIO Video Card
Case: Corsair 5000D AIRFLOW ATX Mid Tower Case
Power Supply: SeaSonic FOCUS Plus Gold 850 W 80+ Gold Certified Fully Modular ATX Power Supply

 

[Koekieezz]

For a while now, I've been having random Windows 10 bluescreens about once a month. They seem to happen during/after watching a YouTube video or doing something with Netflix. I've uninstalled my graphics drivers with DDU and reinstalled many times; however, the issue still persist. Memtest86 shows that my RAM is fine. My BIOS is up to date as well.

minidump zip file link

Specs:

CPU: AMD Ryzen 5 5600X 3.7 GHz 6-Core Processor
CPU Cooler: ARCTIC Liquid Freezer II 360 56.3 CFM Liquid CPU Cooler
Motherboard: Asus TUF GAMING X570-PRO (WI-FI) ATX AM4 Motherboard
Memory: Corsair Vengeance RGB Pro 32 GB (4 x 8 GB) DDR4-3600 CL18 Memory
Storage: Samsung 970 Evo Plus 500 GB M.2-2280 NVME Solid State Drive
Storage: Samsung 980 Pro 1 TB M.2-2280 NVME Solid State Drive
Video Card: MSI GeForce RTX 3080 10GB 10 GB GAMING X TRIO Video Card
Case: Corsair 5000D AIRFLOW ATX Mid Tower Case
Power Supply: SeaSonic FOCUS Plus Gold 850 W 80+ Gold Certified Fully Modular ATX Power Supply

what is the bios bluescreen code?

 

[JunkSniperJoe]

what is the bios bluescreen code?

Not sure if this if what you're looking for, but here's a WhoCrashed report with various BugCheck codes:

On Sun 1/23/2022 3:00:31 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012322-5562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF801594FB320)
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 Mon 12/20/2021 3:34:17 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\122021-5328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72A0)
Bugcheck code: 0xA (0xFFFFFFFF8D481203, 0x2, 0x1, 0xFFFFF80374082AB2)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 11/13/2021 4:12:35 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\111321-5734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72A0)
Bugcheck code: 0xA (0xFFFFFFFF8D481143, 0x2, 0x1, 0xFFFFF80403682AB2)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 8/12/2021 5:36:11 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081221-5218-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x3AD0)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFF8787080BF920, 0xFFFFB90F46528BB0)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
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.



On Sun 7/18/2021 5:33:46 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071821-5156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6F20)
Bugcheck code: 0x139 (0x3, 0xFFFFF68EF4BFF8C0, 0xFFFFF68EF4BFF818, 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 7/18/2021 5:33:46 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: win32kfull.sys (win32kfull+0x3192C)
Bugcheck code: 0x139 (0x3, 0xFFFFF68EF4BFF8C0, 0xFFFFF68EF4BFF818, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
Bug check description: The kernel has detected the corruption of a critical data structure.
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.

 

[JunkSniperJoe]

Had another bluescreen today. In my non expert opinion, it seems that a corrupt driver is causing the problem. However, I'm not sure if there's any way to isolate said driver, or if I need to uninstall/reinstall all of them.

 

[Karadjgne]

Run Memtest86 on 1 stick of ram at a time. Going to take an overnight/all day test. I suspect that one of the modules is bad, but it's taking a while to build up enough usage to find the error.

 

[JunkSniperJoe]

Run Memtest86 on 1 stick of ram at a time. Going to take an overnight/all day test. I suspect that one of the modules is bad, but it's taking a while to build up enough usage to find the error.

Thanks for the reply, I'll give that a shot when I have the time. However, I'm curious as to why an error would show up on an individual stick of RAM when Memtest86 showed that all 4 together had no errors? Does this have something to do with building up usage?

 

[Karadjgne]

If you think about all 4 sticks running simultaneously, and you are only using up 12Gb of ram at any given time, that's only 3Gb per stick. If the error is at the 4Gb mark, it rarely ever sees a hit. Testing sticks individually for @ 4-8Hrs runs the full gammut of tests on the full 8Gb, multiple times, so if there are any errors it has multiple opportunities to get recorded.

The only other thing I can think of is a very slow memory leak, and it's taking that amount of time to build up. But thats also going to require you leaving the pc on 24/7, ram is volitile memory so looses all data at power loss. A fast memory leak isn't all that difficult to locate, a slow leak is a royal pita.