So your system is running well, and then someone decides to change the memory divisions using the System Control Panel Applet and BAM something in your system data aborts. This can be difficult to solve, if you don’t have any idea what the cause is, and a challenge even if you do know. If you follow the data abort back to the code that failed (Windows CE: Finding the cause of a Data Abort) you will find yourself confused because the code there most likely did not cause the data abort, but instead the data abort is a symptom of a bigger problem in your system.
The root cause of the problem is likely that you have an overlap of the systems RAM with some RAM that you have allocated for something else, like the display controller’s frames. To figure this out, you might need to do some digging to figure out your total system memory map of RAM.
Copyright © 2008 – Bruce Eitman
All Rights Reserved