Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
CMD (RUN AS ADMIN)
SFC /SCANNOW
if it needs a repair, use DISM to do that and verify all the OS files.
https://answers.microsoft.com/en-us/insider/forum/all/how-to-repair-your-system-files-using-dism-and-sfc/1021b42a-09ff-41a0-a95a-48f3ee3ae699
Temperature over time.
Ram stick defect.
Old/bad capacitor.
Software fault/error/incompatible software conflict.
Scheduled task erroring / conflicting with an app.
Psu, cpu, mobo or gpu too hot.
Seriously. Check event viewer, run the sfc scannow option given above etc. More information.
Else like previous suggestions, get an actual tech to solve computer issues as you're posting loads of threads needing help which seems very unusual.
SFC is the quick checker. If you actually have a problem, use of DISM will almost be a must.
Win10 22H2 is supported; it's not like we are talking about Win7/8 here. Even when a WinOS expires or becomes EoL, DISM still works as you can verify the OS files from an off-line ISO if available rather then the Online option.
Get-WinEvent -LogName System -ErrorAction SilentlyContinue | Where-Object { $_.Level -eq 1 -or $_.Level -eq2 } | Select-Object -First 20
Then copy paste the system logs here.
Also, the folks at Microsoft Forums are still starting their replies with "Hi! I'm a <insert company position here> at Microsoft! /sfc scannow" to this day. That is just concrete evidence.