Question BSOD, Randomly and Infrequently, include Mini Dump

[TheBlackStalker]

it happens minutes after turning on the pc or after hours of use, once or twice a week and sometimes not at all. I have the pc turned on every day in video games with the gpu at 99% and with good temperatures, I have a 1000w 80 plus gold power supply, a 1080 ti and a ryzen 3700x with a x370 mother with updated bios.


Path validation summary *
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22000 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff80044c00000 PsLoadedModuleList = 0xfffff80045829b90
Debug session time: Thu Mar 31 11:21:41.986 2022 (UTC - 3:00)
System Uptime: 0 days 0:12:50.618
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800450164c0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffc50a1c467c60=000000000000000a
10: kd> !analyze -v
***

• *
• Bugcheck Analysis *
• *

***

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000003eb8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80044f146b8, address which referenced memory

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3186

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 25650

Key : Analysis.Init.CPU.mSec
Value: 562

Key : Analysis.Init.Elapsed.mSec
Value: 112371

Key : Analysis.Memory.CommitPeak.Mb
Value: 151

Key : WER.OS.Branch
Value: co_release

Key : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z

Key : WER.OS.Version
Value: 10.0.22000.1


FILE_IN_CAB: 033122-10921-01.dmp

BUGCHECK_CODE: a

BUGCHECK_P1: 3eb8

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80044f146b8

READ_ADDRESS: fffff80045905450: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
0000000000003eb8

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: UninstallMonitor.exe

DEVICE_OBJECT: ffff930500000000

TRAP_FRAME: ffffc50a1c467da0 -- (.trap 0xffffc50a1c467da0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffc788bcddc2c8
rdx=0000000000000005 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80044f146b8 rsp=ffffc50a1c467f30 rbp=ffffc50a1c468030
r8=fffffb0000000000 r9=8000000000000000 r10=0000000000000008
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiFinishHardFault+0x5a8:
fffff80044f146b8 483987b83e0000 cmp qword ptr [rdi+3EB8h],rax ds:0000000000003eb8=????????????????
Resetting default scope

STACK_TEXT:
ffffc50a1c467c58 fffff800450290a9 : 000000000000000a 0000000000003eb8 0000000000000002 0000000000000000 : nt!KeBugCheckEx
ffffc50a1c467c60 fffff80045025200 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiBugCheckDispatch+0x69
ffffc50a1c467da0 fffff80044f146b8 : 0000000000000002 ffff9305a27ff2b0 ffff930599f939d0 ffffc788bcddc040 : nt!KiPageFault+0x440
ffffc50a1c467f30 fffff80044e757ea : 0000000000000000 0000000000000000 ffff930599f939d0 fffff80000000000 : nt!MiFinishHardFault+0x5a8
ffffc50a1c4680d0 fffff80044e756fb : ffffc50a1c4682a8 0000000000000001 ffff9305a7add078 0000000000000000 : nt!MiPfCompleteInPageSupport+0x9e
ffffc50a1c4681b0 fffff80044f1e640 : 00000000002b8000 0000000000000000 0000000000000001 ffff930597b41738 : nt!MiPfCompletePrefetchIos+0x5b
ffffc50a1c4681e0 fffff80044e8e2e5 : 00000000002b8000 0000000000040000 ffff8082656c0000 ffff9305a7ad88a0 : nt!MmWaitForCacheManagerPrefetch+0x38
ffffc50a1c468220 fffff80045302472 : 0000000000000000 0000000000000000 0000000000000001 00000000002b76b8 : nt!CcFetchDataForRead+0x135
ffffc50a1c468280 fffff80044e8f7bf : 0000000000040000 0000000000000000 0000000000000000 ffff93059d202001 : nt!CcMapAndCopyFromCache+0xf2
ffffc50a1c468330 fffff8004763ba60 : ffffc78800000000 ffff9305a7ad8a18 ffffc788002b76b8 ffffc788a6faaa01 : nt!CcCopyReadEx+0x1bf
ffffc50a1c468410 fffff80047636774 : ffffc788a6faa990 ffffc50a1c468650 0000000000000003 0000000000000000 : Ntfs!NtfsCachedRead+0x17c
ffffc50a1c468480 fffff80047638067 : ffff930598aac798 ffff93059d202050 ffff930500000001 00000000002b76b8 : Ntfs!NtfsCommonRead+0xe94
ffffc50a1c468620 fffff80044e82555 : ffff9305995b8aa0 ffff93059d202050 0000000000000000 ffff93059d202480 : Ntfs!NtfsFsdRead+0x227
ffffc50a1c468710 fffff80046997c75 : ffffc50a1c469000 ffffc50a1c463000 0000000000000000 ffffc50a1c4687f0 : nt!IofCallDriver+0x55
ffffc50a1c468750 fffff80046995913 : ffffc50a1c4687e0 0000000000000000 0000000000000000 0000000000000000 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2b5
ffffc50a1c4687c0 fffff80044e82555 : ffff93059d202050 0000000000000000 000000007fbc0008 0000000000000000 : FLTMGR!FltpDispatch+0xa3
ffffc50a1c468820 fffff800452f96f2 : ffffc50a1c4688c1 ffff9305a8a935a0 ffffc50a1c4688c1 0000000000000001 : nt!IofCallDriver+0x55
ffffc50a1c468860 fffff80044eb98b4 : ffff930500000000 0000000000000000 0000000000000000 ffff93059d2024c8 : nt!IopSynchronousServiceTail+0x1d2
ffffc50a1c468910 fffff8004530e339 : ffff9305a8a935a0 0000000000000000 0000000000000000 0000000000000000 : nt!IopReadFile+0x4e4
ffffc50a1c4689f0 fffff80045028a78 : ffff9305a2ceb080 ffffc50a1c468b60 000000000756f0e8 ffffc50a1c468a88 : nt!NtReadFile+0xc9
ffffc50a1c468a70 0000000077df1cf3 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
000000000756f0c8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x77df1cf3


SYMBOL_NAME: nt!MiFinishHardFault+5a8

MODULE_NAME: nt

IMAGE_VERSION: 10.0.22000.556

STACK_COMMAND: .cxr; .ecxr ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 5a8

FAILURE_BUCKET_ID: AV_nt!MiFinishHardFault

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d767d215-4200-2446-1455-562c97a5882c}

Followup: MachineOwner
---------

I hope you can help me, thank you very much!

 

[Colif]

I have a 1000w 80 plus gold power supply, a 1080 ti and a ryzen 3700x with a x370 mother with updated bios.

what storage do you have?

error occurred after a hard fault. Hard faults are badly named operations where the CPU can't find the info it needs in its on chip caches or ram, and has to go to page file. Its not an error, hard faults and page faults are normal.
it appears the PC didn't like the information it was provided from page file, you might want to run chkdsk c: /f on the C drive and see if that helps.

that isn't a minidump, its the results of one. Dumps can normally show drivers running as well.

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

 

[TheBlackStalker]

it happens minutes after turning on the pc or after hours of use, once or twice a week and sometimes not at all. I have the pc turned on every day in video games with the gpu at 99% and with good temperatures, I have a 1000w 80 plus gold power supply, a 1080 ti and a ryzen 3700x with a x370 mother with updated bios.


Path validation summary *
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22000 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff80044c00000 PsLoadedModuleList = 0xfffff80045829b90
Debug session time: Thu Mar 31 11:21:41.986 2022 (UTC - 3:00)
System Uptime: 0 days 0:12:50.618
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800450164c0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffc50a1c467c60=000000000000000a
10: kd> !analyze -v
***

• *
• Bugcheck Analysis *
• *

***

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000003eb8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80044f146b8, address which referenced memory

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3186

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 25650

Key : Analysis.Init.CPU.mSec
Value: 562

Key : Analysis.Init.Elapsed.mSec
Value: 112371

Key : Analysis.Memory.CommitPeak.Mb
Value: 151

Key : WER.OS.Branch
Value: co_release

Key : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z

Key : WER.OS.Version
Value: 10.0.22000.1


FILE_IN_CAB: 033122-10921-01.dmp

BUGCHECK_CODE: a

BUGCHECK_P1: 3eb8

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80044f146b8

READ_ADDRESS: fffff80045905450: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
0000000000003eb8

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: UninstallMonitor.exe

DEVICE_OBJECT: ffff930500000000

TRAP_FRAME: ffffc50a1c467da0 -- (.trap 0xffffc50a1c467da0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffc788bcddc2c8
rdx=0000000000000005 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80044f146b8 rsp=ffffc50a1c467f30 rbp=ffffc50a1c468030
r8=fffffb0000000000 r9=8000000000000000 r10=0000000000000008
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiFinishHardFault+0x5a8:
fffff80044f146b8 483987b83e0000 cmp qword ptr [rdi+3EB8h],rax ds:0000000000003eb8=????????????????
Resetting default scope

STACK_TEXT:
ffffc50a1c467c58 fffff800450290a9 : 000000000000000a 0000000000003eb8 0000000000000002 0000000000000000 : nt!KeBugCheckEx
ffffc50a1c467c60 fffff80045025200 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiBugCheckDispatch+0x69
ffffc50a1c467da0 fffff80044f146b8 : 0000000000000002 ffff9305a27ff2b0 ffff930599f939d0 ffffc788bcddc040 : nt!KiPageFault+0x440
ffffc50a1c467f30 fffff80044e757ea : 0000000000000000 0000000000000000 ffff930599f939d0 fffff80000000000 : nt!MiFinishHardFault+0x5a8
ffffc50a1c4680d0 fffff80044e756fb : ffffc50a1c4682a8 0000000000000001 ffff9305a7add078 0000000000000000 : nt!MiPfCompleteInPageSupport+0x9e
ffffc50a1c4681b0 fffff80044f1e640 : 00000000002b8000 0000000000000000 0000000000000001 ffff930597b41738 : nt!MiPfCompletePrefetchIos+0x5b
ffffc50a1c4681e0 fffff80044e8e2e5 : 00000000002b8000 0000000000040000 ffff8082656c0000 ffff9305a7ad88a0 : nt!MmWaitForCacheManagerPrefetch+0x38
ffffc50a1c468220 fffff80045302472 : 0000000000000000 0000000000000000 0000000000000001 00000000002b76b8 : nt!CcFetchDataForRead+0x135
ffffc50a1c468280 fffff80044e8f7bf : 0000000000040000 0000000000000000 0000000000000000 ffff93059d202001 : nt!CcMapAndCopyFromCache+0xf2
ffffc50a1c468330 fffff8004763ba60 : ffffc78800000000 ffff9305a7ad8a18 ffffc788002b76b8 ffffc788a6faaa01 : nt!CcCopyReadEx+0x1bf
ffffc50a1c468410 fffff80047636774 : ffffc788a6faa990 ffffc50a1c468650 0000000000000003 0000000000000000 : Ntfs!NtfsCachedRead+0x17c
ffffc50a1c468480 fffff80047638067 : ffff930598aac798 ffff93059d202050 ffff930500000001 00000000002b76b8 : Ntfs!NtfsCommonRead+0xe94
ffffc50a1c468620 fffff80044e82555 : ffff9305995b8aa0 ffff93059d202050 0000000000000000 ffff93059d202480 : Ntfs!NtfsFsdRead+0x227
ffffc50a1c468710 fffff80046997c75 : ffffc50a1c469000 ffffc50a1c463000 0000000000000000 ffffc50a1c4687f0 : nt!IofCallDriver+0x55
ffffc50a1c468750 fffff80046995913 : ffffc50a1c4687e0 0000000000000000 0000000000000000 0000000000000000 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2b5
ffffc50a1c4687c0 fffff80044e82555 : ffff93059d202050 0000000000000000 000000007fbc0008 0000000000000000 : FLTMGR!FltpDispatch+0xa3
ffffc50a1c468820 fffff800452f96f2 : ffffc50a1c4688c1 ffff9305a8a935a0 ffffc50a1c4688c1 0000000000000001 : nt!IofCallDriver+0x55
ffffc50a1c468860 fffff80044eb98b4 : ffff930500000000 0000000000000000 0000000000000000 ffff93059d2024c8 : nt!IopSynchronousServiceTail+0x1d2
ffffc50a1c468910 fffff8004530e339 : ffff9305a8a935a0 0000000000000000 0000000000000000 0000000000000000 : nt!IopReadFile+0x4e4
ffffc50a1c4689f0 fffff80045028a78 : ffff9305a2ceb080 ffffc50a1c468b60 000000000756f0e8 ffffc50a1c468a88 : nt!NtReadFile+0xc9
ffffc50a1c468a70 0000000077df1cf3 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
000000000756f0c8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x77df1cf3


SYMBOL_NAME: nt!MiFinishHardFault+5a8

MODULE_NAME: nt

IMAGE_VERSION: 10.0.22000.556

STACK_COMMAND: .cxr; .ecxr ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 5a8

FAILURE_BUCKET_ID: AV_nt!MiFinishHardFault

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d767d215-4200-2446-1455-562c97a5882c}

Followup: MachineOwner
---------

I hope you can help me, thank you very much!

what storage do you have?

error occurred after a hard fault. Hard faults are badly named operations where the CPU can't find the info it needs in its on chip caches or ram, and has to go to page file. Its not an error, hard faults and page faults are normal.
it appears the PC didn't like the information it was provided from page file, you might want to run chkdsk c: /f on the C drive and see if that helps.

that isn't a minidump, its the results of one. Dumps can normally show drivers running as well.

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

I use an SSD Samsung 960 EVO NVMe M.2 250GB for the operating system and I also have 3 other hdds and an additional SSD Sata and i'm sure they work fine.

31/03/22
https://www.mediafire.com/file/wzu7mopwbubwxfz/033122-10921-01.zip/file

Here I also uploaded another dump that I have, I think it's from another previous BSOD
16/02/22
https://www.mediafire.com/file/79a1x2lxz3cieag/021622-11203-01.zip/file

Thanks for your answer

 

[Colif]

try downloading Samsung Magician and run scans on the NVMe - https://semiconductor.samsung.com/consumer-storage/support/tools/
the drivers below might help as well as they have their own nvme drivers.

I will ask a friend to convert dumps

 

[TheBlackStalker]

try downloading Samsung Magician and run scans on the NVMe - https://semiconductor.samsung.com/consumer-storage/support/tools/
the drivers below might help as well as they have their own nvme drivers.

I will ask a friend to convert dumps

Thanks I will install the nvme drivers and if I have any new BSOD I will let you know here, I will also be aware of this thread in case you have more information for me, once again thanks for your help

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/tfh3m6oc/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

Spoiler: Dump File Results

File information:	033122-10921-01.dmp (Mar 31 2022 - 10:21:41)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:	memory_corruption (Process running at time of crash: UninstallMonitor.exe)
Uptime:	0 Day(s), 0 Hour(s), 12 Min(s), and 50 Sec(s)

File information:	021622-11203-01.dmp (Feb 16 2022 - 21:19:13)
Bugcheck:	PFN_LIST_CORRUPT (4E)
Probably caused by:	memory_corruption (Process running at time of crash: nvcontainer.exe)
Uptime:	0 Day(s), 3 Hour(s), 55 Min(s), and 00 Sec(s)

Comment: The overclocking driver "RTCore64.sys" was found on your system. (MSI Afterburner)

Possible MB support page: https://rog.asus.com/motherboards/rog-crosshair/rog-crosshair-vi-hero-model/helpdesk
You are using the latest stable BIOS available. I usually recommend avoiding BETAs.

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

kind of strange victim of 1st crash, IO bit uninstaller.

lots of guessing..

try running this and update LAN drivers - https://www.intel.com.au/content/www/au/en/support/intel-driver-support-assistant.html
there is a newer version of HWINFO but its not cause, I just noticed

 

[johnbl]

I would guess you have a old filter driver installed that has a bug, it made a call, that went to the nt file system, the system cache manager ended up using a bogus memory address and called a bugcheck.
(remove any overclock driver, since they can mess up anything)
first I would look at what filter drivers I had installed. Look for virus scanners and some malware. you can run cmd.exe as an admin then run: fltmc.exe

(this is what my machine shows, look for items not on this list)
C:\WINDOWS\system32>fltmc.exe

Filter Name Num Instances Altitude Frame
------------------------------ ------------- ------------ -----
bindflt 1 409800 0
WdFilter 6 328010 0
storqosflt 0 244000 0
wcifs 1 189900 0
CldFlt 0 180451 0
FileCrypt 0 141100 0
luafv 1 135000 0
npsvctrig 1 46000 0
Wof 4 40700 0
FileInfo 6 40500 0
----------------

the second thing I would look for would be to look at the status of the drive by running
crystaldiskinfo.exe (google for download)
look at the smart info for the health. If the drive is healthy then look at the firmware version and google to see if there is a update to the drive firmware.

most likely the error is going to be caused by a bad filter driver, then a old storage driver, then a firmware bug. (assuming your drive is healthy and has plenty of free space)

you can use fltmc.exe to uninstall filter drivers
fltmc.exe /? (shows help)
fltmc.exe /detach filterdrivername
(to remove the driver)

you can also use the uninstaller (if it works, often vendors just leave it installed)
-----
there are more rare cases that would cause this but they involve certain cpu bugs and are fixed when you update bios versions.

 

[TheBlackStalker]

I would guess you have a old filter driver installed that has a bug, it made a call, that went to the nt file system, the system cache manager ended up using a bogus memory address and called a bugcheck.
(remove any overclock driver, since they can mess up anything)
first I would look at what filter drivers I had installed. Look for virus scanners and some malware. you can run cmd.exe as an admin then run: fltmc.exe

(this is what my machine shows, look for items not on this list)
C:\WINDOWS\system32>fltmc.exe

Filter Name Num Instances Altitude Frame
------------------------------ ------------- ------------ -----
bindflt 1 409800 0
WdFilter 6 328010 0
storqosflt 0 244000 0
wcifs 1 189900 0
CldFlt 0 180451 0
FileCrypt 0 141100 0
luafv 1 135000 0
npsvctrig 1 46000 0
Wof 4 40700 0
FileInfo 6 40500 0
----------------

the second thing I would look for would be to look at the status of the drive by running
crystaldiskinfo.exe (google for download)
look at the smart info for the health. If the drive is healthy then look at the firmware version and google to see if there is a update to the drive firmware.

most likely the error is going to be caused by a bad filter driver, then a old storage driver, then a firmware bug. (assuming your drive is healthy and has plenty of free space)

you can use fltmc.exe to uninstall filter drivers
fltmc.exe /? (shows help)
fltmc.exe /detach filterdrivername
(to remove the driver)

you can also use the uninstaller (if it works, often vendors just leave it installed)
-----
there are more rare cases that would cause this but they involve certain cpu bugs and are fixed when you update bios versions.

https://prnt.sc/LlmWoH4pCXVn Here's a screenshot, I see 2 items that are not in that list, do you think they could be the cause?
https://prnt.sc/Hxgx4czxJ4JN By the way i also have a screenshot of the crystaldiskinfo, it seems that my firmware version is the most recent for my device

 

[TheBlackStalker]

kind of strange victim of 1st crash, IO bit uninstaller.

lots of guessing..

try running this and update LAN drivers - https://www.intel.com.au/content/www/au/en/support/intel-driver-support-assistant.html
there is a newer version of HWINFO but its not cause, I just noticed

https://prnt.sc/ODCAXA49oXUT I did what you told me, install "intel driver support assistant" and look for any driver update, but there is none, I will delete the iobit software anyway, thanks

 

[johnbl]

https://prnt.sc/LlmWoH4pCXVn Here's a screenshot, I see 2 items that are not in that list, do you think they could be the cause?
https://prnt.sc/Hxgx4czxJ4JN By the way i also have a screenshot of the crystaldiskinfo, it seems that my firmware version is the most recent for my device

it could be the iobit malware scanner but it could also be the xbox game driver
I have seen cases where the game filter driver really messed up when a very old xbox 360 device was plugged into it. (driver gets hidden and you have to show hidden devices and remove the software from each port it was plugged into to resolve the problem)

I think I had disable the xbox driver on my system for some reason.
(making connections to my xbox that I did not want)

 

[johnbl]

edit: posted to wrong thread.