Unfortunately nothing but using the officially purchased map on CF card will give you POI search (as i'm sure you know)..... that is unless you can sweet-talk kunix into extending his interest to also solving this problem when he's fixed the voices for US fw loaded onto EU navi GWs.
But please take a number and join the queue, 'coz i want him to help me with a related SP fw mod first.
BTW, the V4.60 fw was released by Garmin with 2011.10 maps originally, now they are offering 2013.10, and afaik V4.60 fixed the POI search lock-up or 'crash & reboot' problem previously experienced with V4.50. I see that you mentioned that you had reboot on address search which seems a different problem. Interesting that it's now not happening for you using the 2014.10 map with V4.50 fw. Of course there's no POI search bug in V4.50 with 'unofficial' maps when you can't even do one, but did you have your address search re-boot problem happening if you had the original map on the CF?
The following copied from a post made last year in GoldwingDocs forum, my added emphasis in red:Code:Please Login or Register to see the links
Quote credited to themainviking.Another final end of the CF card saga post ..... As Garmin's Version 4.50 firmware update, released in October 2011, caused a POI search to lock up the system, they stopped production and sales. Then in mid February 2012, they came out with Version 4.60 which corrected this. So, the new version 4.60 updates all non US and also CF carded US bikes to use NT maps, and includes mapping information current as of March 2011. It is also available in a different card format to update the 2009 and 2010 SD carded US bikes, and I sorta kinda think that the 2012 could be updated with the same SD cards as this.
For the 2012 though, I think that you would only gain a few months of map info and that would be about it. If you are not above reloading information on your cards, you can get your map info current. I am using map info that was released in February 2012. This information is still several years old, considering that Navteq collects the information and then collates it, and sells it to the GPS manufacturers, all of which takes time, so a two year lag in the time the info is collected to the time it is available is probably the norm.
Anyway, the Version 4.60 update is working as it should, in my bike, and so are the 2012 maps.
It would also be interesting to see if you have that reboot problem using the 2013.40 map with V4.60 fw, or with V4.50 and the 2013.40 map download from another source. I suspect it may have been a problem with the map image rather than another fw glitch in V4.50.