Dead Rising 3

Dead Rising 3

View Stats:
DarkThroat 6 Nov, 2015 @ 11:40am
[FIX] How to Solve Crash every 15 minutes!
After doing research of this crash, I've come across a guaranteed fix for it.

Before I get to the fix, I'd like to go into detail of the crash itself and why it occurs (as well as other games it occurs in)

If one is view the crash in Windows Event Viewer, you will notice that the crash calls for a file named " XAudio2_7.dll." From my understanding, this is a file that is a part of a legacy DirectX audio driver, DirectX9 to be precise. Despite the game requiring DX11 to run, it still relies on legacy drivers to process it's audio.

Now if one were to remove this file altogether, they would be able to play the game without it crashing every 15 minutes, however this results in no audio and cutscenes will result in a crash, but this is mitigated by skipping the scenes.

I observed that a very similar crash occured during the Street Fighter V beta, so similar... It's the exact same crash. At 15 minutes on the dot, the title would crash calling for the same file. Both games are developed by Capcom, so it's not entirely farfetched for the games to share some issues.

Now, the moment you've been waiting for: THE FIX.

If you are victim of this crash, this fix is guaranteed to work for you. A Reddit user by the name of "rickyshea" found that the file XAudio2_7.dll has incompatibilities with something called "TabTip.exe". TabTip is a process that allows the use of an onscreen keyboard with Windows Tablet PCs and Wacom Tablets. He found that by killing the process, he was able to play the Street Fighter V beta without any crashes.

So this got me to thinking. The crashes in both games are the same, so why not try this fix for Dead Rising 3?

Here's how to to it:

1) Press Ctrl+Shift+Esc to open up Windows Task Manager
2) Scroll down and search for a process called "Touch Keyboard and Handwriting Panel" or "TabTip.exe"
3) Right click on the process and click "End Task"
4) Launch Dead Rising 3 and enjoy the game without any crashes!

Thanks for rickyshea from Reddit for finding a fix for SFV, and in turn, DR3!
< >
Showing 1-15 of 31 comments
PockX 6 Nov, 2015 @ 11:49am 
specs?
DarkThroat 6 Nov, 2015 @ 12:32pm 
Originally posted by PockX:
specs?

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
Buck 6 Nov, 2015 @ 1:42pm 
Originally posted by LT Brooklyn the Orifice Offender:
From my understanding, this is a file that is a part of a legacy DirectX audio driver, DirectX9 to be precise. Despite the game requiring DX11 to run, it still relies on legacy drivers to process it's audio.

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).
Last edited by Buck; 6 Nov, 2015 @ 1:55pm
Christian 6 Nov, 2015 @ 6:44pm 
THANK YOU
DeafLeftward 6 Nov, 2015 @ 7:37pm 
You sir are an amazing human being. Thank you
Bellum 6 Nov, 2015 @ 11:16pm 
Thank you so much. :mmmdonut:
Stray 6 Nov, 2015 @ 11:18pm 
Thanks to this post, I can finally co-op with my sister who lives across the country. I love you, you amazing man. Let's get coffee sometime.:FFXIIIvanille:
VALEU CARA! :commando:
Bigodon99 9 Nov, 2015 @ 2:04pm 
somehow, this could solve my annoying crash problems
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
Yeyuden 10 Nov, 2015 @ 8:22am 
thanks a lot!!
It's work!!!!!
Vampireium 19 Nov, 2015 @ 1:39am 
Nice to know. Thanks.

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.
DarkThroat 19 Nov, 2015 @ 8:50am 
Originally posted by Vampireium:
Nice to know. Thanks.

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.
Last edited by DarkThroat; 19 Nov, 2015 @ 8:51am
Buck 19 Nov, 2015 @ 9:36am 
Originally posted by LT Brooklyn the Orifice Offender:
Originally posted by Vampireium:
Nice to know. Thanks.

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.
Fordon Greeman 23 Jul, 2016 @ 1:05pm 
I need help please. I cant either find Touch Keyboard and Handwriting Panel on my Task Manager nor TabTip.exe. I have no idea what i should do. Im using Windows 10. I hope this thread is still alive.
Topping 24 Jul, 2016 @ 6:57am 
Originally posted by Sergio Ramos García:
I need help please. I cant either find Touch Keyboard and Handwriting Panel on my Task Manager nor TabTip.exe. I have no idea what i should do. Im using Windows 10. I hope this thread is still alive.

I have the same problem!!!
< >
Showing 1-15 of 31 comments
Per page: 1530 50

Date Posted: 6 Nov, 2015 @ 11:40am
Posts: 31