Machine specs: Lenovo SL500 laptop with T9800 2.93GHz CPU, 8GB RAM, 320GB hard drive with factory restore partition, Windows XP Pro partition (with Ubuntu 13.04 also installed within a folder on this partition) and Windows 7 Pro partiton which is default boot partiton.
So, here is what has led to my issue but I don't know if it is really related. I had just updated my Piriform Recuva from version 1.4x to the newest version which is 1.51. When the install was finished, it said a reboot was required so I rebooted. Prior to this, the machine has been running fine.
Upon reboot, the machine got as far as the colored swirling patterns that form the Windows 7 logo. The swirling pattern stops and then the BSOD flashes very briefly and the machine reboots. I was able to get a picture of the screen and the following is displayed at the bottom:
STOP: 0x0000007E (0xFFFFFFFFC0000005, 0xFFFFF88001750659, 0xFFFFF880009A8F28, 0xFFFFF880009A8780)
cng.sys - Address FFFFF88001750659 base at FFFFF880001745000, DateStamp 50194fb7
I have tried booting in Safe Mode which also produces the BSOD. I have tried to do Startup Repair but it informs me that a device or something is inaccessible.
Last Known Good Configuration will not boot either. Produces same BSOD. I tried the option to not have the machine restart after error and that BSOD screen had IRQL_NOT_LESS_OR_EQUAL with STOP 0x0000000A (0xFFFFFFFFFFFFFFC0, 0x0000000000000002, 0x0000000000000000, 0xFFFFF80003A95DA2)
Here is where things get weird. I tried booting into Ubuntu and that boots up fine and it is what I am using right now to type this on the machine that wont boot the Windows 7 partition (yet I can see all the files on the Windows 7 partition from UBUNTU).
Gets weirder. I figured I would clone my issue drive to another drive and use the clone for trying to get things fixed before I mess up the original. Since the spare drive I was going to use has a fresh install of Windows 8.1 on it, I installed that drive to see if there are any files I might have wanted to take off the drive before I wiped the drive.
This drive, which has booted just fine every time I have put it in the laptop, freezes shortly into booting at the logo screen. So, this Windows install seems to have issues mimicing my normal Windows 7 (most likely just coincidence). After playing with this for a bit, I got a few different BSOD screens, such as KMODE_EXECUTION_NOT_HANDLED ks.sys, SYSTEM_THREAD_EXECUTION_NOT_HANDLED, and ATTEMPTED_EXECUTE_OF_NONEXECUTE_MEMORY rdbss.sys.
So, I tried booting with just one DIMM to see if it was memory related but no matter which DIMM was used in either slot, keep getting BSOD. I even went so far as to replace the 2 DIMMS with 2 other DIMMS but still get BSOD, yet UBUNTU is able to boot just fine and displays correct CPU and RAM in machine.
Since my Windows 8 drive was just a test, I decided to attempt to clone the Windows 7 drive and work on the clone but I am running into some snags. I have a cheap duplicator made by Cavalry Storage and although it cloned the drive, it did not correctly clone the Windows 7 partition. The partition shows up as having no files.
So, I then attempted to clone through software using HDCLone, but for some reason, HDCLone wont see my Seagate 320GB SATA drive unless I change my BIOS settings for SATA to Compatibilty mode instead of AHCI mode. This produces copy speeds that are way to slow. It would take a day to copy the drive (I did try anyway and it appeared as though it was failing to write to the destination drive according to what was displayed on the screen).
So, I then created a bootable USB drive using Macrium Reflect and booted from this and attempted to clone my drive but this gives an error before starting the clone process stating something about not being able to do something with one of the partitions on the destination drive. I even told it to delete all partitions on the destination drive before starting the clone and still receive same message.
By the way, I am trying to clone to an SSD drive if that makes a difference.
I don't know much about the bootrec, bootsect and bcdedit commands but was wondering if somehow they might help get me back up and running. Plus, since I have multiple partitions, I don't know how this might affect the XP partition if I start messing with these commands.
I really would like to clone my drive first and work with the clone just in case any of the attempts to repair it actually make it harder to recover or fix the drive. I figure once the clone is up and running correctly, I can reproduce the same steps to fix the actual drive that failed.
So, at this point I am at a loss as to what might be going on or what I can try to get my Windows 7 to boot properly again.
Any and all help greatly appreciated.