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

[UltraDef]

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:

---------------------------
Microsoft Visual C++ Runtime Library
---------------------------
Runtime Error!

Program: C:\Program File...

R6025

- pure virtual function call


---------------------------
OK
---------------------------

Frequent crash dialog #2:

Problem signature:
Problem Event Name: APPCRASH
Application Name: <my_app_name>.vshost.exe
Application Version: 10.0.30319.1
Application Timestamp: 4ba2084b
Fault Module Name: dlumd32.dll
Fault Module Version: 8.6.1.35912
Fault Module Timestamp: 4ee813d4
Exception Code: c0000005
Exception Offset: 000247e4
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Read our privacy statement online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

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





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.

[UltraDef]

Nobody??

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

[Dan]

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.

[lg543t]

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.

[Dan]

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

Thanks!

[lg543t]

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.

[Dan]

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!

[lg543t]

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

[kaiken]

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.

[Dan]

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