What would be your next step?

[J-Mag]

I have a 300gb IDE disk that detects on start-up fine and I can browse through the file/folder structure within windows explorer. However, if I try to open any of the files I get a BSOD. I have tried chkdsk and some freeware data recovery program (which i forgot the name of atm) with the same result of a BSOD.

I also, tried replacing the IDE cable and removing all Y adapters from it's power line.

I don't think I have ever had this happen, usually a drive just stops functioning all together. This one seems like it is working...

What would you do next? ANyone else ever get BSODs trying to access any file on a disk?

 

[mikeblas]

You're not crashing accessing any file; you've accessed hundreds of files just bringing up Windows.

I'd get a dump and try to debug it. If you don't know how to do that, you can post a link to the dump file and I'll go through it for you. See here and here for instructions and additional BSOD troubleshooting tips.

I'd also try safe mode.

Short of any evidence or symptoms, I'd guess that you have some spyware, a root kit, or a very broken virus program.

 

[J-Mag]

You're not crashing accessing any file; you've accessed hundreds of files just bringing up Windows.

I forgot to mention it isn't my boot drive, just a data drive.

I'd get a dump and try to debug it. If you don't know how to do that, you can post a link to the dump file and I'll go through it for you. See here and here for instructions and additional BSOD troubleshooting tips.

Thanks for the links I will take gander ...

I'd also try safe mode.

Why didn't I think of that?

Short of any evidence or symptoms, I'd guess that you have some spyware, a root kit, or a very broken virus program.

Maybe, but I have 9 disk drives hooked up (8 SATAs) and this is the only one with the problem. Although my other IDE hard drive died on me a few months ago, it's symptom was radically different as it wouldn't even show during the boot detection phase.

 

[techie81]

Is it always the same BSOD?

 

[mikeblas]

I forgot to mention it isn't my boot drive, just a data drive.
[...]
Maybe, but I have 9 disk drives hooked up (8 SATAs) and this is the only one with the problem. Although my other IDE hard drive died on me a few months ago, it's symptom was radically different as it wouldn't even show during the boot detection phase.

That's all very important information that wasn't in your original post, and is why I described my ideas a guess instead of a diagnosis.

Let us know when you can provide more information.

 

[J-Mag]

Is it always the same BSOD?

I am pretty sure it is the same BSOD every time... I will double check by taking a quick pic of it when I get home.

 

[J-Mag]

OK well I lagged a bit on getting this posted up...

This is the BSOD I got from accessing a file on this disk on the 22nd



This is the BSOD I got from accessing a file on this disk Today



SO the disk seems to run normally and I can browse the file structure, but any time I access a file I get the above BSOD... Any clue as to what is wrong here?

 

[hokatichenci]

Have you tried using it in a different computer? Have you tried using a Linux livecd (Knoppix)?

 

[J-Mag]

Have you tried using it in a different computer? Have you tried using a Linux livecd (Knoppix)?

I brought this disk to work and my machine there reads it fine, no problems at all... I am thinking it could possibly be the IDE controller, but my optical drives work fine... wtf?

 

[RBremen]

Two things. Run diagnostics on it to see if an error comes up. I had a Maxtor drive that did something similar to yours and it was just a bad drive. The other thing that comes to mind is your power supply. I had intermittant drive problems after adding a sixth drive. All kinds of different errors...boot, access files etc... Turns out my power supply wasn't quite up to the task. Unplug all the other drives except for the boot and the problem drive and then see what happens. Good luck...

Bremen