DisplayLinkManager Service Causes Computer to Freeze
 

I have a computer (Dell XPS 12 9Q23) that ever since we've upgraded to windows 10 has had some odd freezing issues after the computer has been asleep. I could never figure it out so I've even re-imaged it and started fresh and then after about a month the freezing is back.

I've tried everything under the sun when it comes to sleep/hibernate and the such and doesn't matter it still happens. I've tried every intel and video driver I can try and made sure display link was up to date but nothing.

Once the computer has been asleep when you start using it and you press the "start button" or run a program from search the computer will freeze anywhere from 10-30 seconds.

I finally got smart and disabled all non MS services and the freezing was gone. After process of elimination I've determined it only happens when the DisplayLinkService is started. Even if you're not connected to a dock at the time, if that service is running upon waking up and using the freezing will be there.

I've ran the diag tool and attacking the zip files.

I'm assuming this is a driver conflict between displaylink and something else...I just can't figure out what the something else is and what version it needs to be to stop this from happening.

Tech Support
 

Any ideas from tech support?

Hello,

How long after the freeze were the logs gathered?
Would you please also indicate what type of sleep mode was the computer in?

We haven't had similar report so far.

Kind regards,
Alban

The logs were taken at a time where the freezing hadn't happened (I already disabled the service) and had rebooted.

As far as sleep it happens with every setting I could try when it came to sleep/hibernation. I disabled Hibernation completely (powercfg.exe /hibernate off) I've tried it with it on. I've turned on and off allow hybrid sleep.

Thanks for your help.

Hello,

Our logs are rolling not to take all the available space. If the event was not recent, then it will not be in the logs.
If our service is stopped, there is no logging either.

The settings you are reporting are part of our general system test done prior to each release. This means that the issue is linked to your configuration or we would have seen it. It will be difficult or impossible for us to investigate without more details I am sorry to report.

Kind regards,
Alban