Fallout 4 + Windows 10 Pro = BSOD?

[RadoGamer]

OK I was able to stop the BSODS by changing graphic settings a bit, and they stopped, But now the system is still doing the same thing without the BSOD and locking up with the same buzz it was making when it would BSOD.

 

I went ahead and checked Even Log and the same issue that appears several times just before the crash each time it does this is as follows.

 

Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 8/31/2019 1:40:39 PM
Event ID: 10016
Task Category: None
Level: Error
Keywords: Classic
User: Redacted
Computer: Redacted
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{8BC3F05E-D86B-11D0-A075-00C04FB68820}
and APPID
{8BC3F05E-D86B-11D0-A075-00C04FB68820}
to the user REDACTED from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="0">10016</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2019-08-31T19:40:39.732773300Z" />
<EventRecordID>81447</EventRecordID>
<Correlation />
<Execution ProcessID="420" ThreadID="1036" />
<Channel>System</Channel>
<Computer>systemname</Computer>
<Security UserID="S-1-5-21-2184833843-735837463-2553727575-1001" />
</System>
<EventData>
<Data Name="param1">application-specific</Data>
<Data Name="param2">Local</Data>
<Data Name="param3">Activation</Data>
<Data Name="param4">{8BC3F05E-D86B-11D0-A075-00C04FB68820}</Data>
<Data Name="param5">{8BC3F05E-D86B-11D0-A075-00C04FB68820}</Data>
<Data Name="param6">SYSTEMNAME</Data>
<Data Name="param7">REDACTED</Data>
<Data Name="param8">S-1-5-21-2184833843-735837463-2553727575-1001</Data>
<Data Name="param9">LocalHost (Using LRPC)</Data>
<Data Name="param10">Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy</Data>
<Data Name="param11">S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723</Data>
</EventData>
</Event>

 

 

I finally was able to narrow it down, and it appears Error 10016 caused by DCOM is a common and widespread issue in the Windows 10 community, causing crashes and software instability on servers as well as user PC's. Several fixes exist but are fairly complicated although I can do them I wouldn't recommend it to anyone who is not use to kicking around in the registry and administrative settings of Windows.

 

If you search the error message you'll find what I'm talking about. After what I've read today and the consistency of this error occurring in multiple instances on the event log just before the crashes. I'd safely say this could very well be the cause. I won't know until I apply the fix.

 

 

[DjinnKiller]

Interesting.

Please keep us posted after you apply the fix, if you wouldn't mind!

[RadoGamer]

Interesting.

Please keep us posted after you apply the fix, if you wouldn't mind!

 

You go it. :thumbsup:

[RadoGamer]

OK so the issue was made worse with the newest Win10 Pro Upgrade Version 1903 (go figure). I went ahead and attempted the fix. Nothing I could do that was suggested would allow me to make the changes needed in the final operation. I changed permissions as well as used a permission script in the Windows Power Shell (Admin) provided by Saujanya, and even though I was able to get to the last Properties area to add the permissions I could not add the needed information to apply the fix.

 

If anyone of you has the savvy and I'm guessing you do DjinnKiller. Here are the links to the information needed to apply the fix. You need to read both of them. More info for changing permissions in the registry are in the second link.

 

https://www.howto-connect.com/event-id-10016-distributedcom-windows-10-error/

 

 

https://social.technet.microsoft.com/wiki/contents/articles/50926.windows-component-services-troubleshooting-unable-to-edit-dcom-security-permissions.aspx

 

This issue is a rampant Windows 10 issue as I mentioned before and the more I searched using the term

 

EventID 10016 DCOM,

 

I found that DCOM has other errors causing very similar issues. If you do search this do not go to the Windows Forums every tech on them is handing out the same BS that is not fixing the issues.

 

Good Luck, I haven't given up yet.

Edited September 15, 2019 by RadoGamer

[DjinnKiller]

Thank you very much for the update.

Sorry to hear it didn't fix your problem, that is a bummer.

 

And, thanks for the links, they are stored for future reference. :)

[RadoGamer]

OK here is an update that does not bode well for Microsoft and Bethesda. Using WinDbg I have found the issue is centered around Windows kernel not being able to identify the time signature of the Killer 2500 driver according to the in depth information in WinDbg. For a while I was sure i needed to remove the on board adapter and go with an external one to see if the issue persists, but. Just the other day, my AMD graphics card updated it's driver with the newest Radeon software and driver there is. When I rebooted form the installation Windows went BSOD.

 

I ran WinDbg and lo and behold the very same error appeared for the new graphics driver. Originally I was running version 1800 series Win10Pro and although it would BSOD from time to time I was able to play FO4 for many hours with out issue. I have tons of dated and timed screen shots to prove that fact. Not too long ago I upgraded my system to Win10Pro 1900 series and that's when the BSODS became more frequent and almost always in FO4 and FO76.

 

Now there have been other BSODs with minor errors but there were basic explanations for them and they don't happen very often. I am convinced the issue lies in Windows 10 and the FO4 engine and not in my system, every possible thing that could be causing it due to hardware is not possible as I have checked all components and updated every driver as well as the bios and have run every possible test there is for the hardware.

 

To qualify this statement this is the tenth computer I have built over the years for my self, and never have I ever had such an issue as persistent on any of them as this one. The only common denominators are Win10 and Fallout 4/76 that are causing the issue. I can't say why but I know that perhaps there is something with the constant updating of Creation Club and the FO4 engine in relationship to Win10 but that doesn't explain why Win10 had the same issue with the Radeon driver. It hasn't happened since so I can't say why.

 

Many other people are having this problem, and they are getting the same schlock answers from people who just won't admit they have no clue why or that perhaps Windows 10 has a problem, from Windows techs.

 

Unfortunately as it is, I can no longer play FO4 or FO76 I can set a clock to how long it takes for either game to BSOD with the same error. Skyrim SE plays fine no issues, I can even play FO3 FONV and many other graphic intensive games like Devil May Cry 5 and others and never see this issue.

 

Oh well.

 

Game on!

[AeonsLegend]

Why would you run this game on win10 pro?

[HeyYou]

If the issue were between the game, and windows, you would see a LOT more folks having the same issue. (you are the only one I have seen with it so far, but, I haven't been looking either.....) Windows should NEVER bluescreen. If it does, there is something not-quite-right going on there. It may be an interaction between windows, and some driver, it may be an interaction between windows and the game, a combination of the two, or, it may just be crappy drivers, or failing hardware somewhere. (which I find those last two much more likely)

 

What was the original bluescreen error you were getting, what file was it whining about, and is it the same error you are getting now? I EXPECT to see a selection of dcom errors in event viewer. I would be flat out shocked if I DIDN'T find any....