Thanks, Gene

I'm not sure anything from the logs with regards to the warm boot (I see it happened, but no indication of why).  About the time changes, it seems that something on the device is changing the clock via an API call.  Its likely that this customer has Fusion setup to synchronize the clock with the AP.  It may be useful to have the customer turn this feature off (and also check if there are other clock sync tools enabled) to try and recreate the problem without the clock changing.  This would just help with the logs - I wouldn't think that the warm boot is due to the clock.

Can someone please review the attached log and process list. Customer reports unit froze and initiated reboot on 04/20/2010 at around 10:04. I checked that time and starting at line 137 i noticed CPU at 100% and battery draw high. Upon checking the process list I could not find stats for the foreground process AgentryClient.exe. Any assistance woulf be appreciated in trying to determine what process was soaking up these resources.

didn't get the full snaps but it looks like they are hitting the 32 process limit. The snap you attached showed this.

Have you looked at the logs?  Is there something specific we should be looking at to explain?

I have reviewed the logs. I am asking for someone else to look at the specific line where customer claims unit rebooted itself. It looks strange to me with the time lapses and no suspend reasons. I have asked for the complete eMscript folder,

All the proclists, memmaps, etc. are available here: ftp://174.143.35.122/eMscript/Push/SN9107520801954_MOTOROLA_MC75/Applica...