BSOD when HD is connected BC Code 50

[jonzes]

I am getting a Page_Fault_In_NonPaged_area BSOD loop. I can get around it by disconnecting one of my internal data drives. I imagine it is dieing or dead but not sure why that would cause it to BSOD as soon as it is connected. Most of it is backed up but there are some recent files I'd like to get at if I can. But as it is I can't run any HD tools as I BSOD as soon as I boot with it connected or if I connect while it is running.

Previously this HD would occasionally drop off and dissapear while running. I looked into it and it seemed like it might be an issue with my BIOS of my MOBO needing to be updated. But it also was fixed by restarting the machine. Not sure if this is related.

 

[JohnPC]

Hello,
MicroSoft states it may be due to a corrupted NTSF device (among many other probable causes.) Since you can't connect it via internal SATA, have you tried a USB dock to run Chkdsk on it? I usually keep a spare SATA to USB case sitting around as an alternative connection source to debug stuff.

Regards,

 

[essenbe]

It looks like the Hard Drive. You had 3 dump files, all saying basically te same thing.

SYMBOL_STACK_INDEX:  3
SYMBOL_NAME[COLOR=red]:  Ntfs!NtfsCheckRestartTable+144[/COLOR]
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME:  [COLOR=red]Ntfs.sys[/COLOR]
DEBUG_FLR_IMAGE_TIMESTAMP:  5167f5fc
IMAGE_VERSION:  6.1.7601.18127
FAILURE_BUCKET_ID:  X64_0x50_Ntfs!NtfsCheckRestartTable+144
BUCKET_ID:  X64_0x50_Ntfs!NtfsCheckRestartTable+144
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:[COLOR=red]x64_0x50_ntfs!ntfscheckrestarttable+144[/COLOR]

You can try what was already suggested, an external dock or something similar to get your data off. Then you can try to run Seatools http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html#Part3 To determine if the file system is the cause or the drive itself.

 

[jonzes]

Thanks a lot for your help guys. I tried out an external USB enclosure and I have had mixed results. Under some combinations of plugging it in after boot I can see the HD in my Disk Management window but without a name or mention of how much is used. It is not in explorer. If I try to do anything with it I get a message that it is no longer there and I need to refresh, but if I do it is still there. If I have it installed during boot I get the BSOD.

What makes this more weird is I hooked the external drive to a work laptop and it works just fine. I would just copy the files off to a new HD on that machine but it is locked down so I can only read to its USB ports.

I tried updating the BIOS on my motherboard because I thought it might be an issue with mounting the drive on the SATA but that does not seem to have changed much.

Any idea why on two Windows 7 64 bit machines one would BSOD just from being attached to the drive and the other would read it just fine?

 

[essenbe]

No, I really can't tell you why other than guess it could be a chipset difference. One thing you can try is recovery with a Linux Live CD/USB http://www.sevenforums.com/tutorials/287439-emergency-kit-save-your-files-dead-os.html