ok will try thanks. my bootloader is in my sig so you should be able to see it now, just done it.

also i had a look about in "C:\Documents and Settings\Owner\Application Data\TomTom\HOME\Profiles\ybn4xs4u.default"
and i have a file called
TomTomHOME_Exception.txt this is what it says if it means anything to you

TomTom HOME version 2.8.2264:
ACCESS VIOLATION:
Offender:10111764
Offended:000002B0(Read)
Exception code: 0
Please contact TomTom at [Please Register or Login to download file]

Downunder35m wrote:Replace the DLL with the one attached (unrar first ).
9-058-568435-1_patched.rar

Thanks for helping out, but nothing has changed, so still get error and Home crashes when i try and "op my go"

gaz9012 wrote:TomTomHOME_Exception.txt this is what it says if it means anything to you

Disregard the file. This is mine.

TomTom HOME version 2.7.1894:
ACCESS VIOLATION:
Offender:68F979C8
Offended:0234001C(Read)
Exception code: 0
Please contact TomTom at [Please Register or Login to download file]

This the bootloader 5.5128 :
2818
It is sort of a long shot but since a wrong bootloader can cause USB and access problems I thought it is worth a try.
Unpack to the root of your device and reboot, the bootloader will be installed after that.
It will show up as 0 and not as 5.5128 - this is the only way.
I assume the usual like copmpletly removing Home and re installing it was not succussful either, a pre patched DLL does not work, so if there is nothing else wrong on your PC I can only suspect it might be caused by an incompatible bootloader.
Might not work either but no harm will be done to your device unless you would interupt the installation of the bootloader.

tendriver wrote:Disregard the file. This is mine.

ok, wasn't sure if it ment anything considering it said access violation. am happy to disregard.

Is there any more info i can get you guys that would help to get to the root of Home crashing?

Downunder35m wrote:This the bootloader 5.5128 :
2818
It is sort of a long shot but since a wrong bootloader can cause USB and access problems I thought it is worth a try.
Unpack to the root of your device and reboot, the bootloader will be installed after that.
It will show up as 0 and not as 5.5128 - this is the only way.
I assume the usual like copmpletly removing Home and re installing it was not succussful either, a pre patched DLL does not work, so if there is nothing else wrong on your PC I can only suspect it might be caused by an incompatible bootloader.
Might not work either but no harm will be done to your device unless you would interupt the installation of the bootloader.

OK thanks,
just before i do so, Is it possible to drop backwards with bootloads that easy? i am assuming the one in your link is older just because of the numbers are lower.

I have tried reinstalling Home and tried all the patches that have been advised to me. I am able to look at what's on my device in Home, and Do updates and mapshare. its only the crash that i have a problem with.

The version number does not indicate that the bootloader is older.
Bootloaders are more or less device specific and should be left alone unless really necessary.
The correct bootloader for any TT is the one included in the original Navcore.

Maybe should install a different navcore properly.

ato wrote:Maybe should install a different navcore properly.

that did cross my mind, but the Mods didn't surgest it so thought it would be the problem. i take it your set up runs a ok then?

Sorry, I did not read the preliminaries carefully.
ACCESS VIOLATION should mean a disk error eiter on your Hard Disk or on your SD card.
If your device works properly should be a problem with your computer or your patched TT Home.
I also had some error with the previous TT Home version on my Windows 7 (TT Home could not recognize my device although I saw it in my Windows Explorer) but repaired with the latest version.

ato wrote:I also had some error with the previous TT Home version on my Windows 7 (TT Home could not recognize my device although I saw it in my Windows Explorer) but repaired with the latest version.

This is usually caused by the device not being correctly disconnected from the computer. A device reset is the normal fix.