Hard Drive causes BSOD

[CyberJourn]

I had a laptop that came in with a BSOD...

0x00000024 NTFS.sys

All the Advanced Boot options (Safe mode, Safe Mode with Command Prompt, Last Known, etc) will get a BSOD.

Booting to the Windows CD and trying repair or anything will BSOD. Booting to Hirens Mini XP will BSOD.

Taking the hard drive out of the computer and putting into an external enclosure and then plugging it into my computer will BSOD immediately with the same error above.

The drive is a Seagate so I ran the SeaTools on it from Hirens and the drive passed diagnostics.

I was able to boot to a Linux Live CD and I could view data on the drive. I downloaded the Kaspersky Live CD and it found no infections on the drive.

I've Googled this and really haven't found anyone with this same type of issue.

Have any of you seen this or have any suggestions?

TIA

 

[The Silent Hobo]

http://answers.microsoft.com/en-us/...-startup/62a7226d-749c-4832-83ba-dd21f9087d12

not to sound mean at all, but next time you try to search for an error code, just search the error code itself and not the ntfs.sys thing, and see what that pulls up

 

[FremontPC]

Can't say that I've ever run into that one before.

If you boot into Ubuntu and use the Disk Utility to take a look at the SMART readings on the drive, do you see any trouble there?

As I recall, you can use Linux to repair NTFS drives, but you might want to backup the drive or at least the data first (if possible).

 

[lcoughey]

If the data on the drive is worth fighting for, then you had better get a full sector-by-sector clone before the drive fails.

If the issue is a logical issue, you have lost nothing and gained a backup. If the issue is physical, you will know right away and then you can decide if you are qualified to deal with the physical issues or if you need to outsource to someone who is.

 

[ComputerRepairTech]

http://answers.microsoft.com/en-us/...-startup/62a7226d-749c-4832-83ba-dd21f9087d12

not to sound mean at all, but next time you try to search for an error code, just search the error code itself and not the ntfs.sys thing, and see what that pulls up

wheres the downvote button

Edit: I never tried this before but...what about ntfsfix from linux?

 

[ShinyTech]

Ive seen multiple computers that when you install a certain brand of drive it will cause this. I know it makes no sense at all but try a new hard drive in it from a different manufacturer. Ive had about 2-3 computers where Ill install a seagate and it will act funky and all tests pass, then I put a WD in and it works fine (manufacturers just an example).

 

[MobileTechie]

Usually 24 stop errors is file system corruption and can, if you're lucky, be corrected with chkdsk /f

I've had a few recently as it happens. Took a few runs of chkdsk to sort it but when it got sorted the filesystem went from RAW back to NTFS.

As for the disk crashing Windows, I've also seen this before. I posted about it years ago but I can't find the post. It's something to do with the corrupted file system. Even when you use UBCD4Win or any other Windows based disk for that matter, despite them not running on the drive, they still have to mount it and the specific corruption causes the error to pop to occur. Can be caused by a bad sector I think but if it's passed Seatools long test then unlikely. I'd still be tempted to run HDD Regen's full regeneration over the first 5% of the drive to rule out slow.

As I remember it you have to find non-Windows disks capable of checking NTFS. Gparted on Parted Magic has the ability to check and repair NTFS I think. Also there are some NTFS utilities on Hirens, at least one of which has a chkdsk function.

If the files are readable by a linux disk then you could try using linux apps to image the drive, format it and restore it.

 

[nonchalant]

I read somewhere recently that Seagate were bought out by maxtor. Maybe this is why their drives are so crappy these days.

Ok back to the topic...