Driver causes WDM problems
 

Hi

We are trying to use a Mimo USB powered touch screen using Display Link
drivers and have a problem. When the drivers are loaded there is a windows desktop manager error wich says that WDM has stopped and been closed then after a reboot the PC has to have a system restore to get it back working. The PC is a small form PC with on board graphics (Intel HD 4000) and we have had it running 3 monitors with no problem.
Anyone got any ideas?

Cheers

Tonyb

PC Spec? DisplayLink driver version? Which OS?

Really need log files to give you useful next steps.

Wim

Hi Wim

OS Windows 7

Have used the latest display link driver from website
and have tried some older versions too.

PC Spec
Small PC
SC240S-i724-4GM-128GF-DDS-3VGA-DL-2S-2SB-VR
Panel mount industrial computer: Intel Core i7 3rd generation
2.4GHz Mobile CPU, 3 VGA Ports, 128GB SATA Solid State Drive in
Drive Shuttle, Second SATA Ready Empty Hot Swappable Drive
Shuttle, 4GB DDR3 Memory, Dual 10/100 LAN, 4 USB 2.0 ports, 2
RS232 Ports, 2 RS422 Ports.

Will sort out the log files asap.

Hope this helps

Regards

Tonyb

Hi Wim

Event Log

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-02-08T09:11:03.000000000Z" />
<EventRecordID>6792</EventRecordID>
<Channel>Application</Channel>
<Computer>SC</Computer>
<Security />
</System>
- <EventData>
<Data />
<Data>0</Data>
<Data>APPCRASH</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>DisplayLinkUserAgent.exe</Data>
<Data>7.1.45125.0</Data>
<Data>5108cb70</Data>
<Data>ntdll.dll</Data>
<Data>6.1.7601.17725</Data>
<Data>4ec4aa8e</Data>
<Data>c0000005</Data>
<Data>0000000000053483</Data>
<Data />
<Data />
<Data />
<Data>C:\ProgramData\Microsoft\Windows\WER\ReportQ ueue\AppCrash_DisplayLinkUserA_fd3e295c4a19a7cb254 18889d4d0153df669de0_0384d567</Data>
<Data />
<Data>0</Data>
<Data>75896932-71cf-11e2-a11d-003018a562eb</Data>
<Data>2</Data>
</EventData>
</Event>

Regards

Tonyb

Can you gather the log files from our tool just after the crash occurs?

http://kb.displaylink.com/269

And post the logs here?

Thanks

Wim

Hi Wim

Logs attached

Regards

Tonyb

Any luck with this problem ?