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

[jabrown85]

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.

[kaiken]

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

[Usacad]

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,

[btsui]

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.

[Dan]

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!

[btsui]

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.

[Dan]

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.

[Usacad]

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

[btsui]

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.