[SOLVED] ObjectDock Crashing

Hi,
 My ObjectDock keeps crashing.

This all started on Friday when I restarted my PC. It just kept crashing afterwards. Unfortunately previous System Restores didn't work, so I didn't have a previous restore point to go back to.

I successfully got it working again after doing Windows Updates, and doing a full uninstall & reinstall.

But my PC was intermittently experiencing lag spikes. I thought that was due to this update:
2019-05 Preview of Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4499178)

So I removed it. Doing so also broke ObjectDock again, and I was back to the crashing. So I did believe the KB4499178 update had fixed it.

After continuing to use it for a day (without ObjectDock), the lag spikes returned. I found the Windows Anti-Malware was spiking up in CPU usage, and read this could be due to bad definitions, which was part of the Windows update.

So I completely reinstalled Microsoft Security Essentials, and the lag spikes went away. I thought I could re-install the update, KB4499178, and proceed with reinstalling ObjectDock to fix it again.

I'm fully updated again, but it still doesn't work.

I had a glimmer of hope when I manually searched REGEDIT for "Stardock", and deleted the entries manually, backed up the data in: AppData\Local\Stardock\ObjectDockPlus\

Wiped it, and deleted the entire folder: C:\Program Files (x86)\Stardock\ObjectDock

After a clean reinstall, it reloaded a default ObjectDock, but the crash error message appeared right after. Every attempt to load it afterwards, doesn't even load the bar, just the crash message.

From the Event Log:
Faulting application name: ObjectDock.exe, version: 2.20.0.862, time stamp: 0x542c5a27
Faulting module name: ObjectDock.exe, version: 2.20.0.862, time stamp: 0x542c5a27
Exception code: 0xc0000005
Fault offset: 0x000cc2ab
Faulting process id: 0x1e48
Faulting application start time: 0x01d520bf454834a3
Faulting application path: C:\Program Files (x86)\Stardock\ObjectDock\ObjectDock.exe
Faulting module path: C:\Program Files (x86)\Stardock\ObjectDock\ObjectDock.exe
Report Id: 999a3bc3-8cb2-11e9-8fec-005056c00008

There's also a strange issue, after ObjectDock crashes, I'm unable to navigate within Event Log. Everything within it is entirely frozen. That's fixed after a restart.

Operating system is Windows 7 Pro 64-bit.

Please provide any insight to resolving this. I've become accustomed to using ObjectDock, and would love this function back.

I also tested RocketDock, just to see if it would crash as well. It was working. But of course ObjectDock's superior with the tabs.

Thank you

9,442 views 6 replies
Reply #1 Top

Apologies for the post, it was written properly spaced out. But it's just not displaying so, I'm not sure why... this isn't my first time using a forum :\

EDIT:

Fixed, it was caused by my browser's NoScript.

Reply #2 Top

Open an Administrative Command Prompt, type sfc /scannow and press Enter. When it finishes reboot and see if the problem is fixed. Sounds like you possibly may be having a system file issue. Hope it helps.

Reply #3 Top

I've just tried that, and it says Verification 100% complete, "Windows Resource Protection did not find any integrity violations".

Reply #4 Top

I just kinda figured it out.

I began shutting down my programs which I believe would auto update on their own, just in case of conflict. I reached a point where pretty much anything extra was closed off. So I decided to unplug my external back up Drive, which is a Western Digital 4TB Black My Passport Portable External Hard Drive:
https://www.amazon.com/Black-Passport-Portable-External-Drive/dp/B01LQQH86A/

After I unplug it, ObjectDock launches just fine. Plugging it back in causes no issues either. ObjectDock just can't launch after, it must launch before.

This makes sense, since I don't normally have this on all the time. I only plug it in when I'm accessing backup data or running backup syncs. But still odd that it conflicts with ObjectDock.

Reply #5 Top

OK, hopefully someone from Stardock can help you then. Have you tried uninstalling and reinstalling ObjectDock?

Reply #6 Top

Quoting LightStar, reply 5

OK, hopefully someone from Stardock can help you then. Have you tried uninstalling and reinstalling ObjectDock?
End of LightStar's quote

Many, many times. But it's solved now. See my solution above.