Destroyed Partition? Invalid BS_jmpBoot in boot block: 000000

So.. I have a rather odd problem with one of my HFS+ partitions all of sudden. I can't get it to mount in Mountain Lion, and when viewing from Disk Utility, it acts like it can't read the partition name, and the Verify process in Disk Utility detected errors, but the Repair process couldn't fix it, because of the error in the title (Invalid BS_jmpBoot in boot block: 000000).

Here's the full log, from Disk Utility:

2012-10-16 15:20:32 -0400: Verifying volume “disk2s3”

2012-10-16 15:20:32 -0400: Starting verification tool:

2012-10-16 15:20:32 -0400: Checking file system2012-10-16 15:20:32 -0400: ** /dev/disk2s3

2012-10-16 15:20:32 -0400: Invalid BS_jmpBoot in boot block: 000000

2012-10-16 15:20:32 -0400: Error: This disk needs to be repaired. Click Repair Disk.2012-10-16 15:20:32 -0400:

2012-10-16 15:20:32 -0400: Disk Utility stopped verifying “disk2s3”: This disk needs to be repaired. Click Repair Disk.

2012-10-16 15:20:32 -0400:

2012-10-16 15:20:54 -0400: Verify and Repair volume “disk2s3”

2012-10-16 15:20:54 -0400: Starting repair tool:

2012-10-16 15:20:54 -0400: Checking file system2012-10-16 15:20:54 -0400: ** /dev/disk2s3

2012-10-16 15:20:54 -0400: Invalid BS_jmpBoot in boot block: 000000

2012-10-16 15:20:54 -0400: Volume repair complete.2012-10-16 15:20:54 -0400: Updating boot support partitions for the volume as required.2012-10-16 15:20:54 -0400: Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.2012-10-16 15:20:54 -0400:

2012-10-16 15:20:54 -0400: Disk Utility stopped repairing “disk2s3”: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.

2012-10-16 15:20:55 -0400:

The last thing I did with it was access this partition from Windows 8, with the latest Bootcamp Windows Support package installed. I recall attempting to create a new folder on this partition from there, which didn't actually happen, since the Windows Support package only allows read-only access. I don't know if it's related, but this is the only thing i can think of...

Now, the really odd thing is that I can access this partition from Windows 8 perfectly fine - it's just in Mac OS that I'm having access problems. So.. whatever happened, thankfully I actually did have Windows installed, so that I can retrieve my precious files.. even though Windows was likely the culprit in some fashion in the first place.

Thanks for any help and insight.. I'm totally confused what might have happened, and I'd like to avoid it in the future.