Windows 10: Persistent BSOD even after reinstalling windows10 in pc DistrubtedCOM?

redlynxks · Nov 23, 2018

Hello, I don't know why but today my pc keeps on freezing and crashing all over again, thus having no choice I did a system reinstall hoping to fix it, but sadly it still won't fix. I checked the event logger and found out 3 errors that keeps on happening and 1 error that's somehow new.

Heres my event logger with their error

Error number 1: Windows.SecurityCenter.WscDataProtection

Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 11/24/2018 2:03:01 AM
Event ID: 10016
Task Category: None
Level: Error
Keywords: Classic
User: SYSTEM
Computer: DESKTOP-SDB1EK9
Description:
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscDataProtection
and APPID
Unavailable
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.
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="2018-11-23T18:03:01.701225400Z" />
<EventRecordID>1324</EventRecordID>
<Correlation />
<Execution ProcessID="464" ThreadID="580" />
<Channel>System</Channel>
<Computer>DESKTOP-SDB1EK9</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="param1">application-specific</Data>
<Data Name="param2">Local</Data>
<Data Name="param3">Launch</Data>
<Data Name="param4">Windows.SecurityCenter.WscDataProtection</Data>
<Data Name="param5">Unavailable</Data>
<Data Name="param6">NT AUTHORITY</Data>
<Data Name="param7">SYSTEM</Data>
<Data Name="param8">S-1-5-18</Data>
<Data Name="param9">LocalHost (Using LRPC)</Data>
<Data Name="param10">Unavailable</Data>
<Data Name="param11">Unavailable</Data>
</EventData>
</Event>
Click to expand...

Error number 2: Windows.SecurityCenter.WscBrokerManager

Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 11/24/2018 2:03:01 AM
Event ID: 10016
Task Category: None
Level: Error
Keywords: Classic
User: SYSTEM
Computer: DESKTOP-SDB1EK9
Description:
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscBrokerManager
and APPID
Unavailable
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.
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="2018-11-23T18:03:01.701225400Z" />
<EventRecordID>1323</EventRecordID>
<Correlation />
<Execution ProcessID="464" ThreadID="508" />
<Channel>System</Channel>
<Computer>DESKTOP-SDB1EK9</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="param1">application-specific</Data>
<Data Name="param2">Local</Data>
<Data Name="param3">Launch</Data>
<Data Name="param4">Windows.SecurityCenter.WscBrokerManager</Data>
<Data Name="param5">Unavailable</Data>
<Data Name="param6">NT AUTHORITY</Data>
<Data Name="param7">SYSTEM</Data>
<Data Name="param8">S-1-5-18</Data>
<Data Name="param9">LocalHost (Using LRPC)</Data>
<Data Name="param10">Unavailable</Data>
<Data Name="param11">Unavailable</Data>
</EventData>
</Event>
Click to expand...

Error Number 3: Windows.SecurityCenter.SecurityAppBroker

Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 11/24/2018 2:03:01 AM
Event ID: 10016
Task Category: None
Level: Error
Keywords: Classic
User: SYSTEM
Computer: DESKTOP-SDB1EK9
Description:
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.SecurityAppBroker
and APPID
Unavailable
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.
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="2018-11-23T18:03:01.701225400Z" />
<EventRecordID>1322</EventRecordID>
<Correlation />
<Execution ProcessID="464" ThreadID="1704" />
<Channel>System</Channel>
<Computer>DESKTOP-SDB1EK9</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="param1">application-specific</Data>
<Data Name="param2">Local</Data>
<Data Name="param3">Launch</Data>
<Data Name="param4">Windows.SecurityCenter.SecurityAppBroker</Data>
<Data Name="param5">Unavailable</Data>
<Data Name="param6">NT AUTHORITY</Data>
<Data Name="param7">SYSTEM</Data>
<Data Name="param8">S-1-5-18</Data>
<Data Name="param9">LocalHost (Using LRPC)</Data>
<Data Name="param10">Unavailable</Data>
<Data Name="param11">Unavailable</Data>
</EventData>
</Event>
Click to expand...

Error number 4

Log Name: System
Source: Service Control Manager
Date: 11/24/2018 2:01:40 AM
Event ID: 7023
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-SDB1EK9
Description:
The SysMain service terminated with the following error:
The parameter is incorrect.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7023</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2018-11-23T18:01:40.284618100Z" />
<EventRecordID>1319</EventRecordID>
<Correlation />
<Execution ProcessID="728" ThreadID="3936" />
<Channel>System</Channel>
<Computer>DESKTOP-SDB1EK9</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">SysMain</Data>
<Data Name="param2">%%87</Data>
<Binary>5300790073004D00610069006E000000</Binary>
</EventData>
</Event>
Click to expand...

:)

Thrackan · Nov 23, 2018

PC reboots (no BSOD) on CPU stress

Hi fellow TPU members,

not too long ago, the box my gf's PC was transported in gave way on the stairs. Yes, you got it right, that sent a PC tumbling down a flight of steps alright.

Stuff broke. Also, stuff remained intact somehow.

I bought her a new case, new CPU cooler and we removed the floppy drive, so far so good. But the PC started crashing for no apparent reason, without a BSOD.

I tested:

Memtest86+, left overnight, 0 errors

Scanned the HDD for errors, nothing there

Left FurMark burning up the GFX card and drawing some power, no problems there

Ran Ubuntu from a Live CD doing nothing special, didn't crash

Ran OCCT, Linpack, Prime95, all 3 caused reboots within minutes

Oh, and I disabled "Restart on error" so I'm sure it's not a BSOD.

Now, I can still try and test something CPU intensive on Ubuntu, but my guess is the CPU didn't survive.
Before I do anything drastic like whippin' out the magic wallet and get her a new AMD quad, is there anything I didn't see?
I'm guessing the motherboard could be borkered as well, but can I check that other than replacing the CPU with a working one?
Any suggestions on which proggies I can use from an Ubuntu Live CD to stress the CPU?

jhumur · Nov 23, 2018

Persistent Disk Activity on Windows 10

Good night!
Click to expand...

FreeBooter, I did as you suggested and rebooted. The problem persisted. I noticed that the Bitdefender services remained checked when I turned off all non-Microsoft related services in the steps above.

Allan Mej · Nov 23, 2018

Windows10 update

Hi Ray,

To troubleshoot your issue, we suggest doing these following troubleshooting methods:

Method 1

Turn off your PC.

Press and hold Shift then turn on your PC.

Wait for the setup (set up fixes the problem automatically).

Method 2

Create a media creation tool by following the steps in this
link.

Select your preferred installation option and wait for the process to finish.

Let us know how it goes.

Regards.

Windows 10: Persistent BSOD even after reinstalling windows10 in pc DistrubtedCOM?

Persistent BSOD even after reinstalling windows10 in pc DistrubtedCOM?

Persistent BSOD even after reinstalling windows10 in pc DistrubtedCOM?

Persistent BSOD even after reinstalling windows10 in pc DistrubtedCOM?

Persistent BSOD even after reinstalling windows10 in pc DistrubtedCOM? - Similar Threads - Persistent BSOD reinstalling

Constant BSODs even after multiple reinstalls

Constant BSODs even after multiple reinstalls

Random BSOD even after reinstall OS

Random BSOD even after reinstall OS

Persistant BSOD even with fresh install

Persistant BSOD even with fresh install

BSOD persists even after a clean install

BSOD with different errors even after reinstall

BSoD Persist After Sending PC For Repairs

Users found this page by searching for:

even windows is reinstall keeps having bsod

Windows.SecurityCenter.SecurityAppBroker permissions