Driver8.3 M0 crashes Minecraft.
 

I installed the 8.3 M0 driver on my laptop And when I try to run Minecraft the game gives me the error: "An unexpected issue occurred and the game has crashed. We're sorry for the inconvenience.". I have run Minecraft numerous times before installing DisplayLink and no such error occurred. Another game I play that is having problems is GZdoom. It crashes at startup and gives the error: "Code: C0000005 (Access Violation - tried to read addresses 00000018) Address 6D43715D".

Hello,

Thank you for taking the time to report this problem. I need more information from you to get a bug report created.
I numbered them so you can reply more easily.

1. Would you remember what version you were using before installing 8.3M0?

2. Can you use the 3rd link in my forum signature to run our Customer Support Tool and post the ZIP file it will create on your Windows desktop? The file uploaded here will only be accessible by employees and includes what is installed, how, but also logs of what is going on. Please run this as soon as possible after the crash happened.

3. If you uninstall 8.3M0 and install an earlier driver, does the behaviour change? I am not sure if it is a new behaviour introduced recently, or you have a new installation.

Kind regards,
Alban

I haven't tried any previous version of the driver on Windows 7, The former laptop I used the device on was Windows XP which is no longer supported but never gave me this problem.

What would be the closest WIndows 7 driver version to the last XP driver? It would give me a starting point.

Attachment 3283

Attachment 3284

I was trying out DisplayLink on my Compal EL80 laptop just a moment ago. The Compal had previously been XP but I upgraded to Windows 7. Anyway, when I plugged in the device, Windows started searching for drivers and then started installing a driver version 7.7.60.366.0 then blue screened. When it restarted, the main video drivers for the Geforce Go 7600 were completely missing.

Thank you Mastrius,

I couldn't see relevant crash dumps in these logs.
Would you please be able to explain or paste a screenshot of the crash you are experiencing so I understand what's happening?
You could also search your hard drive for *.dmp. As this is not a DisplayLink crash, that could be why it is not collected.

Using 7.7 on a recent machine with recent nVidia graphics drivers would indeed create a BSoD. Some hardware manufacturers have not upgraded as this is Windows 7. In any case, DisplayLink driver cannot remove another driver. Even when an incompatible driver is found, we will refuse to install rather than removing third party software. We explain how to remove incompatible software in our FAQ, but we will NEVER do it automatically.
From the hardware ID in your logs, I will look into suggesting a driver upgrade on Windows Update.

Windows XP never gave you any trouble because graphics drivers hadn't been updated for ages. To use a similar DisplayLink driver, you would need to use a similar nVidia driver as, until Windows 10 Anniversary Update and introduction of native support for DisplayLink USB graphics, both drivers have to work hand-in-hand.

Once we have a memory dump file, we can look into what is taking place for that crash. Alternatively, 8.2 M3 driver would be the most deployed driver on Windows 7 today.

Kind regards,
Alban

I already wiped the laptop but I could try and recreate the effect. Where would I find a dump file?

I hate software depreciation.

Hello,

This is really up to you, if you want to go through the bother of finding where this issue lies or if you are satisfied with the explanation that the DisplayLink driver is technically unable to be the source of a BSoD.
As we know it can't be a DisplayLink issue, I will not try to reproduce it locally (I don't play much). This needs to be handled by the company whose code trips the BSoD.

Here is an article on how to manage the Windows dump creation settings with location.

Kind regards,
Alban

I guess it doesn't matter then. But I would like to know what version of the DisplayLink driver would still work with a GeForce Go 7600 adapter.

https://www.dropbox.com/s/wadrsf8u0o...ivers.png?dl=0

On the other hand what do I do about Minecraft not working on my Thinkpad T430? Even if I unplug the adapter, as long as the driver is still installed it will not allow the game to run.

Hello,

Without data, me providing advice would be guesswork.

I got this thread confused. We can actually be the source of the BSoD. This is a Windows 7 and I don't know why, I falsely remembered you were on Windows 10 Anniversary Update.

In this version of Windows, DisplayLink drivers must work hand in hand with the primary graphics card driver. Have you looked at more recent graphics driver? These are from 2009.

Graphics: NVIDIA GeForce Go 7600 (NVIDIA)
Graphics Driver: 7.15.11.7948 Dated 2009/01/30

Kind regards,
Alban

I tried version 7.15.11.7948 and it gave me a BSOD as well but this time it did not remove the driver. Still I think I will use a restore point because DisplayLink is still probably unstable.