Monday, May 26, 2014

Generic Non PNP Monitor problem with Windows 7


If you do enough Windows 7 installs with older hardware, you will run into this problem eventually.  My latest encounter with this error happened when installing an HP vp17 Monitor on a newer Dell Windows 7 Pro machine.  The system would see the HP as a Generic Non PNP monitor.  When it does this, there are only two or three video resolutions available.  Sometimes the environment that you are installing in requires a display resolution that is not one of the few listed.  In my case, I needed a resolution of 1024x768 for a custom full screen application.  You may need something different, but the concept is the same.

So what's going on here?  Put simply, the monitor is not able to tell the PC what it is.  My HP couldn't or wouldn't communicate it's model information to Windows. This could be caused by cable issues, drivers, or actual monitor issues.

The first step is to look for and replace or bypass any sort of extension cable or older monitor cable.  80% of the time (especially is you are working will well seasoned equipment) it will be an older cable issue because not all the required pins are connected.  Testing this may involve actually moving the monitor closer to the PC so it can be direct cabled if at all possible (eliminate the suspects).

If that does not work, then updating the drives seems to be suggested (FYI: This has never worked for me).  While you are at it, update Windows to the newest and latest service packs that your environment will handle.

If there is still no joy, as with my HP, then you may be forced to replace the monitor.  Luckily the site that I was on had a few other monitors used for other purposes, so a swap was rather simple.

So, if you get the error:
1- Replace the cable, do a shortened cable test.
2- Update Windows as far as you can
3- Load new drivers for the monitor and video controller.
4- Replace the monitor.

I may never know whether there was an issue with the HP monitor, or if there is some complex workaround to make it work.  I did a few searches and found others with the same issue, and the threads either died unresolved, or ended with the questionable monitor being replaced.  As a technician, you can't spend too much time chasing issues like this before you simply have to come up with a way to make something work.  If there were no monitors on site, I would have been forced to use a FRU (Field Replaceable Unit), or talk to them about purchasing a newer monitor.

Good Luck!
Shawn

No comments:

Find an article