Unable to boot Windows 7 Home Premium 64bit dv6 using recovery disk

Hello,
I have a HP dv6 that I force shutdown. Upon reboot, it asks me to do a Windows diagnostic and if I select that option, all I see is a blue screen (not the blue screen of death) and nothing else happens.

No progress bar, nothing...a DOS window did appear and disappear in a flash at the beginning.

Now, I had installed Ubuntu (through wubi, I think), and if I choose that OS option while booting, it boots up just fine. I can even see my Windows folders, files, etc., through Ubuntu file manager, though I can't copy, open of course.

Now, I have my 5 CD-R system recovery disks that I'd burned at the beginning.

I changed the boot order to CD in the BIOS, popped in recovery disk 1 and I see the two progress bars "Windows loading files" and then the blue screen appears again and nothing else does.

Thinking my recovery disks were corrupt, I plugged disk 1 into an Acer with the same Windows 7 Home Premium OS. When I attempted to boot my Acer from the HP recovery disk, I got a nice window with a message saying that this laptop is not supported by the recovery disk and to contact HP support.

So, the recovery disks are fine.

I'm not sure what else to do.

Any help will be appreciated.

Thanks for the information. I guess I was too impatient, and I went and bought the Windows Easy RE from neosmart. Initially it looked good, because the automatic repair said it had found an incomplete update and it rolled it back.

It did its checks, rewrote the MBR etc etc.

But thereafter with a reboot, I get the BSOD with "Unmountable boot volume"

So I went a bit crazy and tried everything that was suggested out there...
1. Chkdsk says there were no errors.
2. Tried everything in here https://neosmart.net/wiki/recovering...ows_Bootloader including the "holocaust" option where I rebuild the bcd.
3. Created a System repair disc for windows 7 64 bit ...when I ask it to repair, it gets stuck in the system recovery for ever, as shown in the attached image.
4. I even decided, the heck with it, I'll reinstall. But even there it gets stuck in the "Setup is starting" phase for ever.

The files are all there on C: I can browse them when I use Easy RE's Linux based file manager.

Also, this is what gparted shows

So, I think I'm at a situation where the Windows boot loader is messed up. I followed the bcdedit related steps to add the path to winload.exe, but while booting, it cannot find Windows\System32\winload.exe.

I visited C: and sure enough there's no trace of the familiar file system . But when I boot using the EasyRE and browse using the file manager, I see the familiar directory structure, include Windows\System32\winload.exe

Was my assumption that C: is my boot drive wrong? I have no other partitions...

I did email NeoSmart technical support, but I haven't heard back yet from them.

While it's possible the EasyRE cure either uncovered another problem in my messed up system, or caused it, fact of the matter is, that I'm faced with what seems to be a familiar problem:
0xc000000f missing or corrupt winload.exe

I guess I need help to recreate my boot loader, bcd, etc. such that I can get out of this. As I said, the file system seems to be fine, chkdsk doesn't report any problems.

I did try the bcdedit umpteen times to create a new BCD store from scratch and point it to my partition=C: , file: Windows\System32\winload.exe.

I even substituted a healthy winload.exe from another windows 7 home premium 64 bit install. Still no dice.