This article discusses information regarding the BAD_POOL_CALLER or STOP: 0x000000C2 error during the "Configure Operating System" stage of the conversion.
When performing conversions to physical target the target server may not show the above error and it will constantly reboot.
This error can occur in the following scenarios:
A device driver installed in the machine is now accessing hardware that does not exist
In cases where a device driver is trying to allocate memory for a piece of hardware that does not exist inside the target server. This can be items such as display drivers (such as an ATI video card) or a add on controller board (such as a lights out remote access board)
- Abort the current conversion job
- Uninstall/Remove the driver for this device from your source server.
- Retry the conversion
For more information please read Microsoft KB article at http://support.microsoft.com/kb/q265879/
Marginal or defective memory module
In X2P cases, this same error can be caused by a marginal or defective memory module. Microsoft has a memory test utility at http://oca.microsoft.com/en/windiag.asp that can be used to test the memory inside the server.