reinstall of 1.44 lead to HPHC_Scheduler.exe crashing

[john7]

There is defiantly problems between PC Spyware Dr 1.44 and HP laptop programs. I put the 1.44 back on, totally clean uninstall, via JV16 uninstall, registry cleaned JV16 and CCleaner. This time Smart Update ran OK but something promptly caused an HP program to terminate. Windows log below. Avast disabled for intall and installed as administrater


Problem caused by Spyware Doctor
This problem was caused by Spyware Doctor, which was created by PC Tools. There is no solution for this problem at this time.
Recommendation
________________________________________

A newer version of Spyware Doctor is available for download that might address this problem. PC Tools recommends updating to the latest version of Spyware Doctor to take advantage of security and stability improvements.
Go online to the following website to update Spyware Doctor:

Problem signature
Problem Event Name: APPCRASH
Application Name: HPHC_Scheduler.exe
Application Version: 3.1.9.1
Application Timestamp: 48edff8e
Fault Module Name: guard32.dll
Fault Module Version: 3.8.260.476
Fault Module Timestamp: 49a4b838
Exception Code: c0000005
Exception Offset: 00015bf5
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 2057
Additional Information 1: dfb9
Additional Information 2: 19cbdeb971ba0451995ae42a13620332
Additional Information 3: 5fb7
Additional Information 4: 2078ead080f0bc39e7e9c380bfc93276

Extra information about the problem
Bucket ID: 1163655293

[haapy]

To eliminate one issue, please check the HP website to see if there are software and driver updates for your HP devices.

guard32.dll is for your Comodo Firewall. Do you have the latest version?

[Reodor]

To my experience most of the HP up daters crashes from time to time. Be it printers or others, they just flags up error. Works one day -gone the next.
I usually find it more peaceful just to disable them and to a manual up-date search now and then.

[john7]

HP software is all upto date

[mjq424]

guard32.dll is for your Comodo Firewall.
Hi
To repeat haapy's comment, the problem is with Comodo firewall, not with Spyware Doctor as the "faulting module" is guard32.dll which is the usermode hook protection module used by Comodo firewall.

[john7]

Thanks, confused as to why Vist loged Problem caused by Spyware Doctor
This problem was caused by Spyware Doctor, which was created by PC Tools. There is no solution for this problem at this time.
Recommendation
________________________________________

A newer version of Spyware Doctor is available for download that might address this problem. PC Tools recommends updating to the latest version of Spyware Doctor to take advantage of security and stability improvements.
Go online to the following website to update Spyware Doctor:

[haapy]

It seems like this message ws not generated by PCTools.

Are all components of PCTools and Comodo the latest?

[john7]

Yes both upto date. I don't understand wht I was told there is a updated SD, the problem was after installing the updated one?
But when I had it on befor and had so many problems even the MS problem reports was saying there was an updated version so thats not changed!
I also see the Comodo file is, from looking on the web, to do with there AV which I don't use as its never had a very good reputation/reviews. Its in the system 32 folder though?

[haapy]

From what I read on the Comodo website, Firewall + comes with Anti-virus.

http://personalfirewall.comodo.com/index.html

If that is so, then you have a built-in conflict with Avast.

I would try temporarily disabling everything BUT SD and see if the problem persists.

While disabled, I would do an SD uninstall/reinstall, just to be sure.

Then add Avast and see how it goes and finally add Comodo.

[john7]

It comes with both but you select if you whant all or part of the two. I only selct firewall and the AV isn't part of the program. Evey thing was disabled for the SD install, but will try disabling AV and firewall. The second PC has the same AV and firewall but diffrent IE and SD and its OK

[haapy]

Sorry, I thought we had something there. I am out of ideas on this one.

[john7]

How I did this. I started with closing each programme one after another. I started IE8 timing from starting click until fully loaded. I repeated this at least five time to see is any large difference . I then started reactivating one by one with any differences noted below before activating together.

All running be for and at end of test 12 sec
Avast disabled 11 seconds
Comodo firewall and defence + disabled 10 seconds
SD disabled 5 seconds
I notice until closing SD IE loads in two stages with a distinct gap between
Going in reverse
SD activated 3? to 15 seconds
Comodo firewall 11s again etc , deactivated and with just SD 13sec?
SD disabled back to 11sec?
With Avast enabled i.e. nothing else 12 sec
Adding Comodo firewall and defence + 11 sec
Disabling SD then restarting it SD 12sec

I have no idea what this lot shows other than the loading of IE in two staged with SD running but not with anything else running. That there are changes isn’t surprising, but that there is so little differences to me is surprising as is very variable loading speed when reactivating SD as all the others had very similar times as they were reactivated.