[SOLVED] CRITICAL_PROCESS_DIED BSODs while gaming

[sooraj2906]

Hey guys, So, I've been facing BSODs while gaming for a few days now. Not sure of the reasons.
Things I've tried:

• Reinstall Windows
• DDU GPU drivers
• Run memtest overnight - Reported no errors
• Changed my ram sticks to a different set of sticks
• Removed any overclocks/underclocks to CPU/GPU
• Ran tests of HDD and SSD using their respective manufacturer's tools - Returned no errors in both short and long tests
• Used Driver verifier - Crashed with vgk.sys -uninstalled vanguard and valorant, crashed with intelhaxm.sys - uninstalled intel haxm. When back to windows still bsods happening while gaming.

I've attached the recent 5 minidumps - https://www.mediafire.com/file/tglh5vka6g8mnn4/MiniDumps.zip/file
Also I'm not sure if this is related to this or not but I use my GPU for mining and once in a while the nvidia driver will crash and recover automatically. When checked with Event Viewer, it showed -

"
The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\00000091
21b6(3234) 00000000 00000000

The message resource is present but the message was not found in the message table
"

The \Device\00000091 || 21b6(3234) 00000000 00000000 part changes in every crash.
Hoping you guys can help in any way. Thanks in advance!

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/91rs58m6/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:	051822-9187-01.dmp (May 18 2022 - 12:15:11)
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), 01 Min(s), and 20 Sec(s)

File information:	051822-8171-01.dmp (May 18 2022 - 13:29:34)
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), 01 Min(s), and 44 Sec(s)

File information:	051822-17187-01.dmp (May 18 2022 - 11:47:45)
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), 04 Min(s), and 13 Sec(s)

File information:	051822-12546-01.dmp (May 18 2022 - 11:59:31)
Bugcheck:	CRITICAL_PROCESS_DIED (EF)
Probably caused by:	memory_corruption (Process running at time of crash: services.exe)
Uptime:	0 Day(s), 0 Hour(s), 02 Min(s), and 02 Sec(s)

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

Possible Motherboard page: https://www.gigabyte.com/Motherboard/Z390-AORUS-PRO-rev-10#kf
You are using the latest BIOS, version F12.

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]

right click start button
choose powershell (admin)
copy/paste this command into window:
Repair-WindowsImage -Online -RestoreHealth
and press enter
Then type SFC /scannow
and press enter
Restart PC if SFC fixes any files as some fixes require a restart to be implemented
First command repairs the files SFC uses to clean files, and SFC fixes system files
SFC = System File Checker. First command runs DISM - https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/what-is-dism?view=windows-11

Do you use WIFI or Ethernet cable?
try running this and see if it offers any new drivers, your Ethernet drivers are old - https://www.intel.com.au/content/www/au/en/support/intel-driver-support-assistant.html