Last 3 partitions on 6TB drive became RAW after reinstalling drivers..

Ok I got a odd problem I'd like some input on before I go nuclear and backup all the partitions to external drives and complete reinitialize it. I don't want to do this as this will take a few days to complete due to the amount of data I'd have to move around.

First some details on my system. My primary boot OS is Windows 7 Pro 64bit which is installed on a 500GB SSD. Then got a secondary OS installed (I have a dual boot setup). This one is Windows 8.1 Pro which is on a 500GB standard platter drive. These two drives haven't been giving me issues so I won't go into further detail about them.

The third drive in my system is a 6TB Western Digital drive I pulled out of a SATA USB enclosure (was originally one of those "My Book" external drives) and installed as an internal drive. I then modified the USB enclosure PCB to allow third party drives so the drive I replaced with the 6TB drive now lives in the USB enclosure. That 2TB drive in the USB enclosure is also not giving me issues right now so I'll skip further info on that one.

Anyways I was installing the Intel AHCI drivers over the "Standard" drivers that Windows 7 likes to use. This required that I restarted the computer.

After I did the 6TB drive suddenly has the last 3 partitions show up as RAW. The drive letters were still assigned correctly though. The first 2 showed up fine though chkdsk was giving errors with the second partition (I decided not to allow it to attempt any fixes).

So to check if there was any actual issues with the drive's partitions I restarted into my Windows 8.1 install. Here's the weird thing...the drive shows up correctly there. the last 3 partitions show up fine and I can see all the data. I even ran Windows 8's chkdsk on all the partitions and it found no problems!
I restarted back to Win7 and downloaded TestDisk just to see how it sees the drive. It too is able to see the partitions correctly and they show up as NTFS and I can view the directory tree. But Windows Explorer, Disk Manager, and EaseUS Partition Manager see the partitions as RAW and not NTFS.

Is there something I can do in the registry to make Windows 7 forget about certain details about the drive so it can access it properly? Would changing the Disk ID fix this? I also tried doing the mountvol /r trick to make it forget all the drive letter assignments for hte drive. (I made the drive offline so that it sees the letters as on no longer accessible volumes so that they'd get cleared out from MountedDevices). This did reset the drive letters for the partitions on the 6TB drive but didn't fix the last 3 partitions showing up as raw.

On the subject of Disk ID I do recall I issue with that crop up with this drive when I was installing a LS120 drive. For some odd reason one of the LS120 floppy disks I inserted caused a Disk ID collision and Windows 7 forced the 6TB drive offline. I had set it back to Online in Disk Manager which forced it to give new ID to the 6TB drive. But then all the partitions vanished. I had to use partition recovery software to rebuild the GPT partition entries. But after I fixed that issue the drive had been working fine and had no issues with any data on the partitions I restored. But I don't know if this previous issue has any impact with what happened today. Either way I'm finding GPT drives a pain to work with. It's like it want's to go heywire if you simply look at it wrong. Never had these kind of problems with MBR drives. But I have to keep this drive GPT due to it's size as the last 3 partitions are beyond the 2TB limit for MBR so I guess I'm gonna have to deal with this crap.

Anyways I'll probably still do a drive backup again before I mess with the disk ID again as last time it was changed the GPT partition table went heywire on me and I had to rebuild it.
Anyways any ideas on non destructive ways to fix this issue would be welcome. If all else fails I'll have to boot into Windows 8.1 and backup all the partitions then wipe the drive and reinitialize it. This should definitely resolve the problem but it would take a looong time to do so I want to avoid that if possible.

I just now resolved it. Changed DiskID then moved the drive to the JMicron controller (my mobo has a different SATA controller which has an eSATA port and 2 internal SATA ports wired to it). I did the DiskID change while in Windows 8.1. Before I did this I used HxD (a hex editor) to backup the entire beginning area that stores the GPT partition table so I can go back if that broke things. (it didn't thankfully).

(oh by the way I don't have System Restore enabled with Windows 7 so I can't really use that. I use entire backups of the main boot drive if the OS ever goes belly up. I did try the "Last known Good Configuration option in the F8 menu though and this didn't really change much)

After changing Disk ID and moving the drive to a different SATA port that is on a different controller all the partitions show up correctly now in Windows 7! I guess I'll mark this as solved. (oh by the way I did try to roll back the SATA drivers...it didn't help and if there was an issue with them it would have broke the boot drive and Win 8.1 drive because those 2 are connected to that controller too)

I'll run a chkdsk in read only mode on all partitions on this drive while in Win7 just to make sure everything is good but so far it seems back to normal.

I'm not sure if moving the drive to a new sata port was necessary or just the DiskID change (or vise versa) so if someone else runs into this problem that should fix it.

I would have waited a bit before doing that but since one of the partitions I couldn't access was storing all the media for my Plex server and my mom was complaining that she couldn't watch her movies so I had to do a last minute hail mary with my DiskID change idea to see if that could get things up and running for her. I also decided super make sure by moving the drive to the JMicron controller so it had a completely different driver path to it as well.

I have this entire drive backup up by the way so worst case scenario I'd have to roll back to a 1 to 2 month old backup of all the partitions which would have only lost a few things I added to the Plex server during that time. :P