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

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