Ffs do you want a spare PC?😂😂😂
Could be a stick of dodgy ram?
Let me know if you need owt budHmmmm. I didn't think about that. Probably the cheapest thing I can replace too
I genuinely give up lol. Easy to find why your computer crashes but not tried anything I've suggested.
Hmmmm. I didn't think about that. Probably the cheapest thing I can replace too
Yeah would have thought soDDR3 is probably cheap enough to just lob 2 new sticks in no?
If you have a pair of sticks of ram - you could try just one at a time and see if it falls over - i've just gone through this whole process - tried new graphics card, tried replacement memory - it was just the latest windows update that was causing the crashes like your having with the fuzzy screen etc.. I looked at the reliabilty monitor it said why it was crashing and then just reverted the windows update back and it worked. Prob explains why was working good with win 10 on ssd then its updated and bosh - your having the issue. Same motherboard as you too.
I genuinely give up lol. Easy to find why your computer crashes but not tried anything I've suggested.
Its a 5 min job - worth a shot.Nah rollback windows 10 innit, worked for 1 person so its deffo that
Nah rollback Windows mate, that WILL sort it!Soooooo, when I updated the drivers, seems it updated the onboard intel graphics card, and the PC kept using that, despite the monitors being plugged into the new one.
Checked the new Asus card and that was last updated 2015, LOL. So updated that, and disabled the intel one.
Fingers crossed and touch wood, it’s been alright yesterday today, and I’ve been giving it a beating too, using youtube,, playing vids, accessing hard drives etc in the background whilst using the remote to work, and the temps have been rock steady too at 40deg for the card and CPU. Might even turn down those jet engines for fans.
Soooooo, when I updated the drivers, seems it updated the onboard intel graphics card, and the PC kept using that, despite the monitors being plugged into the new one.
Checked the new Asus card and that was last updated 2015, LOL. So updated that, and disabled the intel one.
Fingers crossed and touch wood, it’s been alright yesterday today, and I’ve been giving it a beating too, using youtube,, playing vids, accessing hard drives etc in the background whilst using the remote to work, and the temps have been rock steady too at 40deg for the card and CPU. Might even turn down those jet engines for fans.
New CPU paste, Windows10debloater, reseat the RAM, Turn OFF the onboard GFX if using a GFX card...
PICNIC is better3 things, the most important in this case
PEBKAC
Do thisJust bin it
But this happened 4 mins approx before the crash - not at the time of crash from the log?DCOM event ID 10016 means that certain processes don't have permissions to the DCOM components that are mentioned in the event logs. To resolve this, kindly follow the steps below:
Important: The section, method, or task provided on the link above contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow the steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, refer to the following Microsoft Knowledge Base article: How to back up and restore the registry in Windows.
1. From the Start menu, type regedit.exe in the search box, and then press Enter. If you are prompted for an administrator password or for confirmation, type the password or provide confirmation.
2. Go to HKEY_Classes_Root\CLSID\{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}.
Note: *CLSID* stand for the ID that appears in your event viewer error. In your case, it's {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}.
3. Right click on it then select Permissions.
4. Click on Advance and change the owner to Administrators. Once done, click the box that will appear below the owner line.
5. Apply full control.
6. Go to HKEY_LocalMachine\Software\Classes\AppID\{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}.
Note: *AppID* is the ID that appears in your event viewer. In your case it's {4839DDB7-58C2-48F5-8283-E1D1807D0D7D}.
7. Right click on it then select Permission.
8. Click on Advance and then change the owner to Administrators group.
9. Click the box that will appear below the owner line.
10. Click on Apply and grant full control to the Administrators group.
11. Close all tabs and go to Administrative tools.
12. Open Component Services.
13. Click on Computer, select My Computer, and then click on DCOM.
14. Look for the corresponding service that appears on the error viewer [Immersive Shell].
15. Right click on it then click on Properties.
16. Click on the Security tab, and then click on Add User. Add Local Service then click on Apply.
17. Tick the Activate local box.
Persistent PC freeze and crash with Dcom 10016 being the problem
Hi all, i get this event ID everytime my pc crashes (freeze), Dcom 10016 The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSIDanswers.microsoft.com
That's the link to the site notifying it...