![]() |
|
[Win7] Dolphin Crashing in [Pal] Xenoblade - Printable Version +- Dolphin, the GameCube and Wii emulator - Forums (https://forums.dolphin-emu.org) +-- Forum: Dolphin Emulator Discussion and Support (https://forums.dolphin-emu.org/Forum-dolphin-emulator-discussion-and-support) +--- Forum: Support (https://forums.dolphin-emu.org/Forum-support) +--- Thread: [Win7] Dolphin Crashing in [Pal] Xenoblade (/Thread-win7-dolphin-crashing-in-pal-xenoblade) |
[Win7] Dolphin Crashing in [Pal] Xenoblade - DMJohn0X - 03-29-2012 Okay, so I'm trying to run Xenoblade Chronicles [PAL] with Dolphin 3.0 r591 I have tried practically every setting there is. Then I updated my vid-card drivers. I've tried at least 6 other old revisions of dolphin including r7676 and r7714. I've gone through more forum threads than I ever wanted two in the last 48 hours. I have tried SLI on and SLI off with and without dedicated PhysX. I am stuck! Here is my rig: [u]Windows 7 Professional 64-bit Core2Duo E8400 3.0ghz OC'd @ 3.83ghz SLI Dual Geforce 8800GT's w/ 1.5gb RAM 6GB Kingston DDR3 1333mhz RAM[/u] Here is my problem: The game loads up great. Everything works no matter what settings I pick. (Some crash sooner) But I always get the game loaded, then Im selecting a new game and in the Opening Video the emulator always crashes! Sometimes it freezes on me (rare) and I alt+control+del it. But most of the time I get an error saying that Dolphin.exe has quit working. I know my machine is fast enough because its running the cutscene flawlessly at 50vps 25fps (Normal Pal FPS). I've seen a couple other people talk about freezes and some about crashes (usually pertaining to overheating) but none really that covers my problem. I ran it again just to get the crash info again: Problem signature: Problem Event Name: APPCRASH Application Name: Dolphin.exe Application Version: 0.0.0.0 Application Timestamp: 4f6fe46d Fault Module Name: Dolphin.exe Fault Module Version: 0.0.0.0 Fault Module Timestamp: 4f6fe46d Exception Code: c000001d Exception Offset: 000000000053bd86 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional Information 1: 8a0d Additional Information 2: 8a0d2927e636ee4549ab1c5967f03187 Additional Information 3: 1ee1 Additional Information 4: 1ee16b053c0d113460b04ee6b7526e54 Any help at all would be amazing as I REALLY want to play this game. <3
RE: [Win7] Dolphin Crashing in [Pal] Xenoblade - LordVador - 03-29-2012 Try to redump your game (if you haven't done it yet) RE: [Win7] Dolphin Crashing in [Pal] Xenoblade - DMJohn0X - 03-30-2012 (03-29-2012, 09:54 PM)LordVador Wrote: Try to redump your game (if you haven't done it yet) Done and done twice. Still no go. Anyone else had similar problems or ideas as to what may fix this issue? I could try a 32bit version of the emulator, I guess. Im running outta options and ideas here. After I try that, I'll try running another game and make sure it is or isnt exclusive to Xenoblade. RE: [Win7] Dolphin Crashing in [Pal] Xenoblade - DefenderX - 03-30-2012 Try the official Dolphin 3.0 release. RE: [Win7] Dolphin Crashing in [Pal] Xenoblade - DMJohn0X - 03-30-2012 I fixed the crashing. Turns out that my processor wasn't OC'd stable at 3.83ghz. Got it stabilized at 3.62ghz. Now Im able to play which is great. Game is beautiful, btw. Running at 2x Internal Res and 4x Anti-Alias. New issue has risen. The game is randomly freezing. Sometimes 4mins in. Sometimes a couple hours. This a known issue? Current 3.0 settings are: Enabled Dual Core Enabled Idle Skipping JIT Recompiler Locked To Threads Audio: Enabled DTK XAudio2 @ 4400mhz Scaled EFB Enabled Ignore Format Changes EFB Copies [Texture] External Frame Buffer Disabled and only Disable Pixel Per Depth RE: [Win7] Dolphin Crashing in [Pal] Xenoblade - LordVador - 03-30-2012 Quote:This is a known issue? It is but should be solved in latest builds RE: [Win7] Dolphin Crashing in [Pal] Xenoblade - DMJohn0X - 03-30-2012 Well I am actually using a 3.0 build I downloaded from the main site Monday. So I'm not sure. Also, there is a minor bug with the music getting stuttery randomly but it normally fixes itself. Otherwise, the game is still totally playable and for that Im greatful. |