iPaq spontaneously reboots

[ctmagnus]

Has anyone ever had an issue whereby their Pocket PC will spontaneoulsy reboot? Mine's been doing that for a while now. :confused totally:

The contents of my \Temp\Pimagent.txt, if anyones interested. The following is actualy two files, the --- being the break between the two.

INFO: PIMAgent Started 31/10/2004 11:12:55
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 11:26:27
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 11:27:10
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 11:29:14
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 11:32:30
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 11:33:32
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 11:36:18
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 11:37:35
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 11:38:02
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 11:39:52
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 11:43:08
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 11:46:24
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 11:46:50
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 11:48:37
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 11:50:18
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 11:51:16
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 11:52:19
INFO: Not starting after reset as OnStartup is not set in the registry
---
INFO: PIMAgent Started 31/10/2004 18:18:30
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 18:18:44
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 18:19:32
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 18:20:30
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 18:21:35
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 18:21:57
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 18:23:16
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 18:23:42
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 18:23:57
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 18:24:26
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 18:25:40
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 18:26:05
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 18:26:27
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 18:26:55
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 18:27:18
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 18:27:46
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 18:28:05
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 18:28:39
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 18:34:24
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 18:37:02
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 18:37:34
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 18:39:39
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 18:40:40
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 18:41:48
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 19:04:51
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 19:07:39
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 19:13:23
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 19:40:34
INFO: Not starting after reset as OnStartup is not set in the registry
INFO: PIMAgent Started 31/10/2004 19:41:02
INFO: Not starting after reset as OnStartup is not set in the registry

[Darius Wey]

Which iPAQ do you own?

[ctmagnus]

The king of iPaqs. Don't you ever read sigs? :p

It's a 5550 ;)

[Darius Wey]

Yeah, the h5550 has some odd errors with PIMAgent sometimes.

PIMAgent.exe is a file used by Sprite Software Backup. If you open up the registry, there may be a key called: HKEY_LOCAL_MACHINE\SOFTWARE\Sprite Software\PIMAgent\OnStartup

I think this is set to 0x1 (1).

The whole purpose of this PIMAgent.exe file is to initiate a backup of your PIM databases when you startup your Pocket PC. If you set this key to 0, it disables this process, and hopefully, it will end all your troubles. :)

[ctmagnus]

8O I didn't know that. I'll give it a whirl. Thanks.

Edit: it's already set to 0. I'll try setting it to one and see if that helps.

[Darius Wey]

The king of iPaqs. Don't you ever read sigs? :p

Ha! Well it was a little obscure... :lol:

Edit: it's already set to 0. I'll try setting it to one and see if that helps.

See how it goes. In some cases, it has been known to cause odd things on the h5550 when it's at 1, but occasionally if it's at 0 too. It really depends on what kind of day your iPAQ is having. :P

Either way, let us know if it works. Thanks!

[rsjeffrey]

The new ipaq 4700 also spontaneously reboots.

[Darius Wey]

The new ipaq 4700 also spontaneously reboots.

Is it for the same reason? Do you have an output of an error text file when this happens?

[ctmagnus]

Edit: it's already set to 0. I'll try setting it to one and see if that helps.

See how it goes. In some cases, it has been known to cause odd things on the h5550 when it's at 1, but occasionally if it's at 0 too. It really depends on what kind of day your iPAQ is having. :P

Either way, let us know if it works. Thanks!

Bleh. One is not good. :evil: It's back at zero, and the unit went from shortly after midnight to now (~8.5 hrs so far) without rebooting. However, my morning alarm failed to wake the unit up and when I got the notification afer it woke up, there was no sound.

I'll have to see how it progresses and if all else fails, I can always call HP and make use of my Care Pack.

[Darius Wey]

Bleh. One is not good. :evil: It's back at zero, and the unit went from shortly after midnight to now (~8.5 hrs so far) without rebooting. However, my morning alarm failed to wake the unit up and when I got the notification afer it woke up, there was no sound.

I'll have to see how it progresses and if all else fails, I can always call HP and make use of my Care Pack.

Odd indeed. I've heard reports of the h5550 doing odd things with the PIMAgent.exe file, but you're one easily beats them all as far as I can see. Probably best to hard-reset if you can't stand the agony any longer, or as you said, call HP. :D

[ctmagnus]

I'll eventually have to do the latter, as I've already tried a few hard-resets as well as a rom refresh :shocked:

[ctmagnus]

I gave in. I called HP. There'll be a replacement here on Wednesday. It sure feels like I'm swapping a child, though :(

[ctmagnus]

Argh! This is the second unit in two weeks to do this now! I've got yet another refurb from HP now, and this unit is not going in the cradle or attaching to the AC adapter in any way. HP sent out a replacement cradle and AC adapter but they haven't arrived yet. I wasted a BoxWave screen protector on the first unit also. :( I was putting it on the new unit and it bent, creating enormous potential to damage the touch screen layer of the display. Fortunately, I had some old iConcepts screen protectors lying around. I put one on the new unit and those protectors are actualy fairly nice!

[ctmagnus]

This is now the third unit to do this. I recieved this unit on/around November 18 and it started rebooting on December 9. However, it started behaving itself on December 14 and hasn't rebooted itself until today, when an older TV (10 years but an el cheapo brand) was turned on for the first time since December 14. When the first unit started misbehaving, the TV in question had temporarily been moved up stairs to replace a larger one, because we were renovating and certain individuals in this household are chronically addicted to the boob tube.

Strange cause, no?