Booting into Windows 7 Gives Snow Leopard A Kernel Panic

[NeoDuragon]

I followed BlackOSX's 10.6.1 Guide Here, and everything is working perfectly in osx. I've updated to 10.6.1 and have a vanilla kernel with Chameleon on a seperate partition. The problem is when I boot into Windows 7 (RTM), and then restart, the Snow Leopard partition kernel panics at the apple logo. That is, it doesn't even get to the spinning circle to show that its booting. Sometimes it takes a minute or so, but it always ends in a KP.

 

Booting into verbose mode shows:

panic(cpu 1 caller 0x28ffba):  "pvh_e exhaustion"@/SourceCache/xnu/xnu-1456.1.25/osfmk/i386/pmap.c:3272

 

Usually, booting the Snow Leopard partition with -x and -f can fix it, but it only lasts until the next time I boot into windows and then back into Snow Leopard.

 

I'm wondering if it is something that Chameleon v2 RC3 (on a separate partition on the same hard drive as Snow Leopard) is doing. I've replaced the boot file with Netkas 10.1 file as per the tutorial.

 

Any ideas / tips / suggestions on how to fix this would be much appreciated.

[srs5694]

First, does the problem occur only when you do a "warm" reboot, or does it also occur if you shut the computer down completely, so that you need to press the power button to start the system up again? If the former, then it appears that Windows is putting the system hardware into a state that's causing problems -- setting some hardware feature that the boot loader/kernel isn't handling well. Pressing the Reset button between boots might work around this problem, and it might be that changing boot loaders would fix it, too, but I can make no promises about either. If even a cold shutdown doesn't solve the problem, then it sounds as if Windows is doing something to the disk that's causing problems. Perhaps it's tweaking the partition table, or maybe a partition type code is set incorrectly or it could even be that the partition table is corrupt, resulting in Windows writing data where it shouldn't.

 

Thus, if a cold shutdown doesn't solve the problem, I suggest you review and, if necessary, post, details of your partition configuration. In OS X, you can open a Terminal window and type "diskutil list /dev/disk0" to see the basic partition layout information, but it's a bit imprecise. The fdisk and gpt utilities give more detailed information for MBR and GPT disks, respectively.

 

Another question: Do you have (or have you ever had) installed Windows software for accessing HFS+ volumes? If so, it's conceivable that this software is causing HFS+ corruption. Removing it may fix the problem.