安裝 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(越南文)
Українська(烏克蘭文)
回報翻譯問題
You can attempt a startup repair with any Windows installation disk. It might fix the issue or it might not.
This issue occurs because of an NTFS file system memory leak issue. Specifically, when an application opens a file that has an oplock on it for modification in a transaction, NTFS will break the oplock and will leak nonpaged pool memory. This causes excessive memory usage and memory allocation failures. https://support.microsoft.com/en-us/help/2764302/0x0000001e-stop-error-occurs-intermittently-in-windows-7-sp1-and-windo
Alternatively use a bootable diag tool like UBCD[www.ultimatebootcd.com]
You need to spam F6 before windows logo shows up, and select the second option below, and select System Restore and select the automatic restore point by Windows.
Restart your comp afterwards and you're all good.
Thanks for the different solutions guys! You can also try those at the top if this one does not work for you.