[SOLVED] BSOD problem

[Alibi]

Hello everyone. I have been having this BSOD problem for a while now and so I thought that you guys could help. I've also just reset my PC thinking that it would help with my problem but it didn't. My minidump will be linked below. Any help given will be greatly appreciated.

Thanks In Advance
Alibi

Minidump: https://we.tl/t-S8vQWmsaw6

 

[Lutfij]

Do you have Norton AnitVirus installed on your platform? If so, uninstall that and see if the issue crops up. I'd advise you to also make sure your motherboard/laptop BIOS is on the latest version. As for your OS, you should ideally be on 21H1, you're currently on 20H1.

Used WinDbg on Windows 10, I could be wrong but I stand to be corrected.

 

[Alibi]

I tried uninstalling Norton and upgrading my windows to 21H1. I also looked into the G11CD BIOS and my current version was the 0807 version which to my knowledge was the latest one for the G11CD-K which I currently use. This did although sadly not work and I got another BSOD. I have linked the new dump file below if needed.

Minidump: https://we.tl/t-ROB4zVkpy9

 

[axe0axe0]

Having issues with decompressing a buffer because nothing valid was returned to be decompressed. I suggest checking your drive for problems.
Norton probably just was requesting data that was compressed.

3: kd> knL
 # Child-SP          RetAddr           Call Site
00 ffffca83`e6b65e78 fffff802`6fd94b6e nt!KeBugCheckEx
01 ffffca83`e6b65e80 fffff802`6fc10a83 nt!SMKM_STORE<SM_TRAITS>::SmStUnhandledExceptionFilter+0x7e
02 ffffca83`e6b65ed0 fffff802`6fbccdaf nt!`SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue'::`1'::filt$0+0x22
03 ffffca83`e6b65f00 fffff802`6fbfffef nt!_C_specific_handler+0x9f
04 ffffca83`e6b65f70 fffff802`6fae6de7 nt!RtlpExecuteHandlerForException+0xf
05 ffffca83`e6b65fa0 fffff802`6fae59d6 nt!RtlDispatchException+0x297
06 ffffca83`e6b666c0 fffff802`6fc091ac nt!KiDispatchException+0x186
07 ffffca83`e6b66d80 fffff802`6fc05343 nt!KiExceptionDispatch+0x12c
08 ffffca83`e6b66f60 fffff802`6fb31620 nt!KiPageFault+0x443
09 ffffca83`e6b670f8 fffff802`6fb06490 nt!RtlDecompressBufferXpressLz+0x50
0a ffffca83`e6b67110 fffff802`6fb061d8 nt!RtlDecompressBufferEx+0x60
0b ffffca83`e6b67160 fffff802`6fb06065 nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x150
0c ffffca83`e6b67220 fffff802`6fb0589c nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xa5
0d ffffca83`e6b67270 fffff802`6fb056cc nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x180
0e ffffca83`e6b67310 fffff802`6fb05519 nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xc8
0f ffffca83`e6b673c0 fffff802`6fb053d1 nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85
10 ffffca83`e6b67440 fffff802`6faf8468 nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
11 ffffca83`e6b67470 fffff802`6fb02f2f nt!KeExpandKernelStackAndCalloutInternal+0x78
12 ffffca83`e6b674e0 fffff802`6fad0e04 nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xc7
13 ffffca83`e6b675b0 fffff802`6fad0838 nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1ac
14 ffffca83`e6b67600 fffff802`6fb039b7 nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xc0
15 ffffca83`e6b67690 fffff802`6fb5ae0b nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x167
16 ffffca83`e6b67700 fffff802`6fa5e0a0 nt!SmPageRead+0x33
17 ffffca83`e6b67750 fffff802`6fa5bb4d nt!MiIssueHardFaultIo+0x10c
18 ffffca83`e6b677a0 fffff802`6fa9f568 nt!MiIssueHardFault+0x29d
19 ffffca83`e6b67860 fffff802`6fc0525e nt!MmAccessFault+0x468
1a ffffca83`e6b67a00 00007ffd`199fc33f nt!KiPageFault+0x35e
1b 0000000b`5fdff100 00000000`00000000 0x00007ffd`199fc33f

3: kd> .exr 0xffffca83e6b66eb8
ExceptionAddress: fffff8026fb31620 (nt!RtlDecompressBufferXpressLz+0x0000000000000050)
   ExceptionCode: c0000006 (In-page I/O error)
  ExceptionFlags: 00000000
NumberParameters: 3
   Parameter[0]: 0000000000000000
   Parameter[1]: 000002516e4023e0
   Parameter[2]: 00000000c000000e
Inpage operation failed at 000002516e4023e0, due to I/O error 00000000c000000e

3: kd> !stack -p
Call Stack : 28 frames
## Stack-Pointer    Return-Address   Call-Site       
00 ffffca83e6b65e78 fffff8026fd94b6e nt!KeBugCheckEx+0 
    Parameter[0] = 0000000000000154
    Parameter[1] = ffff8f02c12b2000
    Parameter[2] = ffffca83e6b65f30
    Parameter[3] = 0000000000000002
01 ffffca83e6b65e80 fffff8026fc10a83 nt!SMKM_STORE<SM_TRAITS>::SmStUnhandledExceptionFilter+7e 
    Parameter[0] = ffff8f02c12b2000
    Parameter[1] = ffffca83e6b65f30
    Parameter[2] = 0000000000000002
    Parameter[3] = (unknown)       
02 ffffca83e6b65ed0 fffff8026fbccdaf nt!`SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue'::`1'::filt$0+22 
    Parameter[0] = ffffca83e6b65f30
    Parameter[1] = ffffca83e6b673c0
    Parameter[2] = (unknown)       
    Parameter[3] = (unknown)       
03 ffffca83e6b65f00 fffff8026fbfffef nt!_C_specific_handler+9f 
    Parameter[0] = ffffca83e6b66eb8
    Parameter[1] = ffffca83e6b673c0
    Parameter[2] = 0000000000000000
    Parameter[3] = ffffca83e6b66530
04 ffffca83e6b65f70 fffff8026fae6de7 nt!RtlpExecuteHandlerForException+f 
    Parameter[0] = ffffca83e6b66eb8
    Parameter[1] = ffffca83e6b66eb8
    Parameter[2] = ffffca83e6b666f0
    Parameter[3] = ffffca83e6b66530
05 ffffca83e6b65fa0 fffff8026fae59d6 nt!RtlDispatchException+297 
    Parameter[0] = (unknown)       
    Parameter[1] = (unknown)       
    Parameter[2] = (unknown)       
    Parameter[3] = (unknown)       
06 ffffca83e6b666c0 fffff8026fc091ac nt!KiDispatchException+186 
    Parameter[0] = b33cab7225100e87
    Parameter[1] = ffffca83e6b61000
    Parameter[2] = 18350787431f6479
    Parameter[3] = 72a40efbb8371cfa
07 ffffca83e6b66d80 fffff8026fc05343 nt!KiExceptionDispatch+12c 
    Parameter[0] = (unknown)       
    Parameter[1] = (unknown)       
    Parameter[2] = (unknown)       
    Parameter[3] = (unknown)       
08 ffffca83e6b66f60 fffff8026fb31620 nt!KiPageFault+443 
    Parameter[0] = ffffa1804e790000
    Parameter[1] = ffffa1804e790000
    Parameter[2] = 000002516e4023e0
    Parameter[3] = 00000000000006c6
09 ffffca83e6b670f8 fffff8026fb06490 nt!RtlDecompressBufferXpressLz+50 
    Parameter[0] = ffffa1804e790000
    Parameter[1] = (unknown)       
    Parameter[2] = (unknown)       
    Parameter[3] = 00000000000006c6
0a ffffca83e6b67110 fffff8026fb061d8 nt!RtlDecompressBufferEx+60 
    Parameter[0] = (unknown)       
    Parameter[1] = ffffa1804e790000 <-- pointer to buffer
    Parameter[2] = 0000000000001000
    Parameter[3] = 000002516e4023e0
0b ffffca83e6b67160 fffff8026fb06065 nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+150 
    Parameter[0] = ffff8f02c12b2050
    Parameter[1] = 0000000000000000
    Parameter[2] = 000002516e4023e1
    Parameter[3] = ffffa1804e790000
0c ffffca83e6b67220 fffff8026fb0589c nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+a5 
    Parameter[0] = ffff8f02c12b2050
    Parameter[1] = 0000000000000000
    Parameter[2] = 000002516e4023e1
    Parameter[3] = ffff8f02d40c5c10
0d ffffca83e6b67270 fffff8026fb056cc nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+180 
    Parameter[0] = (unknown)       
    Parameter[1] = (unknown)       
    Parameter[2] = (unknown)       
    Parameter[3] = (unknown)       
0e ffffca83e6b67310 fffff8026fb05519 nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+c8 
    Parameter[0] = ffffca83e6b67599
    Parameter[1] = ffff8f02d4ee0000
    Parameter[2] = ffff8f02d40c5c10
    Parameter[3] = (unknown)       
0f ffffca83e6b673c0 fffff8026fb053d1 nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+85 
    Parameter[0] = (unknown)       
    Parameter[1] = (unknown)       
    Parameter[2] = (unknown)       
    Parameter[3] = (unknown)       
10 ffffca83e6b67440 fffff8026faf8468 nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+21 
    Parameter[0] = (unknown)       
    Parameter[1] = (unknown)       
    Parameter[2] = (unknown)       
    Parameter[3] = (unknown)       
11 ffffca83e6b67470 fffff8026fb02f2f nt!KeExpandKernelStackAndCalloutInternal+78 
    Parameter[0] = (unknown)       
    Parameter[1] = (unknown)       
    Parameter[2] = (unknown)       
    Parameter[3] = (unknown)       
12 ffffca83e6b674e0 fffff8026fad0e04 nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+c7 
    Parameter[0] = (unknown)       
    Parameter[1] = (unknown)       
    Parameter[2] = (unknown)       
    Parameter[3] = (unknown)       
13 ffffca83e6b675b0 fffff8026fad0838 nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+1ac 
    Parameter[0] = ffff8f02c12b2000
    Parameter[1] = ffff8f02d40c5c10
    Parameter[2] = 0000000000000000
    Parameter[3] = (unknown)       
14 ffffca83e6b67600 fffff8026fb039b7 nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+c0 
    Parameter[0] = (unknown)       
    Parameter[1] = (unknown)       
    Parameter[2] = (unknown)       
    Parameter[3] = (unknown)       
15 ffffca83e6b67690 fffff8026fb5ae0b nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+167 
    Parameter[0] = (unknown)       
    Parameter[1] = ffffca83e6b67730
    Parameter[2] = ffff8f02ce7eca70
    Parameter[3] = (unknown)       
16 ffffca83e6b67700 fffff8026fa5e0a0 nt!SmPageRead+33 
    Parameter[0] = ffff8f02ce7ec9c0
    Parameter[1] = ffff8f02ce7eca70
    Parameter[2] = ffff8f02ce7ec980
    Parameter[3] = ffff8f02ce7ec9b0
17 ffffca83e6b67750 fffff8026fa5bb4d nt!MiIssueHardFaultIo+10c 
    Parameter[0] = (unknown)       
    Parameter[1] = (unknown)       
    Parameter[2] = (unknown)       
    Parameter[3] = (unknown)       
18 ffffca83e6b677a0 fffff8026fa9f568 nt!MiIssueHardFault+29d 
    Parameter[0] = (unknown)       
    Parameter[1] = (unknown)       
    Parameter[2] = (unknown)       
    Parameter[3] = (unknown)       
19 ffffca83e6b67860 fffff8026fc0525e nt!MmAccessFault+468 (perf)
    Parameter[0] = (unknown)       
    Parameter[1] = (unknown)       
    Parameter[2] = (unknown)       
    Parameter[3] = (unknown)       
1a ffffca83e6b67a00 00007ffd199fc33f nt!KiPageFault+35e 
    Parameter[0] = 0000013be2f90ad0
    Parameter[1] = 0000013be2f90a00
    Parameter[2] = 0000013be2f90ac0
    Parameter[3] = 0000000000001000

3: kd> dd ffffa1804e790000
ffffa180`4e790000  ????????`???????? ????????`????????
ffffa180`4e790010  ????????`???????? ????????`????????
ffffa180`4e790020  ????????`???????? ????????`????????
ffffa180`4e790030  ????????`???????? ????????`????????
ffffa180`4e790040  ????????`???????? ????????`????????
ffffa180`4e790050  ????????`???????? ????????`????????
ffffa180`4e790060  ????????`???????? ????????`????????
ffffa180`4e790070  ????????`???????? ????????`????????

 

[Alibi]

So I ran CHKDSK on both of my drives and they both came out clean. I also ran the sfc /scannow command returning "Windows Resource Protection did not find any integrity violations." After that, I downloaded the Western Digital Dashboard thinking that the S.M.A.R.T feature could help me. This feature did although cause a blue screen instead. The programs that I checked all say that my drives are "OK". Any help is appreciated.

 

[axe0axe0]

SFC and DISM have no effect. DISM is meant to fix corruption that prevents SFC from working correctly. SFC is designed to fix problems to make sure Windows keeps running. Neither of them does anything with the drive.

Chkdsk does do something with the drive, but only partial. It only fixes problems in the filesystem, albeit it does work with sectors too.

Let's have a look at the eventlogs. Please run this command in a command prompt, it generates the file eventlog.txt on your desktop. Please upload this file.

wevtutil qe System /f:text > "%USERPROFILE%\Desktop\eventlog.txt"

 

[Alibi]

I've now ran the command and the text file is linked below. I appreciate the help.

File: https://we.tl/t-W9Q6tgxvY5

 

[axe0axe0]

Did you by any chance check more programs for the SMART than have been mentioned here?

Asking because of these events

   2021-08-07T15:07:29.6510000Z        The IO operation at logical block address 0x1367cd8 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:07:30.1610000Z        The IO operation at logical block address 0x32bba8 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:12:52.7850000Z        The IO operation at logical block address 0x668af8 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:12:53.8040000Z        The IO operation at logical block address 0x29323b0 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:12:54.3140000Z        The IO operation at logical block address 0x27ecf50 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:12:54.3400000Z        The IO operation at logical block address 0x2d4cd48 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:12:55.5410000Z        The IO operation at logical block address 0x274270 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:12:56.5890000Z        The IO operation at logical block address 0x291c630 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:12:57.6100000Z        The IO operation at logical block address 0x28deb40 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:12:58.6350000Z        The IO operation at logical block address 0x293f598 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:13:29.1570000Z        Reset to device, \Device\RaidPort0, was issued.
   2021-08-07T15:14:06.4710000Z        The IO operation at logical block address 0x2915f98 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:14:06.9860000Z        The IO operation at logical block address 0x290b9d0 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:14:08.0110000Z        The IO operation at logical block address 0x28a91a8 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:14:42.2270000Z        The IO operation at logical block address 0x2c92d10 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:14:43.4060000Z        The IO operation at logical block address 0x28a9228 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:14:43.4850000Z        The IO operation at logical block address 0x668a78 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:14:47.2140000Z        The IO operation at logical block address 0x2a9dbf8 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:14:47.9780000Z        The system failed to flush data to the transaction log. Corruption may occur in VolumeId: C:, DeviceName: \Device\HarddiskVolume3.
           Failure status: The I/O device reported an I/O error.
           Device GUID: {ecac3360-b0ad-5078-c780-f8a349072dff}
           Device manufacturer: 
           Device model: SanDisk SD8SBAT128G1002
           Device revision: Z2317002
           Device serial number: 165351404295
           Bus type: SATA
           Adapter serial number:
   2021-08-07T15:14:48.4910000Z        The IO operation at logical block address 0x2a82938 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:14:49.5200000Z        The IO operation at logical block address 0x677a68 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:14:53.6250000Z        The IO operation at logical block address 0x9f2c30 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:14:54.1440000Z        The IO operation at logical block address 0x28f1af0 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:14:56.1930000Z        The IO operation at logical block address 0x677a68 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:14:56.7050000Z        The IO operation at logical block address 0xd820d0 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:14:57.2250000Z        The IO operation at logical block address 0x2ab9088 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:14:57.7400000Z        The IO operation at logical block address 0x287bca8 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:14:59.7940000Z        The IO operation at logical block address 0x13687d8 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:15:00.2960000Z        The IO operation at logical block address 0xa98850 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T15:15:31.8430000Z        Reset to device, \Device\RaidPort0, was issued.
   2021-08-07T19:50:06.2540000Z        The IO operation at logical block address 0x6c0de0 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T19:50:12.2730000Z        The IO operation at logical block address 0x67bc50 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T19:52:25.4780000Z        The IO operation at logical block address 0x67c388 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T20:12:22.9670000Z        The IO operation at logical block address 0x668b38 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T20:13:48.5190000Z        The IO operation at logical block address 0x3435db0 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T20:14:07.3510000Z        The IO operation at logical block address 0x34483b0 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T20:14:37.5010000Z        The IO operation at logical block address 0x2d38bb0 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T20:14:37.7940000Z        The IO operation at logical block address 0x309e848 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T20:14:41.9350000Z        The IO operation at logical block address 0x2851120 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T20:15:16.6440000Z        The IO operation at logical block address 0x2d96178 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T20:15:16.7690000Z        The IO operation at logical block address 0x2f2f848 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T20:15:16.9900000Z        The IO operation at logical block address 0x2aa4308 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T20:15:17.1700000Z        The IO operation at logical block address 0x2b04998 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T20:15:17.3360000Z        The IO operation at logical block address 0x6733b8 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T20:17:02.4960000Z        The IO operation at logical block address 0x29416d8 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T20:17:23.6920000Z        The IO operation at logical block address 0x2d51e58 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T20:17:24.2190000Z        The IO operation at logical block address 0x332e860 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T20:17:24.7330000Z        The IO operation at logical block address 0x3311360 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T20:17:25.2460000Z        The IO operation at logical block address 0x3311560 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T20:17:25.7490000Z        The IO operation at logical block address 0x3311760 for Disk 0 (PDO name: \Device\00000036) was retried.
   2021-08-07T20:18:33.8340000Z        The IO operation at logical block address 0x2fc8c48 for Disk 0 (PDO name: \Device\00000036) was retried.

 

[Alibi]

So I've ran SMART a few times from within the Western Digital Dashboard, but sadly with all of them causing a BSOD within a few minutes. I haven't used any other programs to run SMART. I don't recall having used it in the command prompt either if that even is possible.

 

[axe0axe0]

Have you tried CrystalDiskInfo https://crystalmark.info/en/software/crystaldiskinfo/ (blue buttons on the left of the green buttons).

 

[Alibi]

I just checked CrystalDiskInfo and everything was blue, so it didn't catch any errors.

 

[axe0axe0]

Please download and run https://www.sysnative.com/forums/pages/bsodcollectionapp/.

It collects different data that may be needed to have a better look at the problem.

 

[Alibi]

Ok, so I ran the SysnativeBSODCollectionApp as you said and have linked the output ZIP file below.

ZIP file: https://we.tl/t-RXbqdPwtUW

 

[axe0axe0]

The reason I asked you to run it is because it collects that which you already provided and more. Below is an overview of the crashes with some data I could not have found out with the eventlog or the dumps given prior. This is useful because there are hexadecimal values like 'c0000006' and 'c000000e' that have a meaning behind them. These two specifically you can also find in my first post, they indicate an in-page error occurred and a non-existing device was specified. These two are almost always recurring in the crashes. Generally speaking, at a glimpse of data like this it tells me that there are two potential suspects, RAM and storage. Assuming your drives are healthy as indicated by the tests and scans, the RAM is the likely suspect currently.

I suggest following this guide to run MemTest86.

Test RAM with PassMark MemTest86 (version 10.6 was used)

PassMark MemTest86 is a stand alone memory testing software program originally developed for x86 computers. It was re-written to work on x64 devices (with the native 64-bit support) and on new UEFI-based machines. Follow the instructions below for running MemTest86 from either a USB drive...

www.sysnative.com

2021-08-13 08:29    Windows Error Reporting    Fault bucket 0x154_c0000006_c000000e_nt!ExFreePool, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: b3826e7c-baeb-451e-ab68-9ce1b3b0d432

Problem signature:
P1: 154
P2: ffffae0f98370000
P3: ffffe60b0b935910
P4: 2
P5: 0
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\081321-6296-01.dmp
\\?\C:\Windows\TEMP\WER-26125-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER78C9.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER78DA.tmp.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_154_3c74c88d70c23117b7ce254cd50fad990ad14f5_00000000_cab_0424a07f-8827-4e8d-9d57-18fa2e595dc8

Analysis symbol: 
Rechecking for solution: 0
Report Id: c7408fa7-d16a-4160-bde7-cc1f6355b34d
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
2021-08-11 12:06    Windows Error Reporting    Fault bucket 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_c0000005_BAD_IP_nt!PspCatchCriticalBreak, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 656adac1-e483-4de1-b028-868531e42fba

Problem signature:
P1: ef
P2: ffffbf8749e0a080
P3: 0
P4: 0
P5: 0
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\081121-5984-01.dmp
\\?\C:\Windows\TEMP\WER-7578-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER35D5.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER35E5.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3604.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3614.tmp.txt
\\?\C:\Windows\Temp\WER5A46.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ef_7dbdba72e94ca91edc4887a7a73ace6b663341_00000000_cab_e6b08440-036c-4d9b-8857-57eac4e81aef

Analysis symbol: 
Rechecking for solution: 0
Report Id: e2730f7b-b4b4-4808-b50c-8737a41ed474
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
2021-08-11 07:36    Windows Error Reporting    Fault bucket 0xEF_services.exe_BUGCHECK_CRITICAL_PROCESS_IOERR_c000000e, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 8cf647d3-605c-4358-85c2-e0d55757913d

Problem signature:
P1: ef
P2: ffffa709207ca140
P3: 0
P4: 0
P5: 0
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\081121-4750-01.dmp
\\?\C:\Windows\TEMP\WER-6343-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B65.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B85.tmp.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ef_d6d4bc689267f8f544bab765e94a6e3839124b9_00000000_cab_d2df90f4-96c1-4a8e-a1d2-87273b7a560b

Analysis symbol: 
Rechecking for solution: 0
Report Id: c913e6e0-8fc4-4efb-aa55-e23e917a9831
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
2021-08-11 06:30    Windows Error Reporting    Fault bucket 0xEF_services.exe_BUGCHECK_CRITICAL_PROCESS_IOERR_c000000e, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 032faa43-91ad-4926-8dcb-01803d47a015

Problem signature:
P1: ef
P2: ffff94053fb2c140
P3: 0
P4: 0
P5: 0
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\081021-5937-01.dmp
\\?\C:\Windows\TEMP\WER-7593-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3567.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3568.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3596.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3597.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ef_6e292e965526b8eca8713b4336a1af6812a263e_00000000_cab_aa30c240-c6fe-4d84-9174-d5ceb86d4ad8

Analysis symbol: 
Rechecking for solution: 0
Report Id: 3e649251-ffcb-4107-98b8-4cc9a82a1637
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
2021-08-10 19:18    Windows Error Reporting    Fault bucket 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_IOERR_c000000e, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 200c6cde-08c6-47f7-addc-03708d0e08fa

Problem signature:
P1: ef
P2: ffffa80b61c322c0
P3: 0
P4: 0
P5: 0
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\081021-6203-01.dmp
\\?\C:\Windows\TEMP\WER-7781-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BA1.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BB2.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BE0.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BE1.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ef_f94a93dc46196284b53abfc24e284cbfa07bc2_00000000_cab_04ece96e-7b8a-4ed7-8268-f598a2be2134

Analysis symbol: 
Rechecking for solution: 0
Report Id: 605a8011-55e0-41a5-8dc7-3f250860f539
Report Status: 268435460
Hashed bucket: 
Cab Guid: 0
2021-08-10 13:46    Windows Error Reporting    Fault bucket 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_c0000005_nt!PspCatchCriticalBreak, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: b0966254-2bdd-46f1-9ec6-0b90fea1d952

Problem signature:
P1: ef
P2: ffffd28475216080
P3: 0
P4: 0
P5: 0
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\081021-5718-01.dmp
\\?\C:\Windows\TEMP\WER-11328-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4093.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40A3.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40C2.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40D2.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ef_8d62b786955bc78728376a5544d60727a1ba8ef_00000000_cab_f74ce2ce-df66-478c-be9f-b4c615a8e608

Analysis symbol: 
Rechecking for solution: 0
Report Id: 3d971456-8893-499e-8130-2df3d249b3cb
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
2021-08-10 13:37    Windows Error Reporting    Fault bucket 0xEF_services.exe_BUGCHECK_CRITICAL_PROCESS_IOERR_c000000e, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 596c3c55-13b1-419c-ab6a-7ac1f53c2be3

Problem signature:
P1: ef
P2: ffff9e044f321140
P3: 0
P4: 0
P5: 0
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\081021-6281-01.dmp
\\?\C:\Windows\TEMP\WER-12859-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4872.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4873.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4892.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER48A2.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ef_17bd34c21229bb01e324fd7ffe52e7b5e126_00000000_cab_e34b1c94-04db-4ef5-bf61-2da65fe2e0e7

Analysis symbol: 
Rechecking for solution: 0
Report Id: 0b2e059a-a048-4645-aea5-b83cbf42ad56
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
2021-08-09 08:24    Windows Error Reporting    Fault bucket 0xEF_services.exe_BUGCHECK_CRITICAL_PROCESS_IOERR_c000000e, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 2d7f8aca-f7e3-4719-8cfb-f0ef8e8f1cb2

Problem signature:
P1: ef
P2: ffffb30faa0d6140
P3: 0
P4: 0
P5: 0
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\080921-7968-01.dmp
\\?\C:\Windows\TEMP\WER-13656-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER445C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER446C.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER449A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER44AB.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ef_f9f8b9a7aceec1ea57b8b5e58908f226af4e439_00000000_cab_43c7b52c-3dfa-4a7c-baf0-5d9c6574875c

Analysis symbol: 
Rechecking for solution: 0
Report Id: 4f612e16-8f78-4372-b05d-a94f413868ab
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
2021-08-09 08:07    Windows Error Reporting    Fault bucket 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_IOERR_c000000e, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 3e23ff94-ff3e-49eb-8fbc-d921a1dd2daa

Problem signature:
P1: ef
P2: ffff88046d8222c0
P3: 0
P4: 0
P5: 0
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\080921-6406-01.dmp
\\?\C:\Windows\TEMP\WER-11578-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E8F.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3EA0.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3EBE.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3ECF.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ef_1554b87851fff1705d1b503119fc70cf2016a63b_00000000_cab_d6061d43-825e-4dd9-9bf3-8d615352d8dc

Analysis symbol: 
Rechecking for solution: 0
Report Id: a3348c91-7e5d-463a-beef-9bf5448488f7
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
2021-08-09 08:01    Windows Error Reporting    Fault bucket 0xEF_smss.exe_BUGCHECK_CRITICAL_PROCESS_IOERR_c000000e, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: c6261946-1cb7-449b-9928-6681c3fe87de

Problem signature:
P1: ef
P2: ffff80843007c040
P3: 0
P4: 0
P5: 0
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\080921-6703-01.dmp
\\?\C:\Windows\TEMP\WER-12343-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F7A.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F7B.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F99.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FA9.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ef_6df652c63b5b21dd3fcb8d6b8bad43bf84d392f_00000000_cab_0a7d643f-9072-40e4-85b7-4f63fb8af05f

Analysis symbol: 
Rechecking for solution: 0
Report Id: 5f503d85-8e24-4e32-819f-435dda61866a
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
2021-08-08 18:02    Windows Error Reporting    Fault bucket 0x154_c0000006_c000000e_nt!RtlDecompressBufferXpressLz, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 7fd94d1e-f618-4921-8949-91c1041962c4

Problem signature:
P1: 154
P2: ffff8f02c12b2000
P3: ffffca83e6b65f30
P4: 2
P5: 0
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\080821-5578-01.dmp
\\?\C:\Windows\TEMP\WER-10593-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3AE6.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3AE7.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3B05.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3B06.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_154_eaad6174c2b0a2786ba9d84aae7f76e2a9f8cf_00000000_cab_b2811329-8814-4b1d-8079-0b72bafeab06

Analysis symbol: 
Rechecking for solution: 0
Report Id: 11362b0c-5fec-4107-9f5b-dd490eafb232
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
2021-08-08 11:07    Windows Error Reporting    Fault bucket 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_IOERR_c000000e, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: b80f8e44-27fe-43d4-8adc-7ba3c1109e12

Problem signature:
P1: ef
P2: ffffbb8a9bbd02c0
P3: 0
P4: 0
P5: 0
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\080821-8765-01.dmp
\\?\C:\Windows\TEMP\WER-14593-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4A18.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4A19.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4A38.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4A48.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ef_2f3f3e14f27696a4b38618e629eeed4c4da23c_00000000_cab_f05653a9-f60a-4582-a741-bf5cd6458b4a

Analysis symbol: 
Rechecking for solution: 0
Report Id: 707c6590-964e-4bdb-a403-bd212314255f
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
2021-08-08 11:07    Windows Error Reporting    Fault bucket 0x154_c0000006_c000000e_SYMEFASI64!unknown_function, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 106fe6a3-dc47-41d7-95e9-3fac7cf5cd88

Problem signature:
P1: 154
P2: ffffb301a340f000
P3: ffff868878ac0580
P4: 2
P5: 0
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\080821-7046-01.dmp
\\?\C:\Windows\TEMP\WER-15062-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4BFD.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C0D.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C1C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C6B.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_154_73d68875cb8bfa77d2ed3749c0eff6aaa69a62_00000000_cab_52bb6f29-f30c-40d6-8adb-0bcadbeee7d4

Analysis symbol: 
Rechecking for solution: 0
Report Id: 90f7c185-633d-4ace-8b8b-33f64ef6c330
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
2021-08-08 09:04    Windows Error Reporting    Fault bucket 0x3B_c0000006_nt!HvpGetCellPaged, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: da93ff73-fa27-4a33-9969-73d4a1be6946

Problem signature:
P1: 3b
P2: c0000006
P3: fffff804656cbbe2
P4: ffff828a0e4fc470
P5: 0
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\080821-7578-01.dmp
\\?\C:\Windows\TEMP\WER-13656-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46DC.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46FC.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER471B.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER472B.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_2c13498d81a23c3dd7c559fcd5babf102b6c963_00000000_cab_c31788bc-5ca8-4352-ae6f-1a5a35a7ccbb

Analysis symbol: 
Rechecking for solution: 0
Report Id: 71acd83f-e1ba-4e9a-9a76-57b67c165b9c
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0

 

[Alibi]

I ran MemTes86 but it didn't find any errors throughout the search. I Have although linked the MemTest report below if needed.

Report: https://we.tl/t-wJavPKRSdr