[SOLVED] BSOD ntoskrnl.exe+3f72e0 - Need help fixing; dump files attatched

[khaiky5]

Hi, I've been experiencing daily BSODs ever since being gifted a used PC. I reset the PC and since got increasingly frequent BSODs with usually KMODE_EXCEPTION_NOT_HANDLED or IRQL_NOT_LESS_OR_EQUAL, with ntoskrnl.exe+3f72e0 being a common denominator, according to BlueScreenView.

Here's the mini dump files: https://www.dropbox.com/s/43mva86nt9yi063/020722-12000-01.zip?dl=0

If it's relevant, my graphics card is Geforce GTX 1050 Ti. I regularly update it, but I read something about updates conflicting w/ each other but idk what that's all about

If anyone can help me out, I'd be eternally grateful! It bums me out being nervous about the next time my OC crashes!

 

[khaiky5]

Actually disabling iaStorE.sys caused my PC to go into "performing automatic repairs" loop and I restored

 

[gardenman]

I ran the dump files through the debugger and got the following information: https://jsfiddle.net/1e7b83pa/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:	021522-10250-01.dmp (Feb 15 2022 - 07:27:45)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:	memory_corruption (Process running at time of crash: chrome.exe)
Uptime:	0 Day(s), 6 Hour(s), 31 Min(s), and 26 Sec(s)

File information:	021522-10187-01.dmp (Feb 15 2022 - 23:02:45)
Bugcheck:	KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:	memory_corruption (Process running at time of crash: System)
Uptime:	0 Day(s), 15 Hour(s), 34 Min(s), and 03 Sec(s)

File information:	021422-10140-01.dmp (Feb 15 2022 - 00:55:36)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:	memory_corruption (Process running at time of crash: audiodg.exe)
Uptime:	0 Day(s), 2 Hour(s), 54 Min(s), and 05 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.

 

[Colif]

So crash one mentions DirectX which normally means GPU but can also be sound
Crash 3 victim is audiodg.exe which is used by windows to talk to sound drivers.
So getting mixed signals.
is your sound run through motherboard or monitor?
cause it could be

Feb 18 2020

RTKVHD64.sys

Realtek Audio System driver https://www.realtek.com/en/

or

Oct 21 2021

nvhda64v.sys

Nvidia HDMI Audio Device http://www.nvidia.com/

depending where you get sound from.

I don't like errors that keep moving like this. We checked ram which would have been what I looked at...
passes intel tests
wonders if its PSU again

Download Magician and check ssd - https://semiconductor.samsung.com/consumer-storage/support/tools/
checking all the things that might be involved in corrupting info. There are some things unlikely to be cause like the GPU itself (its drivers are another story)

 

[khaiky5]

I have speakers that plug into the green audio port at the back of my PC; that means it runs through the motherboard, right?

Samsung's Magician extended SMART self test yielded these logs I exported:

Spoiler: Logs

SMART Self-Test,2/17/2022
Model Name,Samsung SSD 860 EVO 500GB
Serial Number,S3Z1NB0K938361X
Result,Log #1,Option,EXTENDED
,,Status,Successfully completed{0}
,,Power on hours,7131
,,Failing LBA,0
,Log #2,Option,SHORT
,,Status,Aborted by host{1}
,,Power on hours,7007
,,Failing LBA,10775552
,Log #3,Option,SHORT
,,Status,Successfully completed{0}
,,Power on hours,7007
,,Failing LBA,0

It mentioned "Failing LBA"

The full diagnostic scan says drive is in good condition and has all blue blocks

 

[Colif]

LBA in short terms means bad sector

If you do not receive critical errors from what i know 0x0 code near that means its fine if something like 0x1 appears i would start worrying, however do not quote me 100 per cent on that.

Can you explain this to a dummy like me?
I got the same error: Failing LBA 0x0
My drive is only a few months old.
I'm trying to figure out if my recent issues are Windows, drive, or even BIOS related.

Basically your ssd has sensors on it to known if a part of it is failing and usually the codes used by the ssd are hexadecimal or binary. 0x0 means no, 0x1 means yes in the ssd language. So 0x0 means he is not failing

https://eu.community.samsung.com/t5/computers-it/quick-question-about-860-evo/td-p/1854688

Drive could be fine but ssd don't really give many warnings, a lot of the time they just stop. So you might consider getting a new ssd and put the current one as storage where it doesn't need to think as hard. It might last longer then.

LBA is an acronym for Logical Block Addressing. In this case I assume it is just another, possibly more technically accurate way of referring to a "bad sector".

Unless your hard drive is very old, the file system of your OS probably didn't even know anything had happened. For a while now the firmware in hard drives has been transparently handling sector write errors by remapping the sector to another location on the drive. If you were able to copy all the data on this drive and no errors were reported it seems quite possible that the offending sector was not even being used (yet) by your file system. The bad sector may have only been discovered because the Samsung diagnostic tool you used performed a complete scan of all sectors on the drive.

https://superuser.com/questions/166177/hard-drive-lba-error-how-to-proceed

it could be the bad sector is reason why you keep getting different drivers playing up.

 

[johnbl]

you might go into windows control panel, hardware->device manager
then go to the menu for view-> then select show hidden devices
look at the usb devices and remove the software for any device that is not currently being used. look for a device for Rock Candy Wired Controller for Xbox 360
and remove it.

just a hunch