Corrupt system from hard drive failure - SFC cannot fix all errors

My hard drive most likely sustained some light damage recently. The BIOS hard drive self test returns the error '#10008 - replace hard disk'. Using the Windows utility hooked up as an external hard drive it found 3 bad sectors. At least this is what I was told by my friend, unclear what it did with the bad sectors (reindexed maybe?).

Before the error check the laptop would just stop on a black screen after the Windows logo (both normal and safe mode). Since the error check it has been loading normally but on normal mode it throws a critical error during the start up and the system is forced to restart within a minute. Neither 'shutdown /a', nor 'Disable automatic restart after system failure' from the advanced booting options seem to prevent the shutdown. The good news is that the system is actually stable in safe mode with networking. However, it has resulted to critical errors as well when trying to either fiddle with file/folder privileges from the browser or unlock a file from another process. On safe mode it connects to the internet but on normal mode it only gives me limited access at best. I have also noticed some Base System Devices on Device Manager but I don't know how long they have been there for.


Things I've tried:
- System restore from the booting options didn't have any effect and the service seems to be disabled in safe mode.
- I have tried to repair the system from the advanced booting options and using SFC. Both report that they can't fix all errors.
- I have extracted any reported corrupted files from the installation DVD but either I can't replace them (even by granting admin rights because the files are in use) or the log still insists they are corrupted.
- I think I have tried a clean boot, that is msconfig -> services, hide all Microsoft entries and disable the rest, but on normal boot up the problem persisted.
- I tried boot logging on normal mode but I didn't know what to do with it. The second to last driver, srv.sys, failed to load.


Ideally, I would like to fix this problem without having to reinstall Windows in any shape or form. This is still more preferable though as a last resort than having to buy a new hard drive. What I ask for is some coordinated strategy to find the source of the problem and if possible, fix it too. I'm very hesitant on my own to force start applications on safe mode, change the registry or install a new copy of Windows and keep the old one in case I break what is already working. Even in this state, I have a computer which allows me to do the bare minimum of work I need to do and I have some approaching deadlines.


Specs:
- Windows 7 Ultimate x86
- HP Pavillion dv6700
- Intel Core 2 Duo T8100 @ 2.10 GHz
- 2GB RAM (only one of the two memory slots works, the other got damaged years ago and will result in quick and random BSODs if any RAM is present)
- nVidia GeForce 8400M GS
- WD Scorpio Black 750 GB

Well... I tried that and I had to restart. I attempted to boot up from safe mode in case it the check took too long (I have to leave soon). However, the loading froze like in the past and I had to hard reset. It managed to boot up next time using the last known working settings. What was surprising was that in normal mode it didn't bring up a critical failure, even the internet seemed to be fine. The graphics were a bit messed up though. On my way to report this here nvlddmkm.sys caused a BSOD.

Now, if a check disk is absolutely necessary, I'd prefer to wait either until Monday or try it as an external hard drive (depends on when it'll be convenient with my friend). I don't mind the delay if that's OK with you.

OK, so here's the status so far. Because I was in a hurry before I clean installed the graphics drivers I had (version 301.42). There were still a few glitches in the colours like before but they seemed to go away either by restarting the application or hovering the mouse over them. I left the laptop on in normal mode for a few hours and it hasn't crashed so far. Of course it wasn't doing much but at least baseline stability seems guaranteed. I will install the new drivers you provided me first thing tomorrow morning.


Serial number:
CNF8165QVJ

Product info:
Description=Computer System Product
IdentifyingNumber=CNF8165QVJ
Name=HP Pavilion dv6700 Notebook PC
SKUNumber=
UUID=38464E43-3631-5135-564A-001E6856BD86
Vendor=Hewlett-Packard
Version=Rev 1


The files that SFC claimed to have been corrupt were iTVdata.dll, msv1_0.dll and mstsc.exe. I managed to replace the first two in system32 with fresh copies, though I had to kill lsass.exe for msv1_0.dll. This is the only change that I can think of which has occurred on my computer for days. Maybe these files somehow contributed to the overall stability of the system. Maybe SFC insisted they were still corrupt because it was comparing them with other backed up versions. I attempted to replace a few of them in Windows/winsxs but there may be more.

For the time being I will stay in normal mode and see how things go. I'll probably fire up a couple of games or graphics tests to see how stable the drivers are. I also seem to have lost all previous system restore points. When I get the chance next week I'll run a few check disks to see how that goes. Do you think it's prudent to make an image of my current Windows folder? Any more ideas of what else could be checked or tested for?

I'll report back when I have something new. Thanks for all the help so far.

Right, that should be FE562EA#ABU.

Yes, it does mention that somewhere in the label. The product number though is what I gave you and the product is HP Pavilion dv6700.