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.

    M17x R2 bluescreens when loading windows after teardown

    Discussion in 'Alienware 17 and M17x' started by jackjm, Jul 10, 2013.

  1. jackjm

    jackjm Newbie

    Reputations:
    0
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    5
    Hi,

    I recently took apart my M17x R1 in order to clean and re-paste it. After I put it back together, whenever I boot from the hard drive, windows 7 will start to load, then a BSOD will appear for a second before the computer reboots. I've tried repairing windows by using the resource CD, but that hasn't made any progress. I was using a RAID 1 setup before this all happened.

    Has anyone run into this before? I'm at the point where I think I'm just going to format and reinstall everything, but if possible I'd like to be able to recover a few files (nothing critical that I'm freaking out about).

    Thanks
     
  2. TR2N

    TR2N Notebook Deity

    Reputations:
    301
    Messages:
    1,347
    Likes Received:
    255
    Trophy Points:
    101
    Looks like hardware fault. Focus closely on what parts were removed and then test.
    Good luck.
     
  3. Alienware-Luis_Pardo

    Alienware-Luis_Pardo Guest

    Reputations:
    1,141
    Messages:
    1,459
    Likes Received:
    8
    Trophy Points:
    56
  4. jackjm

    jackjm Newbie

    Reputations:
    0
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    5
    I can't see the stop error code because it literally blue screens for half a second before rebooting, just a flash of blue. I made some "progress" (although not forward), and it's looking more and more like a hard drive failure. Running chkdsk in the command prompt yielded tons of index errors that needed to be rewritten, and it kept getting interrupted. I'm just going to try to wipe everything tonight I think.