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.

    CLevo-170sm hdmi problem

    Discussion in 'Sager and Clevo' started by Grump, Dec 22, 2016.

  1. Grump

    Grump Notebook Consultant

    Reputations:
    0
    Messages:
    261
    Likes Received:
    4
    Trophy Points:
    31
    Computer: CLevo-170sm chassis, Sager NP8278-S

    i7-4810mq 2.80gHZ, 16GB
    Geforce 870M 6GB

    windows 10 64bit

    I'm having increasing problems with running dual monitors from my
    sager. The external monitor is connected through HDMI and will sometimes
    cut out for a few seconds then come back on. Once in awhile, the monitor will
    turn off completely and the system will kick me back to the windows boot screen
    for some reason and the external monitor will not work until restarted.
    Whenever this second thing has happened I was watching Youtube vids. I don't know if that
    is just a srange coincidence. Its slowly been getting more severe. On one recent occassion the laptop
    completely failed to recognize different monitors from the HDMI port even when it restarted
    and I thought it was completely gone until after about a day it suddenly recognized an external
    monitor again for some reason.

    When looking through the event viewer there is no obvious event associated before or during the times
    when the monitor cuts out.

    The closest I could find is an error slightly after the time the monitor fails which is listed as

    Faulting application name: HkeyTray.exe, version: 1.0.0.15, time stamp: 0x52fb3b4d
    Faulting module name: brightness.dll, version: 1.0.0.1, time stamp: 0x50aa6e98
    Exception code: 0xc0000005
    Fault offset: 0x00001905
    Faulting process id: 0x1bc4
    Faulting application start time: 0x01d25c10889dbcf3
    Faulting application path: C:\Program Files (x86)\Hotkey\HkeyTray.exe
    Faulting module path: C:\Program Files (x86)\Hotkey\brightness.dll
    Report Id: ff136aa9-f618-452d-96a4-4b13ce62b9d3
    Faulting package full name:
    Faulting package-relative application ID:

    I've updated the drivers for both the discrete card and the integrated graphics. But it
    doesn't seem to have stopped whatever issue it is. What could be wrong?
     
  2. Prostar Computer

    Prostar Computer Company Representative

    Reputations:
    1,257
    Messages:
    7,426
    Likes Received:
    1,016
    Trophy Points:
    331
    Can you reinstall the chipset driver? Do you see any fluctuation in video output if you move the cable around (near the port and at various points along the cable)?
     
  3. Support.1@XOTIC PC

    Support.1@XOTIC PC Company Representative

    Reputations:
    203
    Messages:
    4,355
    Likes Received:
    1,099
    Trophy Points:
    231
    Have you tried using a different cable to the monitor, or moving around as mentioned? If there is some tiny break internally that could cause issues.
     
  4. Grump

    Grump Notebook Consultant

    Reputations:
    0
    Messages:
    261
    Likes Received:
    4
    Trophy Points:
    31

    When the laptop quit working with the hdmi for a day it didn't respond to switching out cables. I'll try updating the chipset driver.

    Where is the chipset driver for this laptop? I can only find a w8 version.
     
  5. Prostar Computer

    Prostar Computer Company Representative

    Reputations:
    1,257
    Messages:
    7,426
    Likes Received:
    1,016
    Trophy Points:
    331
    Windows 8.1 was the latest supported OS that Clevo published the driver for, but it might still work on Windows 10.

    http://www.clevo.com/en/e-services/download/ftpOut.asp?Lmodel=P1xxSM&ltype=7&submit=+GO+

    It could be a problem with the port, but hopefully not.