BSOD Error PAGE_FAULT_IN_NONPAGED_AREA BCCode: 50

Yes the HD is back on the original computer.

Looks like the recovery fail to happen because of the missing FNTCACHE.DAT



Booting into Safe Mode and trying to go to the control Panel doesnt work either...

essenbe said:

Can you boot into safe mode?

Yes

I just ran also the following, waiting for a reboot (takes forever) to see if anything was fixed...
for %a in (c:\Windows\System32\*.dll) do regsvr32.exe /s "%a"

Kaktussoft said:

Who/what did delete FNTCACHE.DAT and why?

Because that is what allowed me to do anything at all with this HD, and all the research I have been doing suggested that was a good fix. The file is still there, just renamed to "old" but if I rename it back to original I am afraid that will break things again.

Kaktussoft said:

Why do: for %a in (c:\Windows\System32\*.dll) do regsvr32.exe /s "%a" ?
Don't mess around with commands/tricks you don't understand!

Because again the research I have been doing about the errors I am getting suggest those are probably fixes.

Please feel free to suggest things that I can try instead.

essenbe said:

Go to c:\Windows\System32\FNTCACHE.DAT and see if that file is there, not the one you renamed, a new one. It should automatically rebuild the FNTCACHE file. The restore you tried was before we renamed the file. If there is no new file, rename it back like it was and see. That's why I told you to rename it and not delete it.

I cant open windows explorer but I browsed using the command line and the "old" file is no longer there. and there seems to be a new one there.

essenbe said:

Go to c:\Windows\System32\FNTCACHE.DAT and see if that file is there, not the one you renamed, a new one. It should automatically rebuild the FNTCACHE file. The restore you tried was before we renamed the file. If there is no new file, rename it back like it was and see. That's why I told you to rename it and not delete it.

I cant open windows explorer but I browsed using the command line and the "old" file is no longer there. and there seems to be a new one there.

I fixed the error with the desktop by taking ownership of the folder via the command line and using TAKEOWN /F "C:\....

I am still getting the following error when i try to open control panel or windows explorer, etc...