The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Short DST Fail error

    Discussion in 'Dell' started by xxbox, May 17, 2007.

  1. xxbox

    xxbox Newbie

    Reputations:
    0
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    5
    I have a 600m laptop and i received this message a while ago when I ran the BIOS. I did some research and everyone pretty much said a new hard drive was needed. So i got a new hard drive and the same problem happened. My computer would be fine for a month or two then it would go very slow when I was multitasking and downloading files then eventually crash and not boot up at all. It would always give some kind of error that a system32 file was corrupt. My roommate said there might be a RAM problem, even though its rare. So I changed my RAM and I never thought there could have still been a problem with the hard drive functionality and I stupidly never ran the diagnostics to check if the Short DST test passed. Well my computer crashed again with the new ram and the new hard drive and then i ran the diagnostics and i get the Short DST Fail error again!!! I run the diagnostics on the CD and get errors on the reading part of the hard drive. Could my hard drive have broken again in less than a month or could there be a problem thats triggering the DST Short Test Failure? I plan on switching hard drives with my roommate to see if I get the same error. Any other suggestions or similar situations anyone has been in? :confused:
     
    xxbox, May 17, 2007
    #1
  2. WackyT

    WackyT Notebook Deity

    Reputations:
    906
    Messages:
    1,389
    Likes Received:
    1
    Trophy Points:
    56
    Have you tried running chkdsk from the Recovery Console?
     
    WackyT, May 17, 2007
    #2