[SOLVED] BSOD Loop On Startup (WhoCrashed report added)

[HtmHell]

For a while now I have this issue: when I boot my PC, the first windows loading icon appears on a black screen (usual behavior, then it should be replaced with lock screen), and after a few seconds of loading I get BSOD. After that my PC gets restarted and goes to "Diagnosing your PC", it goes through the process, and does nothing. Then I restart the PC, and it happens all over again. Same happens in a loop until after n times (n changes, no constant number of times), sometimes it takes 5 minutes, sometimes 20. (I don't wait for the "diagnosing" process anymore, I just restart)
After n times suddenly it doesn't go to BSOD, and everything is working as it should.

Since it started happening I upgraded my windows several times (which sucks because I have to turn off the PC), and also updated my GPU drivers multiple times.
I also downloaded "Who Crashed" which says an "unknown module" caused the crash. Here's a screenshot:

For now I just take my PC into sleep mode so I don't have to go through all that everyday.
Any suggestions before I give up and reinstall Windows?

 

[Colif]

how big is the memory.dmp file in C:/windows as if its not several GB you could upload it. Who crashed should have set up a folder in C:/windows/minidump so see if anything in there now.

if you can't boot and keep getting that behavior on restart, I would clean install as windows is pretty much borked. You could try a reset instead first.

You are 2 versions behind win 10 now anyway, you on 1809 and we on 1909, so if you do clean install, download the Windows 10 media creation tool and use it to make a win 10 installer on USB, so you on latest version.

 

[HtmHell]

how big is the memory.dmp file in C:/windows as if its not several GB you could upload it. Who crashed should have set up a folder in C:/windows/minidump so see if anything in there now.

if you can't boot and keep getting that behavior on restart, I would clean install as windows is pretty much borked. You could try a reset instead first.

You are 2 versions behind win 10 now anyway, you on 1809 and we on 1909, so if you do clean install, download the Windows 10 media creation tool and use it to make a win 10 installer on USB, so you on latest version.

My minidump folder is empty.
Here's the MEMORY.DMP file:
https://www.mediafire.com/file/5bdlqwlha44rmek/MEMORY.DMP/file

Thank you for helping!

 

[Colif]

i have sent link to a friend, he will reply in the next few hours. His internet isn't very fast so 695mb might take a while.

I voted and then changed my mind but I can't not vote so its remembered my initial reaction.

 

[gardenman]

It took me 45 mins to download and 2 seconds to determine that the file is corrupt and that I can't read it. Sorry.

See if you have any minidump files in C:\Windows\Minidump and upload those and I'll have a look at those.

 

[HtmHell]

It took me 45 mins to download and 2 seconds to determine that the file is corrupt and that I can't read it. Sorry.

See if you have any minidump files in C:\Windows\Minidump and upload those and I'll have a look at those.

I really appreciate your time, thank you. Unfortunately, my Minidump folder is empty. I've changed windows settings to small memory dump following this tutorial.

I will reply you again later with results if that's ok?

 

[gardenman]

Take your time, we'll be here.

 

[HtmHell]

Take your time, we'll be here.

Thank you!
I restarted my PC to get this error, and I did (multiple times)
One file showed up inside the Minidump folder (180 KB):
https://www.mediafire.com/file/nlw5gziloveyj8v/012320-10656-01.dmp/file

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://folksierear.htmlpasta.com/

File information:	012320-10656-01.dmp (Jan 22 2020 - 18:41:41)
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 03 Sec(s)

BIOS info was not included in the dump file. This can sometimes mean an outdated BIOS is being used.

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck. (Colif will likely reply later).

 

[Colif]

Have you gone to the Gigabyte website for motherboard and installed the Gigabyte App Centre? Its the top app here, you probably don't need the utilities but any drivers it offers are of use - https://www.gigabyte.com/au/Motherboard/GA-AB350-Gaming-rev-1x/support#support-dl-utility

You only have 1 driver installed

un 19 2019

amdpsp.sys

Advanced Micro Devices, Inc

so its quite possible the errors caused by missing drivers.

Error occurred in WIndows Hyper V, not sure why it was creating virtual machines.

 

[HtmHell]

I ran the dump file through the debugger and got the following information: https://folksierear.htmlpasta.com/

File information:	012320-10656-01.dmp (Jan 22 2020 - 18:41:41)
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 03 Sec(s)

BIOS info was not included in the dump file. This can sometimes mean an outdated BIOS is being used.

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck. (Colif will likely reply later).

Thank you!

Have you gone to the Gigabyte website for motherboard and installed the Gigabyte App Centre? Its the top app here, you probably don't need the utilities but any drivers it offers are of use - https://www.gigabyte.com/au/Motherboard/GA-AB350-Gaming-rev-1x/support#support-dl-utility

You only have 1 driver installed

un 19 2019

amdpsp.sys

Advanced Micro Devices, Inc

so its quite possible the errors caused by missing drivers.

Error occurred in WIndows Hyper V, not sure why it was creating virtual machines.

I didn't have it installed, just installed it. It doesn't look there is much to it tho.
Should I download all drivers from the link you provided then? Audio, Chipset, LAN, SATA

About virtual machines: I develop mobile apps so I have AVD (android emulator) is this causing the issues?

Thank you for helping

 

[Colif]

Win 10 likely using its own drivers for sound and lan. oir at least copies of realtek drivers that were supplied to it.
You have the newest AMD driver. it's just odd having no other drivers, you might actually have all you need. I should have looked at list.

I don't understand the dump text results well enough to know if that is case, I just found winhvr is one of the last processes run before it crashed. Its the Windows Hypervisor Root Interface driver (Microsoft) . It could be related - https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/about/

If you crash again. share the dumps. We see if it shows anymore.

 

[HtmHell]

Win 10 likely using its own drivers for sound and lan. oir at least copies of realtek drivers that were supplied to it.
You have the newest AMD driver. it's just odd having no other drivers, you might actually have all you need. I should have looked at list.

I don't understand the dump text results well enough to know if that is case, I just found winhvr is one of the last processes run before it crashed. Its the Windows Hypervisor Root Interface driver (Microsoft) . It could be related - https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/about/

If you crash again. share the dumps. We see if it shows anymore.

Thank you for helping,
I got another crash, I still have only one file in the minidump folder,
but it was modified. Here's the updated file:
https://www.mediafire.com/file/m7xljc5x6k4tk8e/012920-14796-01.dmp/file

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://advertentwildboar.htmlpasta.com/

File information:	012920-14796-01.dmp (Jan 29 2020 - 03:51:15)
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 03 Sec(s)

@Colif, I think the dump shows just the driver(s) loaded at the time of the crash. He could (and probably does) have many more drivers installed. Note the uptime of both of the dump files. PC was still loading.

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

 

[Colif]

Heatwave + possible bushfire in city was enough to delay this reply

@Colif, I think the dump shows just the driver(s) loaded at the time of the crash. He could (and probably does) have many more drivers installed. Note the uptime of both of the dump files. PC was still loading.

now you tell me

lets see if you are right

OP - Can you download and run Driverview - all it does is shows what drivers are installed
When you run it, go into view and set it to hide all Microsoft drivers, it will make the listing way shorter.
http://www.nirsoft.net/utils/driverview.html

Can you give me a screenshot From (and including) Driver name to (and including) Creation date (but only if you actually do have more than 1 driver listed (dump.sys files are Microsoft files, they always show)

upload to an image sharing website and show link here.

can you also run this as it might find more - https://www.sysnative.com/forums/pages/bsodcollectionapp/

 

[HtmHell]

@Colif Thank you for replying, I hope everything is OK at you city.

DriverView:

Sysnative:
https://www.mediafire.com/file/1tkrf1oe13d8hhs/SysnativeFileCollectionApp.zip/file

 

[Colif]

you could check to see if G Hub replaces LGS for your devices, and then uninstall LGS - https://www.logitechg.com/en-us/innovation/g-hub.html

Origin web helper sure likes top crash on your PC

what wifi card do you have? USB2? https://www.mediatek.com/products/broadbandWifi/rt5370
netr28ux.sys - Mediatek 802.11n wireless ADapter driver Version 5.1.22.0

regardless of its creation date in system, its actually a driver from at least Oct 2015. I suspect its a rebranded Win 8 driver that could be cause of the errors. This sort of proves it - https://drivers.softpedia.com/get/N...ediaTek-Wireless-Driver-51220-Windows-8.shtml

there maybe newer drivers for it but its more likely you need a newer Wifi adapter as they don't support old hardware for long if they stop making them and make newer things they expect you to buy.

 

[HtmHell]

you could check to see if G Hub replaces LGS for your devices, and then uninstall LGS - https://www.logitechg.com/en-us/innovation/g-hub.html

Origin web helper sure likes top crash on your PC

what wifi card do you have? USB2? https://www.mediatek.com/products/broadbandWifi/rt5370
netr28ux.sys - Mediatek 802.11n wireless ADapter driver Version 5.1.22.0

regardless of its creation date in system, its actually a driver from at least Oct 2015. I suspect its a rebranded Win 8 driver that could be cause of the errors. This sort of proves it - https://drivers.softpedia.com/get/N...ediaTek-Wireless-Driver-51220-Windows-8.shtml

there maybe newer drivers for it but its more likely you need a newer Wifi adapter as they don't support old hardware for long if they stop making them and make newer things they expect you to buy.

1. Done, uninstalled LGS and installed G-Hub instead.
2. What do you mean "Origin web helper" I have EA's Origin software installed. Should I try to uninstall?
3. It's probably have nothing to do with the network driver, because it happened to me a while back when I was using a LAN cable. Currently I'm temporary using a USB 2 wifi card because I'm not close to the router at the moment.

 

[Colif]

2. Yes, its part of Origin and it is why I went to looking at lan driver as I assumed the webhelper might be crashing because of the lan driver. I don't think the cause was Origin, I just noticed it was crashing a lot. It could be a coincidence it crashes at same time as you BSOD.

I normally look at old drivers for cause (apart from Nvidia, their newest drivers are suspect) and according to the driver list, this driver was created on 16th Nov 2017 and yet in the dumps its showing as 2019

Jun 19 2019

amdpsp.sys

Advanced Micro Devices

since its the only driver that shows in them.. but a brief search shows it is current version.

last 2 crashes you have given us dumps for both triggered by Hyper V - https://en.wikipedia.org/wiki/Hyper-V - but what is triggering it? Do you use Windows Defender? I vaguely remember something about the protected folders feature can use Hyper V. They both happened on a Wednesday so that error appears to be on a schedule

looking at sysnative file I see you been getting them almost every day this week? And should have more dumps for us?

Nvidia drivers crashed a few times but last one was on 29th Jan.

@PC Tailor do you mind looking at the sysnative file for me? you might see something my eyes can't. I am not sure if it is just a coincidence that Origin crashes at same time as the BSOD (as obviously, it doesn't list everything that crashes after a BSOD as we would be here all day reading sysinfo just for 1 crash). But its likely the victim as its an exe. Not many exe cause BSOD themselves. I am sure there are some.

 

[PC Tailor]

Only things really of note in some of the sysnative files from my less experienced view is:

802.11n USB Wireless LAN Card netr28ux.inf Ralink Technology, Corp. (along with realtek ethernet drivers) - But I believe OP stated they had the issue with a LAN card previously. Was the WiFi card not installed in the machine at all when this happened?

Ready Boost is also running which can cause issues.

I can see some application hangs, but they are likely unrelated:
Event[175]:- Log Name: Application- Source: Application Hang- AdobeNotificationClient.exe and MoApp crash.

Lastly all I'd say is having an "Unknown_Module" appear in dump files can indicate some hardware issues, if the unknown module keeps reappearing, less so if it's a one off, but if it's repetitive and there are any unknown modules in the dump file lmd list, then it can be more indicative of hardware.

As GM stated, have you installed latest BIOS?
Whilst I'm not jumping to hardware straight away, have you also tried running memtest? https://www.sysnative.com/forums/threads/test-ram-with-passmark-memtest86.24300/

 

[Colif]

Whocrashed appears to not be very good at identifying modules as I have seen that before and then GM would run ADA and it would Identify it. Wonder how often whocrashed is updated

I saw that adobe notification and the occasional Nvidia crash.

while i don't discount ram as cause, most ram errors are way more random and aren't the same error (if you look at 2 GM decoded, its basically same error twice, not just the code but the dump text is almost duplicated. 7 days apart.

I assume Op is on Win 10 Pro (or Edu) since Home doesn't include hyper v - https://docs.microsoft.com/en-us/vi...quick-start/enable-hyper-v#check-requirements

Windows Defender Application Guard (WDAG) is an enhanced security mode for the Edge browser that runs a minimal Windows shell on a 'slimmed down' Hyper-V instance that only runs Edge. this is a little out of date - https://www.techrepublic.com/article/how-virtualisation-is-changing-windows-application-security/

just trying to figure out why it started?

 

[HtmHell]

As GM stated, have you installed latest BIOS?

That was it... I had the F5 version from June 2017. I just updated the bios, and restarted the PC 4 times in a row,
so it's safe to say the issue is resolved!
@gardenman @Colif @PC Tailor thank you all guys, I really appreciate your help!

And just for curiosity, how often should I update the bios? or should I only do that when I'm getting issues?

 

[PC Tailor]

That was it... I had the F5 version from June 2017. I just updated the bios, and restarted the PC 4 times in a row,
so it's safe to say the issue is resolved!
@gardenman @Colif @PC Tailor thank you all guys, I really appreciate your help!

And just for curiosity, how often should I update the bios? or should I only do that when I'm getting issues?

When you're getting issues it's a route to consider. Most BIOS can be left alone without issue, but in circumstances it can create a "communication" problem between your hardware for want of a better phrase. So once you've eliminated other items, the BIOS is an easy check.