Could a DCOM error be causing this BSOD?

Hi, new here.

I've gone through a long, tumultuous drama with my desktop PC and a certain blue screen. I will try my best to be brief but here's a detailed history. My specs are in the usual spot, as detailed as possible from Speccy.

-Computer is now a little over a year old. Had a BSOD about kernel security check failure right from the get-go. I thought it was because Windows didn't update these optional updates. I downloaded those optional updates and it was fine for a long time.

-I can't pinpoint exactly when, but sometime this past summer the BSODs happened again. I believe it has to do with Windows 10 because they became more frequent after the automatic update. The BSODs happened one of three ways - 1: my USB drivers would suddenly stop working, and then the BSOD would happen soon, 2) whenever I downloaded a large file over the Internet (i.e. a game over Steam or Battle.net, etc) the installation would take forever because I kept getting interrupted by a BSOD or 3) I'd leave the PC idle for a long time and return to it having restarted because of a BSOD

-Over time, the BSOD ONLY HAPPENED in situation number 2. This still became intolerable when I wanted to download a really big game - the new Doom through Steam. It wouldn't reach 3% without hitting a BSOD.

-I learned about Event Viewer and saw many DCOM errors. I tried fixing the DCOM errors by changing permissions and making sure that the properties under DCOM Config were set to Local Activation and Local Launch, like everybody says. The awkward part - they were already checked. So I was confused and unsure what to do. Other times I couldn't find the DCOM key or whatever in the DCOM Config (but that could just be me starting to lose my sanity at that point). I also used BlueScreenView but that didn't help much because I tried EVERYTHING to diagnose the issue - SFC scan now, chkdsk, device manager, anti-virus and malware check - ALL OF THAT came out okay. I even checked to see if everything inside the computer was attached correctly.

-It gets stranger - I went on safe mode with networking to download Doom. No BSOD! I was able to reach 20%. I stopped though because IMO there was no sense in fully installing it because I didn't want to just ignore this problem by finding some lazy bypass.

-I reinstalled Windows 10 but saved my files - still got BSOD afterwards. This time I was trying to download something as innocuous as Firefox. Still got interrupted twice in a row.

-I then wanted to reinstall Windows 10 and delete EVERYTHING (I backed up my files in my laptop). The computer went haywire and kept throwing BSODs at me every time I wanted to reinstall a second time. For a few minutes, I couldn't access Microsoft Edge or even ACCESS THE WIFI. But then, sporadically, I was able to reset the entire computer and start from a clean slate.

-Clean slate - PC is practically void of anything except Windows 10. I go to download Firefox - get BSOD yet again. At this point, I am starting to think I am in hell.

-Event Viewer is cleared up EXCEPT FOR ONE DCOM error. NO OTHER ERRORS EXCEPT THIS ONE, which I shall post here right now:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
and APPID
{F72671A9-012C-4725-9D2F-2A4D32D65169}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

-I tried installing Windows 10 updates but got interrupted by yet another BSOD. The Event Viewer showed that this DCOM error occurred right after I clicked to update.

-Like before, I tried fixing the DCOM error in the DCOM Config but, like before, everything is already checked for Local Activation and Local Launch. The odd thing is I can't reverse the ownership of F726 blah blah blah back to TrustedInstaller, which worries me because I don't want to screw anything up so I just stopped fiddling with DCOM Config and regedit.

I'm completely beat a this point. I haven't slept well in the past two nights because this issue kept me up working on it. So I found this site and this is my one last cry for help.

Attached are the necessary files. These are after the first reinstall though. If I should have one from my PC now after the clean slate, let me know. I'll get it later today after work.

Final note: The BSOD is 99.99% of the time a kernel security check failure. I think only once or twice throughout the entire history of owning this PC was it something else, but I unfortunately never bothered to write it down (but I believe one was a driver error)

Final final note: I can't remember if this was before or after the resurgence of blue screens this past summer, but I fell for using a driver update program called Driver Easy, or Booster, something stupid like that. It took me a couple weeks to realize it wasn't doing anything because it would say the same drivers it just updated were outdated for years, which didn't make sense. I hope that wasn't the reason or the catalyst in screwing things up. I mean, if I did a clean install and removed every single thing, wouldn't Driver Easy's effects be long gone by now?

Attachment 112107

Both dumpfile are:

Code:

 BugCheck 139, {3, ffffe580c6d7e050, ffffe580c6d7dfa8, 0}

Unable to load image \SystemRoot\System32\drivers\MRVW24C.sys, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for MRVW24C.sys
Probably caused by : MRVW24C.sys ( MRVW24C+272f1 )

MRVW24C Mon Oct 29 04:22:31 2007 .
This driver is from 2007 and (probably) not compatible with windows 10.
Try to update to a windows 10 driver, else i suspect you need a other compatible windows 10 Wireless USB Network Adapter.

Driver Description: Linksys, NetGear, DLink or Marvell Wireless USB Network Adapter
Driver Update Site: linksysbycisco.com
This is your card PNP Device ID USB\VID_13B1&PID_0029\5&1D65B4DC&0&3

Network Card(s): 2 NIC(s) Installed.
[01]: Wireless-N USB Network Adapter
Connection Name: Wi-Fi

Also update this older/outdated drivers:
ISCTD64 Tue Nov 27 20:52:34 2012
Driver Description: Intel(R) Smart Connect Technology Device Driver
Driver Update Site: Info here: Intel® Smart Connect Technology
Check w/OEM - Also available at Intel Download Center: Search downloads

Yes, i would buy a new adapter, i t is to old and gets only older and with a new adapter you will be future proof the next years.

What about the safemode, i don't known maybe in safemode windows use a standard/different windows driver.

Great it is solved.
Could you mark this thread as solved.