New
#21
pretty sure.... so not 100%?
The solution Blue Screen (Stop 0x50) after applying update KB2982791 to - Microsoft Community
So only thing to do is delete C:\Windows\System32\FNTCACHE.DAT
pretty sure.... so not 100%?
The solution Blue Screen (Stop 0x50) after applying update KB2982791 to - Microsoft Community
So only thing to do is delete C:\Windows\System32\FNTCACHE.DAT
The problem is I cant access the drive contents as I explained when i plug it into another bot it blue screens my machine
So boot to Advanced Boot Options select "repair your computer".
System Recovery Options select "command prompt" as shown in step 6.
Or do Command Prompt at Startup OPTION ONE.
Now in "command prompt" you can do:
Assume Q is the drive letter of your win7 partition (check with commands above). Do:Code:DIR C:\USERS DIR D:\USERS DIR E:\USERS
Replace Q with actual drive letter. Did you successfully delete it, or did an error message popup? Post results.Code:DEL Q:\Windows\System32\FNTCACHE.DAT
I wish I could, all the options you posted I have tried with no success. Even with the HD plugged into my machine as slave and trying to boot from my machine; it makes my machine blue screen before I get to anything.
His computer will not boot with the drive attached and will not boot into the DVD drive with that hard drive attached by USB. I am aware of the update, but even with the update, the computer will not boot in any way with that drive attached.
Now I understand!! The stop 50 error has ntfs.sys in the message. It's not related to the august patches at all!! It's corrupt disk. Even attached as external disk it confuses win7 and crashes. Even the win7 recovery environment is corrupt because it some kind of mini windows and located on C volume as well.
Do you have a win7 install dvd or system repair disc? You can create on in minutes System Repair Disc - Create
^^ that won't work either. I think its safe to say this HD is now a paper weight :) It could be that the patches somehow corrupted the HD, no idea but if I could boot into it or access the drive to try things there might still be a chance but since that is not possible...