DisplayLink overloads Windows Kernel

[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!

[AlbanRampon]

That's alright, I've got the history here and we don't receive many of these!

Would you know what this protector.sys intercepting the calls is?
Is it the Bank of China protector.sys or the trojan protector.sys?

I see you use a disk encryption utility as well.

I would advise you try with a simpler system for the troubleshooting.
Because the call is handled by 4 different parties, removing a few layers would be helpful.

I've trolled the web for that bug check, as everyone does, and I could find that some layers intercepting calls to the hard disk have created similar things in the past: http://www.sevenforums.com/bsod-help...er-update.html

Kind regards,
Alban


UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 8c639750
Arg3: 00000000
Arg4: 00000000

[jdelatorre]

Dear Alban,

Protector.sys is a security software that checks the system looking for unexpected / non registered processes.

Kind regards,

Juan

[jdelatorre]

Dear all,

May I understand that there is no relation between Intel graphics callings and Displaylink driver? I supposed that Displaylink driver called someway intel graphic cards for doing some image processing, am I right?

Kind regards, thanks in advance.