NOD32 2.50.16 (IMON.DLL) conflicts with Diskeeper 9

NOD32 v2.50.16 (IMON.DLL) conflicts with Diskeeper 9 (Smart Schedule) and leads to WinSvcHost determination and forced reboot on Windows XP SP 2. This happens always and as soon as Smart Schedule feature is enabled and active.

 

Hmm...I run NOD32 2.5 and have Diskeeper 9.0 with no problems.Have you tried uninstalling either program and re-installing it to see if it corrects the problem?

 

Yeah, did uninistal and reinstall both, but the conflict reoccurs. Always and as soon as the Diskeeper 9 Smart Schedule feature automatically activates. BTW, I am using both programms for years already and I am a licensed user. The issues begun since I have updated NOD32 to 2.50.16. I was forced to disable Smart Schedule Defragmentation for now.

 

Hi Rationalmind, welcome to Wilders.

Have you tried excluding that file from AMON?

Cheers

 

No, I didn`t try that yet. The conflict seems to be caused by IMON, however reducing efficiency (increasing compatibility) did not make things any better. Why should I exclude it in AMON to eventually make it work in this particular version?

 

I have Diskeeper 9 also I have not any problems with my set up!! I was wondering what is your version? Mine is DiskeeperExecutiveSoftwareInternational, Inc.
Version: 9.0.524.0!!

Cheers

 

Sorry I almost forgot! Welcome to Wilders!!


Cheers

 

im running nod32 2.5 with the latest version of diskeeper9
no problems encountered

 

Gotta add my voice to the no problems brigade, both apps work fine here

 

Well, that seems quite weird to me. Is anyone of you guys using Diskeeper 9 (v9.0.524.0) in Smart Schedule modus? Would be nice to compare pears with pears. Thank you for your replies!

 

Well I just updated from .511 to .524 and still no problems yet - yes I use smart shedule

 

I use the same settings also and still no problems!!

Cheers

 

I've long had this problem with Diskeeper smart scheduling, so I simply use it manually now. I never pinned the problem on NOD32 before though, and don't know if it's involved, since there was no smoking gun in Event Viewer. I've long had Diskeeper excluded from AMON, and I only use the POP3 portion of IMON.

 

All right, I have been researching on this issue a lot lately and seems it is not an exception related to my setup only. From what I have read on various forums, many other folks are getting this very same issue as well.

The conclusion is clear: I have to exclude svchost.exe from AMON in order to eliminate these persistant system restarts as soon as Diskeeper 9 (v9.0.524) Smart Schedule modus activates.

By being somewhat forced to do that, I need one clear explanation here: What are the exact consequences for excluding svchost.exe from AMON? How far am I compromising on my system security settings? Please, advise!

 

Hi Rationalmind

Most likely the svchost.exe that is hanging and causing you problems between Diskeeper9 and NOD32 is related to a profile user environment not unloading properly namely the svchost.exe tied in with any A/V scanner...

The solution I found was to install the M$S User Profile Hive Cleanup Service

http://www.microsoft.com/downloads/details.aspx?familyid=1b286e6d-8912-4e18-b570-42470e2f3582&displaylang=en

Give it a whirl and see if that fixes your situation

Saphire

 

Thank you for your reply Saphire! I carefuly went through the readme of the UPHClean v1.5e (User Profile Hive Cleanup Service), however was not able to find any relation to the problem I describe here. Would you please, provide somewhat more detail on why do you think this will change anything in the way SVCHOST.EXE is being terminated by AMON under NOD32 v2.50.16 and always, as soon as Diskeeper 9 (v9.0.524) Smart Schedule modus begins?

 

Hmmm

Got my first one today. Using DK v9.0.524 with Smart Scheduling enabled. Is this what you are seeing?

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 6/10/2005
Time: 1:02:06 AM
User: N/A
Computer:
Description:
Faulting application svchost.exe, version 5.1.2600.2180, faulting module imon.dll, version 2.50.19.0, fault address 0x0000b1eb.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 73 76 63 ure svc
0018: 68 6f 73 74 2e 65 78 65 host.exe
0020: 20 35 2e 31 2e 32 36 30 5.1.260
0028: 30 2e 32 31 38 30 20 69 0.2180 i
0030: 6e 20 69 6d 6f 6e 2e 64 n imon.d
0038: 6c 6c 20 32 2e 35 30 2e ll 2.50.
0040: 31 39 2e 30 20 61 74 20 19.0 at
0048: 6f 66 66 73 65 74 20 30 offset 0
0050: 30 30 30 62 31 65 62 000b1eb

Followed by:


Event Type: Error
Event Source: EventSystem
Event Category: (50)
Event ID: 4609
Date: 6/10/2005
Time: 1:07:08 AM
User: N/A
Computer:
Description:
The COM+ Event System detected a bad return code during its internal processing. HRESULT was 800706BA from line 44 of d:\qxp_slp\com\com1x\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Then the machine rebooted.

 

Yep! Exactly. This is it.

Here`s what MS has to say about it:

http://oca.microsoft.com/de/response.aspx?SGD=88233b10-e41f-4f2d-bf2e-3d61ff65a8f4&SID=1043

Seems known, yet unresolved issue....

 

Yes I have seen that same error in the event log --although it never caused my system to spontaneously reboot..

I assume that you gentlemen have also configured the MFT using Diskeeper9 to "optimum" recommendations. The solution I found was to ensure that DiskCheck has been run to clear up any file errors then install the M$S Hive Cleanup Service (UPH Clean) since most likely Diskeeper9 in conjunction with the scan engines in NOD32 (roaming processes) or for that matter any A/V live scan that is causing the lsass to spawn a "hanging" svchost and/or "BITS" ---and UPH Clean solves whatever the conflict may be and closes the applicable processes....

Try installing UPH Clean and SEE if that solves it for you ...and there is an uninstaller for UPH Clean if you find that it does not help

Saphire

 

Hi Saphire

I ran a chkdsk/f on the system disk and all was well. I already run UPHclean so that did not prevent the problem. Just checked the MFT configuration in DK and it too is OK. Thanks for the suggestions anyway. The only thing I've done recently is enable Imon when I installed .19. I guess I'll just disable it again...

 

Nada in the DK Knowledge Base.

 

It was a good idea. I hadn't looked there until you mentioned it.

 

I had sent a email to Executive Software asking them to look into this awhile ago but as of yet no reply...A lot of 3rd Party Defragmenters (O&O ect ect) have recently updated their defragmenting applications so hopefully Diskeeper9 will SEE an update soon...although I imagine that most software vendors are waiting to ascertain what "fixes" M$S is sending out for Windows next Tuesday before finalizing any updates ----

Saphire