Question Continuous BSOD after boot

Thomskn

Reputable
Jan 13, 2016
27
2
4,535
0
Since a few days I have been getting BSODs almost immediately after booting into windows. The error message most of the time is memory_management. When using safe mode with networking the BSOD happens, but slightly later than in normal mode. When I use safe mode without networking the crash does not seem to happen at all. Therefore my suspicion is a faulty network driver. However, I have tried to disable networking in the BIOS and then boot into windows normally but the crash still happens. Trying to re-install the driver also did not seem to work. Here's a link to my onedrive folder with the minidump files: https://1drv.ms/u/s!AlnLiZsV-9O4geRmcWMbyA_VxYQKVQ?e=Xgr8sl

Hope you guys can help! :)
 

PC Tailor

Judicious
Ambassador
When using safe mode with networking the BSOD happens
This is one of the big ones for me. If it's still occuring in safe mode, it's not going to be a third party driver unless it's a network one.

Having a look through anyway:
Bugcheck code 0000001A (Memory Management) x 8
Bugcheck code 1000007E (System thread exception)
Bugcheck code 00000050 (Page Fault)
Bugcheck code 0000001E (Kmode exception)

There is one that refers back to your graphics, however I wouldn't expect this to be as much an issue in safe mode. Being as so many are memory management and don't necessarily relate back to third party drivers, I'd perform memtest with at least 4 passes: https://www.tomshardware.com/uk/how-to/how-to-test-ram just to make sure early.

Have you also run safe mode without networking?
 

Thomskn

Reputable
Jan 13, 2016
27
2
4,535
0
Being as so many are memory management and don't necessarily relate back to third party drivers, I'd perform memtest with at least 4 passes: https://www.tomshardware.com/uk/how-to/how-to-test-ram just to make sure early.

Have you also run safe mode without networking?
I have done full runs of MemTest86 maybe two months ago when I had other issues and ended up reinstalling windows, so I'm assuming RAM is okay but I can try nonetheless.
As stated I have run safe mode without networking, and this seems to work (no crashes)
 

PC Tailor

Judicious
Ambassador
I have done full runs of MemTest86 maybe two months ago when I had other issues and ended up reinstalling windows, so I'm assuming RAM is okay but I can try nonetheless.
As stated I have run safe mode without networking, and this seems to work (no crashes)
my apologies I missed the without networking bit.

It could be the network driver, it could also be other hardware accessing the network which can be causing a fault. Where were you downloading the latest network driver from?
 

Thomskn

Reputable
Jan 13, 2016
27
2
4,535
0
my apologies I missed the without networking bit.

It could be the network driver, it could also be other hardware accessing the network which can be causing a fault. Where were you downloading the latest network driver from?
The driver utility called driver talent
 

Thomskn

Reputable
Jan 13, 2016
27
2
4,535
0
Yeah don't use driver updater apps, they have a notorious habit of getting them wrong and causing a lot of issues. Go directly to the manufacturer and download the latest drivers from there. For yourself it'll be your motherboard support page.
Thank you for the tip, will try in the morning
 
Reactions: PC Tailor

Thomskn

Reputable
Jan 13, 2016
27
2
4,535
0
Yeah don't use driver updater apps, they have a notorious habit of getting them wrong and causing a lot of issues. Go directly to the manufacturer and download the latest drivers from there. For yourself it'll be your motherboard support page.
Downloaded and installed from the mobo manufacturer's website and no crashes, so, solved!
 
Reactions: PC Tailor

Thomskn

Reputable
Jan 13, 2016
27
2
4,535
0
Yeah don't use driver updater apps, they have a notorious habit of getting them wrong and causing a lot of issues. Go directly to the manufacturer and download the latest drivers from there. For yourself it'll be your motherboard support page.
So this morning it crashed again. It worked for a full day. I gamed online, was able to browse the internet and downloaded things. However, this morning one of my tabs crashed and quickly after that I got the BSOD again. Looking at the dump files the same error happened again. Again safe mode with networking works just fine.
 

PC Tailor

Judicious
Ambassador
So this morning it crashed again. It worked for a full day. I gamed online, was able to browse the internet and downloaded things. However, this morning one of my tabs crashed and quickly after that I got the BSOD again. Looking at the dump files the same error happened again. Again safe mode with networking works just fine.
Can you post the new minidump files? Each new one is more info for us to work with :)
 

PC Tailor

Judicious
Ambassador
No problem at all my friend, I just want to help you get back up and running and BSOD are not an exact science and require trial and error. So I've looked at the latest ones:

Code:
Bugcheck code 0000001A (Memory_Management)
Bugcheck code 0000001A (Memory_Management)
Bugcheck code 0000001A (Memory_Management)
Bugcheck code 000001c7 (STORE_DATA_STRUCTURE_CORRUPTION)
Now the last one is a bit more interesting and perhaps does shed a little bit more light. So all of these first of all can indeed be caused by faulty drivers.

However on inspection, there doesn't appear to be any obvious third party drivers leading up to the crash, just plenty of loaded third party drivers running generally.

Code:
3ware.sys                   Mon May 18 23:28:03 2015 (555A6773)
ADP80XX.SYS                 Thu Apr  9 21:49:48 2015 (5526E5EC)
AMDPCIDev.sys               Tue Mar  3 05:28:00 2020 (5E5DEAE0)
AtihdWT6.sys                Mon Feb 24 20:48:15 2020 (5E54368F)
HpSAMD.sys                  Tue Mar 26 21:36:54 2013 (515214F6)
ItSas35i.sys                Thu Jun 20 08:35:34 2019 (5D0B3746)
LGBusEnum.sys               Mon Jun 13 19:47:08 2016 (575EFFAC)
LGJoyXlCore.sys             Mon Jun 13 19:47:06 2016 (575EFFAA)
LGVirHid.sys                Mon Jun 13 19:47:03 2016 (575EFFA7)
MegaSas2i.sys               Thu Apr  4 14:28:53 2019 (5CA60695)
RTCore64.sys                Thu Sep 19 11:45:31 2019 (5D835C4B)
Rt630x64.sys                Fri Dec 28 00:04:06 2012 (50DCE1F6)
SiSRaid2.sys                Wed Sep 24 19:28:20 2008 (48DA86C4)
SmartSAMD.sys               Thu Feb 21 17:54:44 2019 (5C6EE5E4)
amdgpio2.sys                Mon Sep 30 04:56:01 2019 (5D917CD1)
amdgpio3.sys                Mon Mar 14 10:19:36 2016 (56E69038)
amdkmdag.sys                Mon May 25 19:41:44 2020 (5ECC1168)
amdkmpfd.sys                Thu Jan 16 19:05:42 2020 (5E20B406)
amdlog.sys                  Thu Apr 30 18:24:23 2020 (5EAB09C7)
amdsata.sys                 Thu May 14 13:14:52 2015 (555491BC)
amdsbs.sys                  Tue Dec 11 21:21:44 2012 (50C7A3E8)
amdxata.sys                 Fri May  1 01:55:35 2015 (5542CF07)
amdxe.sys                   Thu Mar 26 14:43:11 2020 (5E7CBF7F)
arcsas.sys                  Thu Apr  9 20:12:07 2015 (5526CF07)
bxvbda.sys                  Wed May 25 08:03:08 2016 (57454E2C)
cht4sx64.sys                Tue Feb  5 13:51:31 2019 (5C5994E3)
evbda.sys                   Wed May 25 08:01:05 2016 (57454DB1)
iaStorAVC.sys               Thu Sep  5 13:07:32 2019 (5D70FA84)
iaStorV.sys                 Mon Apr 11 19:48:16 2011 (4DA34CF0)
ladfGSS.sys                 Fri Dec  9 02:38:49 2016 (584A1939)
lgcoretemp.sys              Tue Jun  9 17:52:10 2015 (557719BA)
lsi_sas.sys                 Wed Mar 25 19:36:48 2015 (55130E50)
lsi_sas2i.sys               Wed Aug  2 14:29:59 2017 (5981D3D7)
lsi_sas3i.sys               Thu Apr  4 07:54:35 2019 (5CA5AA2B)
lsi_sss.sys                 Fri Mar 15 23:39:38 2013 (5143B13A)
megasas.sys                 Thu Mar  5 02:36:29 2015 (54F7C12D)
megasas35i.sys              Thu Jun 20 11:01:12 2019 (5D0B5968)
megasr.sys                  Mon Jun  3 23:02:39 2013 (51AD127F)
mvumis.sys                  Fri May 23 21:39:04 2014 (537FB1E8)
nvraid.sys                  Mon Apr 21 19:28:42 2014 (5355635A)
nvstor.sys                  Mon Apr 21 19:34:03 2014 (5355649B)
percsas2i.sys               Tue Mar 15 00:50:11 2016 (56E75C43)
percsas3i.sys               Fri Jun  1 22:47:02 2018 (5B11BED6)
rt640x64.sys                Mon Nov 18 09:14:08 2019 (5DD260E0)
rtwlane.sys                 Tue Jan  6 03:52:41 2015 (54AB5C09)
sisraid4.sys                Wed Oct  1 22:56:04 2008 (48E3F1F4)
stexstor.sys                Tue Nov 27 00:02:51 2012 (50B4032B)
t_mouse.sys                 Mon Dec  3 06:19:30 2012 (50BC4472)
tapwindscribe0901.sys       Thu Mar 16 21:37:54 2017 (58CB05B2)
vsmraid.sys                 Tue Apr 22 20:21:41 2014 (5356C145)
vstxraid.sys                Mon Jan 21 19:00:28 2013 (50FD904C)
There does also seem to be a few references to hardware issues. Whilst these don't immediately mean it's hardware, it could be correct:

Code:
MODULE_NAME: hardware
IMAGE_NAME:  memory_corruption
However the last bugcheck is usually caused by 3 things:
  1. Defective RAM.
  2. A driver misbehaving.
  3. Corruption from hardware or firmware.
Purely based off the fact that nothing OBVIOUS is coming out through 3rd party drivers, and that it is fairly easy to test, I would test your RAM as per this guide: https://www.sysnative.com/forums/threads/test-ram-with-passmark-memtest86.24300/

There is still possibility of this being driver based, but I think the above is the best and easiest next step, do you know if you were able to revert all driver downloads made by your app? It could have residual conflciting ones leftover. It's why it's recommended to perform system restores before bulk updating drivers through apps.
 
Feb 23, 2020
5
0
10
0
Maybe a long shot but, i had quite similar problem, getting constant BSODs everytime.

Dumps would tell diferrent story from video drivers, to sound drivers ect... what was the problem was Rams. Even memtests never found any problems with ram.
I had 2 sticks 2x8 they were same model,speed, manufacturer, ect. But they just didnt work together, so what did the job, just removing 1 stick completely. No more BSOD
 

Thomskn

Reputable
Jan 13, 2016
27
2
4,535
0
Purely based off the fact that nothing OBVIOUS is coming out through 3rd party drivers, and that it is fairly easy to test, I would test your RAM as per this guide: https://www.sysnative.com/forums/threads/test-ram-with-passmark-memtest86.24300/

There is still possibility of this being driver based, but I think the above is the best and easiest next step, do you know if you were able to revert all driver downloads made by your app? It could have residual conflciting ones leftover. It's why it's recommended to perform system restores before bulk updating drivers through apps.
I did the MemTest86, in three configurations. My standard set-up (2x4) and then twice a single stick. No errors, the reports are in the onedrive folder though I seem to have forgotten to save a report of the last one (single stick configuration).

So the driver app was used in safe mode without networking, purely to install the network driver since the app had the network drivers in the installer, so it was not able to complete the scan and did not enable me to download anything. Also considering that the original crashes happened before any driver update app was used and that I removed it once I thought it was fixed I would assume that, besides it installing an outdated network driver, it did no harm.
 

PC Tailor

Judicious
Ambassador
I'm wondering if @gardenman is better suited to run these being as there are a collection of dump files. I can unfortunately, only process 1 at a time to give a reported output at the moment. But i've run the latest dump file in your onedrive (latest date stamp anyway) one just for reference...

I have run the dump file(s) and you can see the full report(s) in the link below.
If you are prompted to ""Run only if trusted"" simply click play/run and the html will be viewed. This warning is always present."

Report: https://jsfiddle.net/j9y4a67t/show

Summary of findings:
MEMORY_MANAGEMENT
"Running the Windows Memory Diagnostic tool or memtest could be useful as well to exclude any kind of problem affecting the physical memory modules.

This can be driver or hardware based. If you are encountering other hardware issues, you may have to look at hardware diagnosis.

  • Confirm that hardware is compatible with your system.
  • View the third party modules of the report to view which drivers may be misbehaving."
So just to point out the drivers that appear as though they could be out of date:
t_mouse.sys03/12/2012iBalliBall Mouse Driver
Rt630x64.sys28/12/2012RealtekPCI/PCIe Adapter Driver
rtwlane.sys06/01/2015RealtekRealtek PCI-E Wireless LAN NIC NDIS Driver
lgcoretemp.sys09/06/2015LogitechLogitech Gaming Software Driver
amdgpio3.sys14/03/2016AMDAMD GPIO Controller Driver


  1. So I'd check to see if there are some updates to these.
  2. I can also see you're running RivaTuner/EVGA Prec/MSI Afterburner, whichever one of these I would uninstall as these can commonly cause BSOD.
  3. Can you also confirm that your RAM was bought from 1 single pack and not 2 separate packs? (I can see they are the same model, but appear as if they may be single packs).
  4. There is a BIOS update available that we may try afterwards but as a last action
 

gardenman

Admirable
Moderator
Hi, I ran the newest 10 dump files through the debugger and got the following information: https://jsfiddle.net/bk62L4om/show
File information:081220-7859-01.dmp (Aug 12 2020 - 03:56:54)
Bugcheck:MEMORY_MANAGEMENT (1A)
Probably caused by:memory_corruption (Process: SearchFilterHost.exe)
Uptime:0 Day(s), 0 Hour(s), 01 Min(s), and 08 Sec(s)

File information:081220-7625-01.dmp (Aug 12 2020 - 03:55:15)
Bugcheck:STORE_DATA_STRUCTURE_CORRUPTION (1C7)
Probably caused by:memory_corruption (Process: MemCompression)
Uptime:0 Day(s), 0 Hour(s), 45 Min(s), and 53 Sec(s)

File information:081220-7015-01.dmp (Aug 12 2020 - 05:05:00)
Bugcheck:MEMORY_MANAGEMENT (1A)
Probably caused by:memory_corruption (Process: firefox.exe)
Uptime:0 Day(s), 0 Hour(s), 02 Min(s), and 14 Sec(s)

File information:081220-4890-01.dmp (Aug 12 2020 - 04:30:24)
Bugcheck:MEMORY_MANAGEMENT (1A)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 32 Min(s), and 19 Sec(s)

File information:081020-8734-01.dmp (Aug 9 2020 - 12:16:46)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:memory_corruption (Process: dwm.exe)
Uptime:0 Day(s), 0 Hour(s), 30 Min(s), and 44 Sec(s)

File information:081020-7921-01.dmp (Aug 10 2020 - 15:35:33)
Bugcheck:SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 03 Min(s), and 13 Sec(s)

File information:081020-7843-01.dmp (Aug 10 2020 - 15:29:50)
Bugcheck:MEMORY_MANAGEMENT (1A)
Probably caused by:memory_corruption (Process: WerFault.exe)
Uptime:0 Day(s), 0 Hour(s), 00 Min(s), and 47 Sec(s)

File information:081020-7125-01.dmp (Aug 10 2020 - 16:19:46)
Bugcheck:MEMORY_MANAGEMENT (1A)
Probably caused by:memory_corruption (Process: firefox.exe)
Uptime:0 Day(s), 0 Hour(s), 03 Min(s), and 03 Sec(s)

File information:081020-6703-01.dmp (Aug 10 2020 - 16:22:05)
Bugcheck:MEMORY_MANAGEMENT (1A)
Probably caused by:memory_corruption (Process: CHXSmartScreen.exe)
Uptime:0 Day(s), 0 Hour(s), 01 Min(s), and 18 Sec(s)

File information:081020-6562-01.dmp (Aug 10 2020 - 16:15:04)
Bugcheck:MEMORY_MANAGEMENT (1A)
Probably caused by:memory_corruption (Process: firefox.exe)
Uptime:0 Day(s), 0 Hour(s), 05 Min(s), and 11 Sec(s)
Comment: The overclocking driver "RTCore64.sys" was found on your system. (MSI Afterburner)

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Reactions: PC Tailor

Thomskn

Reputable
Jan 13, 2016
27
2
4,535
0
  1. So I'd check to see if there are some updates to these.
  2. I can also see you're running RivaTuner/EVGA Prec/MSI Afterburner, whichever one of these I would uninstall as these can commonly cause BSOD.
  3. Can you also confirm that your RAM was bought from 1 single pack and not 2 separate packs? (I can see they are the same model, but appear as if they may be single packs).
  4. There is a BIOS update available that we may try afterwards but as a last action
  1. I tried to check, I was able to find the actual driver files on my system but not through the device manager so easily. Do I just go past all the devices, try and find the drivers and the update them manually?
  2. Done. Checked whether there were any excess files leftover including the driver, once I confirmed there were none I tried to boot normally but it quickly crashed again.
  3. Can confirm. It was one pack of 2x4.
 

ASK THE COMMUNITY