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.

    P35W v3 4K Monitor

    Discussion in 'Gigabyte and Aorus' started by fill0104, Apr 11, 2015.

  1. fill0104

    fill0104 Newbie

    Reputations:
    0
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    5
    Hello,

    when I am connecting the P35Wv3 with a Asus 4K Montitor (PB287Q) the Notebook can not boot. It is a blanksreen and I can´t see the gigabyte boot logo. It is with the DisplayPort and the HDMI Port. Both ports can´t boot. When I am connecting the Asus 4K Monitor after the windows boot it works. I have tested with different cables. Is this a Problem with the 4K Resolution on the bootscreen? Has anybody the same problem with a 4K monitor?

    Thanks

    Fill
     
  2. timgarbim

    timgarbim Notebook Enthusiast

    Reputations:
    0
    Messages:
    26
    Likes Received:
    2
    Trophy Points:
    6
    Hello

    I know theres a lot of problem with 4k monitors, like colors, chroma and these things.

    if one can boot and another cant, maybe its something with the monitor.
     
  3. zexel

    zexel Notebook Enthusiast

    Reputations:
    7
    Messages:
    20
    Likes Received:
    0
    Trophy Points:
    5
    By default, the video to the external video port, the secondary display, is not switched on until AFTER the operating system starts to load.

    You may have an option in the bios to switch the default output to external.
     
  4. Prostar Computer

    Prostar Computer Company Representative

    Reputations:
    1,257
    Messages:
    7,426
    Likes Received:
    1,016
    Trophy Points:
    331
    We had this issue on our Prostar/Clevo models until a more recent BIOS update addressed it. It's not very common and may even be subjective to the monitor or cable, but going off of experience, this may be something that can be addressed in a firmware update from Gigabyte.