Hm...I confirmed the user did not suspend the device.  Does the symscript file set I provide tell us anything else?  Give any reason why the device lockup up?  Maybe point to a specific exe, ect?

Nothing else jumps out at me.

Hi Guys, Can someone look at this Symscript log to see if there is any indications pointing to a lockup condition?  Customer reported a lockup on 9/9/2009 at around 6-7 AM, I really cant see anything ehre other than around 5:38 it created a memory map and then the next logging is 8:55 when the device was warm booted. Before the warm boot CPU load was 73%, total memory load is around 80% but the memmap 24 does not point to any dll crunch.  Please let me know if anyone finds anything pointing to a lockup.

Just the fact that logging stopped tells us that the processor stopped executing.  This could be due to a lockup or just that the device suspended.

Nothing in the log suggests a lockup occurred. How long have these terminals been in use?  If this lockup is new, what has changed?

Glen, this might be related to SPR 17494 which was opened recently. We have a customer in Lebanon reporting random lockups on 3-4 devices (out of 100) per day. Herbert is now on site in Beirut and is trying to get more details and collect more logs. I would like to ask you for help in verifying if your device when it's locked up is able to perform a warm boot via key combination (func+enter+side trigger). What we see at customer site is that the device is not reacting on warm boot key press, only cold boot is possible. Also could you please share with us what applications are running on the device? Our customer is using .NET CF and SQL Mobile. We can see in the resource script that the CPU use is quite often hitting 100%. I am attaching the latest logs from Herbert for your reference so you can compare them if needed. Thanks, Petr