Инсталирайте 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)
Украински (Українська)
Докладване на проблем с превода
5950x/3080ti
Also...to second poster, there's no guarantee that you guys are experiencing the same issue. Games are complex and large pieces of software where things like different hardware, operating systems, drivers, etc etc. are all interacting and just because both your games are crashing doesn't mean that it's a related issue whatsover...
Specs:
Intel i5-13600k
32gb RAM
AMD 7900 XTX
Win11
Intel i7 8700
32 gb ram
Geforce 2700 super
win10
For all I know these few crashes can be because storage-related on my windows-drive which is severely starved for space which is a problem for me (game installed on other, still files on C)
Intel 13600k
32GB RAM
GTX 1080
WIN10
29 hours in game, all work perfect, no crashes, lags or other weird things
No AMD driver related dialog pops up just the game crash dialog and a question whether I wish to send the dump to the developers.
Sometimes the game runs fine for 2 hours, other times it crashes right after 5 minutes.
For me the crashes started right after I switched from RX 6600XT to Sapphire Pulse RX 7900XT (my PSU is Seasonic Vertex 850W).
I took a peek at the generated dumps and it always fails at the same place on the same exception...
The game makes a call into D3D12Core.dll (CGraphicsCommandList::OMSetRenderTargets) which in turn calls implementation inside the AMD GPU driver library amdxc64.dll where it crashes with an exception "Access violation reading location" and the target memory address.
Given the fact that this issue is obviously not so widespread... this points to an issue inside AMD Radeon driver 🫠
Have you reported this to AMD? Guerilla appears to be radio silent with HZD these days, but AMD should be able to patch out the bug that gets triggered on that call.
https://www.amd.com/en/support/kb/faq/amdbrt
Off Topic: I updated my drivers via the offical software adrenalin, and guess what, it destroyed windows wich didnt boot correctly afterwards anymore... Bluescreen (they fixed this but still) How can a huge company be so bad at relasing a driver for GPUs... unbeliveable