Datorn stängs av utan felmeddelande

2023-01-10 21:46

Medlem ★

Plats: Norrköping
Registrerad: Jan 2011

●

Datorn stängs av utan felmeddelande

Jag har problem med att datorn stängs av och startar om utan någon bluescreen eller något felmeddelande.
Det händer när jag spelar Escape from Tarkov, men jag har inte spelat något annat senaste månaden. I början på december så fungerade cyberpunk men sedan dess så har jag tex uppdaterat bios och installerat om Windows. Ska testa cyberpunk igen nu tills imorgon kväll.

Om jag reconnectar efter att datorn startat om så kraschar det efter någon sekund igen. Men sen om jag söker en ny match så kan det funka bra och fortsätta fungera bra i flera timmar utan problem. Det har varit drops på Twitch så datorn har stått på med webbläsaren öppen i 10 dagar, under tiden datorn har stått på med bara webbläsaren uppe så har den inte kraschat någon gång. Jag har kollat lite på reddit osv men inte sett någon som haft samma problem.

Jag har även haft problem med att min mikrofon har slutat fungera några gånger i Discord, då hjälper det inte att byta input i inställningar eller i Windows, men efter restart så funkar det igen, osäker om det kan vara relaterat på något sätt.

Specs:
CPU: 12900ks
Moderkort: Asus Z690 APEX
RAM: 32GB G.skill 6600MHz (Men det kraschar i default speed också, dvs utan xmp/manuell ändring)
GPU: Asus Strix 3090 OC
PSU: Seasonic Prime TX 1000W
M2: 2* WD Black SN850 1TB
Mikrofon: Rode Podcaster USB
Övrigt: Logitech G pro Superlight mus, High flow next flödesmätare, Streamdeck, Philips Fidelio X2HR hörlurar
OS: Windows 11 Fullt uppdaterat

CPU,GPU och Ram är vattenkylt

Senaste BIOS
Senaste drivrutiner till GPU
Drivrutiner från ASUS sida till Internet,Ljud,Chipset,"SerialIO",Intel MEI & ME
Senaste firmware till gpu,mus,M2,flödesmätaren, Streamdeck
Jag har testat installera om Windows
OCCT Powertest kördes i en timme utan problem
Temperaturer ser bra ut i Hwinfo.
Default inställningar i BIOS
Ingen GPU OC

Jag har beställt en PSU testare (Den där med en liten skärm på som säljs under massor olika varumärken) men den kommer på Måndag, finns det något mer jag kan kolla/testa medans jag väntar?

Tack i förväg

Visa signatur

CPU : 12900KS GPU : 3090 Strix OC RAM : G.Skill 32GB 6600MHz 34-40-40-105SSD : 2st SN850 1TB Bildskärm 1: Strix PG279Q 1440p@165Hz G-SYNC Bildskärm 2: Asus VG27AQ 27" 1440p@165Hz Bildskärm 3: Asus VG27AQ 27" 1440p@165Hz Vattenkylning CPU,GPU och RAM, 3*360 rad

Rapportera Redigera

Citera flera Citera

2023-01-10 21:50

Permalänk

NordhNet

Moderator

Forumledare ★

Plats: Här
Registrerad: Jul 2009

●

@Boozfob: Står det något i felloggarna/eventviewer när krascherna inträffat? 🤔

Visa signatur

Forumets regler | Har du synpunkter på hur vi modererar? Kontakta SweClockers/moderatorerna

Jag stavar som en kratta

Gillar lök på discord

Rapportera Redigera

Citera flera Citera

2023-01-11 10:44

Permalänk

blunden

Medlem ★

Plats: Stockholm
Registrerad: Dec 2003

●

Ja, kolla som sagt i Event Viewer. Det borde förmodligen stå något där om det inte är nätagget som bryter strömmen.

Är det bara vid load eller även idle som detta händer? Liknande typer av omstarter (särskilt om de sker vid idle) kan exempelvis orsakas av för låga värden på olika CPU- och RAM-relaterade spänningar i vissa fall.

Visa signatur

Rapportera Redigera

Citera flera Citera

2023-01-11 17:02

Permalänk

Boozfob

Medlem ★

Plats: Norrköping
Registrerad: Jan 2011

●

Jag har haft Cyberpunk på i 18 timmar nu utan någon crash (Stående AFK vid en rondell)
(Spelet crashade dock på startup vid första starten)

Skrivet av NordhNet:

@Boozfob: Står det något i felloggarna/eventviewer när krascherna inträffat? 🤔

Gå till inlägget

Skrivet av blunden:

Ja, kolla som sagt i Event Viewer. Det borde förmodligen stå något där om det inte är nätagget som bryter strömmen.

Är det bara vid load eller även idle som detta händer? Liknande typer av omstarter (särskilt om de sker vid idle) kan exempelvis orsakas av för låga värden på olika CPU- och RAM-relaterade spänningar i vissa fall.

Gå till inlägget

Ja det finns ju lite saker i loggarna, såhär ser det ut (Kopierar från en crash till nästa crash, ser ju ungefär likadant ut mellan de olika crasherna.)

Det har bara crashat när jag är i en match samt 1 gång i "hideout", men aldrig i menyn/inventory
Jag hade ju även datorn på i 10 dagar när det var drops på Twitch.tv och under tiden när datorn var idle med bara webbläsaren igång så crashade det inte någon gång.

Critical 2023-01-10 19:41:56 Kernel-Power 41 (63)
Error 2023-01-10 19:42:00 EventLog 6008 None
Warning 2023-01-10 19:39:41 DistributedCOM 10016 None
Warning 2023-01-10 19:39:22 DistributedCOM 10016 None
Warning 2023-01-10 19:39:21 DistributedCOM 10016 None
Warning 2023-01-10 19:39:08 User Device Registration 360 None
Warning 2023-01-10 19:39:07 WMI 63 None
Warning 2023-01-10 19:39:07 WMI 63 None
Warning 2023-01-10 19:39:07 WMI 63 None
Warning 2023-01-10 19:39:06 LSA (LsaSrv) 6155 None
Warning 2023-01-10 19:39:06 LSA (LsaSrv) 6155 None
Warning 2023-01-10 19:39:06 LSA (LsaSrv) 6155 None
Warning 2023-01-10 19:39:06 LSA (LsaSrv) 6155 None
Warning 2023-01-10 19:39:06 LSA (LsaSrv) 6155 None
Warning 2023-01-10 19:39:06 LSA (LsaSrv) 6155 None
Warning 2023-01-10 19:39:06 LSA (LsaSrv) 6155 None
Warning 2023-01-10 19:39:06 LSA (LsaSrv) 6155 None
Warning 2023-01-10 19:39:06 LSA (LsaSrv) 6155 None
Warning 2023-01-10 19:39:06 LSA (LsaSrv) 6155 None
Warning 2023-01-10 19:39:06 LSA (LsaSrv) 6147 None
Error 2023-01-10 19:39:06 Kernel-EventTracing 28 Provider
Warning 2023-01-10 19:39:03 e2fnexpress 27 None
Error 2023-01-10 19:39:06 Eventlog 1101 Event processing
Critical 2023-01-10 19:39:02 Kernel-Power 41 (63)
Error 2023-01-10 19:39:06 EventLog 6008 None

Dold text

Detaljerat:

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 2023-01-10 19:41:56
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: Filips
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />
<EventID>41</EventID>
<Version>9</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2023-01-10T18:41:56.6673471Z" />
<EventRecordID>6810</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Filips</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">0</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
<Data Name="Checkpoint">0</Data>
<Data Name="ConnectedStandbyInProgress">false</Data>
<Data Name="SystemSleepTransitionsToOn">0</Data>
<Data Name="CsEntryScenarioInstanceId">0</Data>
<Data Name="BugcheckInfoFromEFI">false</Data>
<Data Name="CheckpointStatus">0</Data>
<Data Name="CsEntryScenarioInstanceIdV2">0</Data>
<Data Name="LongPowerButtonPressDetected">false</Data>
<Data Name="LidReliability">false</Data>
<Data Name="InputSuppressionState">0</Data>
<Data Name="PowerButtonSuppressionState">0</Data>
<Data Name="LidState">3</Data>
</EventData>
</Event>

Log Name: System
Source: EventLog
Date: 2023-01-10 19:42:00
Event ID: 6008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Filips
Description:
The previous system shutdown at 7:39:06 PM on ‎1/‎10/‎2023 was unexpected.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6008</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2023-01-10T18:42:00.6731100Z" />
<EventRecordID>6796</EventRecordID>
<Correlation />
<Execution ProcessID="2500" ThreadID="2552" />
<Channel>System</Channel>
<Computer>Filips</Computer>
<Security />
</System>
<EventData>
<Data>7:39:06 PM</Data>
<Data>‎1/‎10/‎2023</Data>
<Data>
</Data>
<Data>
</Data>
<Data>6</Data>
<Data>
</Data>
<Data>
</Data>
<Binary>E707010002000A001300270006007503E707010002000A0012002700060075033C0000003C000000000000000000000000000000000000000100000000000000</Binary>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 2023-01-10 19:39:41
Event ID: 10016
Task Category: None
Level: Warning
Keywords: Classic
User: FILIPS\Filip
Computer: Filips
Description:
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 FILIPS\Filip SID (S-1-5-21-145374741-3896552036-1587776726-1001) 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="2023-01-10T18:39:41.4715944Z" />
<EventRecordID>6781</EventRecordID>
<Correlation ActivityID="{ce9b1612-2522-000f-201d-9bce2225d901}" />
<Execution ProcessID="1432" ThreadID="8328" />
<Channel>System</Channel>
<Computer>Filips</Computer>
<Security UserID="S-1-5-21-145374741-3896552036-1587776726-1001" />
</System>
<EventData>
<Data Name="param1">application-specific</Data>
<Data Name="param2">Local</Data>
<Data Name="param3">Activation</Data>
<Data Name="param4">{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}</Data>
<Data Name="param5">{15C20B67-12E7-4BB6-92BB-7AFF07997402}</Data>
<Data Name="param6">FILIPS</Data>
<Data Name="param7">Filip</Data>
<Data Name="param8">S-1-5-21-145374741-3896552036-1587776726-1001</Data>
<Data Name="param9">LocalHost (Using LRPC)</Data>
<Data Name="param10">Unavailable</Data>
<Data Name="param11">Unavailable</Data>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 2023-01-10 19:39:22
Event ID: 10016
Task Category: None
Level: Warning
Keywords: Classic
User: FILIPS\Filip
Computer: Filips
Description:
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 FILIPS\Filip SID (S-1-5-21-145374741-3896552036-1587776726-1001) 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="2023-01-10T18:39:22.9047404Z" />
<EventRecordID>6778</EventRecordID>
<Correlation ActivityID="{ce9b1612-2522-000e-7a20-9bce2225d901}" />
<Execution ProcessID="1432" ThreadID="9396" />
<Channel>System</Channel>
<Computer>Filips</Computer>
<Security UserID="S-1-5-21-145374741-3896552036-1587776726-1001" />
</System>
<EventData>
<Data Name="param1">application-specific</Data>
<Data Name="param2">Local</Data>
<Data Name="param3">Activation</Data>
<Data Name="param4">{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}</Data>
<Data Name="param5">{15C20B67-12E7-4BB6-92BB-7AFF07997402}</Data>
<Data Name="param6">FILIPS</Data>
<Data Name="param7">Filip</Data>
<Data Name="param8">S-1-5-21-145374741-3896552036-1587776726-1001</Data>
<Data Name="param9">LocalHost (Using LRPC)</Data>
<Data Name="param10">Unavailable</Data>
<Data Name="param11">Unavailable</Data>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 2023-01-10 19:39:21
Event ID: 10016
Task Category: None
Level: Warning
Keywords: Classic
User: FILIPS\Filip
Computer: Filips
Description:
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 FILIPS\Filip SID (S-1-5-21-145374741-3896552036-1587776726-1001) 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="2023-01-10T18:39:21.7627389Z" />
<EventRecordID>6777</EventRecordID>
<Correlation ActivityID="{ce9b1612-2522-0016-f519-9bce2225d901}" />
<Execution ProcessID="1432" ThreadID="9396" />
<Channel>System</Channel>
<Computer>Filips</Computer>
<Security UserID="S-1-5-21-145374741-3896552036-1587776726-1001" />
</System>
<EventData>
<Data Name="param1">application-specific</Data>
<Data Name="param2">Local</Data>
<Data Name="param3">Activation</Data>
<Data Name="param4">{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}</Data>
<Data Name="param5">{15C20B67-12E7-4BB6-92BB-7AFF07997402}</Data>
<Data Name="param6">FILIPS</Data>
<Data Name="param7">Filip</Data>
<Data Name="param8">S-1-5-21-145374741-3896552036-1587776726-1001</Data>
<Data Name="param9">LocalHost (Using LRPC)</Data>
<Data Name="param10">Unavailable</Data>
<Data Name="param11">Unavailable</Data>
</EventData>
</Event>

Log Name: Microsoft-Windows-User Device Registration/Admin
Source: Microsoft-Windows-User Device Registration
Date: 2023-01-10 19:39:08
Event ID: 360
Task Category: None
Level: Warning
Keywords:
User: FILIPS\Filip
Computer: Filips
Description:
Windows Hello for Business provisioning will not be launched.
Device is AAD joined ( AADJ or DJ++ ): Not Tested
User has logged on with AAD credentials: No
Windows Hello for Business policy is enabled: Not Tested
Windows Hello for Business post-logon provisioning is enabled: Not Tested
Local computer meets Windows hello for business hardware requirements: Not Tested
User is not connected to the machine via Remote Desktop: Yes
User certificate for on premise auth policy is enabled: Not Tested
Machine is governed by none policy.
Cloud trust for on premise auth policy is enabled: Not Tested
User account has Cloud TGT: Not Tested
See https://go.microsoft.com/fwlink/?linkid=832647 for more details.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-User Device Registration" Guid="{23b8d46b-67dd-40a3-b636-d43e50552c6d}" />
<EventID>360</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2023-01-10T18:39:08.6608820Z" />
<EventRecordID>45</EventRecordID>
<Correlation />
<Execution ProcessID="6840" ThreadID="6956" />
<Channel>Microsoft-Windows-User Device Registration/Admin</Channel>
<Computer>Filips</Computer>
<Security UserID="S-1-5-21-145374741-3896552036-1587776726-1001" />
</System>
<EventData>
<Data Name="Message">Windows Hello for Business provisioning will not be launched.</Data>
<Data Name="DeviceIsJoined">Not Tested</Data>
<Data Name="AADPrt">No</Data>
<Data Name="NgcPolicyEnabled">Not Tested</Data>
<Data Name="NgcPostLogonProvisioningEnabled">Not Tested</Data>
<Data Name="NgcHardwarePolicyMet">Not Tested</Data>
<Data Name="UserIsRemote">Yes</Data>
<Data Name="LogonCertRequired">Not Tested</Data>
<Data Name="MachinePolicySource">none</Data>
<Data Name="UseCloudTrust">Not Tested</Data>
<Data Name="CloudTgt">Not Tested</Data>
</EventData>
</Event>

Log Name: Application
Source: Microsoft-Windows-WMI
Date: 2023-01-10 19:39:07
Event ID: 63
Task Category: None
Level: Warning
Keywords:
User: SYSTEM
Computer: Filips
Description:
A provider, IntelMEProv, has been registered in the Windows Management Instrumentation namespace root\Intel_ME to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WMI" Guid="{1edeee53-0afe-4609-b846-d8c0b2075b1f}" />
<EventID>63</EventID>
<Version>2</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2023-01-10T18:39:07.8183250Z" />
<EventRecordID>2795</EventRecordID>
<Correlation />
<Execution ProcessID="3852" ThreadID="4132" />
<Channel>Application</Channel>
<Computer>Filips</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<data_0x8000003F xmlns="http://manifests.microsoft.com/win/2006/windows/WMI">
<Provider>IntelMEProv</Provider>
<Namespace>root\Intel_ME</Namespace>
</data_0x8000003F>
</UserData>
</Event>

Log Name: Application
Source: Microsoft-Windows-WMI
Date: 2023-01-10 19:39:07
Event ID: 63
Task Category: None
Level: Warning
Keywords:
User: SYSTEM
Computer: Filips
Description:
A provider, IntelMEProv, has been registered in the Windows Management Instrumentation namespace root\Intel_ME to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WMI" Guid="{1edeee53-0afe-4609-b846-d8c0b2075b1f}" />
<EventID>63</EventID>
<Version>2</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2023-01-10T18:39:07.8167013Z" />
<EventRecordID>2794</EventRecordID>
<Correlation />
<Execution ProcessID="3852" ThreadID="4132" />
<Channel>Application</Channel>
<Computer>Filips</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<data_0x8000003F xmlns="http://manifests.microsoft.com/win/2006/windows/WMI">
<Provider>IntelMEProv</Provider>
<Namespace>root\Intel_ME</Namespace>
</data_0x8000003F>
</UserData>
</Event>

Log Name: Application
Source: Microsoft-Windows-WMI
Date: 2023-01-10 19:39:07
Event ID: 63
Task Category: None
Level: Warning
Keywords:
User: SYSTEM
Computer: Filips
Description:
A provider, IntelMEProv, has been registered in the Windows Management Instrumentation namespace root\Intel_ME to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WMI" Guid="{1edeee53-0afe-4609-b846-d8c0b2075b1f}" />
<EventID>63</EventID>
<Version>2</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2023-01-10T18:39:07.8143533Z" />
<EventRecordID>2793</EventRecordID>
<Correlation />
<Execution ProcessID="3852" ThreadID="5544" />
<Channel>Application</Channel>
<Computer>Filips</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<data_0x8000003F xmlns="http://manifests.microsoft.com/win/2006/windows/WMI">
<Provider>IntelMEProv</Provider>
<Namespace>root\Intel_ME</Namespace>
</data_0x8000003F>
</UserData>
</Event>