Table of Contents.PretextThis article provides guidance for users with discrete desktop GPUs from Nvidia and AMD. For mobile GPUs or integrated graphics solutions, including those from Intel, it is recommended that a custom resolution is set using CRU (Custom Resolution Utility). Refer to the Nvidia section on this, specifically the second half of “Second solution: setting a custom resolution” where the process of using CRU is mentioned.IntroductionYou may have heard people say that the image quality of HDMI (High-Definition Multimedia Interface), DP (Display Port) and the now outdated DVI (Digital Visual Interface) are equivalent. They’re digital signals that either ‘work’ so the monitor displays an image or ‘don’t work’ so that it doesn’t. A user just has to consider the bandwidth requirements of their monitor and choose a port on the GPU (Graphics Processing Unit) and monitor that will support the full resolution and refresh rate of their display.Unfortunately things aren’t quite as clear-cut as that, and there is a murky middle ground.

1. Dual Driver In Ear Monitors
2. Second Monitor Not Detected
3. Dual Monitor Drivers Hp

It’s this quagmire in the middle that many users will find themselves stuck in due to how HDMI is typically handled by PC graphics cards. HDMI is designed as a universal signal widely used by TVs and entertainment systems, unlike DVI and DisplayPort which are built from the ground up as computer monitor ports. The aim of this article is not to bog you down with all of the technical fripperies of these different ports and associated aspects. Rather it’s designed to give you some straightforward actionable advice which will allow you to optimise the HDMI colour signal for PC use.How Nvidia GPUs handle the HDMI signal The problemWhenever a monitor with a resolution in common with HDTVs (e.g. 1920 x 1080) is connected to an Nvidia GPU by HDMI or DVI-HDMI cable, the GPU tends to treat the screen as an ‘HDTV’ rather than a monitor. You can see how the graphics driver categorises things for the Full HD resolution as that shared with a TV by opening the Nvidia Control Panel and navigating to ‘Display’ – ‘Change resolution’. It will usually be listed under ‘Ultra HD, HD, SD’ as ‘1080p, 1920 x 1080 (native)’ as shown below.Although this behaviour is typical for 1920 x 1080 (Full HD/1080p) displays connected by HDMI it occasionally applies to such displays connected by DisplayPort as well.

In the image above you may notice that a, connected via DisplayPort, has been categorised in this way. This is rather bizarre behaviour considering DisplayPort is a PC-only connection not currently employed by TV screens. If you connect a monitor up using DVI or a DisplayPort connection that works as it should then the resolution will be listed in a separate list entitled ‘PC’ as shown in the image below.But the problem is not simply that the resolution is put on the wrong list, it’s the effect that this has on the colour signal that is important. With the HDMI (or incorrect DisplayPort) connection the GPU sends out a ‘Limited Range RGB 16-235’ colour signal rather than the ‘Full Range RGB 0-255’ signal the monitor is designed to process and indeed sends out via DVI or correctly functioning DisplayPort. Without going into the intricacies of how these colour signals differ, there is a definite mismatch between the colour signal sent to the monitor and the screens native capabilities. This disparity leaves the monitor unable to display shades with an appropriate depth and variety.

Black appears an obvious dark grey (overall static contrast suffers – this is measureable) and the gamma curve is shifted such that many shades appear a lot lighter than they should. The whole image looks like it has a sort of bleached haze over it, giving what is commonly referred to as a ‘washed out look’. Confusingly, we’ve also observed the GPU defaulting to the ‘Limited Range RGB 16-235’ signal when connected to ‘4K’ UHD (3840 x 2160) screens – even though the resolution is listed under ‘PC’ as ‘3840 x 2160 (Native)’.The table below gives some basic readings taken from the connected by HDMI and set to use both a ‘Limited Range RGB 16-235’ signal and a ‘Full Range RGB 0-255’ signal.

Results for a third signal type discussed below, ‘YCbCr444’, are also included. The ‘Test Settings’ and equipment from the review were used to take these readings – a Spyder4Elite for the gamma and white point measurement and a Konica Minolta CS-200 for the rest. The ‘Test Settings’ simply involved lowering the brightness a bit and making minor colour channel adjustments.

Nvidia signal tableNvidia solutions First solution: functionality now built into the Nvidia display driverAs of driver version 347.09, Nvidia have added a small drop-down to the Nvidia Control Panel (NCP) that will allow you to enforce the correct ‘Full Range’ signal. Simply open NCP and navigate to ‘Display – Change resolution’. You should see a drop down box labelled ‘Output dynamic range’.

At time of writing this is the final drop-down box on the page, under ‘Apply the following settings’ as shown below.Make sure this is set to ‘Full’ rather than ‘Limited’ and press ‘Apply’ to enforce the ‘Full Range RGB 0-255’ signal. Note that this will be set to ‘Limited’ by default on Full HD monitors connected using HDMI and some connected using DisplayPort.

On some monitors you will need to turn the monitor off then on again (using the power button is fine) after setting this correctly in Nvidia Control Panel. It is always available as a toggle when connecting a Full HD monitor using HDMI or DP, but depending on the display and its resolution may be set to ‘Full’ by default or the option may not even be selectable – in these cases it doesn’t need changing. Also be aware that the location and exact labelling may change in future driver versions. If the monitor has an ‘HDMI Black Level’, ‘HDMI RGB PC Range’ or similar option make sure this is set to ‘Normal’, ‘High’, ‘Full’ or ‘RGB (0255)’ rather than ‘Low’, ‘Limited’ or ‘RGB (16235). The exact nomenclature depends on the monitor model.Second solution: setting a custom resolutionIt is possible to enforce a ‘Full Range RGB 0-255’ signal over HDMI or incorrectly functioning DisplayPort by setting a custom resolution.

This resolution can be set such that it is treated exactly the same as the default 60Hz native resolution of the monitor but with the colour signal corrected. The video below shows this process. Again ensure that the ‘HDMI Black Level’ or similar option on the monitor is set correctly, if such an option exists.After creating it, you can see your new ‘Custom Resolution’ listed separately in the Nvidia Control Panel resolution list as shown below.Although this will work with most applications and the desktop, some games ignore custom resolutions and will revert to using your monitor’s native resolution with the default colour signal.

On many such games your custom resolution will be used if you set the refresh rate to a value other 60Hz (essentially or underclocking your monitor). Most monitors will be able to use 65Hz without any issues, some can be pushed further if you’re feeling adventurous. Some users would be uncomfortable changing this from the default 60Hz, which we understand, so for those looking for a simple ‘universal’ fix there are some alternatives.One alternative to setting a custom resolution in the Nvidia Control Panel is to use the ‘’ created by ‘ToastyX’.

Full instructions on how to use this are included in the first post on the thread linked to. Simply run this utility (CRU.exe) and click the ‘Add’ button under ‘Detailed resolutions (4 maximum’) as shown in the image below.This brings up a ‘Detailed Resolution’ configuration box shown to the right in the image above. Select ‘Automatic – LCD standard’ in the ‘Timing’ dropdown and enter the resolution and refresh rate as shown in the image. One key feature of CRU is that after adding a ‘Detailed resolution’ you can move a resolution up to the top of the list so that is treated as the native resolution. You do this by clicking on the resolution you just created and using the little up arrow button to the right of the ‘Reset’ button. This is important because those games that like to ignore Nvidia’s custom resolutions will still use the new native resolution that you set using this utility.

Users of Windows 8.1 or newer should also uncheck the ‘Include extension block’ checkbox which is above and to the right of the ‘OK’ button. Remember to press OK and restart your computer to activate your new resolution.Note that CRU can also be used to monitors connected to both Nvidia and AMD GPUs by setting a higher than native refresh rate, and that is indeed one of its key original purposes. Some users will find that functionality useful, but that’s not necessary to correct the colour signal.

Another good thing about CRU is that it offers a reliable method to correct the colour signal of Nvidia’s mobile GPUs. Because the graphics driver of mobile GPUs is massively cut down you aren’t able to set a custom resolution using Nvidia Control Panel.

For users with Nvidia’s desktop GPUs there are a few alternatives to creating custom resolutions which can be used to correct the signal.Third solution: using the YCbCr444 colour signalIt is very easy to get rid of that ‘washed out’ look and the problematic gamma by setting the graphics card to use the YCbCr444 colour format. Simply open the Nvidia Control Panel and navigate to ‘Display’ – ‘Adjust desktop color settings’. Select ‘YCbCr444’ from the ‘Digital color format’ dropdown as shown below. The ‘Black Level’ option on the monitor, if there is one, should be greyed out after selecting this colour signal type.This will switch the colour signal the graphics card sends out from RGB (‘Limited Range RGB 16-235’ by default) to an alternative which provides a very similar image to ‘Full Range RGB 0-255’ on most monitors.

The measured gamma, white point and contrast are very similar indeed and the image looks very much comparable to a ‘Full Range RGB’ signal on most monitors. Some colour values are changed very slightly, with certain shades displayed more accurately and some less accurately. The images below compare the colour accuracy of the across a broad range of shades using both ‘Full Range RGB (0-255)’, shown on the left and ‘YCbCr444’, shown on the right. These tests were repeated several times and the slight differences were consistent for one signal type vs. The other – so it isn’t just the colorimeter being weird.

Different monitors will of course show different deviations in accuracy, but both colour signals should generally be just as close to each other as in this example. On a minority of monitors the changes can be more pronounced, for example the clarity of text can be affected with a blurred or ‘fringed’ look in places. If you notice such undesirable consequences on your monitor we’d advise using one of the other methods to correct the signal.As you can see there some slight differences here and there but nothing of huge significance.

After selecting the ‘YCbCr444’ colour signal the resolutions will be listed in exactly the same way by the driver, so will remain in the ‘Ultra HD, HD, SD’ list if that’s where they were before. Because the ‘Full Range RGB (0-255)’ signal is used for DVI and most DisplayPort connections you may prefer to enforce this instead of using ‘YCbCr444’, just so you know things are being done ‘the right way’. Our preferred method of enforcing the correct ‘Full Range RGB’ signal over HDMI is to use a nifty little tool mentioned below.Fourth solution: using a third-party tool to enforce Full Range RGBThis solution has now been superceded by the selectable option now added to the Nvidia Control Panel (‘First solution’). For those who want to experiment with an alternative, for whatever reason, there is a small utility called ‘’ which originates from the ‘metaclasofnil’ programming blog. You simply run the executable (.exe) contained in the.zip file and click on ‘Set Full Range (0-255)’ button at the top right as shown below.All this does is changes a few registry entries for the graphics driver which control the RGB colour signal behaviour for HDMI so that ‘Full Range’ rather than ‘Limited Range’ is used. This will not correct the ‘dodgy DisplayPort’ signal.

Once you restart your computer the changes will take effect immediately. You only have to run this tool once, unless you clean install a new graphics driver which will reset all of the registry entries to default again.

As with setting a custom resolution you should ensure any ‘Black Level’ or ‘HDMI Range’ setting on the monitor, if there is one, is set appropriately. This will be using the ‘Normal’, ‘High’, ‘Full’ or ‘RGB (0255)’ setting rather than ‘Low’, ‘Limited’, RGB (16235) or other words to the same effect.The resolution will again be listed as it was before in the Nvidia Control Panel, so you won’t notice a change there. If you’re interested in seeing the difference between ‘Full Range RGB (0-255)’ and ‘YCbCr444’ for yourself then feel free to toggle between ‘RGB’ and ‘YCbCr444’ in the graphics driver (second solution) after employing the toggle tool (third solution).

You can then quickly switch between the two. Because your computer has to restart after correcting the colour signal using the toggle tool you may be unsure whether it has definitely made a difference.

You should see things look much less washed out, but are your eyes just playing tricks on you?Regardless of the technique you use to correct the colour signal, perhaps the easiest way to see the difference is to observe the. Use a browser other than Firefox as Mozilla’s colour management can throw things off here.

Before correcting the signal you should notice that all of the squares are distinct from the background with little individuality in the shades of the first few blocks. The relatively low gamma and inability of the monitor to display distinctions below a grey level of 16 will have this effect. After correcting the colour signal the first few blocks should blend in with the background better and offer more distinction between themselves and neighbouring shades.

The background will appear darker (a grey level of ‘0’ rather than ‘16’) as well.How AMD GPUs handle the HDMI signal The initial problem – scaling (a simple fix)The first and probably most pressing issue you may face when connecting an AMD GPU to a Full HD monitor using HDMI or DVI to HDMI is one of scaling. At least if you’re using an older driver, the image will likely appear compressed and fuzzy with a black border surrounding it. That is because the GPU’s default behaviour, in older drivers at least, is to ‘underscan’ the image. For newer drivers this issue shouldn’t occur, but if you do notice this issue you should find the appropriate slider (mentioned below) in ‘AMD Radeon Settings’ – ‘Display’. To fix this for older drivers, you simply need to Open Catalyst Control Center. Once you’ve got that open navigate to ‘My Digital Flat Panels’ – ‘Scaling Options’ and move the slider to ‘Overscan (0%)’ or all the way to the right as shown in the image below.The other problem – pixel formatFor AMD GPU users DisplayPort connections should always use the correct colour signal by default.

And unlike when connecting a monitor to an Nvidia GPU using HDMI, connecting an AMD GPU via HDMI is a lot less problematic when it comes to the colour signal. The image is not washed out and it looks very much as it should on most monitors. When using HDMI, the default behaviour of AMD GPUs is not to use a ‘Limited Range RGB (16-235)’ signal like Nvidia GPUs, but rather to use a ‘YCbCr 444’ signal which is referred to by AMD as ‘YCbCr 4:4:4’. The use of ‘YCbCr 4:4:4’ compared to ‘Full Range RGB (0-255)’ has a slightly more pronounced effect on white point, contrast and measured colour values compared with on an Nvidia GPU.

It is still nowhere near as pronounced as comparing Nvidia’s default ‘Limited Range’ signal to any other signal type, however. The table below compares some key values on an AMD GPU connected to the AOC i2473Pwy, with the GPU using both ‘YCbCr 4:4:4’ and ‘Full Range RGB 0-255’.

The term ‘RGB 4:4:4’ is used in the table as this is AMD’s preferred terminology for the ‘Full Range RGB’ signal. Again the same ‘Test Settings’ and measuring equipment from our review was used with an AMD Radeon R270X GPU in place of the Nvidia GeForce GTX 780.

AMD signal tableThe differences in these key readings are not exactly huge, most notable is the slight boost in contrast you gain by enabling the ‘RGB 4:4:4’ signal. The black luminance remains the same whilst the white luminance is raised by 5 cd/m2 to give a contrast ratio of 1238:1 compared to 1184:1. This is hardly a massive difference on this particular monitor but any bonus is a good thing. The images below compare the colour values of ‘YCbCr 4:4:4’ (left) and ‘RGB 4:4:4’ (right). Again we took these measurements several times and the results were consistent.You can see that there is greater deviation in colour accuracy between the two signals than there was on the Nvidia GPU. This is true for deep red and certain grey and pastel shades in particular, amongst others.

There is little need to critically analyse the accuracy of specific colour values for one signal type vs. The other as this varies between monitors.

The take home message here is simply that ‘YCbCr 4:4:4’ and ‘RGB 4:4:4’ (‘Full Range RGB, 0-255’) do differ in their shade representation on AMD GPUs to a greater extent than Nvidia GPUs.Unlike Nvidia’s ‘Limited Range RGB (16-235)’ signal AMD’s default ‘YCbCr 4:4:4’ signal never causes things to look washed out by dramatically altering gamma or contrast. But it does slightly affect colour values so some shades are presented slightly differently to how they would over a DVI or DisplayPort connection (i.e. And as with Nvidia cards, this signal type can cause a minority of monitors to display blurred or ‘fringed’ text where certain colours are involved. Most users will probably be quite happy to stick with this default signal, but it is actually very simple to change the signal used using one of two methods.AMD solutions First solution: use a DVI to HDMI cableIn contrast to Nvidia GPUs, connecting an AMD GPU up using a DVI to HDMI cable causes it to use the colour signal it would usually use for DVI; ‘Full RGB’. If you have such a cable handy or are happy to buy one (perhaps if you don’t have a regular HDMI cable handy) then this is one solution. If you only have an HDMI cable or would prefer to use one then don’t fret.

It is very easy to enforce the ‘Full Range’ signal over HDMI in Catalyst Control Centre (CCC) as demonstrated by the following solution. You have to fix the ‘scaling’ issue in CCC anyway, whether using a DVI to HDMI or regular HDMI cable, so having to tweak something else in CCC shouldn’t cause too much hardship.Whether using a DVI to HDMI cable or changing the pixel format (below) you will need to ensure any ‘Black Level’ or ‘HDMI Range’ setting on the monitor, if such a setting exists, is set correctly. Make sure you’re using the ‘Normal’, ‘High’, ‘Full’ or ‘RGB (0255)’ setting on the monitor rather than ‘Low’, ‘Limited’, RGB (16235) or other words to that effect.Second solution: change the pixel formatTo fix this in older drivers, simply open Catalyst Control Centre. After doing this, navigate to ‘My Digital Flat-Panels’ – ‘Pixel Format’ and change this from the default of ‘YCbCr 4:4:4 Pixel Format’ to ‘RGB 4:4:4 Pixel Format PC Standard (Full RGB)’ as shown below. This is the ‘Full Range RGB 0-255’ option for AMD users. The first image below is taken from Catalyst Control Centre, which the earlier drivers used. Newer drivers have replaced Catalyst Control Centre with AMD Radeon Settings.

Open this and click on ‘Display’ – the ‘Pixel Format’ can be changed to ‘RGB 4:4:4 Pixel Format PC Standard (Full RGB)’ as shown in the second image.You will only have to change this option once, unless you clean install a new graphics driver. As noted above you should also make sure the ‘HDMI Black Level’ or similar setting on the monitor is set correctly as well. If you’d like to put yourself in the shoes of an Nvidia user with their default ‘Limited Range RGB (16-235)’ signal then select the ‘RGB 4:4:4 Pixel Format Studio (Limited RGB)’ pixel format. Just remember to change it back afterwards, not that you’ll forget given the fairly significant degradation in contrast and colour quality that you’ll notice.ConclusionMany monitors have moved on from using DVI (which is handled perfectly in both Nvidia and AMD drivers) to using HDMI and DisplayPort.

This is a trend that is set to continue as these two new standards continue to evolve – indeed we’re now on HDMI 2.0 whilst DP 3.0 is on the horizon. Despite this, both AMD and Nvidia GPUs treat Full HD monitors connected by HDMI as ‘HDTVs’ and send out a colour signal that even many modern TVs are moving away from. AMD GPUs have a pesky scaling issue when using HDMI, but this is quite easy to fix universally in the driver once you know how.

Despite their issues seeming to be isolated to the 1920 x 1080 (Full HD) resolution at present rather than any resolution, Nvidia GPUs are worse offenders for users with affected monitors. They use a ‘Limited Range RGB (16-235)’ colour signal by default that completely destroys the image quality of the monitor by hampering contrast, colour vibrancy and shade variety.

To add insult to injury a minority of monitors act this way over DisplayPort as well, despite that being dominantly a PC connection where the GPU treating the monitor as a TV makes little sense.As this article demonstrates it is fairly simple to fix any issues with colour signal that you may come across using HDMI (or ‘dodgy DisplayPort’) and indeed fix AMD’s odd ‘scaling’ issue. But there are many users who will never read this article and don’t know how to fix these issues – cursing away at their monitor and perhaps sending it back to the retailer instead. Still, there is some potential light at the end of the tunnel. As the push continues towards higher resolution, with ‘4K’ UHD (Ultra High Definition) and higher resolutions hitting the mainstream market, the ‘Full HD HDMI curse’ will be weakened. We’re also happy to see that since this article was first published, Nvidia have added that drop-down ‘Dynamic range’ option to the driver.We’d of course like to see the GPU drivers of both manufacturers ‘get with the times’, accepting that things have moved on from HDMI being a TV-only connection.

Indeed many TVs now happily support a ‘Full Range’ RGB signal anyway, so it would make more sense for the GPU to treat a connected display as a monitor rather than TV. And there is really no need for AMD to choose to ‘underscan’ the image by default over HDMI, either, since this is a problem not just on modern monitors but also modern TVs. Even if things aren’t changed by default driver-side, this article will at least provide some solutions for the poor users facing these pesky issues.

How I fixed the Windows 10 'second monitor cannot be detected' problem on my computer.I have a relatively new Lenovo PC with Windows 8.1. I loaded the new free Windows 10. ('Free' = 'Beta version, you have been warned.' ) During loading Windows 10 my primary screen suddenly developed white noise everywhere instead of an image. I ended up having to turn off the computer and restart it.

It had white noise again, I turned it off and on again, and the second time the display came up on the primary computer. However, the additional display could not be detected.I tried reloading Windows 10, thinking there must be a problem, but I had the whole white noise problem over again, turning off and on, completing two novels and a trip to the bathroom while I waited. Turned out that Windows 10 had indeed loaded.After messing around with this for an hour and a half and reading lots of helpful tips from frustrated MS users, I did find a solution on my computer.

Go to control panel, device manager, display adapter. There is a driver showing and it indicated a problem (small yellow triangle next to the name of the driver). At another help site, it was suggested to right click and 'roll back' the driver.

I right clicked on the driver. The 'Roll Back' option was grayed out. But 'Update' was available. After a few minutes of updating the primary screen switched to white noise again. I turned off the computer and turned it back on and Voila! Both monitors were detected and operating just as they had been with Windows 8.For those who have not used additional displays before, to avoid merely duplicating the display on both screens, go to Control Panel, Display, Adjust resolution.

It should show two monitors, #1 and #2. At the 'multiple displays' click the dropdown and select 'Extend these displays.'

Note also that you can choose which display is the 'main display' (where your program icons and system tray show). Also, you can drag the two images of monitors to put one to the left of the other. That helps so that the cursor flows smoothly side to side between the monitors without having to slide off to the right of one to enter at the left of the other.Glad to help if this was helpful.TonyJ.

Brand new Surface pro 4, windows 10, dual monitor works very intermittently. First boot, surface display and the 2nd screen connected through a display port to VGA adapter works fine.

I have windows configured to turn off the displays after x number of minutes of inactivity, and about half of the time, the 2nd screen does not come back. I can reboot, and again, about half of the time the 2nd screen comes back. Additionally, if I unplug the screen, mini display port adapter, then plug it back in again, it may come back. I've searched around, and found reports of the same issue, but no solution. Anyone encountered this and found a fix? Seems windows 10 related.Edit.

one of the fixes I found suggested running something like DisplayFusion or UltraMon to manage the monitors. Which, of course does not seem to completely fix the issue. DisplayFusion is current, Windows10 is currenty, Surface drivers are current. Hi Keith,The resolution is grayed out. When I click 'Detect', nothing happens.

When I click 'Identify', it only shows the number 1 on my laptop. Basically, it isn't detecting the second monitor at all.And the way it's hooked up, through an HDMI cable, is the exact same way I've done it for years with the old Windows.

How come Windows 10 doesn't recognize my second screen (tv)? And what do I do to fix this? Completely insane that this isn't working. It's basic stuff like this that doesn't work on Windows which makes people switch to Macs.

The ease of use and system functionality seems much smoother on Macs. Anyway, I'm stuck with Windows so any help would be greatly appreciated.Thanks,Joe. Ok, here's what I got AMD Phenom II X6 1100T Processor 3.30GHz, 16GB RAM, Win10 Pro 64bit, XFX Radeon R7 260X, Compaq Q2009 Series Wide LCD Monitor and a Niko Monitor. The Compaq is VGA that I use a DVI adaptor.

I got the from the site.For Win10 I got the free upgrade and did a clean install.Like many of the other posts, only 1 monitor is detected. I tried rolling back the driver, I tried windows updating the driver, i tried the AMD site driver, I tried uninstalling the AMD driver and windows driver and re-installing the AMD driver.During boot up, both monitors show the bios, they even both show the windows loading swirl. Right before it gets to the windows log in screen, one monitor goes blank and says no signal. After work tomorrow i'll try switching which plug each monitor goes in and one at a time in each plug. But because they both show the bios, i don't think it's a plug issue.Any tips I should try would be helpful, i already tried everything else I've seen on this thread. I have a similar problem, although it's not a big deal. I think it's a Windows 10 issue.

Running 2 monitors off a video card on a desktop. Maybe 70% of the time on a reboot, only the main monitor displays anything. My workaround is to open display settings where everything looks like it should. (as though the second monitor was working properly, it isn't, just a black screen) I change to 'show only on 1' Accept and keep. Then immediately change it right back to 'extend'. Accept and keep and both displays show the way I want.Sometimes a reboot works properly, but more often than not, these couple of steps need to be done. Hope this helps if someone has a similar problem.

Bit of a pain, but it's quick and easy until a fix comes along.:). Ive been looking everywhere for help and cant seem to find a fix.My second monitor is only being recognized when it is turned off, soon as i power it on my computer doesnt recognize it anymore.ive read its a possoble windows ten issue.build info incase that helps someone figure my issue easieri7 6700kMSI z170a MBEVGA GTX 970 FTW edition.any help is greatly appreciated.also the monitor im hooking it into is to my DVI port. I dont have a display port cable to test if it works with that yet or i would. I'm having a similar problem. I initially got a vga splitter and it was working, but it just mirrored the same stuff on both screens - it didn't extend. I must've messed up something in my settings because now when I plug in a monitor via VGA and a second monitor via HDMI it shows a blank desktop with programs lit up in my taskbar. I have two different home screens on each monitor and when I use the mouse, it will extend to both screens the way I wanted it to originally.

However, when I click the tabs in the task bar to open the program, nothing happens. I cannot open any programs. All I can see is two different backdrops on each screen, with the mouse extending to either screen, but no icons on either of them.If I try to operate by plugging my monitor directly into the VGA port, it will not work.

It is just a black screen. It will only work if I use a vga splitter. Right now I'm currently operating by using one monitor plugged into one of the vga splits. Does this make sense? Essentially it works but not the way it is supposed to.

How can I correct these settings? I have an Lenovo Ideapad P400 and was going to connect two monitors and the second one is not recognized. Each my themselves no issue.

HOwever, one is connected DVI to HDMI and the other one traditionally VGA. Never had issues before, but then again I have always used a port replicator. Not on this one. Is it not possible to have two external monitors connected to the laptop like this? When choosing detecting the laptop display is always 1, even when the lid is closed. Any ideas please?Best,M. Hi, seem to have a similar problem hereI use lenoovo z500, geforece gt 740m, win 10 with a pilot 2nd screen.this first happened to me after upgrading to win 10.

The pilot screen just suddenly not recognized and only gave me the no signal message.i cannot remember how but i managed to find a solution online and fix it. I remember i had to do something in control panaldevice manager and i think it was a problem with the driver.now, a few months later i suddenly had a problem with the laptop's original screen-it was stuck dim. The solusion for this was to update the 'generic pnp monitor' driver under 'monitors'once this update was completed the dim problem was fixed but now the pilot screen is again not recognized. What should i do???tried updating the geforce driveri'd appreciate a copy of your reply tothanks!!!

After reading through everything I was wondering if someone would be able to tell me if my issue is with my laptop or it's simply the hdmi cable I have.I have my laptop plugged into my tv with a hdmi cable so I can watch tv on on a bigger screen with better sound. I have windows 10 but I've had that for months, way before I started using the cable, so unlike what a lot of people are saying in this thread it's not an update issue. The issue now is that whilst my second screen/tv is receiving a signal, or at least something, from the cable (because its black not blue) there's no actual display or sound coming from it.

It's been working fine for months and only having a glitch and losing signal if I moved the wire by accident.If the wire is damaged, is it possible its only slightly damaged? Which would explain why it's taunting me with a black screen and nothing more. My LENOVO Laptop operates using Windows 10.

I purchased an HDMI cable couple of months ago to enable me to watch movies on my television (Samsung). For the past few months everything was running fine UNTIL I recently watched a movie using a DIFFERENT Website.

As a result, I now CANNOT project any movies or computer displays on the television screen BUT laptop display is OK.BEFORE: Advance Display Settings - Multiple Display - Duplicate these displays. This will display 1 + 2.NOW: Advance Display Settings - Multiple Display - Duplicate these displays.

NOW displays 1/2.Seek you assistance. Hello, my laptop which is a DELL is facing the same problems as my lenovo. The DELL laptop is using Windows 8 while the lenovo is using Windows 10. Previously i was able to duplicate the display from my laptop to the TV screen using a HDMI cable (both laptops could do it).

But now it won't duplicate anymore because apparently there's 'no signal' even though the tv detected it. As can be seen from the attachments, I believe that both screens should be labelled as '1' and '2' but now it says '1/2'.

Is this the problem? And if so, how do i rectify it?please help me! @BreedlyI am in exactly the same position mate. One of my computers has got two monitors plugged into it. Sometimes I can switch the computer on and both monitors will come on with extended display, However, today it took about four reboots and then shut down and starts before the second monitor came on.On another note, the computer I am on at the moment uses Windows 7. I have two monitors plugged into it and there's never been a single case where the second monitor has not come on when I put the computer on. I solved my specific problem after a day of troubleshooting.Essentially, the HDMI output to my second monitor connects to the motherboard of my PC.

The VGA connection of my main (working) monitor connects to the GPU. There is also a VGA port on the motherboard so I switched the working monitor to that and it didn't work. I therefore wondered if updating GPU drivers didn't actually affect those connections and I actually needed to update the graphics rendering inbuilt into the CPU. I looked in Device Manager to update the drivers for the on board GPU and it wasn't listed under Display Adaptors.

I then booted into UEFI (BIOS) and checked the video adaptor settings.It was set to AUTO, which means that it prioritises the graphics card over the inbuilt graphics. I changed it to 'IGE' so it prioritises the inbuilt graphics. I had to reboot twice, but after that my second monitor came up! That was the damnedest thing! I was doing everything I could think of to try to get it to recognize my second monitor and nothing was working. It had been displaying the same screen on both monitors but every time I clicked 'Detect' it told me that it couldn't detect a second monitor.Then while I was reading the discussion in this forum, the screens went black for a few seconds and came back on having automatically switched to an Extended display, now recognizing both monitors.

I think that Windows 10 was just doing some behind the scenes downloads to set this up for me without letting me know it was working on it. (The computer was making a lot of clicks, as if it was setting something up).So maybe I just need to leave the new computer alone for a while as it talks to the internet and gets all the drivers it thinks it needs without telling me what it's up to.:. Good Evening,I need some assistance. I have purchased a Lenova desktop PC with a NVIDIA quadro graphics card installed.

I am trying to use a Hannspree monitor and either a LG or Dell monitor along side it.My issue is the second monitor (LG/Dell) isn't being detected by Windows 10. I have looked into the BIOS and changed settings in there but all I have managed to achieve is to make the second monitor come alive and the first monitor go off!!They are connected via VGA & DVI.

The DVI is connected to the graphics card and the VGA is connected to the onboard card.Any suggestions/help would be greatly appreciated.Thank you. Happy new year! I have a lenovo with intel hd graphics family. At first it would have one screen with 1/2 on it.

Then I updated drivers for the intel, now the intel identifies the second screen, but when i go to 'detect', didn't detect another another display. Trying to stay vga (ya i know old school) but for use that's what's available right now where i'd be trying to go dual display. Is there a specific driver needing updated for the vga port? Or another driver i need to update? I ran windows update and everything is up to date. Ran somethings individually, up to date.

By the way, I got this lenovo about a year ago, i've never been able to go dual display. HIComputer specsProcessor: AMD FX-8350 Eigh-core 4.00 GHzEdition: Windows 10GC: Nvidia GeForceGTX 1060Hdmi x1 DVI-D x1 Displayport x12 monitors-1st Vizio TV 1xHDMI 1xVGA2nd: ViewSonic monitor DVI-Dx1 VGAx1so, Im trying to do a HDMI and DVI set up but my computer is not recognizing my dvi monitor. No matter what I do.

On my old comp i just did dual VGA hook ups, because my tower had a VGA port. Now it doesnt so Ive been trying to figure out why it only picks up my HDMI monitor and not my DVI.Help??PS all my drivers are updated and everything and adapters dont seem to work. I have been using Windows 10 Pro on MS Surface 3 with a second monitor via mini display port adapter for over 2 yrs without a problem. It was working fine upto just 30 minutes ago, when Windows prompted me to reboot for an update. After rebooting, the external monitor is black, and Windows doesn't detect an external display.

The power is on, I tried unplugging / replugging the adapter, turning the monitor's power off and on, re-rebooting Windows, and so forth, but no luck. Opening desk.cpl and clicking 'Detect' results in 'Didn't detect another display'. WTF, Microsoft? Hi,this is a long thread, and while the hygiene checks seem to have worked for some people, I believe I am not alone in still having this issue.Issue summary: PC was running Vista! With 2 screens arranged as an extended display.

Upon updating to Windows 10, both screens show the same display. This cannot be changed in display settings as only 1 display is 'detected'.In addition, one screen resolution looks strange (slightly squashed), the other has a color issue (gray appears purple). These are both new issues which were not apparent running Vista with the same hardware.Both screens are attached to the back of the PC, one in the VGA slot, the other in the DVI-D slot. No changes in this set up since it was all working in Vista.Following this thread, the following have been attempted without success:1. Checking cable connections not loose2. Control Panel Device Manager Display Adaptors Update Driver3. Control Panel Device Manager Display Adaptors Disable Device then Enable Device4.

Dual Driver In Ear Monitors

Installing Windows 10 UpdatesSame result each time -'Didn't detect another display'Given that everyone was so critical of Vista and raves about Windows 10, surely the new version is able to cope with such a basic productivity tool as having 2 monitors connected but showing different windows? OMG I finally found something that works, having failed with every single suggestion posted (though thanks to Alan in particular for really trying hard)I came across the original DVD that shipped with my PC about 8 years ago.I then went to control panel device manager display adaptorsI right clicked on generic PnP monitor and selected update driverI then browsed to the DVD for the driver folderIf I could find the actual driver file I'd upload it here, but maybe you can find it online from any clues in my success message, attached.Good luck everyoneBen. Hello everyone,I am surprised that for the last 3 months I have a win 10 HP Envy Laptop that I can not seem to connect any vga monitor to it in anyway thru USB or HDMI. I also have a win 7 that I connect these monitors to without issues.

The monitors I have are both HP LE1901w. They work like they should. Recently I ordered another 3.0 USB to vga for win 7, 8 and 10 this time from Fresco Logic as this came with another mini disk that I loaded, installed, selected Win + P for extended and nothing happened. When I look up PC info it only shows 1 Big PC screen, that's it. I click detect and nothing. I shut down the monitor and turned it back on just to try to grab the signal with luck, well nothing happened so I restarted the PC, same thing. I shut it down swapped monitors and swapped cables from the one I currently use for Win 7 I have the same results from each connected monitor that displays vga input: no signal.

If i disconnect the cable it says vga connection lost. Next I went to the Fresco Logic website and downloaded the latest display driver and tried again restarted and tried again. Next I updated the Windows 10 display driver of course it says it is already updated. I tried again, restarted and tried again. The laptop does not come with a VGA connector. Next I went to Intel website and found Intel® Graphics Driver for Windows.

15.45 for Intel (R) HD Graphics 530 Version: 15. (Latest) as of 5/3 2017 and it failed to install due to incompatibilities.So there is a difference between the the latest version and what I have installed.

So I installed the Intel Update Utility and hopefully iy will find something as the monitor that has no signal is still connected.Anyways thanks for looking into this for me.Thank you CL. This happened to me yesterday.Laptop HP ProBook 450 G4External Monitor Asus VX238HWindows 10I've been using my Laptop with another external monitor (not the one above) at work for several weeks.

No problem using the extended monitor with a VGA connector.Yesterday, I took the Laptop home and attached my Asus Monitor to the HDMI connector.Display Settings detected the new monitor and it configures it as an extended display. Windows10 even detected the monitor speakers. Great.After a couple of hours working with this setup the computer starts to slow down noticeably. The GUI becomes unresponsive and impossible to work with. So, I reboot the Laptop.When Windows10 starts again, it no longer detects the external monitor. I've done many of the solutions suggested above (disabling/enabling the display adapter, rolling back the driver version, etc) but Display Settings no longer sees that monitor again. The monitor works, I've checked it with another PC.Any idea?

I stopped reading all the suggestions here once I found my specific solve so if it's already posted here I apologize for the redundancy.I have an NViDIA graphics card in my Dell Optiplex 880.To get my multiple displays to work I had to go to the NViDIA Control Panel (as opposed to the Windows 10 Control Panel) and turn on the Multiple Display option there first. In the NViDIA control panel I turned on the Multiple Display option as well as set the screen order.To set the Default Screen back to my main computer montitor I had to go to the Windows control panel for that option.I hope this helps somebody.:).

I have two laptops both with Windows 10. Both working perfectly with second monitors. I swapped the HDD's (just to get the best performance for the newer laptop) and now BOTH cannot detect the second monitor in Display settings i.e 'Didn't detect second monitor' and also cannot find monitor in Device Manager?Even stranger, on one of the laptops since the swap over certain keys don't work properly e.g pressing i = '5', j = '1', k = '2', l = '3', m = '0', p = '.' , 0 = '/'. Freaky stuff!Remember both worked perfectly before the swap! Hey, I used to have both of my monitors working, but I reinstalled windows 10 and I've tried to hook both of my monitors up once again which are connect by HDMI and VGA to DVI.

Every time I would boot up my pc the first monitor would load up the windows 10 logo and then after that it will just pop up 'No signal' and it switches over to my other monitor, but that monitor is gray and the only thing I can see is the mouse moving, but I can't log in. Once I disconnect the other monitor that isn't working and use the other monitor I would go into the display settings and then hook up the second monitor and click 'Detect', but it would still be black, but i'm able to move my mouse to the other screen, but the screen is still pitch black. I tried rolling back the drivers, but that doesnt help. I'm able to boot up the second monitor that isn't working in safe mode, but not normally.Help?

Thanks for all the great suggestions. My older Dell second monitor that I have used for many years started to act flakey after a Window 10 update, sometimes worked, sometimes on reboot, then not at all. I tried various connections on the monitor, variations of outputs on my ASUS Laptop N550JX, and a combination of all those, tried a second HP monitor, etc.

Tried a variety of the suggested solution posted here to no avail. What worked was to go on the ASAU website and download the graphic drivers there, and despite the repeated warnings from Windows that there were newer versions already installed on the PC, I installed them anyway, i.e. Rolled the drivers back to older versions. I added a second external monitor, and now the laptop display and two external monitors work great!!! Thanks for all your help!!! I need gurus please!I am trying to connect my laptop to 2 monitors which will show different screens (i.e not duplicate).Laptop: Acer Nitro 5 (7700HQ, GTX 1050 Ti) Intel Core i7-7700HQ (Intel Core i7)Graphics: NVIDIA GeForce GTX 1050 Ti (Notebook) - 4096 MB, Core: 1493-1734 MHz,Connectivity: USB 3.1 gen 1 (Type-C), HDMI along with othersMonitors: Dell UltraSharp 24 InfinityEdge Monitor - U2417H, both the sameWhat I've done: - connected the monitor 1 via HDMI- connected the monitor 2 via hdmi with USB type C adaptorMy laptop cannot detect the monitor 2 for some reason.

I have no option to rollback (found the place to do so but it is blocked out. Possibly because my laptop is barely a month old) and I have updated the drivers.Both monitors worked fine if I connect them directly via the HDMI cable.Please help!!

Thanks in advance! I just fixed this problem and thought it had something to do with upgrading Windows 10 to Windows 10 April 2018 edition. My second display monitor (my TV) was showing No Signal and was not detected in the Display Setup in Windows.(1) Updated the video driver in Device Manager under Display Adapter - Nvidia GeForce GT730 and restarted the computer.

Didn't fix the problem.(2) Shutdown the computer and restarted. Didn't fix the problem.(3) Moved the Nvidia video card to a different slot. Didn't fix the problem.(4) Checked the connections at the TV and the adaptor box for the RGB/VGA/HDMI cables, which all seemed tight when I checked them before step 1 above. I unplugged the HDMI cable from the adaptor box and then plugged it back in. Immediately, the TV monitor was detected and it all works now. I had this issue twice over the past 2-3 years.

Second Monitor Not Detected

It appears randomly and has nothing to do with cable or monitor quality. Neither are refresh rates or resolution to blame - they are normally changed by the adapter automatically.My configuration:- Lenovo Yoga 2 on Atom Z3., Win 10 32, HDMI-to-VGA adapter- LG Flatron L192WSWhat worked for me:- Win Logo + P to enter the projector/multiple displays menu while 2nd monitor is connected and the 'Out of range.' Error message is displayed;- The tablet screen turned on, while the external monitor became inactive;- From there I could change settings: Output to (Extended desktop);- Both screens worked;- Now I could enter the settings of the External display and double check that the resolution was native and the refresh rate was 60Hz;- I changed Output to (Digital television) and it worked.Hope this helps. For all those who lost second monitor upgrading to 10 in device manager display roll back driver i looked for my hp 110-1127nr display or video driver page showed it was a intel driver i downloaded it the one for win 7 installed it walla back to watching all and playing all for free again and computing on my big screen theres a reason bill doesent have this fix he works for the capitalists they dispise we brilliant motherfucker who dont bow to bullies i looked for it on hp site not they work against us too. For all those who lost second monitor upgrading to 10 in device manager display roll back driver i looked for my hp 110-1127nr display or video driver page showed it was a intel driver i downloaded it the one for win 7 installed it walla back to watching all and playing all for free again and computing on my big screen theres a reason bill doesent have this fix he works for the capitalists they dispise we brilliant motherfucker who dont bow to bullies i looked for it on hp site not they work against us too. For all those who lost second monitor upgrading to 10 in device manager display roll back driver i looked for my hp 110-1127nr display or video driver page showed it was a intel driver i downloaded it the one for win 7 installed it walla back to watching all and playing all for free again and computing on my big screen theres a reason bill doesent have this fix he works for the capitalists they dispise we brilliant motherfucker who dont bow to bullies i looked for it on hp site not they work against us too. I have read through all these comments and watched countless youtube videos as well, and none of it has solved my issue which is slightly unique.

Dual Monitor Drivers Hp

I have two monitors and use my laptop from work. Two things changed recently, the first being I unplugged everything and took it on a long trip. The second is right before I left they upgraded me to Windows 10.Now that I am trying to get up and running again, the monitors both work. But they both show just my laptop on each. When I try to detect, it does not find them but unde Device Manager​ if I click Monitors three are listed and all three say 'this device is working properly.' Since it's my work laptop there are some things I can't do as an administrator but considering they worked before and are technically working now, I doubt it is the drivers are a couple of the other suggestions.Thanks for any help!