dlumd32.dll crash in Visual Studio 2010 when debugging WPF programs
 

My WPF applications frequently crash while being debugged in Visual Studio 2010. Fault module always points to dlumd32.dll, a DisplayLink library.

Frequent crash dialog #1:

Frequent crash dialog #2:

Checking "Enable unmanaged code debugging" would sometimes give the following errors:

http://i.imgur.com/Wjjqh.png

http://i.imgur.com/sMIQv.png

Sometimes it freezes up the whole computer including the mouse pointer. The screen would update "ever so slightly" every 3-5 minutes so it isn't a complete freeze... but it's ultimately unusable and needs a hard reboot.

EDIT: Tried the following; didn't help.
- No monitor connected to USB adapter.
- USB adapter not plugged in (drivers including dlumd32.dll still loaded).
- Disabled switchable graphics; use dedicated ATI graphics.
- Disabled switchable graphics; use onboard Intel graphics.

Nobody??

Happened again today when debugging my .NET 4 program. Something is wrong with your DLL:

http://i.imgur.com/upVo3.png

http://i.imgur.com/L7vY3.png

http://i.imgur.com/BIECl.png

Hi UltraDef,

Having our DLL on the stack doesn't really narrow it down much, we are often just passing things onto the OS that came from somewhere else, and even if we could validate every element of the structure passed on, it would probably slow things down an awful lot. I.e. it would not be hard to generate a stack backtrace with our DLL on the list, like the ones you reported in your first entry. I admit that the second one is harder to understand, since our dll seems to be the only culprit to point at.

Have you tried running without our software installed?

If you could share the .dmp file with us we would be able to progress this further.

Hi,

i have the exact same problem, vs 2010, vshost crashes when WPF animation is in progress. It's not happens immediately, the animation needs to run a few times.
If i stop the DisplayLinkManager service everything is fine. (but i loose my third display :( )

The same problem happens when i run the app directly, without debugging.

The previous driver was downloaded on 2011-04-03 which worked fine, i had no such problems, a week ago i had a few upgrades, and that driver crashed, so i've installed the latest, since than i'm having difficulties.

If you can share a sample program that provokes the problem it would really help.

Thanks!

Hi,

i've attached a test app with source code, and the repro steps.

PS: I've played around, downloaded, and installed the latest 5.6.xx version (5.6.31870) and that works fine too.

Hi,

Could you supply "D:\Projektek\Sajat\SimpleReader\SurfacePrototypes \Wpf.UI.Controls\ResourcesCommon.xaml"? There is no 'ResourcesCommon.xaml' in that directory, so even if I patch it to use my local path it doesn't work. If it's meant to be generated somehow, please let me know how.

thanks!

Sorry about that, please remove the referenced ResourceCommon.xaml line from the ...\WPFTester\WpfPrototype\App.xaml file, and it should work.

I met the same problem with my WPF application.
The displaylink software 5.6.31870 work fine but
system alerts me update to the new software when
I attach a USB monitor each time.

Ok, that runs up now. I've not made it crash yet, but we'll look into it. Thanks again for th e help.

This is a major annoyance that we've run into here as well. We've had to stop using the USB devices and uninstall the drivers to make it stop. Have you been able to replicate it yet? I would love to know if/when there is a fix coming, otherwise we may have to find an alternative as we work on WPF apps commonly. It doesn't only happen when debugging either, just running them can cause it.

DL software bug!
 

It seems that this is a D3D bug of the newest DL software.
My application contains some WPF 3D scenes.
Hope this help.

Problem with dlumd32.dll even with other apps
 

Hi guys,

I think this is really a problem with DisplayLink software. I have an application called Street Atlas USA 2011, running since late 2010 and a Diamond BVU195 USB adapter. Windows update recently updated the DisplayLink software and Street Atlas stopped working. I've done a bit of testing, this is the outcome...


With driver version 6.1.36490:

Faulting application name: SA2011.exe, version: 977.0.54.8415, time stamp: 0x4c62e4ac
Faulting module name: dlumd32.dll, version: 8.6.1.36484, time stamp: 0x4f327be9
Exception code: 0xc0000005
Fault offset: 0x00033c88
Faulting process id: 0x177c
Faulting application start time: 0x01cd046973a0f340
Faulting application path: C:\Program Files (x86)\DeLorme\Street Atlas USA 2011\SA2011.exe
Faulting module path: C:\Windows\system32\dlumd32.dll
Report Id: b2f00f01-705c-11e1-aa12-db443f95c14b


With driver version 6.0.34621:

Faulting application name: SA2011.exe, version: 977.0.54.8415, time stamp: 0x4c62e4ac
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0xffffffff
Faulting process id: 0x9cc
Faulting application start time: 0x01cd046b78b41956
Faulting application path: C:\Program Files (x86)\DeLorme\Street Atlas USA 2011\SA2011.exe
Faulting module path: unknown
Report Id: b9070c64-705e-11e1-896a-9bf8c95de176


There's no error at all with driver version 5.6.31870, the one I went back to. Street Atlas works just fine (and my PC too, so I'll stick to this, for the time being).

I did not try simply replacing the DLLs from different versions (I can try that if you want).

Regards,

Any update to this thread?
 

Hi DisplayLink team - any update to this thread? I too have a WPF application that is causing the dlumd dll to die - something about a pure virtual function call.

Thx.

Hi Guys,

Can you quickly give our 6.2M1 release a try? It's on http://www.displaylink.com/support/downloads.php

I've not been able to reproduce the problem using this (using the sample code) if you find it's still happening we'll dive deeper.

thanks!

Good news!
 

Hi Dan, great news, I tried the new driver 6.2M1 - and my dlumd64.dll crashing issue seems to be gone.

Our WPF app is running, we've done about 5 hrs of testing so far - many weeks to go - but so far all seems well.

Our app would crash within the first hour, so I think we are looking stable.

A quick question - The 6.2M1 release - was there a specific fix to address this WPF virtual Address pointer crash within the user mode driver? If you could answer "yes" to that, it would make me feel a lot better than a "maybe" - since we are going into a production environment with the HIS hardware.

Thx.
Ben.

Sorry - we didn't address this issue directly between 6.1 and 6.2, but we did fix a large number of bugs, so it looks like we fixed the one you're worried about. We'll try and use the test app in regression, or at least identify what fixed it, but I can't promise anything.

If any others can chip in with their testing that would be great.

Dan.

Hi Dan,

The problem with Street Atlas 2011 is also gone, so it's probably the same issue. As a side note, my PC is much faster in shutting down. I do not recall having seen such speed.

Thanks

WPF animations and crashing
 

Hi Dan, so far so good. We've gone through about 3 days of testing now and haven't seen our WPF crashing anymore. We have a full compliement of animations, SWF videos, WPF shaders, and all seems well.

For a little background, we are using the HIS MultiView device.