Emulator Issues #7107
closed
Dolphin crashes booting up any GC game after 4.0-1262
0%
Description
[READ THIS: https://forums.dolphin-emu.org/showthread.php?pid=276132 <<<
Your answers are there!]
[Leave the questions as they are and answer them in the next line]
[Remove lines written inside brackets [], but nothing else]
Game Name?
Any GC game, any region (tested PAL and NTSC). Both backends tested.
Game ID?
Any GC game.
What's the problem? Describe what went wrong in few words.
Emulator crashes after launch any GC game.
What did you expect to happen instead?
Load the game correctly.
What steps will reproduce the problem?
[Don't assume we have ever played the game and know any level names. Be as
specific as possible.]
- Clean install (deleting Dolphin Emulator folder from My documents). Extract latest svn version. Launch emulator.
- Launch any GC game.
- Emulator stops working. Change between backends doesn't solves the issue.
Which versions of Dolphin did you test on?
Latest Dolphin 4.0-1262 and 4.0-1264, tested Windows x86 & x64.
Does using an older version of Dolphin solve your issue? If yes, which
versions of Dolphin used to work?
4.0-1255, tested both x86 & x64 working fine.
What are your PC specifications? (including, but not limited to: Operating
System, CPU and GPU)
i7 3770K @4.3Ghz
Nvidia GTX690
Windows 8.1 64bits
Are you using the 32 or the 64 bit version of Dolphin?
Both
Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
Unhandled Exception
Code: 0xC0000005
Call stack info:
Dolphin!0x0086078A : ?
Unhandled Exception
Code: 0xC0000005
Call stack info:
Dolphin!0x0086078A : ?
Unhandled Exception
Code: 0xC0000005
Call stack info:
Dolphin!0x0086078A : ?
Unhandled Exception
Code: 0xC0000005
Call stack info:
Dolphin!0x0086078A : ?
Updated by
Updated by williamderieux almost 11 years ago
GC games fail because a nullptr is returned in function CFileSystemGCWii::GetFileName(u64 _Address) from FileSystemGCWii.cpp
responsible commit: a3e18cd498e6a02dfd615da25e975f110e8cf365 - lioncash/rarc-cleanup
** commit needs to be reviewed for mistakes / or reverted .. to fix the problem (I think it was probably an oversight by lioncash)
Updated by Sonicadvance1 almost 11 years ago
- Status changed from New to Fixed
Fixed with 94ceb4d305cda79d6379dd62f8c2b18495e23c20
Updated by williamderieux over 10 years ago
Windows OS: Windows 7 x64
Memory: 16GB
Graphis: EVGA Nvidia GTX 550 Ti
** NOTE: this only seems broken (now) in olphin-4.0-1268 x86
revision: 94ceb4d305cda79d6379dd62f8c2b18495e23c20 did indeed fill the nullptr issue I reported earlier
https://dl.dropboxusercontent.com/u/104054522/dolphin-4.0-1268-x86/007agentunderfire_assertion.png
Updated by williamderieux over 10 years ago
GC Game tested: 007: Agent under fire
Updated by williamderieux over 10 years ago
JMC4789:
- are you using dolphin-4.0-1268 x86 (on Windows 7 x64) with/without a Nvidia GPU?
- are you testing 007: Agent under fire for the Gamecube?
- do yoy have log settings set to warning and are logging from all sources?
Updated by JMC4789 over 10 years ago
1: Yes, except x64. x86 may have separate problems, I apologize for not reading closely enough. I'll investigate x86.
2: Yes
3: I'm using all default settings. The Logs are on, but the game isn't crashing or hanging and I'm getting no popups.
So, it's sounding like x86 is still broken maybe?
Updated by williamderieux over 10 years ago
Yes, i believe the X86 build is broken.
When using: Windows 7 X64 (i don't know if Windows 7 X86 works)
Updated by JMC4789 over 10 years ago
Have you tried the x64 build? Do you know if that works or not on your system?
Updated by williamderieux over 10 years ago
Yes, I reported that in the original post, after the nullptr fix was released.
Moreover, what needs to be confirmed is this:
- Running dolphin-4.0-1268 x86 on a 64bit cpu (with or without an 64bit OS)
- Running dolphin-4.0-1268 x86 on a 32bit cpu
** a 64-bit cpu should be able to run either the 64-bit or 32-bit build(s)
And in this case, the 32-bit build seems to fail (when run on a 64-bit cpu)
** again, confirmation is needed to see if this is only for 64-bit cpus.
I will probably stick with the 64-bit builds for now ... however, there are times when I need to run the 32-bit build (for debugging/memory hacking [searching values in memory, etc])
Updated by JMC4789 over 10 years ago
I agree with you. I don't know if it's related to his issue; it may need to be a separate issue report.
This issue reported here was x86 and x64.