Daily BSOD

koolip098 · 15 Dec 2020

Hello,

It's been almost 2 years now since I started experiencing those annoying issues with daily BSOD. In all instances it's always the general "irql_not_less_or_equal" error. There are periods where it's better, so I "only" experience a BSOD every second day, but then there are also periods where it's 2-3 times daily and I can't really pinpoint the exact issue. It's gone through multiple updates for all the possible software/drivers that I could think that would cause this issue - my primary suspects are Hyper V/Docker Desktop or Nvidia drivers, but I have no idea how I could pinpoint the exact issue.

Here's the attached diagnostic file that I created with V2 Log collector: [removed]

My current windows version is 2004 (build 19041.685), but that started happening way before this update, so it's probably not really related to the windows updates.

Ztruker · 15 Dec 2020

There are no dumps in the zip file.

The event log shows one of these every day since 11/25.

Attachment 310771

Diagnostics Test
HDD TEST

Run HDTune to

check the health,
scan for errors, not quick scan but full scan
run a benchmark.

Run CrystalDiskInfo Portable and CrystalDiskMark Portable to

Check health of drive
Check performance of drive

Run SeaGate SeaTools for Windows (test ALL hard drives - HDD/SSD/USB/etc)

You can also try the various options available with chkdsk.

Also, please run 1. Tuneup.bat - Run SFC, DISM and CHKDSK commands and use WMIC to change some settings.

Be sure to follow this when the batch file completes to collect to dqata.

Part Three
Capture output of batch file to Clipboard

Follow the directions in Part Two of the Index (first post at the top) to capture the output of the batch file in the Command Prompt or Powershell Window for posting in your BSOD thread at tenforums.com.

koolip098 · 15 Dec 2020

Thank you for your answer! I did run Tuneup1.bat and here's the result:



###########################################################

# The following commands will be run in sequence. #

# They can take quite a while to run, be patient. #

###########################################################



sfc /scannow

dism /online /cleanup-image /scanhealth

dism /online /cleanup-image /restorehealth

sfc /scannow



chkdsk /scan





C:\WINDOWS\system32>sfc /scannow



Beginning system scan. This process will take some time.



Beginning verification phase of system scan.

Verification 100% complete.



Windows Resource Protection did not find any integrity violations.



C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth



Deployment Image Servicing and Management tool

Version: 10.0.19041.572



Image Version: 10.0.19041.685



[==========================100.0%==========================] No component store corruption detected.

The operation completed successfully.



C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth



Deployment Image Servicing and Management tool

Version: 10.0.19041.572



Image Version: 10.0.19041.685



[==========================100.0%==========================] The restore operation completed successfully.

The operation completed successfully.



C:\WINDOWS\system32>sfc /scannow



Beginning system scan. This process will take some time.



Beginning verification phase of system scan.

Verification 100% complete.



Windows Resource Protection did not find any integrity violations.



C:\WINDOWS\system32>chkdsk /scan

The type of the file system is NTFS.



Stage 1: Examining basic file system structure ...

3385344 file records processed.

File verification completed.

Phase duration (File record verification): 18.60 seconds.

10065 large file records processed.

Phase duration (Orphan file record recovery): 0.00 milliseconds.

0 bad file records processed.

Phase duration (Bad file record checking): 0.47 milliseconds.



Stage 2: Examining file name linkage ...

10752 reparse records processed.

4575840 index entries processed.

Index verification completed.

Phase duration (Index verification): 1.34 minutes.

0 unindexed files scanned.

Phase duration (Orphan reconnection): 1.86 minutes.

0 unindexed files recovered to lost and found.

Phase duration (Orphan recovery to lost and found): 3.03 milliseconds.

10752 reparse records processed.

Phase duration (Reparse point and Object ID verification): 49.85 milliseconds.



Stage 3: Examining security descriptors ...

Security descriptor verification completed.

Phase duration (Security descriptor verification): 110.32 milliseconds.

595249 data files processed.

Phase duration (Data attribute verification): 0.42 milliseconds.

CHKDSK is verifying Usn Journal...

40733376 USN bytes processed.

Usn Journal verification completed.

Phase duration (USN journal verification): 161.66 milliseconds.



Windows has scanned the file system and found no problems.

No further action is required.



487274060 KB total disk space.

319314040 KB in 2366167 files.

1214864 KB in 595250 indexes.

0 KB in bad sectors.

3521368 KB in use by the system.

65536 KB occupied by the log file.

163223788 KB available on disk.



4096 bytes in each allocation unit.

121818515 total allocation units on disk.

40805947 allocation units available on disk.

Total duration: 3.51 minutes (211001 ms).

As for the error. I'm not fully sure which "Harddisk2" is, but with CrystalDiskInfo I indeed see some issues in my "E:" drive (WDC WD1003FZEX-00K3CA0). Probably that's the one? There are 2 warning attributes there:
C5 Current Pending Sector Count - 200 current - 200 worst
C6 Uncorrectable Sector Count - 200 current - 200 worst

SeaTools - all 5 disks seem to pass the Short Generic test, but for Long Generic, up to that point the above mentioned "E:" drive failed.

The thing is however, that all my docker data from Hyper-V is on my "I:" drive

Ztruker · 15 Dec 2020

You ran the wrong batch file. I wanted you to run Tuneup.bat which included some WMIC commands.

Please run Tuneup2.bat next.

Run Tuneup2.bat from the BSOD batch repository. Follow Part One, Part Two and Part Three to Download, Run and Collect output data from the batch file to post here.

You can see what the batch file does when you click on the above link.

koolip098 · 15 Dec 2020

Whops, sorry - here we go, Tuneup2.bat



C:\WINDOWS\system32>wmic recoveros get DebugInfoType

DebugInfoType

7





C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7

Updating property(s) of '\\BORUT-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk4\\Partition1"'

Property(s) update successful.



C:\WINDOWS\system32>wmic recoveros get DebugInfoType

DebugInfoType

7





C:\WINDOWS\system32>wmic pagefile list /format:list





AllocatedBaseSize=4864

CurrentUsage=96

Description=C:\pagefile.sys

InstallDate=20190509174313.096797+120

Name=C:\pagefile.sys

PeakUsage=130

Status=

TempPageFile=FALSE









C:\WINDOWS\system32>wmic Computersystem where name="BORUT-PC" get AutomaticManagedPagefile

AutomaticManagedPagefile

TRUE





C:\WINDOWS\system32>wmic Computersystem where name="BORUT-PC" set AutomaticManagedPagefile=True

Updating property(s) of '\\BORUT-PC\ROOT\CIMV2:Win32_ComputerSystem.Name="BORUT-PC"'

Property(s) update successful.



C:\WINDOWS\system32>wmic Computersystem where name="BORUT-PC" get AutomaticManagedPagefile

AutomaticManagedPagefile

TRUE





C:\WINDOWS\system32>bcdedit /enum {badmemory}



RAM Defects

-----------

identifier {badmemory}