安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
讨论规则及指引
2 
举报此帖
In 300 hours or so, I've had 45-50 crashes, the sort that hard lock up my machine. Requiring a full reboot, which is needless to say, not happy mood making.
It isn't a graphical setting issue as these crashes seem to happen anywhere between 1 hour from playing all the way to 8+, I say 8+ because there was no crash but I needed to turn off the game at that point.
The only thing I have noticed about the crashes is they seem connected with the auto save/cloud sync feature, when ever it triggers. Their servers lag or something gets corrupted and then there is some sort of cascade failure going. The in game sounds end up in a loop but the graphics just lock up along with the inputs, both keyboard and mouse.
About 50% of the time it seems related to that, the other 50% I am not sure wtf caused it, overlapping quest updates/triggers or one of those avenge fallen player quests that spawn in sometimes, there is always a weird hitch/stutter when those happen. Then the lock up, its about 20% chance to create a lock up, I've avenged 30+ players and ignored about 30 more.
I'll add that I play this under Linux so, my issue is probably something related more with Wayland and Wine/Proton rather than the game, but if similar things happen for windows people then its probably the game itself.
The only good news is that the auto saves are so frequent the most you lose is 2 minutes of progress. Still annoying.
The driver im using is : 531.41.
Rolling back to that really helped a lot.
Im using a rtx 3080ti with an I9 processor. 64 GB RAM. Windows 10
Oh, and im 212 hours into the game, so its not terrible often at all now.
There is no replay value for me, since the story is rails mostly, I won't be farming all the different gear sets in the endless mini-grind side stuff they have. I figure I have probably 10-15 hours tops left to game out.
Also I am not technically savvy enough to figure stuff out under Linux yet. Since I am not sure what I am looking at, what I looking for, let alone what it should be, in order to attempt anything.
So just view my post as an idea to try. If you have no real reason why the game seems to randomly crash.
Anyway uninstalled now, turned out only had 3 hours of game left to play.
just change swap file depends on your system RAM , you could do it long time ago , that's it
1. Whatever game your are playing, play it and generate a random crash.
2. Check in Event Viewer if you have the below error regarding nvlddmkm:
The description for Event ID *number* from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\Video3
Error occurred on GPUID: 100 (or any other number basically)
The message resource is present but the message was not found in the message table
3. If you have the above message mentioning this nvlddmkm.sys search for it in Windows/System32. The original file should be found on a path/folder like: Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_52f3d9d461d3ba3c. Not sure if the end of the folder name will be the same for you but until "_amd64_" it'll be probably the same.
4. Change the file owner of this nvlddmkm.sys from TrustedInstaller to your Windows User ID and give yourself FULL access! Reboot your PC and it should be done. If it's not working then:
5. Copy the found nvlddmkm.sys file into your Windows/System32/drivers folder.
6. Also change permission on the copied file. Give your User full access on this file. Admins full access is not enough!
7. Disable all Nvidia related audio devices in Device Manager. (Not sure if this one is actually needed but worth a try too if the above still doesn't resolve the issue)
8. If none of the above works, try to change your XMP profile. Lower your RAM's Mhz by a bit. For me I had them on 3600 Mhz, changed them to 3200 Mhz and this one actually removed all of my crashes. The above just reduced the occurance
I tried this and I can confirm I finally played 2.5 hours in a row without crashing. Even after a few alt+tab. After I removed full access from "Users" the game crashed again with the same error after just loading up my savegame. So the permission part is definitely necessary.
Hope it helps to you guys.