[SOLVED] Random IRQL_NOT_LESS_OR_EQUAL related BSOD's, various DistributedCOM 10016 errors. Help!

[Futurebus_]

This has been a serious headache for the past month and a half or so and I'd really appreciate if anyone can help!

To preface, I bought a pre-built pc about 3 months ago, and it was working absolutely just fine for about a month. I worked with a single monitor setup and shortly after buying a second monitor, I seemingly out of nowhere began to get bsod's at completely random times, sometimes even messing up my system to the extent where I can't boot and have to do a startup repair. Most of these errors are IRQL_NOT_LESS_OR_EQUAL, sometimes DRIVER_IRQL_NOT_LESS_OR_EQUAL stating that amdpps.sys is the culprit, and sometimes even SYSTEM_SERVICE_EXCEPTION.
However none of my files seem to be affected, and when I'm not crashing randomly my computer still works just fine. I've run memory diagnostics, System file checker scans, disk checks, and yet nothing comes up in any of these.

These particular errors seem to be showing up a lot in my event viewer post-bsod:
---The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user DESKTOP-IULF9TG\USER SID (S-1-5-21-2740351081-3863700851-2380627218-1005) 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.
---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.
(^^This same error usually pops up alongside it, except with CLSID Windows.SecurityCenter.WscDataProtection and CLSID Windows.SecurityCenter.WscBrokerManager respectively)

After looking at various forums I was told that my main solution to solve these DistributedCOM errors were to simply go to the registry editor, apply administrator/system permission to the registry keys corresponding to the IDs shown in the errors, then essentially do the same thing in component services. I have done this, Yet still I seem to get the very same errors as if absolutely nothing has changed.

Also, if it makes any difference, my monitors are 2x Sceptre E205w-1600. One of the monitors is a slightly newer version of the same model however.

Lastly, here are my computer specs:
AMD Ryzen 5 2600
Gtx 1060 3gb
2x8 gb of 2400mhz DDR4 RAM
HP S700 500gb SSD
MSI A320M PRO-VH Plus
Thermaltake Smart 650w PSU

Help would be oh, oh so appreciated!

 

[Colif]

Run MSI Live update 6 on PC and see if it offers any new drivers. If you don't have it, you can get it here

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a file sharing web site, and share the link here and I will get

 

[Futurebus_]

Run MSI Live update 6 on PC and see if it offers any new drivers. If you don't have it, you can get it here

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a file sharing web site, and share the link here and I will get

Done. I don't know when my next BSOD will be, but when it does happen I will post the minidump immediately afterwards.

 

[Colif]

amdpps.sys is part of the chipset driver, so if you already run LIve update 6, you should have latest version.

BSOD can be forced to happen but if you willing to wait, it may not happen again... which is a good outcome.

 

[Futurebus_]

amdpps.sys is part of the chipset driver, so if you already run LIve update 6, you should have latest version.

BSOD can be forced to happen but if you willing to wait, it may not happen again... which is a good outcome.

Done. I don't know when my next BSOD will be, but when it does happen I will post the minidump immediately afterwards.

I do have MSI Live Update 6 and I have been able to use it in the past, but for some reason it won't open for me now. I have absolutely no clue why. I'm getting a 7034 Service Control Manager error that says "The MSI Live Update Service service terminated unexpectedly. It has done this 1 time(s)."

 

[Colif]

what happens if you install the new version of Command Centre that is on same page as Live update, since command centre seems to be related to the problem. Update both live update 6 & command centre and then try it again

https://forum-en.msi.com/index.php?topic=180757.0

 

[Futurebus_]

what happens if you install the new version of Command Centre that is on same page as Live update, since command centre seems to be related to the problem. Update both live update 6 & command centre and then try it again

https://forum-en.msi.com/index.php?topic=180757.0

I was able to update my MSI command center that was working beforehand. After updating, I was immediately met with a SYSTEM_SERVICE_EXCEPTION Bsod, stating that win32kbase.sys was the culprit. I reinstalled Command center through a download on MSI's site and it seems to be working just fine now, though it did state that "Startup files are corrupted" before I installed for some reason.
I still can't open Live Update, however. Debating whether or not I should reinstall that through the MSI site.

Regardless, here's the minidump file for my latest BSOD: https://drive.google.com/open?id=19sgGUnpEXRGAmOsv1lRzdqz08xj74k63

 

[Futurebus_]

I was able to update my MSI command center that was working beforehand. After updating, I was immediately met with a SYSTEM_SERVICE_EXCEPTION Bsod, stating that win32kbase.sys was the culprit. I reinstalled Command center through a download on MSI's site and it seems to be working just fine now, though it did state that "Startup files are corrupted" before I installed for some reason.
I still can't open Live Update, however. Debating whether or not I should reinstall that through the MSI site.

Regardless, here's the minidump file for my latest BSOD: https://drive.google.com/open?id=19sgGUnpEXRGAmOsv1lRzdqz08xj74k63

One additional thing: I just reinstalled MSI Live Update, and it's still unexpectedly terminating. So I still can't start the program.

 

[Colif]

live update is not really important, though would be nice if it worked.

I will ask @gardenman to convert dmp files into something I can read, and hopefully we can zero in on true cause. That might fix live update as well.

 

[Futurebus_]

live update is not really important, though would be nice if it worked.

I will ask @gardenman to convert dmp files into something I can read, and hopefully we can zero in on true cause. That might fix live update as well.

Thank you. Much, much appreciated if you guys can.

 

[Colif]

The dumps will at least show us what drivers are running,

DCOM is a programming construct that allows a computer to run programs over the network on a different computer as if the program was running locally. DCOM is an acronym that stands for Distributed Component Object Model. DCOM is a proprietary Microsoft software component that allows COM objects to communicate with each other over the network. (Network OLE was the precursor to DCOM if anyone remembers seeing that in Windows 3.1.)

https://www.varonis.com/blog/dcom-distributed-component-object-model/

i would link wikipedia but they essentially copied half that link above into their article.

I wonder if its the realtek lan drivers, only 1 available on here - https://www.msi.com/Motherboard/support/A320M-PRO-VH-PLUS#down-driver&Win10 64

 

[gardenman]

Hi, I ran the dump file through the debugger and got the following information: https://pste.eu/p/RaB1.html

File information:	030819-6500-01.dmp (Mar 8 2019 - 04:53:54)
Bugcheck:	SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:	win32kbase.sys (Process: Command Center)
Uptime:	0 Day(s), 21 Hour(s), 12 Min(s), and 55 Sec(s)

Comment: 2 or more types of RAM are installed.

Possible Motherboard page: https://www.msi.com/Motherboard/a320m-pro-vh-plus.html
There are BIOS updates available for your system. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

I can't help you with this. Someone else will post with more information soon. Please wait for more answers. Good luck.

 

[Colif]

Try updating bios as almost everyone between yours and current improves memory compatability

Could be caused by having 2 different types of ram in the same channel in PC... which memory diagnostic did you run?
Try running memtesst86 on each of your ram sticks, one stick at a time, up to 8 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

If both sticks test out fine, try running PC with just 1 of them in and see if you still get bsod.

 

[Futurebus_]

Try updating bios as almost everyone between yours and current improves memory compatability

Could be caused by having 2 different types of ram in the same channel in PC... which memory diagnostic did you run?
Try running memtesst86 on each of your ram sticks, one stick at a time, up to 8 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

If both sticks test out fine, try running PC with just 1 of them in and see if you still get bsod.

Will do! Although I will note that the 2 different ram sticks were a fairly new addition. I actually bought a second stick just for gaming purposes and while they're at the same frequency, speed, voltage, and gb they are from different brands as noted. The issues that I've been having with my pc have preceded the addition of the second ram stick. However that doesn't mean that that isn't the issue. Lord knows I ain't the computer tech specialist here. I'll remove one and the other and do some tests.

 

[Colif]

new bios may work better with command centre and update.. something strange if both those apps don't run.

 

[Futurebus_]

new bios may work better with command centre and update.. something strange if both those apps don't run.

Heya! I know it's been a few days but I just wanted to give an update.

So to elaborate on my ram situation, the initial stick that the pc came with was a single G.Skill Ripjaws V series 8gb, 2400mhz DDR4. The one I had recently bought was a Corsair Vengeance LPX 8gb, also 2400mhz DDR4. After some reluctance I decided to take out the G.Skill Ripjaws stick and simply just have the Corsair stick to replace it. I've been BSOD free for about 4 days so far and really haven't had any issue in the slightest. I still get the distributedCOM errors and I still can't use MSI Live, but I really just suspect that the former is a negligible issue and the latter doesn't really matter all that much to me personally. I'm still not completely 100% sure what the issue truly was, but I'm just gonna mark it down to most likely being a faulty ram stick. Which sucks, cus that's like a $50 stick.

Thanks so much for your help in helping me deliberate the issue!

 

[Colif]

Yes, bad ram can be cause of random errors, yours just didn't seem that random to warrant me suggesting you run memtest. Fact you had two different make memory in could also be a reason for random errors.

I never worry about event viewer errors unless I am trying to figure out a problem. I guess that is why you were there. I think I get dcom errors too.