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.

    help, clevo M860TU not booting!

    Discussion in 'Sager and Clevo' started by Damonkashu, Aug 14, 2011.

  1. Damonkashu

    Damonkashu Notebook Consultant

    Reputations:
    0
    Messages:
    101
    Likes Received:
    0
    Trophy Points:
    30
    I tried to upgrade my clevo m860TU to 8GB of RAM, but when I tried to boot up, nothing would happen. The power light goes on but the screen does not display anything. and it doesn't sound like the processor or hard disk are spinning.

    I tried putting the old 4GB of RAM back in and it didn't help anything! What should I do?
     
    Damonkashu, Aug 14, 2011
    #1
  2. Damonkashu

    Damonkashu Notebook Consultant

    Reputations:
    0
    Messages:
    101
    Likes Received:
    0
    Trophy Points:
    30
    I read in the manual the laptop will go through a POST routine to detect memory, does it normally take a long time to go through this?
     
    Damonkashu, Aug 14, 2011
    #2
  3. MrDJ

    MrDJ Notebook Nobel Laureate

    Reputations:
    2,594
    Messages:
    10,832
    Likes Received:
    363
    Trophy Points:
    501
    not sure if the user manual has been updated but it says max 4gb ram in mine.
    Two 204 Pin SO-DIMM Sockets Supporting DDRIII (DDR3) at 1066 MHz
    Supports Dual Channel DDRIII (DDR3) SDRAM
    64-bit Wide Per Data Channel
    Memory Expandable up to 4GB (1024/ 2048 MB DDRII Modules)
     
    MrDJ, Aug 15, 2011
    #3
  4. Kevin

    Kevin Egregious

    Reputations:
    3,289
    Messages:
    10,780
    Likes Received:
    1,782
    Trophy Points:
    581
    The few times this has happened to me, it was because the HDD or CPU wasn't fastened tightly.
     
    Kevin, Aug 15, 2011
    #4