BSOD IRQL_NOT_LESS_OR_EQUAL caused by ntoskrnl.exe

Hello there,

I have been receiving multiple BSOD... I downloaded "BlueScreenView" and it shows this:

irql_not_less_or_equal ntoskrnl.exe
BAD_POOL_CALLER ntoskrnl.exe
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY Netwtw10.sys

PC Specifications: Lenovo Legion 5 (Ryzen 7 4800h, GTX 1660 TI, 16 GB, SAMSUNG MZVLB512HBJQ-000L2 512.1 GB, CT1000MX500SSD1 1000.2 GB)
Windows Version Number: Version 20H2 (OS Build 19042.985)

Looking at the internet, it says that it could be the following things:

Faulty Ram: I used memtest86 for 4 passes and it completed succesfully with no errors at all
Bad drivers: This is a tricky one... How can I identify the driver which is causing the problem in order to reinstall it?
Corrupted system: I used the following cmd commands and it shows no errors: dism /online /cleanup-image /restorehealth and sfc /scannow
Damaged/Failing hard drive: This laptop is fairly new and it has two SSDs, the main one (512 GB) where the OS is installed is the one that is used, but the other one (1 TB Crucial 500) is totally new. Nonetheless, I used CrystalDiskInfo and both of them show a health status of 100%
CPU issues: Performed 2 hours of Prime95 stress testing to see if the problem lies in CPU - 0 errors or warning

Windows is fully updated and Lenovo Vantage doesn't reflect any extra driver updates. I went ahead and used DriversCloud to update any drivers just in case and updated AMD Chipset (this didn't solve the issue).

I uploaded the dump files to onedrive so you guys can check it out if needed: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online. (I also uploaded the V2 log collector zip file there)

Thanks! I'd really appreciate your help here.

Hello Ramadeus,

I have processed your crash dumps and the following summary shows the findings:

Built by: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Tue May 25 21:47:56.976 2021 (UTC + 1:00)
System Uptime: 0 days 16:19:01.850
BugCheck A, {fffffffffffff000, ff, 0, fffff80539b61f49}
*** WARNING: Unable to verify timestamp for win32k.sys
Probably caused by: ntkrnlmp.exe ( nt!PpmIdleUpdateConcurrency+79 )
BUGCHECK_STR: AV
PROCESS_NAME: System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Tue May 25 05:28:33.444 2021 (UTC + 1:00)
System Uptime: 0 days 0:43:36.076
BugCheck 1E, {ffffffffc0000005, fffff80081c09f22, 0, ffffffffffffffff}
Probably caused by: ntkrnlmp.exe ( nt!KiDispatchException+1b589b )
BUGCHECK_STR: 0x1E_c0000005_R
PROCESS_NAME: League of Legends.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Tue May 25 00:11:32.970 2021 (UTC + 1:00)
System Uptime: 0 days 0:22:53.602
BugCheck A, {6, 2, 1, fffff8033d3104c3}
Probably caused by: ntkrnlmp.exe ( nt!KiDeferredReadySingleThread+2f3 )
BUGCHECK_STR: AV
PROCESS_NAME: Ableton Live 10 Suite.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Mon May 24 23:32:31.082 2021 (UTC + 1:00)
System Uptime: 0 days 0:10:58.714
BugCheck C2, {d, ffffba0224f79160, fffff801, bea53a721f09e1ea}
*** WARNING: Unable to verify timestamp for FocusriteusbAudio.sys
Probably caused by: FocusriteusbAudio.sys ( FocusriteusbAudio+6d3f )
BUGCHECK_STR: 0xc2_d
PROCESS_NAME: svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Mon May 24 23:21:05.650 2021 (UTC + 1:00)
System Uptime: 0 days 0:23:16.282
BugCheck A, {188, ff, 0, fffff806830087db}
Probably caused by: hardware ( nt!KiSystemServiceExit+11b )
BUGCHECK_STR: AV
PROCESS_NAME: Ableton Live 10 Suite.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


The driver highlighted in red is the only one identified in the crash dumps. Please see if you can update your Focusrite Audio drivers. The ntkrnlmp.exe is a Microsoft kernel process and is not the problem although it is identified as a probable cause simply because it was active on the stack at the time of the crash trying to read an invalid address.

philc43 said:

Hello Ramadeus,

I have processed your crash dumps and the following summary shows the findings:

Built by: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Tue May 25 21:47:56.976 2021 (UTC + 1:00)
System Uptime: 0 days 16:19:01.850
BugCheck A, {fffffffffffff000, ff, 0, fffff80539b61f49}
*** WARNING: Unable to verify timestamp for win32k.sys
Probably caused by: ntkrnlmp.exe ( nt!PpmIdleUpdateConcurrency+79 )
BUGCHECK_STR: AV
PROCESS_NAME: System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Tue May 25 05:28:33.444 2021 (UTC + 1:00)
System Uptime: 0 days 0:43:36.076
BugCheck 1E, {ffffffffc0000005, fffff80081c09f22, 0, ffffffffffffffff}
Probably caused by: ntkrnlmp.exe ( nt!KiDispatchException+1b589b )
BUGCHECK_STR: 0x1E_c0000005_R
PROCESS_NAME: League of Legends.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Tue May 25 00:11:32.970 2021 (UTC + 1:00)
System Uptime: 0 days 0:22:53.602
BugCheck A, {6, 2, 1, fffff8033d3104c3}
Probably caused by: ntkrnlmp.exe ( nt!KiDeferredReadySingleThread+2f3 )
BUGCHECK_STR: AV
PROCESS_NAME: Ableton Live 10 Suite.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Mon May 24 23:32:31.082 2021 (UTC + 1:00)
System Uptime: 0 days 0:10:58.714
BugCheck C2, {d, ffffba0224f79160, fffff801, bea53a721f09e1ea}
*** WARNING: Unable to verify timestamp for FocusriteusbAudio.sys
Probably caused by: FocusriteusbAudio.sys ( FocusriteusbAudio+6d3f )
BUGCHECK_STR: 0xc2_d
PROCESS_NAME: svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Mon May 24 23:21:05.650 2021 (UTC + 1:00)
System Uptime: 0 days 0:23:16.282
BugCheck A, {188, ff, 0, fffff806830087db}
Probably caused by: hardware ( nt!KiSystemServiceExit+11b )
BUGCHECK_STR: AV
PROCESS_NAME: Ableton Live 10 Suite.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


The driver highlighted in red is the only one identified in the crash dumps. Please see if you can update your Focusrite Audio drivers. The ntkrnlmp.exe is a Microsoft kernel process and is not the problem although it is identified as a probable cause simply because it was active on the stack at the time of the crash trying to read an invalid address.

Hello! Thank you so much for your assistance as it's been impossible for me to fix this

I went ahead and re-installed windows 10 from scratch using a Boot USB - My Focusritedrivers are up to date according to their webpage. I've noticed that this only happens when I'm using any audio production related software (with or without Focusrite drivers). I've attached the last crash dumps I have received since I reinstalled windows 10 here: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

- - - Updated - - -

RJARRRPCGP said:

"A" is usually CPU instability, in my experience.
But, I only received that, when I OC'ed the CPU core too much or not enough Vcore. (Used to get this with my Athlon Thunderbird 900 @1050 Mhz, even with Vcore @ 1.85V and I couldn't get it stable at 1050 Mhz) (socket 462) (possibly was my poop PSU!) (that was in 2002, IIRC)

(Second CPU I received "A" with, was my Pentium E2180 (Core 2) (socket 775) at 2.8 Ghz (or 2.7) when running Linpack, before I bumped up the Vcore) (2008, IIRC)

I've received "1E" before from Windows 2000 back in 2007, most likely had to be a CPU overheat and that was with an overclock applied as well. (The second one I mentioned, was with an Athlon XP 3000+ (Barton) (socket 462) with Vcore at 1.80V, IIRC)

Thanks for providing your insights!

While I understand where you're coming from, I don't think there's any overclock done to this laptop as Lenovo doesn't provide us the option to do so. Nonetheless, I went ahead and set up my BIOS to default settings just in case but the problem still persists...

I thought it was high temps but monitoring it while using Ableton 10 or any other daw doesn't show high temps at all. Furthermore, when I play demanding game the laptop runs smoothly. This laptop has a particular issue with audio production in general for some reason.

One thing I noticed though is that the crash doesn't seem to happen when my laptop is unplugged. This might be placebo as I haven't extensively tested this theory.

When the computer boots can it boot with only disk 1 with C: ?



Run Memtest86 version 9.0 (or newer version if available) for four passes.
Repeat the test so that eight passes are performed.

MemTest86 - Official Site of the x86 and ARM Memory Testing Tool

Use a camera or smart phone camera to take pictures and post images into the thread.
In case there are any problems uploading images use share links (one drive, drop box, or google drive)

Memtest86 has a feature to produce a text report.
Please post this in addition to the images.



Open administrative command prompt and type or copy and paste:
chkdsk /r /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

C:\Windows\system32>chkdsk /r /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)

Type: Y
reboot

Use the information in this link to find the chkdsk report in the event viewer.
Copy and paste into notepad > save to desktop > post into the thread using a one drive, drop box, or google drive share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10

Code:

Event[3721]:
  Log Name: System
  Source: Ntfs
  Date: 2021-05-23T00:50:29.9740000Z
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-IMG8BIE
  Description: 
A corruption was discovered in the file system structure on volume C:.

The exact nature of the corruption is unknown.  The file system structures need to be scanned and fixed offline.

Code:

Event[1845]:
  Log Name: System
  Source: Microsoft-Windows-StartupRepair
  Date: 2021-05-21T17:25:37.3230000Z
  Event ID: 1121
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-IMG8BIE
  Description: 
The following file necessary for Windows startup was corrupt: d:\windows\system32\drivers\amdpsp.sys

Code:

Event[2758]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2021-05-22T20:07:45.5200000Z
  Event ID: 1
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: WHEA Error Event Logs
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: DESKTOP-IMG8BIE
  Description: 
A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event.

Code:

------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 367.3 GB
Total Space: 487.8 GB
File System: NTFS
      Model: SAMSUNG MZVLB512HBJQ-000L2

      Drive: D:
 Free Space: 905.0 GB
Total Space: 953.9 GB
File System: NTFS
      Model: CT1000MX500SSD1

Code:

The following file necessary for Windows startup was corrupt: d:\windows\system32\drivers\amdpsp.sys

Code:

amdpsp	AMD PSP Service	c:\windows\system32\drivers\amdpsp.sys	Kernel Driver	Yes	Boot	Running	OK	Ignore	No	Yes

zbook said:

When the computer boots can it boot with only disk 1 with C: ?



Run Memtest86 version 9.0 (or newer version if available) for four passes.
Repeat the test so that eight passes are performed.

MemTest86 - Official Site of the x86 and ARM Memory Testing Tool

Use a camera or smart phone camera to take pictures and post images into the thread.
In case there are any problems uploading images use share links (one drive, drop box, or google drive)

Memtest86 has a feature to produce a text report.
Please post this in addition to the images.



Open administrative command prompt and type or copy and paste:
chkdsk /r /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

C:\Windows\system32>chkdsk /r /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)

Type: Y
reboot

Use the information in this link to find the chkdsk report in the event viewer.
Copy and paste into notepad > save to desktop > post into the thread using a one drive, drop box, or google drive share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10

Code:

Event[3721]:
  Log Name: System
  Source: Ntfs
  Date: 2021-05-23T00:50:29.9740000Z
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-IMG8BIE
  Description: 
A corruption was discovered in the file system structure on volume C:.

The exact nature of the corruption is unknown.  The file system structures need to be scanned and fixed offline.

Code:

Event[1845]:
  Log Name: System
  Source: Microsoft-Windows-StartupRepair
  Date: 2021-05-21T17:25:37.3230000Z
  Event ID: 1121
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-IMG8BIE
  Description: 
The following file necessary for Windows startup was corrupt: d:\windows\system32\drivers\amdpsp.sys

Code:

Event[2758]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2021-05-22T20:07:45.5200000Z
  Event ID: 1
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: WHEA Error Event Logs
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: DESKTOP-IMG8BIE
  Description: 
A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event.

Code:

------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 367.3 GB
Total Space: 487.8 GB
File System: NTFS
      Model: SAMSUNG MZVLB512HBJQ-000L2

      Drive: D:
 Free Space: 905.0 GB
Total Space: 953.9 GB
File System: NTFS
      Model: CT1000MX500SSD1

Code:

The following file necessary for Windows startup was corrupt: d:\windows\system32\drivers\amdpsp.sys

Code:

amdpsp	AMD PSP Service	c:\windows\system32\drivers\amdpsp.sys	Kernel Driver	Yes	Boot	Running	OK	Ignore	No	Yes

Hello Zbook!


When the computer boots can it boot with only disk 1 with C: ? Nope, I'm able to select another boot options such as an USB drive (I previously performed a memtest86 and yesterday reinstalled windows using usb boot)

I've already ran memtest86 on two separate occasions (yesterday I performed the second attempt) and in both cases there were no errors with 4 passes being successful each time. Is it required to do it again?

I'm going to try out the chkdsk /r /v one to see what it finds and I'll post the results later as soon as it finishes.

- - - Updated - - -

Here's the chkdsk /r /v for both C and D drives, everything seems to be ok.

Chkdsk both drives were unremarkable > just cleaning.


What's the disk drive history?
Upgrades from 7 or 8, prior dual boot, upgrades while multiple drives attached, etc.


For all steps / tests it's best to have images with text reports posted into the thread.
Memtest can be run overnight.

Open disk management > by default some columns are compressed > widen each Status and Volume > make sure the contents within the parenthesis are in full view and that none of the characters are cutoff > view disk 0 > widen this row as needed so that all of the characters are in full view > post an image into the thread
https://www.tenforums.com/tutorials/...creenshot.html

Download and install Minitool Partition Wizard > click launch > post an image of the results into this thread
MiniTool Partition Wizard Free Edition - Free download and software reviews - CNET Download
MiniTool Portable Partition Magic Brings Easier Disk Management



Run:

Tuneup.bat - Click here to go to the BSOD batch repository to download and run this batch file.


DiskParInfo.bat - Click here to go to the BSOD batch repository to download and run this batch file.

Tuneup:

Code:

###########################################################
# The following commands will be run in sequence.         #
# The first 5 will take quite a while to run, be patient. #
###########################################################

sfc /scannow
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restorehealth
sfc /scannow

chkdsk /scan

wmic recoveros get autoreboot
wmic recoveros set autoreboot = false
wmic recoveros get autoreboot
wmic recoveros get DebugInfoType
wmic recoveros set DebugInfoType = 7
wmic recoveros get DebugInfoType

wmic pagefile list /format:list
wmic Computersystem where name="DESKTOP-4RJ9ASJ" get AutomaticManagedPagefile
wmic Computersystem where name="DESKTOP-4RJ9ASJ" set AutomaticManagedPagefile=True
wmic Computersystem where name="DESKTOP-4RJ9ASJ" get AutomaticManagedPagefile

bcdedit /enum {badmemory}


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 found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

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

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.985

[==========================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.844

Image Version: 10.0.19043.985

[==========================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 ...
  341504 file records processed.
File verification completed.
 Phase duration (File record verification): 2.11 seconds.
  3162 large file records processed.
 Phase duration (Orphan file record recovery): 0.00 milliseconds.
  0 bad file records processed.
 Phase duration (Bad file record checking): 1.22 milliseconds.

Stage 2: Examining file name linkage ...
  8092 reparse records processed.
  471030 index entries processed.
Index verification completed.
 Phase duration (Index verification): 7.71 seconds.
  0 unindexed files scanned.
 Phase duration (Orphan reconnection): 744.05 milliseconds.
  0 unindexed files recovered to lost and found.
 Phase duration (Orphan recovery to lost and found): 1.55 milliseconds.
  8092 reparse records processed.
 Phase duration (Reparse point and Object ID verification): 16.54 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 48.29 milliseconds.
  64764 data files processed.
 Phase duration (Data attribute verification): 0.66 milliseconds.
CHKDSK is verifying Usn Journal...
  39902968 USN bytes processed.
Usn Journal verification completed.
 Phase duration (USN journal verification): 142.26 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

 499476450 KB total disk space.
  63009656 KB in 273327 files.
    161556 KB in 64765 indexes.
         0 KB in bad sectors.
    465098 KB in use by the system.
     65536 KB occupied by the log file.
 435840140 KB available on disk.

      4096 bytes in each allocation unit.
 124869112 total allocation units on disk.
 108960035 allocation units available on disk.
Total duration: 10.78 seconds (10786 ms).

C:\Windows\system32>wmic recoveros get autoreboot
AutoReboot
TRUE


C:\Windows\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\DESKTOP-4RJ9ASJ\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\Windows|\\Device\\Harddisk1\\Partition3"'
Property(s) update successful.

C:\Windows\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\Windows\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\Windows\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\DESKTOP-4RJ9ASJ\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\Windows|\\Device\\Harddisk1\\Partition3"'
Property(s) update successful.

C:\Windows\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


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


AllocatedBaseSize=2944
CurrentUsage=0
Description=C:\pagefile.sys
InstallDate=20210526183318.249603-300
FFF

DiskParInfo:

Code:

 Disk 0 : SSD. It has 2 partition(s). Model: CT1000MX500SSD1    
    Disk 1 : SSD. It has 4 partition(s). Model: SAMSUNG MZVLB512HBJQ-000L2   

    The script has found the above 2 storage device(s) in total.
=======================================================================

Microsoft DiskPart version 10.0.19041.964

Copyright (C) Microsoft Corporation.
On computer: DESKTOP-4RJ9ASJ

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          931 GB  1024 KB        *
  Disk 1    Online          476 GB  1024 KB        *

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     D   Excelsior    NTFS   Partition    931 GB  Healthy            
  Volume 1     C                NTFS   Partition    476 GB  Healthy    Boot    
  Volume 2                      FAT32  Partition    100 MB  Healthy    System  
  Volume 3                      NTFS   Partition    498 MB  Healthy    Hidden  

Disk 0 is now the selected disk.

CT1000MX500SSD1
Disk ID: {173F3410-00C0-4F8D-BBB6-6307F43F6F68}
Type   : SATA
Status : Online
Path   : 0
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(0802)#PCI(0000)#ATA(C00T00L00)
Current Read-only State : No
Read-only  : No
Boot Disk  : No
Pagefile Disk  : No
Hibernation File Disk  : No
Crashdump Disk  : No
Clustered Disk  : No

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     D   Excelsior    NTFS   Partition    931 GB  Healthy            

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Reserved            15 MB    17 KB
  Partition 2    Primary            931 GB    16 MB

Partition 1 is now the selected partition.

Partition 1
Type    : e3c9e316-0b5c-4db8-817d-f92df00215ae
Hidden  : Yes
Required: No
Attrib  : 0000000000000000
Offset in Bytes: 17408

There is no volume associated with this partition.

Partition 2 is now the selected partition.

Partition 2
Type    : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
Hidden  : No
Required: No
Attrib  : 0000000000000000
Offset in Bytes: 16777216

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 0     D   Excelsior    NTFS   Partition    931 GB  Healthy            

Disk 1 is now the selected disk.

SAMSUNG MZVLB512HBJQ-000L2
Disk ID: {E50E508F-F2EB-4CB6-AC72-AAA6CBC840D3}
Type   : NVMe
Status : Online
Path   : 0
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(0102)#PCI(0000)#NVME(P00T00L00)
Current Read-only State : No
Read-only  : No
Boot Disk  : Yes
Pagefile Disk  : Yes
Hibernation File Disk  : No
Crashdump Disk  : Yes
Clustered Disk  : No

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 1     C                NTFS   Partition    476 GB  Healthy    Boot    
  Volume 2                      FAT32  Partition    100 MB  Healthy    System  
  Volume 3                      NTFS   Partition    498 MB  Healthy    Hidden  

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    System             100 MB  1024 KB
  Partition 2    Reserved            16 MB   101 MB
  Partition 3    Primary            476 GB   117 MB
  Partition 4    Recovery           498 MB   476 GB

Partition 1 is now the selected partition.

Partition 1
Type    : c12a7328-f81f-11d2-ba4b-00a0c93ec93b
Hidden  : Yes
Required: No
Attrib  : 0X8000000000000000
Offset in Bytes: 1048576

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 2                      FAT32  Partition    100 MB  Healthy    System  

Partition 2 is now the selected partition.

Partition 2
Type    : e3c9e316-0b5c-4db8-817d-f92df00215ae
Hidden  : Yes
Required: No
Attrib  : 0X8000000000000000
Offset in Bytes: 105906176

There is no volume associated with this partition.

Partition 3 is now the selected partition.

Partition 3
Type    : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
Hidden  : No
Required: No
Attrib  : 0000000000000000
Offset in Bytes: 122683392

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 1     C                NTFS   Partition    476 GB  Healthy    Boot    

Partition 4 is now the selected partition.

Partition 4
Type    : de94bba4-06d1-4d40-a16a-bfd50179d6ac
Hidden  : Yes
Required: Yes
Attrib  : 0X8000000000000001
Offset in Bytes: 511586598912

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 3                      NTFS   Partition    498 MB  Healthy    Hidden  

===============================================================================

Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Enabled
    Windows RE location:       \\?\GLOBALROOT\device\harddisk1\partition3\Recovery\WindowsRE
    Boot Configuration Data (BCD) identifier: d15347d1-be93-11eb-8c29-983b7b0dcf2c
    Recovery image location:   
    Recovery image index:      0
    Custom image location:     
    Custom image index:        0

REAGENTC.EXE: Operation Successful.
    
===============================================================================

Firmware Boot Manager
---------------------
identifier              {fwbootmgr}
displayorder            {bootmgr}
                        {2fe299d2-7395-11eb-a239-806e6f6e6963}
                        {2fe299d3-7395-11eb-a239-806e6f6e6963}
                        {2fe299d4-7395-11eb-a239-806e6f6e6963}
timeout                 0

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume1
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {d15347cf-be93-11eb-8c29-983b7b0dcf2c}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 30

Firmware Application (101fffff)
-------------------------------
identifier              {0bd66102-7352-11eb-943f-5405db6e2bc0}
description             EFI PXE 0 for IPv6 (54-05-DB-6E-2B-C0) 

Firmware Application (101fffff)
-------------------------------
identifier              {2fe299d2-7395-11eb-a239-806e6f6e6963}
description             EFI USB Device

Firmware Application (101fffff)
-------------------------------
identifier              {2fe299d3-7395-11eb-a239-806e6f6e6963}
description             EFI DVD/CDROM

Firmware Application (101fffff)
-------------------------------
identifier              {2fe299d4-7395-11eb-a239-806e6f6e6963}
description             EFI Network

Firmware Application (101fffff)
-------------------------------
identifier              {779819c4-be9a-11eb-a11b-806e6f6e6963}
device                  unknown
description             EFI USB Device (SanDisk Cruzer Blade)

Firmware Application (101fffff)
-------------------------------
identifier              {779819c5-be9a-11eb-a11b-806e6f6e6963}
device                  unknown
description             EFI USB Device 1 (SanDisk Cruzer Blade)

Firmware Application (101fffff)
-------------------------------
identifier              {f6ee7b7c-2928-11eb-ac23-fd33b5b2dc45}
device                  unknown
description             EFI PXE 0 for IPv4 (54-05-DB-6E-2B-C0) 

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.efi
description             Windows 10
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {d15347d1-be93-11eb-8c29-983b7b0dcf2c}
displaymessageoverride  Recovery
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \Windows
resumeobject            {d15347cf-be93-11eb-8c29-983b7b0dcf2c}
nx                      OptIn
bootmenupolicy          Standard

Windows Boot Loader
-------------------
identifier              {d15347d1-be93-11eb-8c29-983b7b0dcf2c}
device                  ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{d15347d2-be93-11eb-8c29-983b7b0dcf2c}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  en-us
inherit                 {bootloadersettings}
displaymessage          Recovery
osdevice                ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{d15347d2-be93-11eb-8c29-983b7b0dcf2c}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {f6ee7b80-2928-11eb-ac23-fd33b5b2dc45}
device                  ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{f6ee7b81-2928-11eb-ac23-fd33b5b2dc45}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  en-us
inherit                 {bootloadersettings}
displaymessage          Recovery
osdevice                ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{f6ee7b81-2928-11eb-ac23-fd33b5b2dc45}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
detecthal               Yes
winpe                   Yes

Resume from Hibernate
---------------------
identifier              {d15347cf-be93-11eb-8c29-983b7b0dcf2c}
device                  partition=C:
path                    \Windows\system32\winresume.efi
description             Windows Resume Application
locale                  en-US
inherit                 {resumeloadersettings}
recoverysequence        {d15347d1-be93-11eb-8c29-983b7b0dcf2c}
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
filedevice              partition=C:
filepath                \hiberfil.sys
bootmenupolicy          Standard
debugoptionenabled      No

Windows Memory Tester
---------------------
identifier              {memdiag}
device                  partition=\Device\HarddiskVolume1
path                    \EFI\Microsoft\Boot\memtest.efi
description             Windows Memory Diagnostic
locale                  en-US
inherit                 {globalsettings}
badmemoryaccess         Yes

EMS Settings
------------
identifier              {emssettings}
bootems                 No

Debugger Settings
-----------------
identifier              {dbgsettings}
debugtype               Local

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

Global Settings
---------------
identifier              {globalsettings}
inherit                 {dbgsettings}
                        {emssettings}
                        {badmemory}

Boot Loader Settings
--------------------
identifier              {bootloadersettings}
inherit                 {globalsettings}
                        {hypervisorsettings}

Hypervisor Settings
-------------------
identifier              {hypervisorsettings}
hypervisordebugtype     Serial
hypervisordebugport     1
hypervisorbaudrate      115200

Resume Loader Settings
----------------------
identifier              {resumeloadersettings}
inherit                 {globalsettings}

Device options
--------------
identifier              {d15347d2-be93-11eb-8c29-983b7b0dcf2c}
description             Windows Recovery
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\WindowsRE\boot.sdi

Device options
--------------
identifier              {f6ee7b81-2928-11eb-ac23-fd33b5b2dc45}
description             Windows Recovery
ramdisksdidevice        partition=\Device\HarddiskVolume4
ramdisksdipath          \Recovery\WindowsRE\boot.sdi

- - - Updated - - -

zbook said:

Chkdsk both drives were unremarkable > just cleaning.


What's the disk drive history?
Upgrades from 7 or 8, prior dual boot, upgrades while multiple drives attached, etc.


For all steps / tests it's best to have images with text reports posted into the thread.
Memtest can be run overnight.

Open disk management > by default some columns are compressed > widen each Status and Volume > make sure the contents within the parenthesis are in full view and that none of the characters are cutoff > view disk 0 > widen this row as needed so that all of the characters are in full view > post an image into the thread
https://www.tenforums.com/tutorials/...creenshot.html

Download and install Minitool Partition Wizard > click launch > post an image of the results into this thread
MiniTool Partition Wizard Free Edition - Free download and software reviews - CNET Download
MiniTool Portable Partition Magic Brings Easier Disk Management



Run:

Tuneup.bat - Click here to go to the BSOD batch repository to download and run this batch file.


DiskParInfo.bat - Click here to go to the BSOD batch repository to download and run this batch file.

What's the disk drive history?
Upgrades from 7 or 8, prior dual boot, upgrades while multiple drives attached, etc.

No upgrades at all from 7 or 8. Disk C came with laptop and it is fairly new (this laptop got used by someone previously for a very short time)- Disk D is totally new and recently installed by the person who sold me this laptop.

When I bought it I performed a reset via windows, then the BSOD problems started to arise when using audio production software so I resetted it again but the problems are still showing up.

First scannow:

Code:

Windows Resource Protection found corrupt files and successfully repaired them.

Second scannow:

Code:

Windows Resource Protection did not find any integrity violations.

Please run tuneup.bat again and then run:

Tuneup_plus_log.bat ─ Click here to go to the BSOD batch repository to download and run this batch file.