I also noticed that issue quite often in the past. It unfortunately happens if data on the USB bus is acting up - like 1 byte was missed during transfer - that would mean that a whole block (WiiRd and Gecko dotNET transfer blockwise) is moved in memory by 1 byte back and forth.. kenobi and me back then tried to prevent that from happening using a Checksum, however, the checksum thing never really worked so it was dropped.. in Gecko dotNET you should be able to try to undo your search and retry. The effect does not happen as often it seems if you safely pause the game BEFORE doing a ramdump - the safest way to pause would be to put an Execute breakpoint on 800018A8 (several games run special threads which continue if you pause - like if you check SEGA games: click "pause" and you'll notice that music continues playing, a breakpoint however, will definitely stop EVERYTHING).
This should make searches more reliable: what worked in my case: I went with multiple USB cables - from very short (half a metre cable - while still being expensive because of high quality) to ultra long ones (10 metres - I know this exceeds the specification! - with cheap plugs and everything) and it also seems the cable quality is a parameter here. If you have multiple cables, please try replacing yours with another, maybe it helps the problem.
Sorry, yes, I am aware of the problem, but no, I hardly know what to do about it
.