Over the last couple of days I’ve started to get the following error window pop up when I start my laptop up.
It’s to do with the 3D mouse. As soon as you press OK 3DXVirtualLCD stops working and crashes. This doesn’t affect the operation of the 3D mouse in Solidworks though. I’ve uninstalled and re-installed the latest version of the 3D Xware to try and resolve the problem and the same thing happened.
I have checked permissions to the location, quoted in the error message, and i have full permissions. I have also tried deleting this folder, then carrying out the re-install to no avail.
thanks for your report. Can you please let us know the exact driver version and the operating system you are using?
Which 3Dconnexion device do you have?
Which version of SolidWorks are you using?
Please stop the driver.
Then go to your folder C:\Users\Mark.Asbery\AppData\Local\Local\3Dconnexion\ and delete all folders where the name starts with 3DxVirtualLCD.
Then restart the driver.
Which 3Dconnexion device do you have?
3D Navigator Mouse – P/N: 3DX-600036 and PID: C4314035735
Which version of SolidWorks are you using?
We Are using both 2015 & 2016 Versions of Solidworks
Please stop the driver.
Then go to your folder C:\Users\Mark.Asbery\AppData\Local\Local\3Dconnexion\ and delete all folders where the name starts with 3DxVirtualLCD.
Then restart the driver.
The above did not resolve the issue, and am still seeing error message when logging into windows.
Is it recommended that users begin new threads for the same issue such as the 3dvirtualLCD Unhandled Exception alert.
Have a SpaceNavigator on Windows 7/64 which has been running great with this years new drivers.
Only thing new was having switched from AVG to Bitdefender. Still on all default settings.
Anyway. Am from the old school where people on forums used to take your head off if you repeated an old topic/issue instead of helping to keep the thread tidy and efficient.
In that spirit let me contribute that on Win7/64 the only other annoyance of late was the Windows Management Instrumentation (TSR?) that would infrequently refuse to "Terminate" before ever deciding to "Stay Resident". On that mystery, one that neither AVG nor Trend could find with their new ginned up tuneup gizmos, nor apparently by BitD either, the only sensible reliable fix I could find was to put a batch file icon on the desktop. And trigger that batch file, not once but twice to finally get the WMI service to reset using DOS level commands.
Are Windows 10 users running into more or fewer of these issues does anyone know?
Well years later.
One of my Users has a kinda simmilar Error Message.
Funny thing is, he Uses the SpacePilot. It works fine.
The error pops up when logging in to the local notebook.
He uses the mouse only in a virtual system running SolidEdge and Co.
Screenshot of Errorscreenshot
2022-12-16 14_14_15-Meine Ticketübersicht __ Matrix42.png (169.44 KiB) Viewed 2066 times
