[paulb100]

thanks for your help - i had him uninstall comodo AND restore the PC to a date before it was installed... I havent spoke to him since....

Ive since added spybot real-time shield to make the same running processes up on my setup as his (to replicate problem) and since doing that upon shutdown it wouldnt restart and kept turning off during boot - even on safe-mode... it was 'Last Known Good Configuration' that has just got me on now....

according to that analysis it was messenger using the afd.sys driver ...

again thanks for your help - i will let you know the outcome

[peterdiva]

I'm getting probably caused by cmdhlp.sys, which is a Comodo file. You've got some old AV files left behind that could be causing a conflict. You need to remove these.

f23aa000 f23c6dc0 SYMEVENT SYMEVENT.SYS Sat Sep 16 14:48:19 2006 (450B9023) <-- Norton AV.
f23ef000 f242ece0 SYMTDI SYMTDI.SYS Wed Apr 06 03:10:52 2005 (4252D4AC) <-- Norton AV

BugCheck 35, {84c66ee8, 0, 0, 0}
Probably caused by : cmdhlp.sys ( cmdhlp+1c1c )

STACK_TEXT:
f17c9990 8052011d 00000035 84c66ee8 00000000 nt!KeBugCheckEx+0x1b
f17c9a00 804e13d9 85301248 00000000 84c66fa0 nt!IopfCallDriver+0x17
f17c9a68 804e13d9 857c7f10 84c66ee8 00000004 nt!IopfCallDriver+0x31
f17c9a78 f78c4c1c f17c9a98 f78c4ce4 857c7f10 nt!IopfCallDriver+0x31
WARNING: Stack unwind information not available. Following frames may be wrong.
f17c9a80 f78c4ce4 857c7f10 84c66ee8 84c66eb0 cmdhlp+0x1c1c
f17c9a98 804e13d9 852578a8 84c66ee8 84d8f0b0 cmdhlp+0x1ce4
f17c9aa8 f237040a 00000000 00000008 f17c9b1c nt!IopfCallDriver+0x31
f17c9b10 f2363492 84ca3008 0006f97c f2363492 afd+0x1040a
f17c9c5c 80586e63 8505dc78 00000001 0006f8f0 afd+0x3492
f17c9d00 80586eee 000008c4 000003f4 00000000 nt!IopXxxControlFile+0x255
f17c9d34 804dd99f 000008c4 000003f4 00000000 nt!NtDeviceIoControlFile+0x2a
f17c9d34 7c90eb94 000008c4 000003f4 00000000 nt!KiFastCallEntry+0xfc
0006f944 00000000 00000000 00000000 00000000 0x7c90eb94

[paulb100]

Originally Posted by peterdiva

I'm getting probably caused by cmdhlp.sys, which is a Comodo file. You've got some old AV files left behind that could be causing a conflict. You need to remove these.

f23aa000 f23c6dc0 SYMEVENT SYMEVENT.SYS Sat Sep 16 14:48:19 2006 (450B9023) <-- Norton AV.
f23ef000 f242ece0 SYMTDI SYMTDI.SYS Wed Apr 06 03:10:52 2005 (4252D4AC) <-- Norton AV

BugCheck 35, {84c66ee8, 0, 0, 0}
Probably caused by : cmdhlp.sys ( cmdhlp+1c1c )

STACK_TEXT:
f17c9990 8052011d 00000035 84c66ee8 00000000 nt!KeBugCheckEx+0x1b
f17c9a00 804e13d9 85301248 00000000 84c66fa0 nt!IopfCallDriver+0x17
f17c9a68 804e13d9 857c7f10 84c66ee8 00000004 nt!IopfCallDriver+0x31
f17c9a78 f78c4c1c f17c9a98 f78c4ce4 857c7f10 nt!IopfCallDriver+0x31
WARNING: Stack unwind information not available. Following frames may be wrong.
f17c9a80 f78c4ce4 857c7f10 84c66ee8 84c66eb0 cmdhlp+0x1c1c
f17c9a98 804e13d9 852578a8 84c66ee8 84d8f0b0 cmdhlp+0x1ce4
f17c9aa8 f237040a 00000000 00000008 f17c9b1c nt!IopfCallDriver+0x31
f17c9b10 f2363492 84ca3008 0006f97c f2363492 afd+0x1040a
f17c9c5c 80586e63 8505dc78 00000001 0006f8f0 afd+0x3492
f17c9d00 80586eee 000008c4 000003f4 00000000 nt!IopXxxControlFile+0x255
f17c9d34 804dd99f 000008c4 000003f4 00000000 nt!NtDeviceIoControlFile+0x2a
f17c9d34 7c90eb94 000008c4 000003f4 00000000 nt!KiFastCallEntry+0xfc
0006f944 00000000 00000000 00000000 00000000 0x7c90eb94

thanks very much...
i will remove the norton filess....

[Elvandil]

Get AVG Free or something for anti-virus. Free, very good, and very few conflicts. Also uses less resources than Norton.

[paulb100]

well he's using Kaspersky and Spybot - I removed Norton whent he got the PC and i used the norton removal tool - why do symantec do this? leav files behind that break the system?
I mean the normal uninstaller and symantec removal tool left behind these files

[Elvandil]

Symantec seems to be one of the worst offenders in this area, but changing AV's can always lead to problems. They try to protect themselves from viruses and uninstallation by malware. Many have drivers that load at boot so that the machine is protected until the other protective software is initialized. I'm not defending lousy uninstallers in general, but there are certain technical hurdles to making an app impervious to viruses and at the same time making easy to remove by users.

The best idea is to choose your AV carefully and then to stick with it.