Question Random BSODs Unsure of Problem

[heyb5]

I've started having a lot of BSODs as of last week. I can boot the PC and play for a bit but it inevitably BSODs constantly after use for a few hours. I've reinstalled graphics drivers, updated windows, used sfc scan/DISM/memory diagnostic none of which came up with problems. I'd really appreciate any help I can get.
Minidumps:

BSODs – Google Drive

drive.google.com

 

[Colif]

Conversion of Dump files

results - click run as fiddle to read

File: 042023-9812-01.dmp (Apr 21 2023 - 10:38:40)
BugCheck: [KERNEL_SECURITY_CHECK_FAILURE (139)]
*** WARNING: Unable to verify timestamp for EasyAntiCheat.sys
Probably caused by: EasyAntiCheat.sys (Process: System)
Uptime: 0 Day(s), 1 Hour(s), 09 Min(s), and 29 Sec(s)

File: 041923-8750-01.dmp (Apr 19 2023 - 14:04:34)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: memory_corruption (Process: LOSTARK.exe)
Uptime: 0 Day(s), 0 Hour(s), 24 Min(s), and 16 Sec(s)

File: 041823-8859-01.dmp (Apr 19 2023 - 13:38:39)
BugCheck: [KERNEL_SECURITY_CHECK_FAILURE (139)]
Probably caused by: ntkrnlmp.exe (Process: Discord.exe)
Uptime: 0 Day(s), 0 Hour(s), 43 Min(s), and 44 Sec(s)

File: 041623-8750-01.dmp (Apr 17 2023 - 04:42:51)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: memory_corruption (Process: LOSTARK.exe)
Uptime: 0 Day(s), 1 Hour(s), 59 Min(s), and 42 Sec(s)

File: 041623-26015-01.dmp (Apr 17 2023 - 13:21:11)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)]
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 04 Sec(s)

so the last one was caused by Easy Anti Cheat. Might need to update it
some of the others not so obvious.
Bottom one mentions hdaudio so what sound devices do you have?

what are specs?
CPU - Ryzen 7 2700X
Ram - 32gb Corsair Vengeance RGB Pro
MB - MSI B350 PC MATE

I can't see anymore than that though
Update LAN drivers:
Download Win10 Auto Installation Program (NDIS) from under windows header here - https://www.realtek.com/en/componen...0-1000m-gigabit-ethernet-pci-express-software

try updating chipset drivers - https://www.amd.com/en/support/chipsets/amd-socket-am4/b350

 

[heyb5]

CPU - Ryzen 7 2700X
Ram - 32gb Corsair Vengeance RGB Pro
MB - MSI B350 PC MATE
GPU - RTX 3060
PSU - EVGA bronze 550w
SSDs: ADATA SU800, Samsung 870 QVO
HDDs: WDC WD10EURX-63FH1Y0, WDC WD2003FYYS-70W0B0

I ran the EasyAntiCheat repair.
The only sound device I use is a Hyperx Cloud 2 headset and I guess a VR headset as well.
I'm updating those drivers now also.

 

[ubuysa]

The 042023-9812-01.dmp and the 041923-8750-01.dmp can be laid at the door of EasyAntiCheat. I see you've updated it since the dump upload, the version in the dumps is about 4 months old now...

 14: kd> lmDvmEasyAntiCheat
Browse full module list
start             end                 module name
fffff802`ec0a0000 fffff802`ecdfc000   EasyAntiCheat T (no symbols)        
    Loaded symbol image file: EasyAntiCheat.sys
    Image path: EasyAntiCheat.sys
    Image name: EasyAntiCheat.sys
    Browse all global symbols  functions  data
    Timestamp:        Wed Dec  7 14:56:16 2022 (63908D70)
    CheckSum:         00D464DA
    ImageSize:        00D5C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

The 041823-8859-01.dmp is a stack pointer overrun, the bugcheck happened immediately the kernel was called, so it seems that the calling user-mode code created the problem and that would appear to be discord.exe. This may not be a kernel problem at all.

The 041623-26015-01.dmp is an exception during audio processing. The Microsoft driver HDAudio.sys appears frequently on the call stack. This isn't the problem however (because it's a Microsoft driver) so we need to look lower down in the driver stack at the third-party audio driver. This is RTKVHD64.sys, the Realtek audio driver. The version you have installed is very old, dating from 2018...

2: kd> lmDvmRTKVHD64
Browse full module list
start             end                 module name
fffff800`59320000 fffff800`59957000   RTKVHD64   (deferred)          
    Image path: RTKVHD64.sys
    Image name: RTKVHD64.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Jun 19 14:24:36 2018 (5B28E7F4)
    CheckSum:         006076FB
    ImageSize:        00637000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

The 041623-8750-01.dmp is an exception during networking operations, we see the Microsoft NETIO.sys driver called. Again, this isn't the problem however (because it's a Microsoft driver) so we need to look lower down in the driver stack at the third-party network driver. This is rt640x64.sys, the LAN driver. The version of this driver you have installed is a couple of years old...

10: kd> lmDvmrt640x64
Browse full module list
start             end                 module name
fffff805`6b0d0000 fffff805`6b1ea000   rt640x64   (deferred)          
    Image path: rt640x64.sys
    Image name: rt640x64.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Nov 11 12:24:02 2021 (618CEF42)
    CheckSum:         00127523
    ImageSize:        0011A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

I would certainly update those three drivers if you've not already done so.

You said that you've run a memory test? Which one did you run? RAM could be a common denominator here, so it's worth testing it properly. The Windows memory tester is very basic, a much better memory test is Memtest86. You use the extracted tool to create a bootable USB drive (it doesn't need to be large) containing Memtest. You then boot that USB drive and Memtest will start running. Allow it to complete all 4 iterations of the 13 tests. If no errors were found res-start Memtest and run another 4 iterations.

 

[geofelt]

Failure after a time smacks of a heat issue.
Run Hwmonitor or such to see the current, minimum and maximum cpu temperatures.

 

[heyb5]

Thanks for all the help. I've done everything that was posted. It was fine for a day and I ran in to another BSOD. I appreciate all the help!
Link: https://drive.google.com/drive/folders/1plW62BZ1sVGl0nrca-NsoHDdEnmINMIf?usp=sharing

 

[heyb5]

I've posted before with other minidumps, I didn't BSOD for a day but now it's back. I have updated many drivers ran many tests, sfcscan/memtest86/dism. I've also reinstalled graphics drivers fresh using DDU. I've also updated windows. I keep getting different BSODs. Wondering how I figure out if it's a hardware problem, cause the software problem just isn't making sense. Also, if anyone has any troubleshooting tips that would be helpful. Thanks.
Specs
CPU - Ryzen 7 2700X
Ram - 32gb Corsair Vengeance RGB Pro
MB - MSI B350 PC MATE
GPU - RTX 3060
PSU - EVGA bronze 550w
SSDs: ADATA SU800, Samsung 870 QVO
HDDs: WDC WD10EURX-63FH1Y0, WDC WD2003FYYS-70W0B0
New Dumps: https://drive.google.com/drive/folders/1plW62BZ1sVGl0nrca-NsoHDdEnmINMIf?usp=sharing

 

[Colif]

its still same problem, better to keep it in one thread. I let ubuysa answer since he is already

did you run memtest?

 

[ubuysa]

I wouldn't want to stop @Colif from posting, none of us know everything and we're only strong as a collective.

The three latest dumps (from Sunday 23rd) point in two different directions - nothing is ever easy!

Two dumps (042323-9390-01.dmp and 042323-11093-01.dmp) contain nvlddmkm.sys, the Nvidia graphics driver, on the call stack. One of those two dumps (042323-11093-01.dmp) also contains EastAntiCheat.sys on the call stack, and that's a well known cause of BSODs, as I've mentioned. Your version of nvlddmkm.sys seems current, it's dated April 8th 2023...

6: kd> lmDvmnvlddmkm
Browse full module list
start             end                 module name
fffff804`7b9f0000 fffff804`7f287000   nvlddmkm   (deferred)          
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Sat Apr  8 10:19:44 2023 (64311590)
    CheckSum:         0378E805
    ImageSize:        03897000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Often with graphics driver issues it's useful to also try each of the two previous versions (using DDU each time).

The version of EasyAntiCheat hasn't changed, it's still Dec 2022...

14: kd> lmDvmEasyAntiCheat
Browse full module list
start             end                 module name
fffff805`2c400000 fffff805`2d15c000   EasyAntiCheat T (no symbols)        
    Loaded symbol image file: EasyAntiCheat.sys
    Image path: EasyAntiCheat.sys
    Image name: EasyAntiCheat.sys
    Browse all global symbols  functions  data
    Timestamp:        Wed Dec  7 14:56:16 2022 (63908D70)
    CheckSum:         00D464DA
    ImageSize:        00D5C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Was there no update for this available? Because it's a known cause of BSODs this still must be very suspect.

The third dump (042423-9640-01.dmp) failed during a networking operation, the Windows drivers NETIO.sys and tcpip.sys are on the call stack (but being Windows drivers they are not at fault). You have updated the LAN driver rt640x64.sys, it's now dated October 14th 2022...

6: kd> lmDvmrt640x64
Browse full module list
start             end                 module name
fffff804`6ee70000 fffff804`6ef91000   rt640x64 T (no symbols)        
    Loaded symbol image file: rt640x64.sys
    Image path: rt640x64.sys
    Image name: rt640x64.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Oct 14 12:12:15 2022 (634927EF)
    CheckSum:         0012C317
    ImageSize:        00121000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

In addition, the 042323-9390-01.dmp dump also contains networking calls (ndis.sys, tcpip.sys and afd.sys are all on the call stack) in addition to the graphics driver calls (to nvlddmkm.sys).

The support site for your motherboard contains a LAN driver dated 30th Dec 2022 (10.62.824.2022). That looks to be a few days later than the version you have? There is also a chipset driver update there dated 24th Feb 2023, and an AMD graphics driver update also dated 24th Feb 2023.

There is also a BIOS update (which is in Beta) dated 15th July 2022 (version 7A34vAN5(Beta version)) which contains AMD AGESA support. Keeping AGESA support updated can be important for AMD CPUs. You might want to consider that?

I would certainly update the chipset drivers, the LAN driver, and EasyAntiCheat (if you can) and try the the immediately previous versions of the Nvidia graphics driver. It would be very useful if you can possibly uninstall EasyAntiCheat (even for a time) to see whether the BSODs stop. It's always the prime suspect when we find it on the call stack of a BSOD dump.

 

[Colif]

i think I gave him link to the newest realtek LAN driver already

Update LAN drivers:
Download Win10 Auto Installation Program (NDIS) from under windows header here - https://www.realtek.com/en/componen...0-1000m-gigabit-ethernet-pci-express-software

i also gave him link to chipset drivers in same post

try updating chipset drivers - https://www.amd.com/en/support/chipsets/amd-socket-am4/b350

I was just staying out as its often easier if they only following 1 persons instructions and not many

 

[heyb5]

After searching a lot on google I think I've come to the conclusion it is most likely EasyAntiCheat at fault. I found a very long LostArk forum post about many people having this problem. I've also not had a single BSOD when I am not playing LOA. I will try things when I get home but the repair for EAC did not work when I tried the last time. I also reinstalled the game completely already. I'm going to try to delete the EAC.sys file and have it reinstall and see if anything happens after that. I'll update all the drivers you guys have mentioned as well. I went through and installed all of the ones suggested but I guess I did some wrong. Again thanks for the help, if there's any suggestions that might be triggering EAC I would appreciate that a lot.
Edit: Could something be interfering with EAC, I've already uninstalled virus protection programs that could interfere. Is there anything else?

 

[heyb5]

its still same problem, better to keep it in one thread. I let ubuysa answer since he is already

did you run memtest?

I have run memtest twice with all passes both times.

 

[ubuysa]

EAC is a regular causer of BSODs, we see it often in memory dumps. It's not just EAC either, all of the anticheat 'tools' have been seen to cause BSODs. I don't game, so I know next to nothing about them, except that I see them in memory dumps!