Operating system is Windows 7 Pro 64-bit. There's also a strange issue, after ObjectDock crashes, I'm unable to navigate within Event Log. Every attempt to load it afterwards, doesn't even load the bar, just the crash message.įaulting application name: ObjectDock.exe, version: 2.20.0.862, time stamp: 0x542c5a27įaulting module name: ObjectDock.exe, version: 2.20.0.862, time stamp: 0x542c5a27įaulting application start time: 0x01d520bf454834a3įaulting application path: C:\Program Files (x86)\Stardock\ObjectDock\ObjectDock.exeįaulting module path: C:\Program Files (x86)\Stardock\ObjectDock\ObjectDock.exe Wiped it, and deleted the entire folder: C:\Program Files (x86)\Stardock\ObjectDockĪfter a clean reinstall, it reloaded a default ObjectDock, but the crash error message appeared right after. 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\ I'm fully updated again, but it still doesn't work. I thought I could re-install the update, KB4499178, and proceed with reinstalling ObjectDock to fix it again. So I completely reinstalled Microsoft Security Essentials, and the lag spikes went away. 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 did believe the KB4499178 update had fixed it.Īfter continuing to use it for a day (without ObjectDock), the lag spikes returned. Doing so also broke ObjectDock again, and I was back to the crashing. I thought that was due to this update:Ģ019-05 Preview of Monthly Quality Rollup for Windows 7 for 圆4-based Systems (KB4499178) I successfully got it working again after doing Windows Updates, and doing a full uninstall
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |