Repeated Crash

SysWOW64 and ntdll.dll error

from Stardock Forums

Today, I installed ObjectDock Free to evaluate. Worked well on one computer. Another computer it seems to work, but when I change and settings and save, I get a crash. The event log generates this error:

Faulting application name: ObjectDock.exe, version: 1.99.0.742, time stamp: 0x4cacdb41
Faulting module name: ntdll.dll, version: 6.1.7601.19045, time stamp: 0x56258e62
Exception code: 0xc0000374
Fault offset: 0x000ced0b
Faulting process id: 0xb70
Faulting application start time: 0x01d11ca620e942b5
Faulting application path: C:\Program Files (x86)\Stardock\ObjectDockFree\ObjectDock.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: d6d676b9-8899-11e5-bedd-902b34154b6f      

 

This computer is on Windows 7 - 64

objectdock
8,625 views 6 replies
Reply #1 from Stardock Forums Top

Having the same issue this morning on Win 7 x64.  System boots fine, but as soon as ObjectDock was utilized it would lock up explorer.exe interactions.  Can hotkey pop the task manager, but unable to kill the process.  Have to log off or reboot to unlock the machine.  Uninstalled old free version, expecting comparability issues.  Purchased and installed latest version today and it has the same issue, with a slightly different experience.  The program locks up on interaction, but is able to gracefully be killed by windows.

Just did the following updates:

  • KB890830
  • KB3081320
  • KB3102810
  • KB3097996
  • KB3101246
  • KB3100773
  • KB3101746
  • KB3092601
  • KB3107998
  • KB3098781
  • KB3097877
  • KB3100213
  • KB3101722
  • KB3097989

Application Error Logged:

Faulting application name: ObjectDock.exe, version: 2.20.0.862, time stamp: 0x542c5a27
Faulting module name: ntdll.dll, version: 6.1.7601.19045, time stamp: 0x56258e62
Exception code: 0xc0000374
Fault offset: 0x000ced0b
Faulting process id: 0x23f4
Faulting application start time: 0x01d11caddc839b5a
Faulting application path: C:\Program Files (x86)\Stardock\ObjectDock\ObjectDock.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 235d9468-88a1-11e5-8c48-0c8bfd99d913

 

Suspect KB3101746:

ntdll.dll updated in this update, which sources to the crash.  Not guaranteed to be the source, but a good target.

https://support.microsoft.com/en-us/kb/3101746 

 Removed KB3101746, crash still occurs.

KB3097877 seems to be the cause.  I uninstalled all the updates and was working through one by one.  Object Dock crashed upon reboot after this one update.

 

Confirmed.  After removing KB3097877 again, Object Dock functions fine.  https://support.microsoft.com/en-us/kb/3097877

 

UPDATE 11/12/2015: Reapplied the update this morning after M$ modifications, it now doesn't cause issues with OD.

Reply #2 from Stardock Forums Top

Well... At least I don't feel alone. :( LOL

 

I have had problems with SysWOW64\ntdll.dll on another machine with another 32 bit program. I have fought with it for a year and have never resolved it. Getting where I hate 32 bit programs.

64 bit has been common for a decade. Time to recode. 

TouchTasks - Access tasks with ease on Windows touchscreens.
Reply #3 from Stardock Forums Top

Uninstalled KB3101746, still crashes.  ntdll.dll is 6.1.7601.19018, instead of 6.1.7601.19045.



Reply #4 from Stardock Forums Top

The Free version is no longer supported. Those with v2.20 can look below to continue the conversation.

Please move here for v2.20 assistance-> https://forums.stardock.com/473191/page/1/#3601181 

Reply #5 from WinCustomize Forums Top

Current crashing of various programs [including Outlook] are caused by the latest Microsoft Updates.

Uninstall as suggested above.

It's always advisable to disable 'automatic updates' as it is not uncommon for MS Updates to cause issues with existing software.

Set them to 'notify' only, so you will be aware of cause and effect when updating manually...;)

Reply #6 from Stardock Forums Top

The crash appears to be from MS update: KB 3097877. 

http://www.infoworld.com/article/3004441/microsoft-windows/microsoft-surreptitiously-reissues-botched-patch-kb-3097877-for-windows-7.html%20

They appear to have re-released it with a 'fix'. Please try to update windows again, reboot, and see if OD is still having issues.