Emulator

Oh, I forgot to mention that I did the dump myself with CleanRip, which mentions the dump has been verified, but I don't think this causes the problem since I went through the game without problems.
I didn't compute the MD5 hash because CleanRip said it was verified and because I suppose hashing 4GB will take a while...

Have you tried the latest development version (4.0-4247)? In the NTSC-U version, there is no freeze in the final trial.

Well I will try, and I don't have the NTSC-U version so I don't know about that.
But now that I think about it, the problem may be caused by my graphics card, because the first time I ran into the problem, ShadowPlay stopped working at the same moment.
(Of course I tried without recording after)

4.0-4247 doesn't work either...
And the problem isn't caused by my graphics card since I used my integred graphics card this time (Intel(R) HD graphics 4600)

Try checking or unchecking the PAL60 option in the Wii menu, out of curiosity.

No, it doesn't work, sorry.

I should mention what I've tested, because I suppose there is also obscure settings that I haven't tested, so :

• OpenGL and Direct3D backend
• HLE/LLE
• Idle skipping / Dual core
• Native resolution / upscale
• French, English
• Nvidia / Intel graphics card
• Pal60 or not
• real wiimote or emulated

Okay, By looking at other issues I found something :
By enabling real XFB in the gameini, it didn't froze to 0FPS.
But the game still displays the level presentation screen ( level 8 : Another dimension) forever, so that's not really a big improvement.

Ok I found how to make logs so here is the pastebin link :
With File manonitor (good luck) : http://pastebin.com/6UZ1Gmfd

Without it : http://pastebin.com/2dFV53Fw

I always get scared when IPC-HLE could be involved.

Well that would be strange if that's HLE because I played with LLE...
I forgot to say that this is the log from start to the level screen where it freezes.
And what I found strange is that when the level starts to load (well, try to) after the cutscene, it is always that note that pop up :46:28:845 HW\EXI_DeviceIPL.cpp:271 N[OSREPORT]: << RVL_MWM - MOBICLIP_MO release build: Jan 5 2011 16:15:18 (0x4302_188) >>
I feel like this has nothing to do with the crash, but I don't know...

IPC always runs with HLE. It's separate from DSP HLE/LLE.

Could you try the following build and see if it changes anything? It wasn't made to fix this issue, but it might have an effect. http://dl.dolphin-emu.org/prs/pr-1617-dolphin-latest-x64.7z

There is no change with the build.
Oh, and the last line isn't showed when it starts loading, but when the cutscene starts actually

And I made a log with only the IPC_HLE logs that show, here it is : http://pastebin.com/2NHuwNKS

To save you some time : everything is a warning.

So, after seeing that the last line of the file manager is always the same, I've been wondering if it wasn't a bad dump all the time...
Here is the md5 : 8ec72814c16861915224c5c2d0130218
I think it's finally a bad dump, but I haven't been able to find two md5 that matches on Internet, it's never the same, so I have to ask you...
Anyway, I will retry dumping

Dumped again, and no it's not because of the dump
One note : Dolphin's md5 (above) is not the same that the md5 CleanRip gives, and the md5 of CleanRip is 3e7e59cf9507ff5f7fb1fe536a730459
This md5 match with one of those in the sites so I guess it is a good dump.

Hopefully someone else will show up with this game and confirm or deny it happens so we can figure out more about what's going on. Please keep tabs with the emulator and try it once in a while in case something accidentally fixes it.

Any chance this could be PAL-related in the same manner as Issue #7474 ( https://code.google.com/p/dolphin-emu/issues/detail?id=7474 )?
Just a wild guess, as there are not that many freezing issues that are PAL/NTSC -dependent.

This could since Skidau said there was no freeze in the NTSC-U version
Also this seems like issue 7937 because it has the same behavior (FPS still going when using RealXFB) : https://code.google.com/p/dolphin-emu/issues/detail?id=7937

This could be IPC HLE stuff too; if you're really desperate, dump a Wii NAND, and boot the game from the Wii System Menu in dolphin.

Maybe I'm just dumb, but I've my NAND dumped (system menu 4.3, Bootmii/Homebrew channel installed if that matters), I configured the path to it in dolphin, yet it doesn't want to boot System menu. I just can't select the option.

Ok so after reading progress report and seeing a build that heavily optimised the loading screens (4.0-5612 - Asynchronize some GPU Events) (since it hangs at what seems to be a loading screen), I tried a build after (4.0-5725) that one, to see if that would work due to that and patience, or if a build fixed it, maybe...
But it still hangs.
For the system menu I still not managed to boot it.
I have the nand path configured, but not the apploader, nor the DVD path. Does that change something ? I don't know what it is...

No, you don't need to set the apploader or DVD root. Those are only used when opening a DOL using a folder as a disc image.

Then I don't know why Dolphin won't let me launch the System Menu...
Maybe I'm missing something, but reading the guide, it seems that i did it correctly...
I tried using for the folder my whole SD card backup (that also has the NAND in it, but also bootmii launcher), or created a folder with just nand.bin and keys.bin, but neither works...

Does this happen on latest master? Does it still happen with fast disc speed?

While it fixes TWW credits hang, it seems different here, since it still doesn't work, fast disc speed or not.
Now that you bump it, I will finally try to boot the system menu with NUSdownloader (I actually forgot...) and update if it works that way.

Ok, I finally managed to boot system menu.
... I was just a dummy, I didn't think decrypting the NAND would be needed and I just copied the encrypted .bin.
And so... it doesn't work either :/
Still, I have my completed save files on Dolphin now, so still thanks for making me try that. (+SM64 VC)
Would you like the log info ?
Also since it was asked a while ago I used my current revision (6144) and not the latest, but I don't think it matters.

Tested 4.0-7015 today, had some free time, and I thought that it maybe would work with the latest PAL fixes. Spoiler : It didn't. VPS are still going this time though.
Anyways, I made a savestate when it hanged, since VPS where still going, hoping that the game actually ran and loading it would allow me to get pass the loading screen. Again, didn't work.
I logged the errors that popped while loading the savestate (Warnings not included, because selecting them just crashed Dolphin. Too many Warnings ?), however it doesn't seem there is anything special, since errors of this type also popped while launching the game.
But just in case : http://pastebin.com/pUMm9ugQ
Also, the Savestate : (Kirby's Adventure Wii PAL, 4.0-7015) : http://www.filedropper.com/sukp01

Can you try this with PR3601 -> https://dl.dolphin-emu.org/prs/pr-3601-dolphin-latest-x64.7z

Nope, still not working, unfortunately.

I tested this with the (almost) latest Dolphin master 4.0-9100 (portable installation with default setup) and SUKP01 PAL version of Kirby's Adventure Wii. Since I'm not near the finish, I used a 100% completed .bin found at http://www.gamefaqs.com/wii/935607-kirbys-return-to-dream-land/saves (the only European version, of course). This was easily imported using Dolphin's save game importing option.
I found the last level as adviced in the issue description (go to "Dangerous Dinner" level, last stage at the top of the tower, and of the two options I selected the final challenge). There was a cutscene, which I skipped with +, and the stage started just as I would have expected (it's a left to right scrolling R-type-like stage).
So I can't verify the issue exists, at least not anymore.

I'm using Windows 8.1, Intel i5 4670S, Intel HD 4600 with the latest drivers as of March 2016.

Didn't work. I used the checksum again and the only result in Google was that thread, so it sounds like I redumped it, and it had the same error. And I didn't thought of checking the checksum again before. Genius.

Anyways, it's likely the reason, because you failed to reproduce it, and I tested it on different computers, with different hardware and so drivers. (I also tested with default settings so it's not that)

So, I will just try dumping again and keep you updated, thanks for trying to verify the issue though !

Annnnnnnd it was a bad dump. Stupid me for not checking the md5 the second time. Dunno how I got the same bad dump twice but anyways, it works now.