ติดตั้ง 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 (เวียดนาม)
Українська (ยูเครน)
รายงานปัญหาเกี่ยวกับการแปลภาษา
BTW, the error code means, the game had some issue writing to memory which can have all kinds of causes.
One thing you can also try, once you get back is go into the Display Settings in Windows --> Graphic Settings and disable "Hardware-Accelerated GPU Planning".
Hopefully dark-breed stops by at some point and maybe helps shed some light on that particular offset.
Also, out of interest, what GPU/CPU do you use and what GPU driver are you running?
Again, memory-access issues can have a large amount of possible causes, ranging from simple conflicts with other programs to hardware issues or a configuration issue with the OS. It can be a pita to troubleshoot, if you have no other leads to go by and have tried all the common troubleshooting steps for crashing with this particular game.
The napalm-strike solution would be to re-install Windows, since that almost always fixes any software/OS related problems. But chances are it's fixable without having to go through that trouble.
Do you run Tools like process lasso, process explorer or System explorer ?
This offset is a initialisation of a encryption function used over directx.
Most common it appears at running this tools in the System but there are more possible causes (faulty Windows files, malfunction gpu driver, other Background apps, instable overclock, the worst cases are faulty directx or Hardware problem)
So it would be needed to know what cpu and gpu you use too.
I use a i7 12th gen and a 3080
But again, it may be avoidable and it's more of a last resort thing, after you've troubleshooted enough, that you think it's worth going through the trouble.
Currently on Ryzen 7 2700x, 3060ti on driver 531.41, so it doesn't appear to be a difference in driver functions.
I wonder if dark breed could illuminate whether things like windows MPO, sysmain superfetch, and other misc things could relate to these issues.
I just don't want to go crazy making system changes when everything else works, and has worked, for the longest time.