Hotsync BSD

[clit]

This seemed like the best place to pose this question, so here it is:
I've been intermittently getting this crash occurring on a hotsync of my PEG-S360, on my new laptop running XP; it results in a full blown spontaneous reboot.
This screen comes up for a second right before it reboots:
http://img465.imageshack.us/img465/2363/palmbsd6bh.jpg


This doesn't happen on any other PC that I hotsync the unit on, and it goes through normally if reboot fresh with nothing else running. Nothing seems to be lost permanently when this happens, but it can't be a good thing, especially when any apps I happen to have running undergo this uncontrolled shutdown.
If anyone's seen this before, any insight on what might be causing it and how I can avoid it, other than rebooting before each hotsync?

[MortDeRire]

Your lucky I was around at the right time, I think the memory of your laptop is dodgey (its a common enough occurance). Download and use the memtest86 (http://www.memtest86.com/) tool on your laptop to confirm my suspicions.

You don't need to be very techically competent to do this, download the iso image, create a cd from the image see this description of the procedure (http://www.bay-wolf.com/burnimage.htm), then boot from the new cd, you may need to change bios settings to do this, and run the test ....

You may say .... uh ... couldn't be bothered, but if you do have memory issues you will be encountering other weird behaviour as well, and this would explain it.

[clit]

Worth a shot, I'll try it.
Haven't noticed any other problems like this except during the hotsync, but the laptop's new, so I just may not have encountered them yet.

[clit]

Ran through one pass, and it seemed to go through without errors- I'll try letting it cycle longer in case it's something intermittent.

[MortDeRire]

Hum thats odd, I would let it work away for a while. I had a very similar problem to this recently turned out that one of the RAM slots was dodgy. I presume you have _all_ your service packs and drivers up to date on this machine, I know it rarely helps but its always worth a try.

[clit]

It was able to run through 7 cycles without any errors, so maybe the memory is okay.

It's not really that bad, since it works most of the time, and if it doesn't, rebooting for a fresh start always works. Might be some conflicting app running in the background, I'll have to see if I can determine a pattern to it somehow.