I see a number of errors in the log but I'm not sure which ones are significant. I think I'll try to capture the log in the working VM and compare that to the 10 & 20 logs. I can also boot a live cd on this embedded system so I should probably do that again and capture a new log of that as well.

I'm still new at ReactOS so any help and suggestions are very much appreciated.

These lines in the 10 log happen right before the failure:
(ntoskrnl/mm/mmfault.c:147) Address: 8aa67c71
(ntoskrnl/mm/mmfault.c:147) Address: 8aa67c71

Please create a file called KDBinit in C:\ReactOS\system32\drivers\etc, put set condition * first always into it.

There will be a few spurious errors like "Memory at 0x000007C0 could not be written: Page not present." when booting, just type cont. But when it will be related to the address 8aa67c71, then type bt and cont. Then, at second error, bt again.

With r54221 I can now use the full 2 GB CF without the previous crash on my system (that has just 256 MB RAM) when it tries to create a page file larger than about 256 MB. So that bug looks like it is gone!