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.

    Computer detecting generic non pnp monitor (that doesn't exist)

    Discussion in 'HP' started by chigurh, May 16, 2012.

  1. chigurh

    chigurh Newbie

    Reputations:
    0
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    5
    Hi everyone- Sorry in advance if this was addressed in a previous thread. The search function was not working for me.

    The problem started a long time ago. I had just got the computer in July of last year (2011) and after about two months it started flipping out and trying to adjust the screen to do 'dual display' with my monitor and another "ghost" monitor (as i like to call it). In other words, it thinks there is a second monitor when there is none. After a bunch of driver installs (plus BIOS) and recovering my windows, it stopped happening. That was about three months ago now...

    ... And just in the last couple weeks it has started up again. My computer will randomly decide to adjust the screen resolution to put me on dual display. I can change it to just display on monitor 1 (i.e. my only real monitor) while the second one is just black on the screen resolution page. When I restart the computer, it is gone. Until it decides to come haunt me again.

    As far as I can tell there is no rhyme or reason for it except that it seems to happen more when I am watching a video or playing a game (but I do both a lot so that could easily be coincidence).

    I have a Pavilion dv6-6135dx with dual graphics: AMD radeon HD 6750M and AMD radeon HD 6620G.

    I am moving to Korea tomorrow and I am kinda worried since this computer will be my lifeline in many ways. I think I will try and restore windows again, but if anyone else has any ideas please let me know!

    And yes, I did reinstall/update the graphics drivers and BIOS driver
     
    chigurh, May 16, 2012
    #1
  2. chigurh

    chigurh Newbie

    Reputations:
    0
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    5
    Sorry for the double thread post too.... :(
     
    chigurh, May 16, 2012
    #2
  3. DanaGoyette

    DanaGoyette Notebook Consultant

    Reputations:
    102
    Messages:
    226
    Likes Received:
    0
    Trophy Points:
    30
    Hmm, you try disabling that bogus monitor in Device Manager, perhaps?
     
    DanaGoyette, May 16, 2012
    #3
  4. namaiki

    namaiki "basically rocks" Super Moderator

    Reputations:
    3,905
    Messages:
    6,116
    Likes Received:
    89
    Trophy Points:
    216
    Did the issue happen when you were using the original graphics drivers that the laptop came with?
     
    namaiki, May 16, 2012
    #4
  5. chigurh

    chigurh Newbie

    Reputations:
    0
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    5
    Dana- Yes. I actually uninstalled it. It was still there in the "screen resolution" page. When I restarted, as usual, it was gone. Hasn't happened again.... yet.

    Nama- I had the computer for a little while before it started happening, so I am sure it had updated the drivers by then.
     
    chigurh, May 16, 2012
    #5
  6. DanaGoyette

    DanaGoyette Notebook Consultant

    Reputations:
    102
    Messages:
    226
    Likes Received:
    0
    Trophy Points:
    30
    Actually, if it comes back, disabling it will likely be better. When you uninstall something, it can come back; if you disable it, it'll probably stay disabled.
     
    DanaGoyette, May 16, 2012
    #6
  7. chigurh

    chigurh Newbie

    Reputations:
    0
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    5
    Hmm okay I will try that.

    I was hoping this was a more common problem.
     
    chigurh, May 17, 2012
    #7