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

UltraDef · 02-04-2012, 04:41 AM

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:

Quote:

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

Program: C:\Program File...

R6025

- pure virtual function call

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

Frequent crash dialog #2:

Quote:

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 · 02-18-2012, 05:05 AM

Nobody??

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

Dan · 02-26-2012, 08:38 PM

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 · 03-09-2012, 04:35 PM

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 · 03-09-2012, 11:59 PM

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

Thanks!

lg543t · 03-10-2012, 05:11 PM

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 · 03-12-2012, 09:13 AM

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!

kaiken · 03-13-2012, 12:25 AM

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.

kaiken · 03-17-2012, 06:23 AM

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

Usacad · 03-17-2012, 06:26 PM

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,

03-17-2012, 06:23 AM	#9
kaiken Junior Member Join Date: Mar 2012 Posts: 5	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.

03-17-2012, 06:26 PM	#10
Usacad Junior Member Join Date: Mar 2012 Posts: 13	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,

02-18-2012, 05:05 AM	#2
UltraDef Junior Member Join Date: Feb 2012 Posts: 2	Nobody?? Happened again today when debugging my .NET 4 program. Something is wrong with your DLL:

02-26-2012, 08:38 PM	#3
Dan Banned Join Date: Nov 2009 Posts: 104	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.

03-09-2012, 04:35 PM	#4
lg543t Junior Member Join Date: Mar 2012 Posts: 3	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.

03-09-2012, 11:59 PM	#5
Dan Banned Join Date: Nov 2009 Posts: 104	If you can share a sample program that provokes the problem it would really help. Thanks!

03-12-2012, 09:13 AM	#7
Dan Banned Join Date: Nov 2009 Posts: 104	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!

03-13-2012, 12:25 AM	#8
kaiken Junior Member Join Date: Mar 2012 Posts: 5	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.