安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
Then i say few steam user have discover this, dont forget steam has 1 billion account, so it can look like many then its actual not., so as yoiu see then few complain over disk its still seen as so rare, but not on steam. then we all are here or know this place.
i recommend remove or move that line down so other dont make same mistake , because i think you trigger wrong buzz word with it, because all things is connect in a pc and need eachother dont mean they cause the error, You have GPU DRIVER issue if Nvidia use custom install and make clean install then checkbox is there.
and after that , then recheck installed VC++ , use MS own support page with all then diffrent VC++ 32/64 bit version on MS page per diffrent year , or google "all-in-one VC++ "as most do.
many forget VC++ is still seen as runtime drivers, that was a huge thing in the past, and the better they are optimized the better a pc is running. game devs and steam support dont get this and they never will.
ps.
dont forget validate game intergrity of files and reinstall games has seen cause double old version of same, try avoid this, problem is old script force them.
dont forget the more games you have, then you learn this, so many dont get that, im sure you have seen corrupted VC++ before , the net is flooding with them now, and it has take users years to discover, before games act odd. this has increased over the many year from 2015.
this is why you use MS page and not what game devs and steam think.
gl with it.
ps.
AMD user , update you BRAND board pc bios and chipset driver, and stop use igpu if you have 2 cards, im done with AMD user here at steam, they make to many mistake in every steam post.
and you can send thanks to previous AMD steam user for that.
Okay i will check for that, i also noticed that i was playing a game within that 1-2 hour time period with 80+ temp on my gpu, do you think this might of caused damage to my GPU?
Thanks, that's easier to understand :)
2 gpu card and AMD not update, windows is not AMD support, they have own BRAND Contact AMD, if this is another lost AMD user
this is not a steam issue that AMD users keep make mistake.
75 % of all steam post is AMD user in trouble if this is not more.
i bet im not the only one that, can see it in any game hub.
As the other poster mentioned, it won't damage it. However, a gpu does not necessarily need to overheat to cause a game to crash. Faulty drivers or even a small faulty component on the gpu could also result in the gpu causing it to crash. It could also be due to the PSU not being able to supply enough power to it.
Sounds for me like a typical hdd misconfiguration. 80° is high but normally overheat is protected anyway. But who knows. If you just switched the hdd and the system was stable before, I see no interrelation.
I have reinstalled windows, i gave the Witcher 3 a go just to test if anything changed and it did run for longer but now the game still crashes around the 1-2 hour mark, the event logs shown here:
Event 1000, Application error.
Faulting application name: witcher3.exe, version: 4.0.1.17107, time stamp: 0x00000000
Faulting module name: witcher3.exe, version: 4.0.1.17107, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000da2890
Faulting process ID: 0x18dc
Faulting application start time: 0x01d9ae02754d2e1e
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\The Witcher 3\bin\x64\witcher3.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\The Witcher 3\bin\x64\witcher3.exe
Report ID: 1d7d3e6d-689f-48b2-ade1-2fc47089db26
Faulting package full name:
Faulting package-relative application ID:
Also the Event name: APPCRASH
Fault bucket 1566951663550186225, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: witcher3.exe
P2: 4.0.1.17107
P3: 00000000
P4: witcher3.exe
P5: 4.0.1.17107
P6: 00000000
P7: c0000005
P8: 0000000000da2890
P9:
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6EC.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER94E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER96F.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER96D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER97D.tmp.txt
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_witcher3.exe_e74bce02fb03c4538bad3d117f02b47c05b7268_e4516822_14ec2016-8d69-4d3b-8024-a8f3d062d72b
Analysis symbol:
Rechecking for solution: 0
Report Id: 1d7d3e6d-689f-48b2-ade1-2fc47089db26
Report Status: 268435456
Hashed bucket: 3881f25e4718747435beee3c661dc2f1
Cab Guid: 0
No sign of direct3D so i dont think its a GPU issue, i have noticed the Microsoft defender antivirus is quite prominent in the event logs, could it be that?. Any advice would be greatly appreciated, as i have tried almost everything and nothing has helped.
There are a couple of things you could try if you have not done so already.
The first would be to verify (verify integrity) the game files through steam. The alternative is to reinstall the game. Reason for doing so is due to the possibility that the cloning software you used might not have transferred the game files over properly. If this method does work out, then there is a good chance that your other games that were copied over could have been affected as well.
If the above doesn't work, then the next thing you could try would be to play Witcher 3 in DX11 (ie direct x 11) mode. I heard that the game isn't that stable on directx 12.
Good luck.
Dont forgert just becuse we dont agree on anything, other can still helper you maybe if you let them.
4 months ago*
All of Samsung ssds seem to have issues from what I’ve read. Also there’s a dispute on if the firmware is the issue or rather the fix. I think it impacts all 900 series ssds.
Recent article that covers the issue pretty well.
https://nascompares.com/2023/02/02/samsung-980-pro-970-evo-plus-pm9a1-and-more-reporting-failures-everything-we-know-so-far/
This suggest one of the following.
- Bad driver install. Basically reinstall drivers.
- Using out of date driver. Update said drivers.
- Overheating, or faulty hardware. Check hardware for temp, and do error check on SSD, can use crystal disc info, now it can't be GPU, CPU, or RAM, because they would've cause a much more noticeable issues such as system shutoff, bsod, or freezing, and shuttering. So I'm more to believe the SSD may have an issue, but you have to check on the SSD for errors, and writes been done, if you see a large amount of writes, or health on ssd dropping fast, then you can check to see firmware update done for your SSD, but if it is latest, and having issues, then you have to RMA the SSD for being faulty if within warranty policy.
- Corrupted Windows system files. To check on this, simply do the following run CMD as administrator, then type in " sfc /scannow " without quotes, if there no issue, then go ahead, and type this next into CMD " DISM /Online /Cleanup-Image /RestoreHealth " without quotes, what this does is compare your windows image to what online to ensure nothing faulty files, after this done, and no issues click windows start then click restart PC, after that when get back on windows run CMD as administrator again, do last scan just to double check for any issue, " sfc /scannow " without quotes.