-
1
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
1
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Archived Topics
- Notebooks Archive
- Re: Display via 3005pr HP USB3.0 Port Replicator not functio...

Create an account on the HP Community to personalize your profile and ask a question

03-16-2013 04:29 PM
I purchased a HP 3005pr USB3.0 Port Replicator as a (universal) docking station for my laptop (BTO 15CL48-GTX660 running under Windows 8 Pro 64-bit). Everything works quiet well, but the monitor display via the Port Replicator is not fully stable, often a bit flickering, and also shows some 'jpg like' symptoms; if I move the mouse over icons in the taskbar, the icon on which the mouse resides shows a kind of noise and the whole screen lights a 'bit up and down' or gets 'noisy'. Altogether it's quiet annoying. Is there a way to get rid of these artifacts?
Note: I downloaded the latest drivers for the graphic cards (primary card: Intel(R) HD Graphics 4000, secondairy card: NVIDIA GeForce GTX 660M) as well as for the Port Replicator.
03-29-2013 03:12 PM
Hi,
I seem to be having a similar problem. I am running a Windows 8 machine (Envy touchsmart ultrabook) and I can't get any video out of either the 2.0 or the 3.0 port replicators. I called support and they basically said that currently windows 8 is not supported with the Port Replicator
Peter
07-07-2013 10:35 PM
I am having the same issues with the port replicator and my HP laptop running Windows 8 Pro 64 bit. When I first got both back in February, the port replicator worked fine with Windows 8. In fact when I was ordering my laptop online on the HP site, and customizing it, the stand and replicator were recommended to me along with the laptop. I started having some issues with it - I would unplug the replicator from the USB port, and then plug it in again. Sometimes Windows 8 would say it experienced a problem though and would restart. I had to reformat my HD recently. When I did, the replicator worked fine again. Suddenly, a week ago when I plugged in the port replicator my screen went black. I could get audio and nothing else. It was after a Windows update, so I uninstalled the update. Still not working. I have downloaded the latest drivers, ran tons of scans and still nothing. If this isn't going to work with Windows 8 they better refund me. Deceptive practices offering it as a useful hardware to go with my new Windows 8 ENVY dv7.
04-29-2014 10:06 PM - edited 04-29-2014 10:08 PM
I am tech and installed one of these on customers Surface Pro 8 with dual monitors and it worked a dream, so much so the secratary at the office went out and bought a new surface pro 8.1 and then got me to do the same thing, except the screens kept cutting out and reapearing.
I tried
1. Connecting the monitors in different orders.
2. Changing screen resolution.
3. Install latest driver from HP website which supports 8.1
4. Lastest driver from diplay link website
5. Uninstalling and re-installing with monitors connected and disconnected. Every possible sequence possblie.
6. 6 hours later I had to give up and go home.
7. I am now faced with the daunghting task of remotely trying to fix the issue.
8. After a week to think about this issue and navigate through 100s of posts on the issue which provide no definite causes on the issue I am going to start looking at the graphics chip driver.
9. Why? look at the graphics chip driver you say. The 2 surface pro's (the first one i installed and the 2nd newer one) are a build apart and the graphics chips are different and thus the graphics chips driver is different. I have read in a forum that someone disabled there driver and it worked and it was the only thing out of all the wild guesses that people are making that, makes sense.
07-14-2014 05:43 PM
Don't forget everything comes out the USB 3.0 port. So it is either the USB3 or graphics driver that is the f@%ker causing it.
