I had weird issues trying to get boot camp to load/run windows. Tried everything and it turned out to be the RAM. I put back in the factory RAM, installed boot camp, then put back my newer RAM after it worked.
It may not be your issue, but thought I would try.
It is hard to answer your questions. Mostly, because you have not fully answer my questions. I am going to guess that you are trying to install Windows to boot using the EFI firmware interface instead of the legacy BIOS interface. If so, you have not been the first to try. It is really not a question of whether or not you can get Windows to boot using the EFI, but rather what method the "Boot Camp Support Software" expects you to use.
I did an experiment last night. I have a mid 2011 iMac. The "Boot Camp Support Software" for 64 bit Windows 7 is version 5.1.5621. Your Mac would use the same software. My internet connection is 40 Mbps so downloading was not a problem. I also used the Boot Camp Assistant running under OS X 10.11 to download the software to a flash drive. I then compared every single file using windiff.exe. The files are identical. This is not proof that version 5.1.5621 do not contain any EFI drivers, but I do not think the drivers have not changed since the release of Windows 7. When Windows 7 was released, no Macs were booting Windows using the EFI.
OS X does not boot using the EFI specification. To use the specification, OS X would have to store software in the FAT formatted EFI partition. It does not. OS X does not even require a EFI partition to boot. The firmware is capable to reading HFS formatted partitions and recognizing the OS X operating system. Many Linux operating system take advantage of this. Fedora, for example, appears to the Mac firmware to be OS X. Once loaded, it transfers control to grub to finish the booting process.
In the end, I think you are trying to do something that can not be done. If your MBP was a year newer, the story would probably be different.
Best Answer
Have you tried trashing the Dock plist? Maybe a corrupted file.
Run that in terminal it will remove the file and a new one will generate on next log in. Only downside to trying is it will reset your dock so you will have to put yours apps back to it any other setting you may have changed on it.