Quote:
Originally Posted by Sparsely
check windows update
Printable View
Quote:
Originally Posted by Sparsely
check windows update
lol I just edited my last post :P
woah there killa! Sry I missed it. Glad u got all riled up over a missed post.Quote:
Originally Posted by {I}{K}{E}
take a deep breath and let it all go. everything will be o.k.
;)
Baaaa..... I'm I fucking sheep, I downloading too! Wish I knew what is was ? :blink: Does n't say what Virus program was effected did it ? No reboot either.
ya, microsoft are always so vague on their update and program descriptions. :dry:Quote:
Originally Posted by peat moss
Quote:
Originally Posted by rossco_2004
Ya bud ,or firewall for that matter........... probably their OWN!!!! :lol:
I didn't get it at work, because it didn't list what AV is the problem...we use NAV corp, so i dunno, we've never had a problem, and our firewalls are mega-hardware firewalls.
all the XP SP2 machines on the domain have security center, windows firewall, and automatic updates disabled. (as should anyone in a domain envrionment).
at home, I don't need it, cause I don't use SP2 :D
though I suspect I will be using it soon, as that's the only way you'll be able to install IE7 :rolleyes:
avast! might be one of the AVs that was causing sytem freeze ups.
I wanted to get the new update for windows yesterday, but had to wait for avast! to update its program files first.
This morning avast! needed to access windows update before it could get the latest virus signatures.
Maybe I should get a new AV... :ph34r:
another tidbit for those who wont visit the links :P
dont ask me to make heads or tails out of it though...Quote:
CAUSE
This problem occurs because a coding error in the Http.sys file causes stack corruption. This problem occurs if the following conditions are true:
• TDI filter drivers are installed on your computer. TDI filter drivers are typically installed by antivirus or firewall programs.
• The installed TDI filter drivers return STATUS_PENDING to the TDI_SET_EVENT_HANDLER I/O request, so that the call is processed as an asyncronous APC.
google for info about your AV/FW..or...somethin...hell i dont know :lol:
i'm just a monkey posting randomly now, i cant be blamed :P
:P lol Thanks monkey. I'll explain what they mean now. The coding error has to do with ..... poof me turns into monkey. :lol:Quote:
dont ask me to make heads or tails out of it though...
google for info about your AV/FW..or...somethin...hell i dont know
i'm just a monkey posting randomly now, i cant be blamed