Frequent and Varied BSODs

ThinkLess · Jun 26, 2022

Hello,

I have an ongoing BSOD problem that has persisted with this PC build for over a year. Sometimes, I go a week without crashing. Sometimes, it crashes within seconds of booting into windows and logging in. A variety of errors have occurred, for example these:

IRQL_NOT_LESS_OR_EQUAL- Most Frequent
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
KMODE_EXCEPTION_NOT_HANDLED- Second most frequent
KERNEL_SECURITY_CHECK_FAILURE
SYSTEM_SERVICE_EXCEPTION
DPC_WATCHDOG_VIOLATION

What seems to cause it to crash more frequently is browsing the internet. It crashes way less often while playing a game. I have attempted the following:

Clean install of Windows 10 and 11, memtest86 on each stick of RAM with no errors, chkdsk with no errors, replaced the RAM, replaced the HDD, updated BIOS to latest version, swapped RAM into different slots. I have spent most of the time focused on drivers though as that seems to be the leading cause according to Google. I have installed the latest drivers from the motherboard manufacturer, and done a clean install where I grabbed the drivers individually from the vendors. I also did a clean install of windows and let windows update grab the drivers. I am doing no overclocking whatsoever, and do not have any overclocking utilities installed. I have not touched any voltage or speed settings in the BIOS.

Here is the log

DESKTOP-L0ARUEK-(2022-06-26_20-57-25).zip

drive.google.com

zbook · Jun 27, 2022

There were five collected BSOD mini dump files.
One was corrupt.
Three of the four displayed misbehaving Nvidia GPU driver nvlddmkm.sys

The BIOS is out of date.

The log BSOD and live kernel bugchecks were:

133
141
1AA
D1
A
189
BE
7F
139

Please perform the following steps:

1) Uninstall the Nvidia GPU driver nvlddmkm.sys using Display Driver Uninstaller
Reinstall from the Nvidia website
Make sure the clean install box is checked and if available install the physx driver.

2) Run:

https://www.tenforums.com/attachments/bsod-crashes-debugging/360137d1645183388-batch-files-use-bsod-debugging-tuneup_plus_log.bat

Post a share link into this thread.

3) Check the Motherboard version.
Upgrade the BIOS to the most up to date non-beta BIOS

4) Run Memtest86 for two tests of four passes (total eight passes)

MemTest86 - Official Site of the x86 Memory Testing Tool

MemTest86 is the original self booting memory testing software for x86 and ARM computers. Supporting both BIOS and UEFI, with options to boot from USB.

www.memtest86.com

Take pictures and post images or share links into this thread.
Memtest86 has a feature to create text reports.
If possible, include the text reports with the images in the share links.

5) For BSOD after performing the above steps post a new V2 into the newest post

Name NVIDIA GeForce RTX 2060
PNP Device ID PCI\VEN_10DE&DEV_1F08&SUBSYS_86F01043&REV_A1\4&1FC990D7&0&0019
Adapter Type NVIDIA GeForce RTX 2060, NVIDIA compatible
Adapter Description NVIDIA GeForce RTX 2060
Adapter RAM (1,048,576) bytes
Installed Drivers C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_c43eff7079c4c90c\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_c43eff7079c4c90c\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_c43eff7079c4c90c\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_c43eff7079c4c90c\nvldumdx.dll
Driver Version 31.0.15.1640
INF File oem2.inf (Section001 section)
Driver C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NV_DISPIG.INF_AMD64_C43EFF7079C4C90C\NVLDDMKM.SYS (31.0.15.1640, 41.66 MB (43,683,808 bytes), 6/23/2022 2:59 PM)

ThinkLess · Jun 27, 2022

I have completed steps 1-3. Crashed several times in safe mode while using DDU, but eventually was able to complete it and restart twice. Installed Nvidia drivers with no network connection. Here is the latest V2 log as well. I will be running memtest a bit later.

DESKTOP-L0ARUEK-(2022-06-27_16-33-28).zip

drive.google.com

Code:

 Microsoft Windows 11 Pro  Version 21H2 (OS Build 22000.739)
 
==================================================================

    Started on Mon 06/27/2022 at 16:25:25.47
    
        [SFC /ScanNow]
    
Beginning system scan.  This process will take some time.

Results:
 
Windows Resource Protection did not find any integrity violations.
 
==================================================================

    Started on Mon 06/27/2022 at 16:26:55.88

        [DISM /online /cleanup-image /ScanHealth]

Deployment Image Servicing and Management tool
Version: 10.0.22000.653

Image Version: 10.0.22000.739
 
No component store corruption detected.

The operation completed successfully.
 
==================================================================

    Started on Mon 06/27/2022 at 16:27:57.27

        [DISM /online /cleanup-image /RestoreHealth]

Deployment Image Servicing and Management tool
Version: 10.0.22000.653

Image Version: 10.0.22000.739
 
The restore operation completed successfully.

The operation completed successfully.
 
==================================================================

The second "SFC /ScanNow" was skipped, as the first output the following:

Windows Resource Protection did not find any integrity violations.
 
==================================================================

    Started on Mon 06/27/2022 at 16:28:42.34

        [ChkDsk /Scan] 
 
The type of the file system is NTFS.
 
Stage 1: Examining basic file system structure ...
916224 file records processed.                                                       
File verification completed.
Phase duration (File record verification): 6.86 seconds.
14797 large file records processed.                                   
Phase duration (Orphan file record recovery): 6.75 milliseconds.
0 bad file records processed.                                     
Phase duration (Bad file record checking): 0.04 milliseconds.
 
Stage 2: Examining file name linkage ...
324 reparse records processed.                                     
1120330 index entries processed.                                                       
Index verification completed.
Phase duration (Index verification): 11.47 seconds.
0 unindexed files scanned.                                       
Phase duration (Orphan reconnection): 776.07 milliseconds.
0 unindexed files recovered to lost and found.                   
Phase duration (Orphan recovery to lost and found): 0.10 milliseconds.
324 reparse records processed.                                     
Phase duration (Reparse point and Object ID verification): 3.12 milliseconds.
 
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 36.28 milliseconds.
102054 data files processed.                                           
Phase duration (Data attribute verification): 0.04 milliseconds.
CHKDSK is verifying Usn Journal...
40052608 USN bytes processed.                                                           
Usn Journal verification completed.
Phase duration (USN journal verification): 208.79 milliseconds.

Windows has scanned the file system and found no problems.

No further action is required.
 
487686470 KB total disk space.
380366524 KB in 299511 files.
217604 KB in 102055 indexes.
0 KB in bad sectors.
1043286 KB in use by the system.
65536 KB occupied by the log file.
106059056 KB available on disk.
 
4096 bytes in each allocation unit.
121921617 total allocation units on disk.
26514764 allocation units available on disk.
Total duration: 19.37 seconds (19378 ms).
 
==================================================================
 
    Started on Mon 06/27/2022 at 16:29:08.83
 
AutoReboot   
 
TRUE       
 
==================================================================
 
        [Set AutoReboot = False]
 
Updating property(s) of '\\DESKTOP-L0ARUEK\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.
==================================================================
 
AutoReboot   
 
FALSE       
 
==================================================================
 
DebugInfoType   
 
3             
 
==================================================================

        [Set DebugInfoType = 7]

Updating property(s) of '\\DESKTOP-L0ARUEK\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.
==================================================================
 
DebugInfoType   
 
7             
 
==================================================================

        [WMIC PageFile list]

AllocatedBaseSize=2048
CurrentUsage=0
Description=C:\pagefile.sys
InstallDate=20211216182428.081537-360
Name=C:\pagefile.sys
PeakUsage=1
Status=
TempPageFile=FALSE
 
==================================================================
 
AutomaticManagedPagefile   
 
TRUE                     
 
==================================================================

        [Set AutomaticManagedPagefile = True]

Updating property(s) of '\\DESKTOP-L0ARUEK\ROOT\CIMV2:Win32_ComputerSystem.Name="DESKTOP-L0ARUEK"'
Property(s) update successful.
==================================================================
 
AutomaticManagedPagefile   
 
TRUE                     
 
==================================================================

        [BcdEdit /enum {badmemory}]

RAM Defects
-----------
identifier              {badmemory}
 
==================================================================

    Finished on Mon 06/27/2022 at 16:29:09.76
    It took 3 minutes and 44 seconds to complete the operations.

zbook · Jun 27, 2022

Tuneup plus results were good.
The startup and recovery system failure settings are optimal for witnessing BSOD and dump file creation.

BSOD while in safe mode is very typical of malfunctioning hardware.
There were five new BSOD and the debugging did not find any misbehaving drivers.

The next steps will depend on the two reports from the Memtest86 testing.

ThinkLess · Jun 27, 2022

I am about to start memtest86. One thing that I have been told is that the power supply I'm using might not be sufficient for my graphics card and could cause unstable behavior. Is this possible?

zbook · Jun 27, 2022

Insufficient power can cause unexpected shutdowns and restarts.
They are typical of event 41 entries.
Many times these entries present as unexpected shutdowns and restarts without BSOD.

At a later time boot to the BIOS > post images for CPU voltages and frequency: 3.3, 5, and 12 voltages

There are stress tests that can be performed.
Often though they don't find the malfunctioning hardware.
Typically swap testing is required to rule in and / or rule out malfunctioning hardware.

ThinkLess · Jun 28, 2022

Here's the result from the first 4 passes of memtest86. I'll do the next 4 passes overnight tonight.

MemTest86-Report-20220627-200552.html

drive.google.com

Also, I swapped in a higher rated PSU and am still experiencing crashes

zbook · Jun 28, 2022

Please check to see if the installed RAM is or is not on the Qualified Vendor List (QV).

The installed RAM modules (CMK32GX4M2D3600C18) were not seen on the Qualified Vendor List (QVL).

https://download.gigabyte.com/FileList/Memory/mb_memory_b450_4L4D_matisse.pdf?v=a0a08d71b3b84f0182d326e14d5c21fe

For testing purposes test RAM on the QVL.

Monitor computer stability using:

Reliability Monitor is the Best Windows Troubleshooting Tool You Aren't Using

When it comes to hidden gems in Windows, nothing beats the Reliability monitor tool, hidden behind a link inside of another tool that you don't use either.

www.howtogeek.com

ThinkLess · Jun 28, 2022

I will do that. Side note, I've been running driver verifier with all drivers selected for an hour now. Watching videos and playing games simultaneously with no crashes. Obviously the performance has taken a hit, but it's working. Any thoughts?

zbook · Jun 28, 2022

Running WDV is useful for finding misbehaving drivers.

If there are no BSOD while running the tool then look for malfunctioning or incompatible hardware.

Post a new V2.

Open command prompt and type or copy and paste:
verifier /querysettings
Post a share link into this thread.

ThinkLess · Jun 28, 2022

New v2 log

DESKTOP-L0ARUEK-(2022-06-28_20-37-47).zip

drive.google.com

zbook · Jun 28, 2022

Make a new restore point:

If there were no performance problems including very slow boot with the current WDV settings then modify the customized tests.

Select all customized settings except:
[ ] 0x00000004 Randomized low resources simulation.

Test all non-Microsoft drivers.
Test no Microsoft drivers.

If there is no immediate BSOD then open administrative command prompt and type or copy and paste:

verifier /querysettings

For any BSOD post a new V2.

Frequent and Varied BSODs

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Similar threads