I really need some help and advice. I'll set out the problem as briefly as I can below and any assistance would be hugely appreciated.
I have one hard drive with two partitions. Windows XP SP3 is installed on the c: drive along with all the program files I've downloaded since upgrading my computer. Everything else - including cloned copies of two older disk drives - was on my d: drive.
A couple of weeks ago after installing a new graphics card and running multi monitors I kept getting BSOD caused by Nvidia drivers. I sorted this out but thought I had better run chkdsk on both drives/partitions.
Chkdsk ran smoothly for the c:drive. It only ran on the d: drive after being dismounted and there were a couple of things it claimed to fix, namely 'discovered free space marked as allocated in volume bitmap' and a similar thing but 'allocated in master file table'.
Next time I switched the computer on I got a BSOD with the following error message:
STOP: 0x00000024 ntfs.sys B7E55167 base at B7E48000 datestamp 48025be5
Now I can't boot into safe mode or even into the recovery console without receiving the same blue screen. Even worse, XP was pre-installed on this computer so I have no cd (though I assume the files are somewhere on the system). I do have an Acronis boot cd but can't see anything useful on here apart from basically wiping the entire thing.
So I guess I have two questions:
(1) Does anyone know of why the above could have happened and what a potential solution might be? I wondered if chkdsk had somehow found and rebuilt the ancient XP installations from my cloned hard drives buried deep in partition d: an that has caused havoc. But i'm purely guessing - I now next to nothing about how these things work!
(2) Assuming the worst and that I'll never be able to get back in, is it possible to buy a new hard drive, install Windows 7 on it and then set my current hard drive up as some kind of 'slave' so that I can still access all the programs and files on it even though I can no longer boot from it?
Many thanks in advance for any help and apologies if some of you would have put this in a different forum. I find it hard to judge if this is a hard drive issue or an XP one (or both).