MattBoySlim
08-25-2012, 02:35 PM
This being my first time trying Dolphin, I started with the x64 version of 3.0-757. I wanted to pick up Skyward Sword where I had left off on my actual Wii, so I adjusted the graphics settings per the compatibility suggestions, imported the save from my SD card and gave it a shot. No matter what I tried, all I could get is the black screen with "Clearing code cache." on it, among a few other notes about my CPU and Backend choice (Direct3D11). See this screenshot.
I was able to hit esc and return to the main Dolphin screen as long as I didn't let it sit there for very long. I tried Direct3D9 and OpenGL, both of which produced the same result. I also tried some random earlier builds, as well as the stable 3.0 build. I began to notice that in the Graphics options, the adapter would always default to my integrated Intel graphics. Changing the setting in the Nvidia control panel to force Dolphin to run under the GeForce didn't change it. Then, once, while trying to select the GeForce from the dropdown menu, Dolphin crashed. Every time after that, it would crash just by clicking the graphics button. This would happen with any x64 version I'd download, regardless of whether I deleted the previous versions or not. And now, instead of the black screen with "Clearing code cache.", it also crashes when I try to run the game without adjusting the graphics.
I also tried the x32 version (3.0-758). That does not crash, but it does return to my previous code cache problem. It also lists my GeForce as an option for Direct3D11...but only before trying to run Skyward Sword. Afterward, the Intel adapter is the only one available. I read another thread that seems to say that even though the integrated Intel adapter is what's listed, that's not actually what's going to be USED, so I'm not too worried about that. What I'm more worried about is getting the x64 versions to work (and why did they work at first but not now?) and ultimately getting a game running.
I updated my Nvidia driver, DX11 & VC 2010 SP1. No dice. You want the details from the crash reports? There's sometimes two of them...either 2 APPCRASHes or an APPCRASH and a BEX64. Sometimes the second one doesn't actually get to happen and I have to end the process manually. I think that only happens with 3.0, and the BEX64 only actually shows up 3.0-673. Anyway, here's the text from 3.0-757's crashes:
And 3.0-673's BEX64:
I know that's a lot of info, but please let me know if you have any ideas or suggestions, or if you need any further info. Logs or anything? I gather that since my laptop specs are in my profile, you should be good with that, right? I'm giving up for tonight, so I'll check in tomorrow. Thanks!
I was able to hit esc and return to the main Dolphin screen as long as I didn't let it sit there for very long. I tried Direct3D9 and OpenGL, both of which produced the same result. I also tried some random earlier builds, as well as the stable 3.0 build. I began to notice that in the Graphics options, the adapter would always default to my integrated Intel graphics. Changing the setting in the Nvidia control panel to force Dolphin to run under the GeForce didn't change it. Then, once, while trying to select the GeForce from the dropdown menu, Dolphin crashed. Every time after that, it would crash just by clicking the graphics button. This would happen with any x64 version I'd download, regardless of whether I deleted the previous versions or not. And now, instead of the black screen with "Clearing code cache.", it also crashes when I try to run the game without adjusting the graphics.
I also tried the x32 version (3.0-758). That does not crash, but it does return to my previous code cache problem. It also lists my GeForce as an option for Direct3D11...but only before trying to run Skyward Sword. Afterward, the Intel adapter is the only one available. I read another thread that seems to say that even though the integrated Intel adapter is what's listed, that's not actually what's going to be USED, so I'm not too worried about that. What I'm more worried about is getting the x64 versions to work (and why did they work at first but not now?) and ultimately getting a game running.
I updated my Nvidia driver, DX11 & VC 2010 SP1. No dice. You want the details from the crash reports? There's sometimes two of them...either 2 APPCRASHes or an APPCRASH and a BEX64. Sometimes the second one doesn't actually get to happen and I have to end the process manually. I think that only happens with 3.0, and the BEX64 only actually shows up 3.0-673. Anyway, here's the text from 3.0-757's crashes:
Quote:Problem signature:
Problem Event Name: APPCRASH
Application Name: Dolphin.exe
Application Version: 0.0.0.0
Application Timestamp: 50375f6e
Fault Module Name: StackHash_eb62
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 000007feefc10004
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: eb62
Additional Information 2: eb62e5db4fc15993f6eff504df30b018
Additional Information 3: a58f
Additional Information 4: a58f43cc3a9419db718e970d3e8e1f14
Quote:Problem signature:
Problem Event Name: APPCRASH
Application Name: Dolphin.exe
Application Version: 0.0.0.0
Application Timestamp: 50375f6e
Fault Module Name: Dolphin.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 50375f6e
Exception Code: c0000005
Exception Offset: 000000000011bc14
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 844a
Additional Information 2: 844a04105244a161a8cff855d53b9d8e
Additional Information 3: b4d8
Additional Information 4: b4d8bc6ba442010873a48c9139c9a318
And 3.0-673's BEX64:
Quote: Problem Event Name: BEX64
Application Name: Dolphin.exe
Application Version: 0.0.0.0
Application Timestamp: 4fc0513e
Fault Module Name: StackHash_4eee
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 0000000000000000
Exception Code: c0000005
Exception Data: 0000000000000008
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 4eee
Additional Information 2: 4eeeaa32a1ac46e8baa95d91c2a7c2cc
Additional Information 3: 529e
Additional Information 4: 529e73301e498ccfc7a5f338dd5593bb
I know that's a lot of info, but please let me know if you have any ideas or suggestions, or if you need any further info. Logs or anything? I gather that since my laptop specs are in my profile, you should be good with that, right? I'm giving up for tonight, so I'll check in tomorrow. Thanks!
