Page 1 of 1

Dexcube crash

Posted: 14.02.2012 10:56:20
by Mr_Incredible
I've tried the beta for the first time having never used Dexpot before. On my setup (Dual monitors running 1920x1200 and 1920x1080, with a GTX260, Win 7 x64), the Dexcube option can be set initially but 3D desktop swapping crashes the plugin, after which the Dexcube option cannot be reselected. If I stop and start Dexpot, Dexcube is enabled, but will crash again if I try to swap desktops. I cannot get 3D switching to work with the Dexcube plugin.

Image

Re: Dexcube crash

Posted: 14.02.2012 11:19:58
by Mr_Incredible
Just to add another comment....

I uninstalled the beta and installed the released version 1.5.15 Build 1799, and that exhibits the same crash problem.

I don't know if it's relevant or not, but I also use Stardock Fences Pro.

Re: Dexcube crash

Posted: 15.02.2012 15:43:02
by Patrick
:dex:

If you'd like to help us resolve the problem, please follow these steps:

  • Re-install Dexpot 1.6 Beta.
  • Save the attached file to the Dexpot plugin folder (C:\Program Files (x86)\Dexpot\plugins).

    dexcube.exe
    (739.5 KiB) Downloaded 309 times

  • Start Dexpot, enable the Dexcube plugin, and switch desktops.
  • When the "3D desktop switching plugin for Dexpot has stopped working" message appears, open the 32-bit Task Manager (i.e. run C:\Windows\SysWOW64\taskmgr.exe).
  • Go to the "Processes" tab, right-click on "dexcube.exe", and select "Create Dump File".
  • Zip the dump file and email it to info@dexpot.de. Or upload the file somewhere and send us a link.
Thanks!

Re: Dexcube crash

Posted: 17.02.2012 22:31:04
by Mr_Incredible
Hi,

Sorry I didn't reply sooner, I've been away on business!

I've emailed you a link to the zipped up dump file when Dexcube bombs out.

Hope that helps you!

Re: Dexcube crash

Posted: 22.02.2012 02:06:38
by Mr_Incredible
Did you get the correct file I sent the link for? (wave)

Re: Dexcube crash

Posted: 23.02.2012 13:31:21
by Patrick
I did. I'll send you an email.

Re: Dexcube crash

Posted: 13.03.2012 15:39:45
by Patrick
Update: The problem was fixed by disabling the "EVGA Precision" graphics tuning utility.