\ntldr is corrupt or missing error C0000007

I installed XP and then Vista on a separate partition, same hdd. XP crashed
and now Vista reports that \ntldr is corrupt or missing when loading
"Earlier Version of Windows".
The error code printed is C0000007. The Vista repair process did not detect
any problems. I used then the XP recovery and did a fixboot. This had the
efect that the Vista preload options were made unavailable. I reinserted the
Vista DVD and did a second repair so now I have the dual boot environment
that existed before.
My question is why did the ntldr became corrupted?

Could be any number of reasons, but the error code indicates a driver fault.
What's important is that you were able to get it repaired. If it should
happen again, I would suggest you have the memory dump from the XP
installation examined for additional clues.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

"Calin Iaru" <> wrote in message
news:11E720BF-5B87-47D3-B92A-...
>I installed XP and then Vista on a separate partition, same hdd. XP crashed
>and now Vista reports that \ntldr is corrupt or missing when loading
>"Earlier Version of Windows".
> The error code printed is C0000007. The Vista repair process did not
> detect any problems. I used then the XP recovery and did a fixboot. This
> had the efect that the Vista preload options were made unavailable. I
> reinserted the Vista DVD and did a second repair so now I have the dual
> boot environment that existed before.
> My question is why did the ntldr became corrupted?

I know the driver that caused it, however, the same dual boot happens on an
identical machine with no side effects. The driver crashes there too, again
under same circumstances. The driver and it has nothing to do with File
Systems. The one thing I cannot guarantee is that the machine was rebooted
after the full dump was taken. If a reboot occurs during the memory dump,
then that could cause some problems.

"Rick Rogers" <> wrote in message
news:eN4EmMU%...
> Could be any number of reasons, but the error code indicates a driver
> fault. What's important is that you were able to get it repaired. If it
> should happen again, I would suggest you have the memory dump from the XP
> installation examined for additional clues.
>
> --
> Best of Luck,
>
> Rick Rogers, aka "Nutcase" - Microsoft MVP
> http://mvp.support.microsoft.com/
> Windows help - www.rickrogers.org
> My thoughts http://rick-mvp.blogspot.com
>