Hye, my explorer.exe is always draining half my cpu, and neither Spy-bot nor Ad Aware nor Nortons nor anything else can solve it.

I downloaded a program that lets me see the threads acting within Explorer.exe and the problem is coming specifically from something called -

ddabx.dll!CreateProtectProc+oxb10

which contains a stack that looks what you see below...anyway I tired killing this thread and it solves my problem, however it comes back on whenever i start up. I was wondering if if it would be detrimental to remove the thread permantally because its a win32 file.  Any thoughts?

the stack for ddabx.dll!CreateProtectProc+oxb10 looks like this -

ntoskrnl.exe+0x584d
ntoskrnl.exe!KeQueryRuntimeThread+0x5e8
hal.dll+0x2ef2
hal.dll!KeReleaseQueuedSpinLock+0x3c
ntoskrnl.exe!CcPurgeCacheSection+0x21b
afd.sys+0xe202
afd.sys+0xb2c7
ntoskrnl.exe!Kei386EoiHelper+0x237d
ntoskrnl.exe!RtlIntegerToUnicode+0x66
ntoskrnl.exe!RtlRemoveUnicodePrefix+0x10e4
ntoskrnl.exe!ZwSetSystemInformation+0x23
ntdll.dll!KiFastSystemCallRet
WS2_32.dll!select+0xa7
WININET.dll!InternetTimeFromSystemTimeA+0x7f4b
WININET.dll!InternetReadFile+0x1a4b
WININET.dll!Ordinal101+0x142
WININET.dll!Ordinal101+0xf0
WININET.dll!InternetReadFile+0x19c9
WININET.dll!InternetReadFile+0x1628
WININET.dll!InternetReadFile+0x15e1
WININET.dll!Ordinal101+0x142
WININET.dll!Ordinal101+0xf0
WININET.dll!InternetReadFile+0x1570
WININET.dll!InternetReadFile+0x14e7
WININET.dll!InternetReadFile+0x14b1
WININET.dll!Ordinal101+0x142
WININET.dll!Ordinal101+0xf0
WININET.dll!InternetReadFile+0x1b8
ddabx.dll+0xd13c
ddabx.dll+0xe9a2