[SOLVED] ntoskrnl.exe+3f72e0 please help

[Inerald]

Hi, lately, every time after startup, my computer has a BSOD. It used to be much rarer. Perhaps the problem is in the HDD or some driver.
My PC has Windows 10 Home 21H1.
Intel Core i7-4770 3.40GHz.
Asus STRIX-GTX950-DC2OC-2GD5-GAMING (2 GB).
Motherboard - Gigabyte GA-B85-HD3 rev 1.0. Latest BIOS version (F11).
DIMM2: Crucial ST102464BA160B.16F 8 GB and DIMM4: Crucial ST102464BA160B.16F 8 GB = 16.0 GB (15.2 GB) RAM.
64-bit operating system, x64 processor.
Reinstalling Windows does not help.
Minidump folder - https://drive.google.com/drive/folders/1-rUoiKH6GMidYfid5o_5FgorCtU8zsbx?usp=sharing

 

[Colif]

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it

try turning this off - https://www.tenforums.com/tutorials/4189-turn-off-fast-startup-windows-10-a.html

I ask a friend to convert dumps.

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/7bv18n52/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:	012622-62125-01.dmp (Jan 26 2022 - 06:54:29)
Bugcheck:	CRITICAL_PROCESS_DIED (EF)
Probably caused by:	memory_corruption (Process running at time of crash: csrss.exe)
Uptime:	0 Day(s), 0 Hour(s), 02 Min(s), and 29 Sec(s)

File information:	012622-52000-01.dmp (Jan 26 2022 - 02:42:18)
Bugcheck:	CRITICAL_PROCESS_DIED (EF)
Probably caused by:	memory_corruption (Process running at time of crash: svchost.exe)
Uptime:	0 Day(s), 0 Hour(s), 02 Min(s), and 46 Sec(s)

File information:	012522-36078-01.dmp (Jan 24 2022 - 09:07:36)
Bugcheck:	UNEXPECTED_STORE_EXCEPTION (154)
Probably caused by:	hardware_disk (Process running at time of crash: MemCompression)
Uptime:	0 Day(s), 5 Hour(s), 12 Min(s), and 57 Sec(s)

The following dump files were 0 bytes long which means they are invalid:
012622-61406-01.dmp
012622-45796-01.dmp

Comment: The overclocking driver "XtuAcpiDriver.sys" was found on your system. (Intel Extreme Tuning Utility)

Possible Motherboard page: https://www.gigabyte.com/Motherboard/GA-B85-HD3-rev-1x#ov
You are using the latest BIOS available for your system, version F11.

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]

memtest is worth checking, all 3 errors did occur after accessing ram.

top 2 errors generally only happen to microsoft files, as it can be a number of any criticial files that cause windows to crash if they do. Top one is the client that your user runs in. Other was Service host.

unless its further down the error text and not showing in report, i don't see any mention of the hdd in error 3. Only mention it as error blames hardware disk.

try running this on CPU - https://www.intel.com/content/www/us/en/download/15951/19792/intel-processor-diagnostic-tool.html?

 

[Inerald]

memtest is worth checking, all 3 errors did occur after accessing ram.

top 2 errors generally only happen to microsoft files, as it can be a number of any criticial files that cause windows to crash if they do. Top one is the client that your user runs in. Other was Service host.

unless its further down the error text and not showing in report, i don't see any mention of the hdd in error 3. Only mention it as error blames hardware disk.

try running this on CPU - https://www.intel.com/content/www/us/en/download/15951/19792/intel-processor-diagnostic-tool.html?

Thanks for the advice to check the RAM. I checked my RAM one by one and it turned out that there were errors on one. I already thought I wouldn't see the blue screen anymore, but today there was a bsod again.
Intel Processor Diagnostic Tool utility did not detect any problems on my processor.
Link to the minidump file - https://drive.google.com/drive/folders/1Ri4gm7yris-44qiX_GZck2YSV5Ylkw92?usp=sharing

 

[Colif]

did you take the ram stick out that had the errors as it will only cause more if left in PC.
if you have proof of purchase of ram, and can print out report showing it failed memtest, most memory makers will let you return set for a full replacement. Crucial probably do it.

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://jsfiddle.net/912gzfuc/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.

File information:	012922-61531-01.dmp (Jan 29 2022 - 04:29:25)
Bugcheck:	CRITICAL_PROCESS_DIED (EF)
Probably caused by:	memory_corruption (Process running at time of crash: svchost.exe)
Uptime:	0 Day(s), 0 Hour(s), 04 Min(s), and 23 Sec(s)

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