安裝 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(越南文)
Українська(烏克蘭文)
回報翻譯問題
Download the Media creation tool from the Microsoft website. It can found here[www.microsoft.com]. Then use the media creation tool to download and mount the Windows 10 installation files on a flash drive. Then once the tool is done boot form the flash drive on the PC you wish to install it on.
If you've overclocked anything put it back to default speeds.
If you've done a fresh win 10 install I'd be looking at hardware, tbh not less or equal to is generally bad OC or Ram.
Ps, put your full specs in your profile so we know what you've got right down to the psu make / model.
i encoountered this problem more than a decade ago when mixing memory modules of different brands. same speed, same latency, same voltage, different brands, would manifest only in certain games like the sims.
maybe do what upcoast suggested.
Download WhoCrashed and it'll give more details about the crash dump and what caused it
Also check the BIOS to ensure RAM is setup correctly; enable XMP, otherwise your RAM is setup wrong. Which can lead to such errors because the RAM is not operating at the correct timings.
If you have no clue start at the beginning. Update Chipset, reboot and then sound, network, gpu and any others as required. Do Not rely on windows for drivers, go to manufacturers sites and get the correct ones.
Really, that's your first suggestion. Hopefully no-one listens to you.
its almost always psu, ram or unstable overclock
It can be faulty motherboard and or GPU but tbat is much more rare
I left the IT field around the time XP was released so my knowledge is a bit dated but surely we would treat drivers and possible OS corruption first to rule them out before we start throwing hardware away.
Edit; Re-reading the post, the OP states that the last time this happened they re-installed windows to fix it. Were correct drivers installed ?