[SOLVED] PC having randoms BSODS

[AndrewM2019]

For the last couple of weeks my PC has been blue screening everyday, sometimes twice a day. First time it started was after my AMD driver update failed. I used DDU to uninstall any potential corrupt or faulty drivers before reinstalling the drivers successfully. Since then I have changed GPUs from an RX 560 4GB to a GTX 1060 6GB and have correctly installed the latest drivers for it.

I have had the UNEXPECTED_STORE_EXCEPTION, MEMORY_MANAGEMENT and CRITICAL_PROCESS_DIED stop codes. But at this point the only stop code I am receiving is the CRITICAL_PROCESS_DIED stop code. Today it even occured twice upon rebooting my PC with it hanging on the "100% Complete" screen.

I have also noticed on Passmark DiskCheckup that in the 'Device Info' section under 'Status' it is saying "Warning (Temperature warning level exceeded)". I do not know if this would be a contributing factor to why my PC is blue screening, but I thought I would include it anyway incase it would help.

I have included a link to a .zip of the two minidumps that were on my PC if they will help on why I am having so many blue screens. If anyone could help it would be very much appreciated.

Link to .zip of minidumps: https://ufile.io/umhzv27r

 

[Johnwmel]

"to the website that I've uploaded the image to"
Imgur or File Convoy are better sites ( no time delays/Captcha-I'm not a Robot/account/registration needed

Imgur

Imgur: The magic of the Internet

i.imgur.com

https://www.fileconvoy.com/

https://imgur.com/upload

View: https://imgur.com/upload

https://imgur.com/7UiiqWr

View: https://i.imgur.com/7UiiqWr.gif

https://imgur.com/6N1gfOj

View: https://i.imgur.com/6N1gfOj.gif

 

[Johnwmel]

Upload an SS of everything Snail finds, don't Update any drivers.

SnailDriver for PC's
https://www.softpedia.com/get/System/System-Miscellaneous/Snail-Driver.shtml

https://snailsuite.com/download-snaildriver

 

[Colif]

Actually just as I was turning the PC back on, it BSOD’d and gave me a BAD_SYSTEM_CONFIG_INFO stop code with the stick in slot #4 being the only one in. So I opened the PC up and took out the stick in slot #4 and put the stick in slot #2 back in. It BSOD’d again and gave me the CRITICAL_PROCESS_DIED stop code I was having before.

Sorry, I sort of assumed you knew which slot to run 1 stick of ram in, its normal for motherboards to have special ones that 1 stick should be put in to work.

Try running with other stick by itself and see if you still BSOD.

 

[AndrewM2019]

Sorry, I sort of assumed you knew which slot to run 1 stick of ram in, its normal for motherboards to have special ones that 1 stick should be put in to work.

Try running with other stick by itself and see if you still BSOD.

So run my first stick of RAM in the first slot?

 

[Colif]

Try both sticks in slot DIMMA2, if you have tried one already in that slot and it bsod, try the other one.
Page 6 shows that is right choice - https://download.msi.com/archive/mnu_exe/mb/E7B79v2.1-GSE-LITE.pdf

if 1 stick, DIMMA2 (from left, slot 2)
if 2 sticks, DIMMA2 & DIMMB2 (from left, slots 2 & 4)
if 4 sticks, obvious
not sure about 3 sticks, manuals never show.

 

[AndrewM2019]

Try both sticks in slot DIMMA2, if you have tried one already in that slot and it bsod, try the other one.
Page 6 shows that is right choice - https://download.msi.com/archive/mnu_exe/mb/E7B79v2.1-GSE-LITE.pdf

if 1 stick, DIMMA2 (from left, slot 2)
if 2 sticks, DIMMA2 & DIMMB2 (from left, slots 2 & 4)
if 4 sticks, obvious
not sure about 3 sticks, manuals never show.

Ok I’ll try that tomorrow after I wake up, as it’s pretty late where I am. Thanks for helping with me with this, I truly appreciate all the help regardless of how small it may be.

 

[AndrewM2019]

@Colif Hi, so I tried the other RAM stick in the correct slot this time and initially it loaded onto the desktop with no problems. Upon sitting on the desktop for about a minute, the PC BSOD’d with the same CRITICAL_PROCESS_DIED stop code as the first stick RAM

 

[Colif]

well, its probably not the ram but we had to try.

My friend probably still asleep and I have to go soon, but as soon as I see his conversion I might have something to work with.

critical process died likely needs a solution other than ram.

 

[AndrewM2019]

well, its probably not the ram but we had to try.

My friend probably still asleep and I have to go soon, but as soon as I see his conversion I might have something to work with.

critical process died likely needs a solution other than ram.

Ok no problem, at least we know it's not RAM now

 

[AndrewM2019]

Upload an SS of everything Snail finds, don't Update any drivers.

SnailDriver for PC's
https://www.softpedia.com/get/System/System-Miscellaneous/Snail-Driver.shtml

https://snailsuite.com/download-snaildriver

I'm not able to download from the softpedia link and the snailsuite.com link doesn't load

 

[Colif]

Upload an SS of everything Snail finds, don't Update any drivers.

SnailDriver for PC's
https://www.softpedia.com/get/System/System-Miscellaneous/Snail-Driver.shtml

https://snailsuite.com/download-snaildriver

this program is a 3rd party driver updater, I know you say not to install any but its still a temptation. I don't like 3rd party driver updaters as they make mistakes and people have to jump through hoops to get PC working again.

I know you think http://www.nirsoft.net/utils/driverview.html is the same thing, but difference is, it only looks. It doesn't install. It can't install. You have to actually look at what PC has and go find newer versions of those drivers. If you go to makers websites and not some of the sites on web that have many drivers for everyone (which are just as trustworthy as Driver booster and other 3rd party updaters), you are likely to get right drivers.

@AndrewM2019 the dump conversions by Gardenman show what drivers are running

Mar 14 2016	amdgpio3.sys	AMD GPIO Controller Driver from Advanced Micro Devices http://support.amd.com/
Oct 11 2017	YSDrv.sys	VirtualBox Support driver
Aug 14 2018	rtwlane.sys	Realtek PCI-E Wireless LAN NIC NDIS driver https://www.realtek.com/en/
May 24 2019	rt640x64.sys	Realtek NICDRV 8169 PCIe GBE Family Controller driver https://www.realtek.com/en/
Jan 17 2020	Nahimic_Mirroring.sys	Nahimic driver https://www.nahimic.com/
Mar 06 2020	amdpsp.sys	Advanced Micro Devices, Inc http://support.amd.com/
Mar 11 2020	amdgpio2.sys	AMD GPIO Controller Driver from Advanced Micro Devices http://support.amd.com/
Aug 17 2020	RzDev_0203.sys	Razer driver
Oct 16 2020	nvhda64v.sys	Nvidia HDMI Audio Device http://www.nvidia.com/
Jan 13 2021	AMDPCIDev.sys	Advanced Micro Devices PCI Device driver
Mar 30 2021	RzCommon.sys	Razer Common driver (Razer Inc)
Apr 23 2021	nvlddmkm.sys	Nvidia Graphics Card driver http://www.nvidia.com/

those ones were in first lot of bsod. Not sure about latest.

 

[AndrewM2019]

this program is a 3rd party driver updater, I know you say not to install any but its still a temptation. I don't like 3rd party driver updaters as they make mistakes and people have to jump through hoops to get PC working again.

I know you think http://www.nirsoft.net/utils/driverview.html is the same thing, but difference is, it only looks. It doesn't install. It can't install. You have to actually look at what PC has and go find newer versions of those drivers. If you go to makers websites and not some of the sites on web that have many drivers for everyone (which are just as trustworthy as Driver booster and other 3rd party updaters), you are likely to get right drivers.

@AndrewM2019 the dump conversions by Gardenman show what drivers are running

Mar 14 2016	amdgpio3.sys	AMD GPIO Controller Driver from Advanced Micro Devices http://support.amd.com/
Oct 11 2017	YSDrv.sys	VirtualBox Support driver
Aug 14 2018	rtwlane.sys	Realtek PCI-E Wireless LAN NIC NDIS driver https://www.realtek.com/en/
May 24 2019	rt640x64.sys	Realtek NICDRV 8169 PCIe GBE Family Controller driver https://www.realtek.com/en/
Jan 17 2020	Nahimic_Mirroring.sys	Nahimic driver https://www.nahimic.com/
Mar 06 2020	amdpsp.sys	Advanced Micro Devices, Inc http://support.amd.com/
Mar 11 2020	amdgpio2.sys	AMD GPIO Controller Driver from Advanced Micro Devices http://support.amd.com/
Aug 17 2020	RzDev_0203.sys	Razer driver
Oct 16 2020	nvhda64v.sys	Nvidia HDMI Audio Device http://www.nvidia.com/
Jan 13 2021	AMDPCIDev.sys	Advanced Micro Devices PCI Device driver
Mar 30 2021	RzCommon.sys	Razer Common driver (Razer Inc)
Apr 23 2021	nvlddmkm.sys	Nvidia Graphics Card driver http://www.nvidia.com/

those ones were in first lot of bsod. Not sure about latest.

Do you want me to send my latest dumps over? or should I try making sure these drivers are up-to-date?

 

[Colif]

just send dumps, i only showed list to show you don't need to run that snail to see what drivers are actually running. thats not all the drivers, its just the non windows ones. You can't update the windows ones, so no point seeing them - They all installed by Microsoft.

 

[AndrewM2019]

just send dumps, i only showed list to show you don't need to run that snail to see what drivers are actually running. thats not all the drivers, its just the non windows ones. You can't update the windows ones, so no point seeing them - They all installed by Microsoft.

Ok that's fine, here are the latest dumps:

https://ufile.io/7rd128yu

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/me3tfbq2/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:	050921-40078-01.dmp (May 9 2021 - 09:11:18)
Bugcheck:	CRITICAL_PROCESS_DIED (EF)
Probably caused by:	ntkrnlmp.exe (Process: svchost.exe)
Uptime:	0 Day(s), 0 Hour(s), 03 Min(s), and 42 Sec(s)

File information:	050921-37343-01.dmp (May 9 2021 - 08:55:02)
Bugcheck:	CRITICAL_PROCESS_DIED (EF)
Probably caused by:	ntkrnlmp.exe (Process: svchost.exe)
Uptime:	0 Day(s), 0 Hour(s), 03 Min(s), and 08 Sec(s)

File information:	050921-33421-01.dmp (May 9 2021 - 09:05:28)
Bugcheck:	CRITICAL_PROCESS_DIED (EF)
Probably caused by:	ntkrnlmp.exe (Process: svchost.exe)
Uptime:	0 Day(s), 0 Hour(s), 03 Min(s), and 21 Sec(s)

File information:	050921-29125-01.dmp (May 8 2021 - 21:43:40)
Bugcheck:	CRITICAL_PROCESS_DIED (EF)
Probably caused by:	ntkrnlmp.exe (Process: svchost.exe)
Uptime:	0 Day(s), 0 Hour(s), 00 Min(s), and 47 Sec(s)

File information:	050921-24640-01.dmp (May 8 2021 - 21:46:26)
Bugcheck:	CRITICAL_PROCESS_DIED (EF)
Probably caused by:	ntkrnlmp.exe (Process: services.exe)
Uptime:	0 Day(s), 0 Hour(s), 02 Min(s), and 12 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.

 

[Johnwmel]

How to fix the 'CRITICAL_PROCESS_DIED' error in Windows 10 - 0x000000EF - Troubleshooting Central

What is the 'CRITICAL_PROCESS_DIED' error? The occasional Blue Screen of Death (BSoD) has plagued us all over the years of Windows’ existence. BSoDs are

www.troubleshootingcentral.com

How To Fix Critical_Process_Died Error In Windows | WhatsaByte

If you are encountering a Blue Screen Of Death error with this message: Critical_Process_Died, then take a few minutes to read this step-by-step guide, it

whatsabyte.com

How to Fix "Critical Process Died" in Windows 10

The "critical process died" stop code is one of the most undesirable sights for a Windows user. Here's how to fix it in a few easy steps.

www.makeuseof.com

How to Fix ‘CRITICAL_PROCESS_DIED’ BSoD Error? | WHATT.ORG

The ‘CRITICAL_PROCESS_DIED’ error is a type of Window 10 Blue Screen of Death(BSoD). Let's take a look at possible ‘CRITICAL_PROCESS_DIED’ error ✅ fixes.

whatt.org

Fix Critical Process Died in Windows 10 Error - gHacks Tech News

The following troubleshooting guide provides you with information on the Windows 10 Blue Screen of Death (BSod) error Critical_Process_Died.

www.ghacks.net

https://www.partitionwizard.com/partitionmagic/critical-process-died.html

 

[AndrewM2019]

So PC has managed to go more than 24hrs without BSODing, not sure if anything has changed as I haven't installed or uninstalled anything. I'll monitor how things go and see what happens.

 

[Colif]

I had a headache yesterday so didn't look in here

If you stop crashing completely, don't do this:

it could be a driver still

every crash starts after
nt!KiPageFault+0x443
page faults are normal operations of windows, they occur when cpu doesn't have the info it needs and looks in ram. this could mean its the same driver all 5 times or that area of ram is problem

as is usual with me, I skipped a step
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

I know you bsod off both sticks but that doesn't prove they are not the problem really

I feel its still a driver but the means of finding that out can be dangerous for windows to run, and its part of windows - https://forums.tomshardware.com/threads/driver-verifier-instructions.3686888/

 

[AndrewM2019]

I had a headache yesterday so didn't look in here

If you stop crashing completely, don't do this:

it could be a driver still

every crash starts after
nt!KiPageFault+0x443
page faults are normal operations of windows, they occur when cpu doesn't have the info it needs and looks in ram. this could mean its the same driver all 5 times or that area of ram is problem

as is usual with me, I skipped a step
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

I know you bsod off both sticks but that doesn't prove they are not the problem really

I feel its still a driver but the means of finding that out can be dangerous for windows to run, and its part of windows - https://forums.tomshardware.com/threads/driver-verifier-instructions.3686888/

That’s fine don’t worry about it. I’ll see how it runs tomorrow and report back if there’s still no more BSODs. I restarted it today and it didn’t BSOD either which is good. As for Memtest86, I have that in a USB already so I can test that out. We’ll see what happens over the next 24hrs or so.