Instalar Steam
iniciar sesión
|
idioma
简体中文 (chino simplificado)
繁體中文 (chino tradicional)
日本語 (japonés)
한국어 (coreano)
ไทย (tailandés)
Български (búlgaro)
Čeština (checo)
Dansk (danés)
Deutsch (alemán)
English (inglés)
Español de Hispanoamérica
Ελληνικά (griego)
Français (francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (húngaro)
Nederlands (holandés)
Norsk (noruego)
Polski (polaco)
Português (Portugués de Portugal)
Português-Brasil (portugués de Brasil)
Română (rumano)
Русский (ruso)
Suomi (finés)
Svenska (sueco)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraniano)
Comunicar un error de traducción
My new computer has had 9 of these in the last 7 days : {
Critical 1/3/2022 6:49:56 AM Kernel-Power 41 (63)
That is no bueno. Bad PSU or motherboard.
Quick google-fu says that is related to Brother iPrint&scan. Most likely not related to game crashing issue, but if you're not using it might well uninstall the thing if it is throwing errors.
Thanks... I checked this app and there is an update... I'll try again and get the time of my issue and re-check the event viewer to pinpoint the time and problems...
It is possible (issue with resuming from sleep mode). Monitor ir.
True. When there are issues, a clean re-install is a good idea. Generally speaking updating from GFE should be no problem.
Heres the last warning i got in the events viewer b4 the crash
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 1/7/2022 10:27:54 AM
Event ID: 10016
Task Category: None
Level: Warning
Keywords: Classic
User: SYSTEM
Computer: DESKTOP-S0UI88U
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>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2022-01-07T18:27:54.4021565Z" />
<EventRecordID>18580</EventRecordID>
<Correlation ActivityID="{2722c943-40e3-41f2-afda-9c86c54c1456}" />
<Execution ProcessID="1148" ThreadID="1292" />
<Channel>System</Channel>
<Computer>DESKTOP-S0UI88U</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>
I thought it worked, but didn't.. went to an older driver version, but still doing the same thing.
Are you getting BSOD even if you don't play the game?
something must have changed, last time I got a BSOD was a recent driver update, I had to rollback and that fixed it.
in your case either a driver or a new hardware? just need to start ruling out things one by one :/
At first it was kernal errors but those are all gone now.