Disk boot failure after BSODs

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 13
    Windows 7 x64
    Thread Starter
       #11

    TVeblen said:
    Well, it's obviously not failed totally if you can access data from the enclosure. But a fail-ing drive can behave awful strange.

    Have you reset the BIOS defaults as Wishmaster suggested?

    One WAG (wild-ass-guess): See if there is a jumper on the drive to switch between SATA mode 1 and SATA mode II. Set it to SATA mode 1 and test.
    I did what Wishmaster suggested. According to my manual, there is a Reset CMOS button which I used and then proceeded to load the defaults. But there was still no change.

    I tried the jumper switch but it still doesn't recognize the hard drive.

    I wonder if I should just use a new hard drive, but I'm worried about that nvlddmkm.sys error and this possibly happening again.
      My Computer


  2. Posts : 4,517
    Windows 7 Home Premium 64bit
       #12

    The drive is recognized on another computer as a secondary drive correct?

    Have you tried running a check disk or HD test from the PC that does see it?
    this way we can determine if the drive itself is good or going bad.

    The nvlddmkm.sys error I believe was a Nvidia driver error.
    Although this will need to be addressed, this would be software related.

    It should not cause the HD to be unbootable.
    Last edited by Wishmaster; 05 Sep 2010 at 00:23.
      My Computer


  3. Posts : 13
    Windows 7 x64
    Thread Starter
       #13

    Yes, it is recognized as a secondary drive. I haven't done a check disk yet. I have the HD Tune Pro program and can do a test with that tomorrow. Any suggestions with it would be helpful.
      My Computer


  4. Posts : 12,177
    Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
       #14

    Just a suggestion, backup any data you don't want to loose from the possibly failing HDD, before it's too late.

    Then the HD test as previously suggested.
      My Computer


  5. Posts : 13
    Windows 7 x64
    Thread Starter
       #15

    I tested today and the health status tab said everything was OK. I did a scan for errors and there were no damaged blocks. So, I'm rather confused.
      My Computer


  6. Posts : 6,292
    Windows 7 64 Bit Home Premium SP1
       #16

    Yours is not an easy problem to diagnose, my friend. But lets keep at it.

    When you attach this drive to the two different computers you are using the SATA cable connection, using 2 different cables, and the drive is not recognized in either computer's BIOS.

    But when you connect it inside an external enclosure that connects to the computer by USB it is recognized.

    What kind of connections are made to the hard drive inside the external enclosure?
    A SATA cable or a big IDE ribbon cable?
    A SATA power connector, or the old style molex connector?

    And, when the drive is connected inside the computers, is it powered by a SATA power connector?
      My Computer


  7. Posts : 13
    Windows 7 x64
    Thread Starter
       #17

    When you attach this drive to the two different computers you are using the SATA cable connection, using 2 different cables, and the drive is not recognized in either computer's BIOS.
    Yes, that's correct.
    What kind of connections are made to the hard drive inside the external enclosure?
    A SATA cable or a big IDE ribbon cable?
    A SATA power connector, or the old style molex connector?
    This is the enclosure I'm using: Vantec NexStar 3 NST-360SU-BK 3.5-Inch SATA to USB 2.0 and eSATA External Hard Drive Enclosure (Onyx Black)

    There's a built-in plug on the plate inside. It uses the same heads of a SATA cable and a SATA power connector. It doesn't use the big IDE ribbon cable head nor the old style molex connector head.
    And, when the drive is connected inside the computers, is it powered by a SATA power connector?
    Yes, they were powered by a SATA power connector. They are also two different SATA power connectors.
      My Computer


  8. Posts : 6,292
    Windows 7 64 Bit Home Premium SP1
       #18

    Damn!
    I was thinking it could be just a bad connector or power plug.

    For the others: if the MBR got corrupted, would that explain the symptoms?
      My Computer


  9. Posts : 53,364
    Windows 10 Home x64
       #19

    TVeblen said:
    Damn!
    I was thinking it could be just a bad connector or power plug.

    For the others: if the MBR got corrupted, would that explain the symptoms?
    This was what I suggested was possible in the Guru discussion of this thread. the fact it will work as a non boot drive. Have a look at this:

    MBR - Restore Windows 7 Master Boot Record

    A Guy
      My Computer


  10. Posts : 13
    Windows 7 x64
    Thread Starter
       #20

    A Guy said:
    TVeblen said:
    Damn!
    I was thinking it could be just a bad connector or power plug.

    For the others: if the MBR got corrupted, would that explain the symptoms?
    This was what I suggested was possible in the Guru discussion of this thread. the fact it will work as a non boot drive. Have a look at this:

    MBR - Restore Windows 7 Master Boot Record

    A Guy
    I didn't use this method, but I did try to use Startup Repair option before, which didn't work. It didn't detect my operating system like picture #3 though. I'm guessing that this won't work unless it does?
      My Computer


 
Page 2 of 3 FirstFirst 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:34.
Find Us