Persistent BSOD even after reinstalling windows10 in pc DistrubtedCOM?

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>

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>

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>

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>

Sorry forgot my dm log collector here it is

There are two log collectors: DM and BETA
At some time the BETA log collector will replace the DM log collector.
The BETA log collector will collect more useful folders and files.
Run the BETA log collector and post a zip into the thread:
The link is in the lower portion of this webpage:
BSOD - Posting Instructions - Windows 10 Forums
https://www.tenforums.com/attachment...-v2-beta15.zip
(extract all > open)

The logs displayed many BSOD with problems creating the dump files.

This is the regular clean install:
Clean Install Windows 10 | Tutorials
Download Windows 10

Another type of clean install is the "vanilla clean install"
Perform a clean install with a Windows 10 iso version 1809 or 17763 with the computer disconnected from the internet.
Install no windows updates, drivers, applications, files, etc.
The computer at this stage will have a clean install of Windows with Windows installed Microsoft and non-Microsoft drivers.
There remains no connection to the internet and no drivers installed from Gigabyte or the component manufacturers yet.


Modify the default windows settings in startup and recovery system failure:

In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
a) > on the advanced tab under startup and recovery > click settings > under startup and recovery system failure uncheck automatic restart > post an image in to the thread > reboot to maintain the new setting

b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > make sure that the paging file is on C: and that the box is checked to automatically manage page file size for all drives > post an image of the virtual memory tab into the thread

With the "vanilla" clean install evaluate the computer for freezes and crashes > report the results into the thread

If there are freezes and crashes that is one direction for troubleshooting.
If there are no freezes and crashes that is another method for troubleshooting.

Please evaluate for a sufficient period of time so that you are convinced that there are reproducible freezes and crashes or no freezes and crashes.

zbook said:

There are two log collectors: DM and BETA
At some time the BETA log collector will replace the DM log collector.
The BETA log collector will collect more useful folders and files.
Run the BETA log collector and post a zip into the thread:
The link is in the lower portion of this webpage:
BSOD - Posting Instructions - Windows 10 Forums
https://www.tenforums.com/attachment...-v2-beta15.zip
(extract all > open)

The logs displayed many BSOD with problems creating the dump files.

This is the regular clean install:
Clean Install Windows 10 | Tutorials
Download Windows 10

Another type of clean install is the "vanilla clean install"
Perform a clean install with a Windows 10 iso version 1809 or 17763 with the computer disconnected from the internet.
Install no windows updates, drivers, applications, files, etc.
The computer at this stage will have a clean install of Windows with Windows installed Microsoft and non-Microsoft drivers.
There remains no connection to the internet and no drivers installed from Gigabyte or the component manufacturers yet.


Modify the default windows settings in startup and recovery system failure:

In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
a) > on the advanced tab under startup and recovery > click settings > under startup and recovery system failure uncheck automatic restart > post an image in to the thread > reboot to maintain the new setting

b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > make sure that the paging file is on C: and that the box is checked to automatically manage page file size for all drives > post an image of the virtual memory tab into the thread

With the "vanilla" clean install evaluate the computer for freezes and crashes > report the results into the thread

If there are freezes and crashes that is one direction for troubleshooting.
If there are no freezes and crashes that is another method for troubleshooting.

Please evaluate for a sufficient period of time so that you are convinced that there are reproducible freezes and crashes or no freezes and crashes.

Hello, 2 hours has passed since using my pc, I followed your steps and so far pc isn't freezing and crashing. Now i'm just downloading and installing stuffs and hopefully crash won't happen again. anyway here's my Beta log collector and the rest of the images you requested.

The DM log collector zip was posted again.

Please run the BETA log collector with the link(s) in the earlier post.

The DM log collector displayed that the vanilla clean install was not yet performed:
Original Install Date: 11/24/2018, 7:22:18 AM
System Boot Time: 11/24/2018, 2:00:50 AM

Which of the steps in the prior post were performed?
Which of the steps in the prior post were not performed?

zbook said:

The DM log collector zip was posted again.

Please run the BETA log collector with the link(s) in the earlier post.

The DM log collector displayed that the vanilla clean install was not yet performed:
Original Install Date: 11/24/2018, 7:22:18 AM
System Boot Time: 11/24/2018, 2:00:50 AM

Which of the steps in the prior post were performed?
Which of the steps in the prior post were not performed?

Wrong file sorry,

I didn't vanilla install again since I already did it earlier ago and I can't do it again (boot drive was taken by my friend so either I have to wait till Monday to vanilla install again). The only steps I didn't perform was the vanilla install one, and the rest I did.

and this is the output file of the log collector gave me.

1) Download and install: Everything
voidtools

2) Use everything to search for: win32k.sys-20181124-1253.dmp

Code:

win32k.sys-20181124-1253.dmp 11/24/2018 12:53:44 PM    749.75

3) zip the file > post a share link using: one drive, drop box, or google drive



4) Open administrative command prompt and type or copy and paste:
5) sfc /scannow
6) dism /online /cleanup-image /restorehealth
7) chkdsk /scan
8) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

9) Make sure that there is no over clocking while troubleshooting.

zbook said:

1) Download and install: Everything
voidtools

2) Use everything to search for: win32k.sys-20181124-1253.dmp

Code:

win32k.sys-20181124-1253.dmp 11/24/2018 12:53:44 PM    749.75

3) zip the file > post a share link using: one drive, drop box, or google drive



4) Open administrative command prompt and type or copy and paste:
5) sfc /scannow
6) dism /online /cleanup-image /restorehealth
7) chkdsk /scan
8) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

9) Make sure that there is no over clocking while troubleshooting.

Hello, here is the https://drive.google.com/file/d/1d9D...ew?usp=sharing

And here's the result in the command prompt

Microsoft Windows [Version 10.0.17763.134]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>
C:\Windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.134

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\system32>
C:\Windows\system32>chkdsk/scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
167936 file records processed.
File verification completed.
5913 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
178 reparse records processed.
231558 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
178 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
31812 data files processed.
CHKDSK is verifying Usn Journal...
37975576 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

243567615 KB total disk space.
82096148 KB in 129941 files.
88820 KB in 31813 indexes.
0 KB in bad sectors.
281827 KB in use by the system.
65536 KB occupied by the log file.
161100820 KB available on disk.

4096 bytes in each allocation unit.
60891903 total allocation units on disk.
40275205 allocation units available on disk.

C:\Windows\system32>

Which link had you read for the "vanilla" clean install?

Plan two weeks of testing for the vanilla clean install.
Allow two days or more for each steps A and B. Then one day or more for each steps C and D.

When possible please use this method and allow sufficient time for each step so that you are confident that enough time was spent to rule in / rule out freezes and crashes for each of these steps:
a) Windows clean install of just Microsoft and non-Microsoft drivers (no Windows updates)
b) Windows clean install of just Microsoft and non-Microsoft drivers with Windows updates (no drivers from the computer or motherboard manufacturer's)
c) Windows clean install of Windows with one driver from the computer or motherboard manufacturer's websites
d) Add one driver and perform at least on day of testing before adding additional drivers
e) Keep repeating step d until all drivers are installed

If there are freezes or crashes with steps a or b then there will be other tests performed. So the first four or more days of testing are critical.

zbook said:

Which link had you read for the "vanilla" clean install?

Plan two weeks of testing for the vanilla clean install.
Allow two days or more for each steps A and B. Then one day or more for each steps C and D.

When possible please use this method and allow sufficient time for each step so that you are confident that enough time was spent to rule in / rule out freezes and crashes for each of these steps:
a) Windows clean install of just Microsoft and non-Microsoft drivers (no Windows updates)
b) Windows clean install of just Microsoft and non-Microsoft drivers with Windows updates (no drivers from the computer or motherboard manufacturer's)
c) Windows clean install of Windows with one driver from the computer or motherboard manufacturer's websites
d) Add one driver and perform at least on day of testing before adding additional drivers
e) Keep repeating step d until all drivers are installed

If there are freezes or crashes with steps a or b then there will be other tests performed. So the first four or more days of testing are critical.

Thank you for the help sir. I did the 1st link one from the vanilla install. Anyway can I ask if there any alternatives than vanilla installing my pc in the next 2 days? Since I doubt that I can connect to our dorm wifi easily after doing that, and I badly need my pc for our projects this week