Hail Mary? I broke it (Win7 Pro x64), can you help? Unbootable

[hoping4better]

I have a complicated problem and have searched seemingly endlessly with nearly zero help. What I did was stupid, but I was in a hurry . . . not an excuse, but was the reason. Hardware does not appear to be an issue. Both brand new Seagate Barracuda drives are easily read in linux with zero issues and gparted reports that they are fine and have ntfs volumes.

My current errors are this: One boot it bluescreens and the error is the one ending in 7b with the following detail:
0xFFFFF880009B3928
0xFFFFFFFFC0000034
0x0
0x0

Repair disk is unable to repair. I have run bootrec /Fixmbr /fixboot /rebuildbcd
The system did not recognize Win7 already installed.
None of that helped at some point I managed to remove the bcd then did bcdedit /createstore, bcdedit /import, del bcd
This allowed the repair disk to recognize the installation. But, still no ability to repair regardless of running the bootrec commands above.

Safeboot results in the bluescreen as well. I forget what F8 option I chose, but one of them shows everything as it tried to load and it hangs on Classpnp.sys and reboots everytime.

Here is what happened best I can remember:
The Dell T5500 with the Raid Controller set to "on", had two drives. The one with installation media ("primary") and a second drive for data("data"). I was attempting to replace the data drive first. The primary was full (so I thought) and I decided to DD the data drive using a Gparted boot flash drive, which took FOREVER (2TB and for some reason it was only copying at about 30MB/second)!! While it was still running I looked at the primary drive and saw that there was a very large portion that was unallocated and a linux partition I never use anymore, so like an idiot, I deleted the linux partitions and extended the Windows partition. On reboot it failed. Don't remember all the original errors, but basically at first it couldn't see the drives, loading a Windows Repair Disk and in command line running Diskpart identified the drives as RAW. Apparently this has something to do with the bios having been set to RAID on, so apparently they were single drive RAID 0? Anyway, I figured that out and went into the bios and changed the setting to autoselect (which used to make the system unbootable), but this allowed the repair disk to actually see the drive, but still saw it as raw even though linux sees the disk as ntfs and had zero issues reading or writing files of any kind. Running the detail listed above after the error codes resulted in the current situation. System is unbootable, but readable by the repair disk. I did decide to reinstall to a new folder, that installation did boot. But, since I don't want to reinstall years of programs and reconfigure years of configurations I haven't touched in over a year, I followed Microsoft's directions for recovering the Windows.old to the current installation . . . now it's unbootable again with the same errors.

Why does a new installation boot fine, but copying the appropriate windows.old data (according to microsofts directions) to the current installation fail and bluescreen to the errors listed above?

How do I fix this? I have spent over a week trying to find a solution and ask all the knowledgeable people I know about it. They all said I was screwed and had to reinstall again. BUT why?? If it will boot with a new installation, shouldn't there be a way to reconfigure that and use it to recover my previous installation? I know it won't be easy or quick, but I'm fine with that.

Hoping I can find a solution. Help, PLEASE!

 

[SIW2]

"Why does a new installation boot fine, but copying the appropriate windows.old data (according to microsofts directions) to the current installation fail and bluescreen"

Sounds like a Problem with windows\system32\config system hive.

1. You could try installing ( to the same partition). If that boots, keep a copy of the windows\system32\config system hive.

2. Rename windows.old\windows\system32\config system to system.backup

3. then copy in the system hive you just saved into windows.old\windows\system32\config

 

[hoping4better]

That was a definite improvement. Made is passed Classpnp.sys and a mouse cursor appeared, then it rebooted.I chose the bootlogging choice and it loaded everything up to and including classpnp.sys then nothing until null.sys, beep.sys, vga.sys then nothing until msfs.sys, npfs.sys,wmiacpi.sys then nothing for a bunch then just hit and miss. There was a whole lot not loaded.

What else can I use to troubleshoot?

--Edit--
Tried the auto startup repair utility. It found no errors.