DisplayLink overloads Windows Kernel

[JH_MMC]

Dear Community, we're developing a product working under DisplayLink with this 10" USB LCD (http://lilliputdirect.com/lilliput-um1010-touchscreen).

We're detecting some troubles with the Windows 7 PosReady and the Windows Kernel due this is overloaded for the DisplayLink driver.

Our scenario is:
- Win 7 PosReady x32bits
- The USB 10" display by USB 2.0 connection. Driver DisplayLink_7.6M1
- No peripherals (the display is for Maintenance of the system)

We see the next analyzing the system kernel consumption:

In Windows 7 32-bit kernel stack apparently are 12 Kbytes.
What is the Kernel stack size of the displayLink software? It is a "normal" environment this memory?

Any knows any recommendation to (something that is available to disable) release the kernel load.

Many thanks in advance!
Regards

[AlbanRampon]

Hello JH,

We do not support, test or maintain drivers for Windows Embedded and family.
As Microsoft indicates the Windows 7 POSready will be end of life in 4 months, we are unlikely to be able to start development/test for that OS.

Unfortunately, the only recommendation we can do without analysis would be to try with different versions of our drivers to see if one works. However, even if one is working, any change you make to the system may break it as your configuration is not tested.

Kind regards,
Alban
Minimum PC requirements for Windows drivers.

[JH_MMC]

Many thanks for your quick reply AlbanRampon... But in Win7 Pro the problem is the same...

Regards

Originally Posted by AlbanRampon

Hello JH,

We do not support, test or maintain drivers for Windows Embedded and family.
As Microsoft indicates the Windows 7 POSready will be end of life in 4 months, we are unlikely to be able to start development/test for that OS.

Unfortunately, the only recommendation we can do without analysis would be to try with different versions of our drivers to see if one works. However, even if one is working, any change you make to the system may break it as your configuration is not tested.

Kind regards,
Alban
Minimum PC requirements for Windows drivers.

[JH_MMC]

Many thanks for your reply AlbanRampon.

But we tested under Windows 7 Pro x32bits and we have the BOSD too...

Regards.

[jdelatorre]

Dear Alban,

Really, we would like to have more info about the software stack size that DisplayLink requires, mainly for knowing if some feature can be shutdown.
The main problem is that displaylink related drivers take many space at this kernel.

Indeed, could be useful to know if some driver previous versión has a lighter Windows Kernel stack usage.

Thanks a lot,

[AlbanRampon]

Hey JH,

In that case, if you provide the system_details.txt and memory minidump our support tool would gather from your Win7 Pro, I will have a look!

Generally, it's because of an inadequate primary graphics card driver. But with 7.6 M1, it wouldn't be surprising as this is a 2 year old driver which doesn't benefit from the last 2 years of bug fixing. Do you get the same BSoDs on Win7 Pro x86 when using 7.9 M7 and the latest primary graphics card drivers?
On Windows Embedded 7 with 7.9, you will need to restart the DisplayLink Manager service manually to try.

If we comment on the size of the software, then we have to keep updating that comment. That's not something we specify. We unfortunately don't have the resource to create custom drivers with or without selected features. I hope you can understand it is even more difficult to justify allocating resource to an OS we don't support and will be end of lifed in 4 months.
Previous drivers versions are available from the download page by scrolling down: http://www.displaylink.com/downloads/windows

We are releasing 8.0 Beta 4 within a week and you'll also be able to try. However it will not be suitable for production. We have heard it might not need the manual service restart on Windows Embedded 7, an unplanned improvement for this unsupported and already end-of-lifed OS.

Kind regards,
Alban

[JH_MMC]

Hey AlbanRampon!

Attached you have the BSOD pic, the MINIDUMP of Windows, the system details using “DisplayLink USB Graphics Software for Windows 7.9 M7”.

Thanks in advance!

[AlbanRampon]

Hello,

Logs provided are not from big Windows, but a Windows Embedded Standard...
I've never seen such calling stack or BSoD, and I've seen a few.

There is a trip on the carpet with the Intel graphics driver, us and something else I haven't seen before, but the Microsoft tool is accusing another module called volmgr.sys
I'd recommend removing DL drivers, updating Intel graphics driver and then try to install DisplayLink version 7.7 M4.

Kind regards,
Alban


************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
BugCheck 7F, {8, 8e907750, 0, 0}
*** ERROR: Module load completed but symbols could not be loaded for dcrypt.sys
*** ERROR: Module load completed but symbols could not be loaded for Protector.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for igdkmd32.sys -
Probably caused by : volmgr.sys ( volmgr!RtlStringCbPrintfW+3a )

[JH_MMC]

Thanks! We will try your detailed info...

When I will test it i'll post our feedback.

Regards

[JH_MMC]

Dear AlbanRampon, sorry for my last reply...

Attached you have the dump file extracted following your recommended instructions.

Please could you check it and let me know what we're doing wrong...

Thanks in advance!