BSOD on Boot - IRQL_not_less_or_equal

fzy1999 · Jan 11, 2024

My laptop has been getting frequent BSODs on boot. It happens regularly on boot and restart, but once the laptop is booted it usually works fine. At first a variety of error codes were given, but recently they have been IRQL_not_less_or_equal. I have followed some advice on other forums and run through the usual suspects, e.g. updating BIOS, reinstalling core drivers, sfc, memory management. I thought it was a RAM issue, but I have run Memtest 86+ for 15 passes with no errors, so don't think it is that now.

V2 logs here (one from a few months ago, one just now): OneDrive

zbook · Jan 11, 2024

Some of the prior steps may be repeated.

Please perform the following steps:

1) Run Tuneup plus > post a share link

https://www.tenforums.com/attachments/bsod-crashes-debugging/360139d1645183596-batch-files-use-bsod-debugging-tuneup_plus_log.zip

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

2) Open administrative command prompt and copy and paste:

PowerShell $D=(New-Object -ComObject Wscript.Shell).SpecialFolders(4);Compress-Archive "%WinDir%\MEMORY.DMP" "$D\Memory_dmp"

Post a share link into this thread.

3) The BIOS Version/Date LENOVO JUCN59WW, 15/03/2023

Upgrade the BIOS: 59WW > 63WW

BIOS Update for Windows 11 (64-bit) - Legion 5 15ARH7, Legion 5 15ARH7H, Legion 5 Pro 16ARH7, Legion 5 Pro 16ARH7H - Lenovo Support US

pcsupport.lenovo.com

4) Run Memtest86+ for 8 or more 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

The more the passes the better the test conditions.

It sometimes takes passes in the 20s to find malfunctioning RAM.

Take pictures > post images or share links

MemTest86+ - Test RAM

Test your RAM with MemTest 86+

www.tenforums.com

5) Run Lenovo Diagnostics UEFI (x64)

laptops and netbooks :: legion series :: legion 5 15arh7h :: 82rd :: 82rd005ruk :: pf3ygkng - Lenovo Support US

pcsupport.lenovo.com

Take pictures > post images or share links displaying the tests performed with results

fzy1999 · Jan 12, 2024

I’ve done everything except Lenovo Diagnostics, which is currently running. I’ve uploaded all the other files/photos into the Onedrive folder, thanks!

zbook · Jan 12, 2024

Nice progress.

Open administrative command prompt and copy and paste:

chkdsk /b /v

Run on all drives using the syntax: chkdsk /b /v C: or chkdsk /b /v D: or chkdsk /b /v E: etc.

Make sure that these switches run on the Windows drive overnight while sleeping.

C:\WINDOWS\system32>chkdsk /b /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) n

Type: Y

Reboot as needed.

When all are completed run:

https://www.tenforums.com/attachments/bsod-crashes-debugging/317041d1612147952-batch-files-use-bsod-debugging-chkdskfromevent.bat

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

When available post share links for post #2 step #5.

Code:

    Found corrupt basic file structure for "\ProgramData\Microsoft\Windows\AppRepository\STATER~1.SRD <0x2,0xd2ecf>"
        ... queued for offline repair.
                                                                                     
 Phase duration (Orphan reconnection): 1.54 seconds.
    Found lost file "\$Extend\$RmMetadata\$TxfLog\$Tops <0x1,0x20>"; requesting reconnection to index "$I30" of directory "\$Extend\$RmMetadata\$TxfLog <0x1,0x1e>"
        ... queued for offline repair.
    Found a file "\ProgramData\Microsoft\Windows\AppRepository\StateRepository-Deployment.srd <0x2,0xd2ecf>" with bad links
        ... queued for offline repair.

Code:

Windows has found problems and some were fixed online;
the remaining problems must be fixed offline.

Code:

      Drive: C:
 Free Space: 212.9 GB
Total Space: 974.5 GB
File System: NTFS
      Model: SKHynix_HFS001TEJ9X115N

      Drive: D:
 Free Space: 842.0 GB
Total Space: 1907.7 GB
File System: NTFS
      Model: WD Blue SN570 2TB

fzy1999 · Jan 13, 2024

I ran Lenovo Diagnostics fully with all tests passed, but I couldn't save the log. I only have a picture of the end of the log, which is in the Onedrive.

I ran the chkdsk commands, but as you will see from the log below it seems that the C: drive check did not register. I looked at the screen after restarting throughout and the C: drive check seemed to be running fine until it reached 100% and the laptop attempted to restart, at which point there were multiple IRQL_not_less_or_equal BSODs. Should I try running it again?

Code:

TimeCreated : 14/01/2024 02:04:55
Message     : Chkdsk was executed in read/write mode. 
              
              Checking file system on D:
              The type of the file system is NTFS.
              Volume label is New Volume.
              
              Stage 1: Examining basic file system structure ...
                381440 file records processed.                                                       
              File verification completed.
               Phase duration (File record verification): 2.04 seconds.
                1464 large file records processed.                                   
               Phase duration (Orphan file record recovery): 1.45 milliseconds.
                0 bad file records processed.                                     
               Phase duration (Bad file record checking): 0.25 milliseconds.
              
              Stage 2: Examining file name linkage ...
                136 reparse records processed.                                     
                419458 index entries processed.                                                       
              Index verification completed.
               Phase duration (Index verification): 2.78 seconds.
                0 unindexed files scanned.                                       
               Phase duration (Orphan reconnection): 67.54 milliseconds.
                0 unindexed files recovered to lost and found.                   
               Phase duration (Orphan recovery to lost and found): 1.07 milliseconds.
                136 reparse records processed.                                     
               Phase duration (Reparse point and Object ID verification): 1.85 milliseconds.
              
              Stage 3: Examining security descriptors ...
              Cleaning up 9 unused index entries from index $SII of file 9.
              Cleaning up 9 unused index entries from index $SDH of file 9.
              Cleaning up 9 unused security descriptors.
              Security descriptor verification completed.
               Phase duration (Security descriptor verification): 0.81 milliseconds.
                19009 data files processed.                                           
               Phase duration (Data attribute verification): 0.26 milliseconds.
              
              Stage 4: Looking for bad clusters in user file data ...
                381424 files processed.                                                               
              File data verification completed.
               Phase duration (User file recovery): 13.57 minutes.
              
              Stage 5: Looking for bad, free clusters ...
                215542151 free clusters processed.                                                       
              Free space verification is complete.
               Phase duration (Free space recovery): 1.51 minutes.
              
              Windows has scanned the file system and found no problems.
              No further action is required.
              
              1953497087 KB total disk space.
              1090695280 KB in 360576 files.
                  126088 KB in 19011 indexes.
                       0 KB in bad sectors.
                  507115 KB in use by the system.
                   65536 KB occupied by the log file.
               862168604 KB available on disk.
              
                    4096 bytes in each allocation unit.
               488374271 total allocation units on disk.
               215542151 allocation units available on disk.
              Total duration: 15.17 minutes (910381 ms).
              


TimeCreated : 12/01/2024 20:55:02
Message     : Chkdsk was executed in scan mode on a volume snapshot. 
              
              Checking file system on C:
              The type of the file system is NTFS.
              Volume label is Windows-SSD.
              
              Stage 1: Examining basic file system structure ...
                1417216 file records processed.                                                       
              File verification completed.
               Phase duration (File record verification): 6.09 seconds.
                24780 large file records processed.                                   
               Phase duration (Orphan file record recovery): 12.24 milliseconds.
                0 bad file records processed.                                     
               Phase duration (Bad file record checking): 0.03 milliseconds.
              
              Stage 2: Examining file name linkage ...
                2658 reparse records processed.                                     
                  Found an unneeded link ($FILE_NAME: "$Tops") in index "$I30" of directory
              "\$Extend\$RmMetadata\$TxfLog <0x1,0x1e>"
                      ... repaired online.
                1677436 index entries processed.                                                       
              Index verification completed.
               Phase duration (Index verification): 13.26 seconds.
                2 unindexed files scanned.                                       
                  Found corrupt basic file structure for "\ProgramData\Microsoft\Windows\AppRepository\STATER~1.SRD
              <0x2,0xd2ecf>"
                      ... queued for offline repair.
                                                                                                      Phase duration
              (Orphan reconnection): 1.54 seconds.
                  Found lost file "\$Extend\$RmMetadata\$TxfLog\$Tops <0x1,0x20>"; requesting reconnection to index
              "$I30" of directory "\$Extend\$RmMetadata\$TxfLog <0x1,0x1e>"
                      ... queued for offline repair.
                  Found a file "\ProgramData\Microsoft\Windows\AppRepository\StateRepository-Deployment.srd
              <0x2,0xd2ecf>" with bad links
                      ... queued for offline repair.
                0 unindexed files recovered to lost and found.                   
               Phase duration (Orphan recovery to lost and found): 8.25 milliseconds.
                2658 reparse records processed.                                     
               Phase duration (Reparse point and Object ID verification): 10.25 milliseconds.
              
              Stage 3: Examining security descriptors ...
              Security descriptor verification completed.
               Phase duration (Security descriptor verification): 25.36 milliseconds.
                130111 data files processed.                                           
               Phase duration (Data attribute verification): 0.08 milliseconds.
              CHKDSK is verifying Usn Journal...
              Usn Journal verification completed.
              Windows has found problems and some were fixed online;
              the remaining problems must be fixed offline.
              Please run "chkdsk /spotfix" to fix the issues.
              
               997872639 KB total disk space.
               764722276 KB in 587983 files.
                  371732 KB in 130112 indexes.
                       0 KB in bad sectors.
                 1520791 KB in use by the system.
                   65536 KB occupied by the log file.
               231257840 KB available on disk.
              
                    4096 bytes in each allocation unit.
               249468159 total allocation units on disk.
                57814460 allocation units available on disk.
              Total duration: 20.96 seconds (20966 ms).
              
              ----------------------------------------------------------------------
              
              
              Stage 1: Examining basic file system structure ...
              
              Stage 2: Examining file name linkage ...
              The parent 0x100000002001e of index entry $Tops of index $I30
              in file 0x20 is incorrect.  The expected parent is 0x100000000001e.
              Deleting index entry $Tops in index $I30 of file 1E.
              CHKDSK is scanning unindexed files for reconnect to their original directory.
              Recovering orphaned file $Tops (20) into directory file 1E.
              Recovering orphaned file $Tops (20) into directory file 1E.
              There is no NTFS file name attribute in file 0xd2ecf.
              Correcting minor file name errors in file D2ECF.
                2 unindexed files recovered to original directory.
              
              Stage 3: Examining security descriptors ...
              


TimeCreated : 22/12/2023 12:02:13
Message     : Chkdsk was executed in verify mode on a volume snapshot. 
              
              Checking file system on \Device\HarddiskVolume5
              Volume label is Windows-SSD.
              
              Examining 1 corruption record ...
              
              Record 1 of 1: Corrupt File "\ProgramData\Microsoft\Windows\AppRepository\StateRepository-Deployment.srd
              <0x2,0xd2ecf>" ... no corruption found.
              
              1 corruption record processed in 0.1 seconds.
              
              Windows has examined the list of previously identified potential issues and found no problems.
              No further action is required.
              


TimeCreated : 24/10/2023 00:44:47
Message     : Chkdsk was executed in scan mode on a volume snapshot. 
              
              Checking file system on C:
              The type of the file system is NTFS.
              Volume label is Windows-SSD.
              
              Stage 1: Examining basic file system structure ...
                1417216 file records processed.                                                       
              File verification completed.
               Phase duration (File record verification): 6.51 seconds.
                20085 large file records processed.                                   
               Phase duration (Orphan file record recovery): 9.95 milliseconds.
                0 bad file records processed.                                     
               Phase duration (Bad file record checking): 0.03 milliseconds.
              
              Stage 2: Examining file name linkage ...
                2249 reparse records processed.                                     
                1655124 index entries processed.                                                       
              Index verification completed.
               Phase duration (Index verification): 14.76 seconds.
                0 unindexed files scanned.                                       
               Phase duration (Orphan reconnection): 2.42 seconds.
                0 unindexed files recovered to lost and found.                   
               Phase duration (Orphan recovery to lost and found): 0.29 milliseconds.
                2249 reparse records processed.                                     
               Phase duration (Reparse point and Object ID verification): 9.23 milliseconds.
              
              Stage 3: Examining security descriptors ...
              Security descriptor verification completed.
               Phase duration (Security descriptor verification): 25.88 milliseconds.
                118955 data files processed.                                           
               Phase duration (Data attribute verification): 0.04 milliseconds.
              CHKDSK is verifying Usn Journal...
                41545552 USN bytes processed.                                                           
              Usn Journal verification completed.
               Phase duration (USN journal verification): 101.14 milliseconds.
              
              Windows has scanned the file system and found no problems.
              No further action is required.
              
               997872639 KB total disk space.
               790786772 KB in 642198 files.
                  367724 KB in 118956 indexes.
                       0 KB in bad sectors.
                 1560519 KB in use by the system.
                   65536 KB occupied by the log file.
               205157624 KB available on disk.
              
                    4096 bytes in each allocation unit.
               249468159 total allocation units on disk.
                51289406 allocation units available on disk.
              Total duration: 23.86 seconds (23865 ms).
              
              ----------------------------------------------------------------------
              
              
              Stage 1: Examining basic file system structure ...
              
              Stage 2: Examining file name linkage ...
              
              Stage 3: Examining security descriptors ...
              


TimeCreated : 12/10/2023 22:20:32
Message     : Chkdsk was executed in read/write mode. 
              
              Checking file system on D:
              The type of the file system is NTFS.
              Volume label is New Volume.
              
              Stage 1: Examining basic file system structure ...
                126720 file records processed.                                                       
              File verification completed.
               Phase duration (File record verification): 868.96 milliseconds.
                1557 large file records processed.                                   
               Phase duration (Orphan file record recovery): 1.55 milliseconds.
                0 bad file records processed.                                     
               Phase duration (Bad file record checking): 0.29 milliseconds.
              
              Stage 2: Examining file name linkage ...
                106 reparse records processed.                                     
                140718 index entries processed.                                                       
              Index verification completed.
               Phase duration (Index verification): 1.25 seconds.
                0 unindexed files scanned.                                       
               Phase duration (Orphan reconnection): 18.88 milliseconds.
                0 unindexed files recovered to lost and found.                   
               Phase duration (Orphan recovery to lost and found): 0.86 milliseconds.
                106 reparse records processed.                                     
               Phase duration (Reparse point and Object ID verification): 2.35 milliseconds.
              
              Stage 3: Examining security descriptors ...
              Cleaning up 12 unused index entries from index $SII of file 0x9.
              Cleaning up 12 unused index entries from index $SDH of file 0x9.
              Cleaning up 12 unused security descriptors.
              Security descriptor verification completed.
               Phase duration (Security descriptor verification): 2.21 milliseconds.
                6999 data files processed.                                           
               Phase duration (Data attribute verification): 0.33 milliseconds.
              
              Stage 4: Looking for bad clusters in user file data ...
                126704 files processed.                                                               
              File data verification completed.
               Phase duration (User file recovery): 13.63 minutes.
              
              Stage 5: Looking for bad, free clusters ...
                250996161 free clusters processed.                                                       
              Free space verification is complete.
               Phase duration (Free space recovery): 1.89 minutes.
              
              Windows has scanned the file system and found no problems.
              No further action is required.
              
              1953497087 KB total disk space.
               949230264 KB in 111914 files.
                   29848 KB in 7001 indexes.
                       0 KB in bad sectors.
                  252327 KB in use by the system.
                   65536 KB occupied by the log file.
              1003984648 KB available on disk.
              
                    4096 bytes in each allocation unit.
               488374271 total allocation units on disk.
               250996162 allocation units available on disk.
              Total duration: 15.56 minutes (933804 ms).
              










TimeCreated : 12/01/2024 21:08:22
Message     :
              
              Checking file system on C:
              The type of the file system is NTFS.
              Windows will now check the disk.                         
              Volume label is Windows-SSD.
              
              Examining 3 corruption records ...
              
              Record 1 of 3: Corrupt File "\ProgramData\Microsoft\Windows\AppRepository\StateRepository-Deployment.srd
              <0x2,0xd2ecf>" ... no corruption found.
              
              Record 2 of 3: Index entry for file "\$Extend\$RmMetadata\$TxfLog\$Tops <0x1,0x20>" is missing from
              index "$I30" of directory "\$Extend\$RmMetadata\$TxfLog <0x1,0x1e>" ... no corruption found.
              
              Record 3 of 3: Adding lost file
              "\ProgramData\Microsoft\Windows\AppRepository\StateRepository-Deployment.srd <0x2,0xd2ecf>" to index
              "$I30" of directory "\$Secure <0x9,0x9>" ... no corruption found.
              
              3 corruption records processed in 0.1 seconds.
              
              Windows has examined the list of previously identified issues and found no problems.
              No further action is required.
              


TimeCreated : 21/10/2023 17:08:10
Message     :
              
              Checking file system on C:
              The type of the file system is NTFS.
              Volume label is Windows-SSD.
              
              
              A disk check has been scheduled.
              Windows will now check the disk.                         
              
              Stage 1: Examining basic file system structure ...
                1417216 file records processed.                                                       
              
              File verification completed.
               Phase duration (File record verification): 5.07 seconds.
                20078 large file records processed.                                   
              
               Phase duration (Orphan file record recovery): 9.23 milliseconds.
                0 bad file records processed.                                     
              
               Phase duration (Bad file record checking): 2.05 milliseconds.
              
              Stage 2: Examining file name linkage ...
                2241 reparse records processed.                                     
              
                1654658 index entries processed.                                                       
              
              Index verification completed.
               Phase duration (Index verification): 13.85 seconds.
                0 unindexed files scanned.                                       
              
               Phase duration (Orphan reconnection): 1.50 seconds.
                0 unindexed files recovered to lost and found.                   
              
               Phase duration (Orphan recovery to lost and found): 507.65 milliseconds.
                2241 reparse records processed.                                     
              
               Phase duration (Reparse point and Object ID verification): 13.21 milliseconds.
              
              Stage 3: Examining security descriptors ...
              Cleaning up 1346 unused index entries from index $SII of file 0x9.
              Cleaning up 1346 unused index entries from index $SDH of file 0x9.
              Cleaning up 1346 unused security descriptors.
              CHKDSK is compacting the security descriptor stream
              Security descriptor verification completed.
               Phase duration (Security descriptor verification): 92.46 milliseconds.
                118722 data files processed.                                           
              
               Phase duration (Data attribute verification): 2.43 milliseconds.
              CHKDSK is verifying Usn Journal...
                40795744 USN bytes processed.                                                           
              
              Usn Journal verification completed.
               Phase duration (USN journal verification): 90.56 milliseconds.
              Correcting errors in the Volume Bitmap.
              
              Windows has made corrections to the file system.
              No further action is required.
              
               997872639 KB total disk space.
               778313436 KB in 640126 files.
                  366312 KB in 118725 indexes.
                       0 KB in bad sectors.
                 1559595 KB in use by the system.
                   65536 KB occupied by the log file.
               217633296 KB available on disk.
              
                    4096 bytes in each allocation unit.
               249468159 total allocation units on disk.
                54408324 allocation units available on disk.
              Total duration: 21.19 seconds (21190 ms).
              
              Internal Info:
              00 a0 15 00 d6 93 0b 00 d6 1f 14 00 00 00 00 00  ................
              bd 07 00 00 04 01 00 00 00 00 00 00 00 00 00 00  ................

zbook · Jan 13, 2024

There are multiple Lenovo diagnostics.

Which one was selected?

What tests were selected?

What tests were not selected?

If possible run the Lenovo UEFI hardware diagnostics > take pictures with a camera or smart phone camera > post a share link into the newest post with only the Lenovo UEFI hardware diagnostic results.

1) Please boot to safe mode with command prompt (shift + restart) > type: chkdsk /b /v C:

Boot to Safe Mode in Windows 11 Tutorial

This tutorial will show you how to boot Windows 11 into normal mode, Safe Mode, Safe Mode with Networking, or Safe Mode with Command Prompt. Safe mode starts Windows in a basic state, using a limited set of files and drivers. If a problem doesn't happen in safe mode, this means that default...

www.elevenforum.com

C:\WINDOWS\system32>chkdsk /b /v C:
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y

Reboot

Run overnight while sleeping.

2) Please post a new V2 share link into the newest post. (not into the opening post)

The Lenovo diagnostics reported some drive test results.

The laptop appears to have malfunctioning hardware.

For indirect verification the computer stability / instability can be tested with either or both Windows Driver Verifier (WDV) and safe mode.

3) Read this link on Windows Driver Verifier (WDV):

Enable and Disable Driver Verifier in Windows 10

How to Enable and Disable Driver Verifier in Windows 10

www.tenforums.com

Learn the methods to recover from using the tool by booting into safe mode and running one or more of these commands:

verifier /reset

verifier /bootmode resetonbootfail

4) Make a new restore point:

Create System Restore Point in Windows 11 Tutorial

This tutorial will show you how to manually create a restore point in Windows 11. Turning on system protection for a drive allows System Restore to include the drive when restore points are created so you can undo undesired system changes by reverting to a previous point in time. System...

www.elevenforum.com

5) Start WDV with these settings:

a) Select all non-Microsoft drivers
b) Select no Microsoft drivers
c) Start the WDV testing with the 3 customized tests in the TF tutorial

6) Plan to run WDV with various customized tests for approximately 48 hrs

7) If there is no immediate BSOD when WDV is started then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link into the newest post with only the querysettings results.

8) For any BSOD post a new V2 share link into the newest post with only the V2 log collector results.

x BlueRobot · Jan 14, 2024

Please do not follow that Driver Verifier tutorial unless you want random unrelated crashes. It's proven to be incorrect time and time again. Could you please open an elevated (administrative) command prompt and then the following command:

Rich (BB code):

fltmc filters >> %userprofile%\Desktop\filters.txt

Please attach the filters.txt file to your next post. In addition to that, please enable Driver Verifier using the following tutorial, however, please only enable the following three settings for now:

Special Pool
Security Checks
Force IRQL Checking

It is important that you enable Driver Verifier on fltmgr.sys as well. Additionally, from an elevated command prompt, please run the following command:

Rich (BB code):

reg save HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services %userprofile%\Desktop\services.hiv

Please attach the file named services.hiv to your next post.

P.S. zbook will most likely say that the Driver Verifier tutorial which I recommended is "unsafe" or "inadequate", yet they'll be able to provide no reason as to why this is the case.

fzy1999 · Jan 14, 2024

Oddly enough the problem is even worse in Safe Mode. If I try the shift + restart method, there is an inevitable crash on boot before Windows just boots normally. I tried to force Safe Mode in msconfig, which resulted in several crashes. I did manage to get into Safe Mode a few times, but it just BSODs or completely freezes after about 5 seconds, whereas I can run regular Windows just fine.

New V2 logs here: OneDrive

x BlueRobot · Jan 14, 2024

Another Stop 0x139 again for the exact same reason as the previous ones, could you please follow the instructions mentioned in my previous post?

x BlueRobot · Jan 14, 2024

I would strongly recommend removing McAfee WebAdvisor using the removal instructions. I've seen third-party security programs cause far too many crashes, especially Avast, AVG and McAfee. Once it has been removed, then please open an elevated command prompt and then enter the following command:

Rich (BB code):

sc query McAfee WebAdvisor

zbook · Jan 14, 2024

The BSOD in safe mode typically indicate malfunctioning hardware.

Make free or pay backup images and save them to another disk drive or the cloud.

(Acronis, Aoemi, EaseUS, Macrium, Paragon, etc.)

Backup and Restore with Macrium Reflect

How to Create and Restore a System Image Backup with Macrium Reflect

www.tenforums.com

Please run:

https://www.tenforums.com/attachments/bsod-crashes-debugging/358470d1643456903-batch-files-use-bsod-debugging-gather_additional_dump_files.bat

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Post a share link.

fzy1999 · Jan 14, 2024

Hi BlueRobot, here is the link to the files you requested: OneDrive

McAfee has been removed, will run Verifier soon.

zbook · Jan 14, 2024

For verifier make sure that this tutorial is used:

Enable and Disable Driver Verifier in Windows 10

How to Enable and Disable Driver Verifier in Windows 10

www.tenforums.com

This tutorial is one of the safest methods in using the tool.

The other link on verifier has many mistakes.

fzy1999 · Jan 14, 2024

zbook, these are the additional dumps you requested: OneDrive

zbook · Jan 14, 2024

Please uninstall the Nvidia GPU drivers nvlddmkm.sys using DDU and reinstall from the Lenovo website.

Display Driver Uninstaller: How to use

How to Use Display Driver Uninstaller to Uninstall any Installed Display Driver

www.sevenforums.com

Display Driver Uninstaller (DDU) download latest version 18.0.7.6

Official Display Driver Uninstaller (DDU) download website. DDU is a driver removal utility that can help you completely uninstall AMD/NVIDIA/INTEL graphics card drivers and packages from your system, trying to remove all leftovers (including registry keys, folders and files, driver store).

www.wagnardsoft.com

Code:

Name    NVIDIA GeForce RTX 3060 Laptop GPU
PNP Device ID    PCI\VEN_10DE&DEV_2560&SUBSYS_3AFE17AA&REV_A1\4&2693600A&0&0009
Adapter Type    NVIDIA GeForce RTX 3060 Laptop GPU, NVIDIA compatible
Adapter Description    NVIDIA GeForce RTX 3060 Laptop GPU
Adapter RAM    (1,048,576) bytes
Installed Drivers    C:\WINDOWS\System32\DriverStore\FileRepository\nvlti.inf_amd64_9a2c79b60d6607c6\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvlti.inf_amd64_9a2c79b60d6607c6\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvlti.inf_amd64_9a2c79b60d6607c6\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvlti.inf_amd64_9a2c79b60d6607c6\nvldumdx.dll
Driver Version    31.0.15.4633
INF File    oem47.inf (Section274 section)
Driver    C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NVLTI.INF_AMD64_9A2C79B60D6607C6\NVLDDMKM.SYS (31.0.15.4633, 56.02 MB (58,741,280 bytes), 06/01/2024 17:30)

zbook · Jan 14, 2024

Please make free or pay backup images and save them to another disk drive or the cloud.

fzy1999 · Jan 14, 2024

Nvidia driver was uninstalled with DDU and then reinstalled from Lenovo website. Some BSODs happened along the way, so I have run V2 log collector again: OneDrive

Verifier is now running.

fzy1999 · Jan 14, 2024

Forgot to ask - what am I looking for with Driver Verifier and when should I stop running it?

x BlueRobot · Jan 14, 2024

zbook said:
This tutorial is one of the safest methods in using the tool.

The other link on verifier has many mistakes.

Yet, I've demonstrated on this forum that that is not the case on more than one occasion. What mistakes? Can you please tell me what they are?

fzy1999 said:
Forgot to ask - what am I looking for with Driver Verifier and when should I stop running it?

Which set of instructions are you following? I would strongly recommend that you follow the instructions I provided in post #7, particularly the option called Security Checks. The tutorial suggested by zbook is just going to lead to a number of false positives, I think it just strengthens my point really when zbook can't provide any solid argument why the TF tutorial is better, other than using vague terms like "safest" and my tutorial having "mistakes". I guarantee that he will provide no clarification or actual technical explanation on what mistakes there are.

fzy1999 · Jan 14, 2024

BlueRobot, I am currently following your tutorial, with the 3 listed settings, all the non-Windows drivers selected, and the 4 Windows drivers you listed in the tutorial including fltmgr.sys.