Dolphin, the GameCube and Wii emulator - Forums

hey ,, this is my first topic here and i wished if it were helping topic not needing help ^^
i'm using dolphin from a long time and i've stopped using it after i bought Nintendo wii
but when i checked the website to see hows dolphin progress and found that there's a version 3 released i've downloaded it but it not work tried different things but nothing work ,installed VCredistx64 nothing work , and last direct x nothing work .... downloaded all dlls put it in root directory also didn't work ... and keep this silly message appears: The application was unable to start correctly (0xc000007b) click ok to close application ..
so any help want to try this version plz .. thanks alot and sorry for bla bla bla
btw im using windows 7 x64 and all older builds are working fine but from build 3 to the last one nothing works ...

(08-14-2011, 05:45 PM)Anti-Ultimate Wrote: [ -> ]That's the Haters gonna hate, or Noobers gonna noob error, when not using google

http://forums.dolphin-emu.org/showthread...0xc000007b
http://forums.dolphin-emu.org/showthread...0xc000007b
http://forums.dolphin-emu.org/search.php...order=desc

Allow me to refer to this post amongst the other "answers" to take into account: Dolphin 64-Bit Doesn't Work
(By the way, the 0xC000007B error code stands to STATUS_INVALID_IMAGE_FORMAT according to this list)


The very-frequently-encountered case is that, on native 64-bit systems, Dolphin x86 may run gracefully, but Dolphin x64 may fail to run because people have dropped a few incompatible (32-bit/x86 instead of 64-bit/x64), separately-downloaded DLLs into System32 or Dolphin's folder.
The thing is: most (if not all) of those random DLL websites only host x86 (32-bit) DLLs for download, not x64 (64-bit). And, on 64-bit systems with WOW64 support, x86 DLLs do NOT go into the System32 folder, but into the SysWOW64 folder instead.
If you did the mistake of dropping a x86 build of VCOMP100.dll into a folder where x64 is expected (such as Dolphin's folder or, worse, System32), and you're getting the 0xC000007B error because of this, try reverting/renaming/deleting/moving the DLL away. (If the error code still appears, try using Dependency Walker to pinpoint the cause.) Once the 0xC000007B error is gone, you can then worry about properly installing any eventually missing DLLs (preferably using official/proper installation packages).