Установить Steam
войти
|
язык
简体中文 (упрощенный китайский)
繁體中文 (традиционный китайский)
日本語 (японский)
한국어 (корейский)
ไทย (тайский)
Български (болгарский)
Čeština (чешский)
Dansk (датский)
Deutsch (немецкий)
English (английский)
Español - España (испанский)
Español - Latinoamérica (латиноам. испанский)
Ελληνικά (греческий)
Français (французский)
Italiano (итальянский)
Bahasa Indonesia (индонезийский)
Magyar (венгерский)
Nederlands (нидерландский)
Norsk (норвежский)
Polski (польский)
Português (португальский)
Português-Brasil (бразильский португальский)
Română (румынский)
Suomi (финский)
Svenska (шведский)
Türkçe (турецкий)
Tiếng Việt (вьетнамский)
Українська (украинский)
Сообщить о проблеме с переводом
so thats not the problem and running with windows 8 compabilyty? pfff serius?
@__SpOO__ ok ill check it now
i thout that is cosing by amd user experience (amd telemetry) and i disable it but that not helped
About the error, it is exactly the same error(Event 10016, DistributedCOM) that I had and think fixed already. So far crash clear here, but we will see.
I am 99% sure that at least my QC game crashes are caused by this s h i e t...
I will try now this.. fix:
"Yes, get rid of the error by going into the Event Viewer and clicking on the event then click on the details tab and then finally the (+) symbol next to System. The GUID will be revealed and just simply copy and paste it into the Registry Search function with the "Keys" checkbox ticked and delete the GUID wherever it appears in the Registry.
My GUID appeared in two locations in the registry and I deleted both without harm being done to Start Up and booting procedures.
Make sure you have a backup of the Registry first, that you get through the Command Prompt in the Recovery environment just in case anything should go wrong."
It is a win 10 problem, not QC it seems.
i reinstall driver to older version
heh maby this will fix this
heh i dont have idea why this game is crashing for me...
"Hi,
I have read here and in many other places to suppress event 10016. That is, if you as me, a bad approach.
In this case, with Windows.SecurityCenter it is not as easy to fix as the old classics with the RuntimeBroker, ShellWindows etc which is solved by giving full rights to Administrator in registry and then give SYSTEM, Local Service or whatever launch permissions in DCOM Config. The reason is that you, in this case, don't have any ApplicationId to play around with.
The problem in this case is that the service for Windows SecurityCenter (wscsvc) have a delayed autostart while "things" like the WscBrokerManager and WscCloudBackupProvider tries to initiate very early in the startup process. It will fail with error event 10016. wscsvc will initiate after ~2 minutes and then everything will be instantiated as normal so you will have no side effects of these errors in the event log but it's annoying.
You solve this by changing the service wscsvc from delayed autostart to normal autostart. You don't (normally) have permission to do it from the services app so you must do it in the registry.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wscsvc
Change the DWORD DelayedAutoStart from 1 to 0."
Upłynął limit czasu (60000 ms) podczas oczekiwania na połączenie się z usługą BcastDVRUserService_34b25.
next:
Nie można uruchomić usługi BcastDVRUserService_34b25 z powodu następującego błędu:
Usługa nie odpowiada na sygnał uruchomienia lub sygnał sterujący w oczekiwanym czasie.
next:
Model DCOM odebrał błąd 1053 podczas próby uruchomienia usługi BcastDVRUserService_34b25 z argumentami Niedostępny w celu uruchomienia serwera:
Windows.Media.Capture.Internal.AppCaptureShell
next:
Zgodnie z ustawieniami uprawnienia właściwe dla aplikacji nie jest udzielane uprawnienie Lokalny Aktywacja do aplikacji serwera COM z identyfikatorem klasy CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
i identyfikatorem aplikacji APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
użytkownikowi DESKTOP-U3OD7SR\jakub o identyfikatorze zabezpieczeń SID (S-1-5-21-1643748424-3511953992-1170482374-1001) z adresu LocalHost (użycie LRPC) działającemu w kontenerze aplikacji o identyfikatorze SID Niedostępny (Niedostępny). To uprawnienie zabezpieczeń można modyfikować przy użyciu narzędzia administracyjnego Usługi składowe.
all in the same time and game crashed
Just do that final fix in my post above and lets hope it will be a final fix for this problem.
Go into Registry with regedit, find and do this:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wscsvc
Change the DWORD DelayedAutoStart from 1 to 0