Explorer Crashing on Bootup with Fences

Windows 7 x64

Each time I start my PC, Explorer crashes just before Fences starts. I've uninstalled Fences and no longer getting IE crashes. I like the program so if this gets fixed, I would re-install. I am running Windows 7 x64

10,963 views 13 replies
Reply #1 Top

Explorer crashes just before Fences starts. I've uninstalled Fences and no longer getting IE crashes.
End of quote

Firstly...is it 'Explorer' that crashes or 'IE' [Internet Explorer]?

They are two different things.

Reply #2 Top

No issue here with Explorer and IE. Running Win7 x64.

something else might have a problem Fences.

Reply #3 Top

Sorry about that folks. It is the Windows Explorer that crashes, i.e. the desktop.

Reply #4 Top

System specs?

I have Fences here running happily on 3 Win 7 installs...2 64bit...one 32bit...and a Vista 32bit....lowest spec is a P4 3.0 and 2gig of ram...3850 AGP graphic.

You 'shouldn't' be having Explorer crashes.

Reply #5 Top

caper7ca - Yikes. If you could could you please navigate to the folder "%appdata%\stardock\Fences\TroubleshootingLog" and send us the files located there? I can be reached at fencesbeta - at - stardock.com, mention in the subject that we'd chatted on the message boards. Thanks!

Reply #6 Top

Sent an e-mail showing logs. It will also crash if I start and then restore a previously stored config.

Reply #7 Top

I had exactly the same issue after installing the new versions of Fences and Deskscapes.  It was showing the crash caused by DesktopDock.dll.  I uninstalled Fences Pro and Windows Explorer was still crasjomg on boot up but was showing it caused by StackHash or something like that.  I uninstalled the latest version of Desckscapes and everything seems fine now.  I'm not sure which program was causing the issue.  It might have been both.  

 

 

 

Reply #8 Top

I have Fences installed in Windows 7. I noticed today that after renaming a desktop icon, within Fences, Windows Explorer crashed. I've had regular Fences crashes of Windows Explorer on this Windows 7 PC, but not on my other Windows XP computer.

Reply #9 Top

I'm having a similar problem. Since installing an update today my CPU useage has been at nearly 100%. When I check to see what process is causing the problems, it's always explorer.exe.  I'm running Windows XP. I don't want to uninstall Fences. I've come to depend on Fences to keep me organized with the amount of programs and files I use. I've rebooted the computer several times and it never changes.

Reply #10 Top

Since installing an update today my CPU useage has been at nearly 100%.
End of quote

I've also noticed a spike in CPU usage since updating Fences, though not as pronounced.  My CPU was comfortably idling around 2 - 4%, spiking occasionally up to 10 - 12% prior to the latest update.  Now it's sitting on 10 - 12%, spiking up to 25 - 30%.  Explorer.exe is the process named as being the one responsible.

It's not a major issue at this time, but I'd like to see my CPU get back to 'normal' rates some time soon. :)

Reply #11 Top

Ugggh, I should've thought to check here first!

 

I've been to he!! and back with system restores and everything else the last few days.

 

I have the same problem with WinXP SP3 and explorer.exe using 100% CPU

 

I will uninstall now and look for a bug fix in the New Year?  they're down from Dec18 on for the Holidays, correct?

 

eta:  I went into Impulse / Fences / Tools / More Tools and checked off the Disable Fences and IMMEDIATELY my CPU usage went back down to normal

 

So there is a bug in this last update.  I'm new here - any way to get the older version since they probably won't work on it for the next 2 weeks?

Reply #12 Top

Yikes - Ok, CPU issue was indeed a problem on XP systems; thanks to the help of users sending in their debug log we found it!!! Please give Fences an update using Impulse to the new version released today and see if that helps. Thanks...

Reply #13 Top

I'm running Windows 7 64bit and very frequently during boot up, my desktop explorer will crash and each time the log shows desktopdock64.dll as the main culprit that caused the crash. I've already sent the debug log. Any idea what's causing it?