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
Please provide more information.
Sharing your log files would also be a great help.
https://steamcommunity.com/sharedfiles/filedetails/?id=463645931
And also how should i paste the output log?
https://www.filemail.com
https://www.filemail.com/d/dwcmlupfldmqfwk
(it will be available for 7 days)
so follow this info to fix any corruptions.
Open up command line tool and run these two commands let each one finished its process before copying the next command.
Open the command line tool with the keyboard shortcut Windows Key + X.
It'll appear in the menu twice: Command Prompt and Command Prompt (Admin). The second option will open an "elevated" Command Prompt, which gives you administrator privileges, which are required for some commands. In nearly all cases, it's better to use the elevated Command Prompt — it can do everything that the normal Command Prompt can and more.
So click the admin one.
Run this line first..
DISM.exe /Online /Cleanup-image /Restorehealth
Then once the 1st is finished run this one
sfc /scannow
These checks will find and try to fix any file corruption in Windows.
Report back on what each one reports back.
C:\Windows\system32>DISM.exe /Online /Cleanup-image /Restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.19041.844
Image Version: 10.0.19045.2604
[] The restore operation completed successfully.
The operation completed successfully.0
And the SFC /SCANNOW:
C:\Windows\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.
Since it's physically impossible for an application running in user space to trigger a BSOD, it's either a driver or hardware issue (faulty RAM, inadequate cooling, failing SSD etc.).