login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem


OS: Windows 10 64-bit
GPU: EVGA GTX 750ti 2GB
CPU: AMD FX-4100 3.6ghz (Quad Core)
RAM: 8GM
Input Method: Xbox One Controller
It's an XAudio 2 library file (version 7 specifically, which shipped with Windows 7) which superceeds both the earlier XAudio and even earlier Directsound. It happens to be distributed with the earlier DX9 redistributable, but that's got nothing to do with the graphics API the game uses though.
I actually stumbled across an interesting MSDN (Microsoft Developer Network) blog earlier today which seems to explain why the crash happens.
http://blogs.msdn.com/b/chuckw/archive/2015/10/09/known-issues-xaudio-2-7.aspx
"The XAudio2 library in the legacy DirectX SDK makes use of COM creation and reference counting for lifetime management, and a recent investigation has found a problem in this implementation. In short: in some situations the XAudio DLL itself is unloaded before the XAudio2 objects are completely destroyed, thus leading to an access violation. This normally happens on exit, although the exact details of when it might be evident depends on exactly which version of Windows you are using and the overall process layout for your application."
The article explains how the issue can be easily worked around on the application level with a simple code modification, something I'd previously stated (incorrectly) probably wasn't possible.
To be clear, this is NOT a game issue. The problem absolutely is with the XAudio file, but can probably be fixed by CV if they so choose to (and they really should imo).
i think it was gone for the good now! i played for over half hour without any crashes
maybe works, i have to test more
but thank you very much
It's work!!!!!
need to mention that Fallout 4 also had this problem on launch but bethesta patched it under 24 hours from release so im still giving little bit evil eye to capcom on this matter.
Surprisingly enough, I haven't had any crashes with Fallout 4, and I've been playing it since launch with nearly 40 hours logged, so that crash must've been an issue with certain hardware configurations. Glad Bethesda quickly fixed it, though.
This is not the FO4 forum, but why is that so surprising?
I myself didn't experience the issue but the fix is a simple code change.
I have the same problem!!!