Next Generation Emulation banner

"No possible memory base pointer found!"

5841 Views 24 Replies 14 Participants Last post by  TheWWEFan28
I searched around has haven't found any relevant threads on this, so I guess I can come to you guys for help.

The problem is pretty simple, whenever I start up Dolphin and double click on one of the games in my list, it gives me the error notice from above, attempts to start the game, then crashes.

The odd thing is, when I go into a menu (say, the GFX menu) before I double click on a game, the message doesn't pop up, and the game plays fine.

I'm playing on Windows Vista 32 bit, and running Dolphin SVN Build 4525.
1 - 20 of 25 Posts
What game are you trying to run?
It's a general problem with the emulator, as it occurs with every game I double click on.

But to answer your question;

Animal Crossing (U)
Legend of Zelda: Wind Waker, The (U)
Pikmin (U)
Pikmin 2 (U)
Try redownloading the emulator.
Anyways, what specs do your computer have?
My computer is relatively weak, but I doubt that would be a problem.

Intel Core 2 Duo 2.5Ghz, Nvidia 9400GT, 2.5GB RAM
i have use the emu much on the weekend but i tried 2 load a title and got the same thing,,but i think when i selected the wiimote options and un-select it again it worked,,until i close the game or maybe the i close the emu out...i was just reading a few comments i saw this,,and thought on a response for it...
i have use the emu much on the weekend but i tried 2 load a title and got the same thing,,but i think when i selected the wiimote options and un-select it again it worked,,until i close the game or maybe the i close the emu out...i was just reading a few comments i saw this,,and thought on a response for it...
Well, yes, but like I said, it persists every time you reopen Dolphin.
Issue 1624 - dolphin-emu - No possible memory base pointer found error - Project Hosting on Google Code

If you searched through the forum you will notice I also made a post on this weeks back. Easy workaround is to delete your dolphin.ini file (user/config) and redo pathway to your iso's each time. Its a known problem and happened after commit 4505 and affects many windows xp 32 bit users and some linux users.

http://forums.ngemu.com/dolphin-discussion/129128-no-possible-memory-base-pointer-found.html
Issue 1624 - dolphin-emu - No possible memory base pointer found error - Project Hosting on Google Code

If you searched through the forum you will notice I also made a post on this weeks back. Easy workaround is to delete your dolphin.ini file (user/config) and redo pathway to your iso's each time. Its a known problem and happened after commit 4505 and affects many windows xp 32 bit users and some linux users.

http://forums.ngemu.com/dolphin-discussion/129128-no-possible-memory-base-pointer-found.html
I did search on the forums, and I did come upon that. Deleting my ini and redoing the pathway to my ISOs did nothing, the problem persisted. It wasn't much of a fix at all.
Dolphin does some crazy memory management tricks to do fast emulated memory handling, unfortunately this is not compatible with various virus scanners and stuff that likes to inject itself into every process on the system. So try disabling antivirus if you are still getting this error.
As was stated on the issue page. Antivirus doesn't fix anything. It was the change in memory handling itself after commit 4505 that broke and caused this for many people ector. To bad it seemd developers didn't see people stating in the issue section and forum that the problem has hindered them from using dolphin all together. Offcourse it seems to be different for people but from what i've seen peolpe on windows xp 32 bit OS and a few others on linux suffer the worst since that commit. Read through the issue page ector and you will see someone asked the exact same thing on antiviruses.
Is this a new error? Or a re-wording of the old "unable to find 1GB od contigious Ram" error that used to affect some people before 4505
Don't know if it was a new error but it did start after they attempted to fix the 1 gb continous memory.
hm? It's weird now it's working in later versions I don't no if they changed anything or what but I havent had the problem yet
Yep. I'm getting this too.

It's annoying, but not a dealbreaker...would love to get a fix though.
It's a general problem with the emulator, as it occurs with every game I double click on.

But to answer your question;

Animal Crossing (U)
Legend of Zelda: Wind Waker, The (U)
Pikmin (U)
Pikmin 2 (U)
Weird, I run perfectly fine on my Vista 32-bit Home Premium.

Yep. I'm getting this too.

It's annoying, but not a dealbreaker...would love to get a fix though.
I suppose they haven't encountered your problem in their builds yet. Even I didn't encounter it.

The fastest solution is to get the latest SVN rev and see if the problem still persist. If yes, you need to find a way to save some evidence. Post them on Imageshack, then link them to the issue mentioned above. It should help them in some way.
Weird, I run perfectly fine on my Vista 32-bit Home Premium.



I suppose they haven't encountered your problem in their builds yet. Even I didn't encounter it.

The fastest solution is to get the latest SVN rev and see if the problem still persist. If yes, you need to find a way to save some evidence. Post them on Imageshack, then link them to the issue mentioned above. It should help them in some way.
Of course you didn't have the problem, it's been established that it only occurs on WinXP 32bit systems.
Yeah. There's not much to say about this. We know a few things:

1. It only happens with Win XP 32-bit.
2. It only happens with Gamecube games. Wii games are fine.
3. It does not occur if any other menu (as in, window that Dolphin opens, such as a config menu or memory card manager) has been opened in the program's lifetime.
4. It happens reliably.

I dunno what else you want.
1 - 20 of 25 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top