安裝 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(越南文)
Українська(烏克蘭文)
回報翻譯問題
The fancy blue screen - does it look like this?
http://i1-win.softpedia-static.com/screenshots/Blue-Screen_1.png
Yes, it looks exactly like that- except without the text. I've never seen it happen with that text, or any kind of text on it for that matter.
RunDLL
There was a problem starting:
C:/Users/"MyUserName"/AppData/Local/Conduit/BackgroundContainer/BackgroundContainer.dll.
The specified module could not be found.
Also, I don't click on any ads, download any malware or anything suspicious or something that sounds even slightly dumb without proof. Plus, to back it up, I have Norton, so even with my standards if something got through Norton would get rid of it and alert me. I really think it might have something to do with my PC though.
http://answers.microsoft.com/en-us/protect/forum/protect_scanner-protect_scanning/run-dll-error-messagebackground-containerdll/49612202-667e-4a71-8e9a-d02161d8bc19
So, check your PC with antivirus (best is offline via a linux boot cd -> eg "Avira Rescue System") and antimalware (eg the one from Malwarebytes).
Try using GameAssistant[www.iobit.com] to monitor your CPU/GPU temps in-game. U have to enable the option once u launch the app for first time.
If the temps are ok, but the issue continues, please update to latest drivers, namely the ones for your Intel Chipset and Intel HD GPU. Linked below.
Intel Chipset 8/9 series
https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=20775&lang=eng&ProdId=816
Intel HD 2500 series GPU Driver
https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=24329&lang=eng&ProdId=3711
Steam Updater popping up is normal whenever Steam crashes; which if ur system is hard-locking and/or rebooting, Steam is technically being forced closed, cause it doesn't get exited properly. So upon next launch of Steam, it simply does a check on the core client files before logging in and all that.
I'd open Command Prompt as an Admin user and run the following as well, to check for Local Disk and OS File related issues.
CHKDSK /F (verifies your HDD data; checks for a marks off bad sectors if present)
SFC /SCANNOW (verifies your OS files; let's u know if OS files are corrupted)