I've had the very same problem on two Boot Camp installs. I tried nicholaspwojtowicz's first solution and all that did was create a 3rd config that came up with a missing or bad hal.dll file. I have no idea why cleaning out Tiger's caches would fix a boot camp error, but I tried that too. No change at all. I tried rebaser's idea which did allow me to boot up in boot camp, but every time I would run the PDM I'd have to go back and re-fix hal.dll to use Boot Camp again. It's not a memory problem, all memory tests pass.
It's something in Parallels as with my last reformat I started using VmWare for the Boot Camp partition only and I've not had an issue. I find it very interesting that VmWare uses the same h/w configuration as Boot Camp but Parallels cannot. The problem seems to stem from the swap around of the boot files.
