This is happening on multiple systems so it doesnt appear to be.
When the crash happens, event 1000 and event 1001 is logged in windows event viewer. This occurs every other time we try to update. I'll be leaving for the evening in about an hour, but I'll check in when I get back later this evening. We are having an issue where SAP crashes on updating delivery tickets and equipment cards. So the bottom line is that the DCOM error may have been occurring for a long while, and since it doesn't seem to affect the computer operation, I never knew it was occurring. FYI, I fixed the freeze up problem by opening the computer and tightened the various electrical connections. I was getting an atapi error message when the freeze ups occurred and just happened to notice the DCOM error message. The only reason I even noticed this error message is that I was working on another problem that was freezing up my computer and stopping it from running at all. I had the following anti virus programs at one time:McAfee, Norton, and AVE They have all been removed, but who knows what they left behind.Īs I mentioned in the original posting, the computer is running fine right now. VersionIndepentantProg Default ehomeSchedulerServive.Recording Dispatcher We are using kernel32, user32, and winmm, for various file system and sound functions.
In terms of API calls, I don't see any from ntdll.dll. ProgID Default Value Data: ehomeSchedulerServive.Recording Dispatcher In the Windows Application event log, when this happens, there is an Event ID 1000 faulting a seemingly random module - so far, either ntdll.dll or lpk.dll. Local server 32 Default Value Data: C\Windows\ehome\ehRec.exe Every time I boot, I get a DCOM Event ID 10010 error which occurs during the boot.
0 kommentar(er)
