OZONE Asylum
Forums
OZONE
Computer locking up in rotation... awakward!
This page's ID:
27564
Search
QuickChanges
Forums
FAQ
Archives
Register
Edit Post
Who can edit a post?
The poster and administrators may edit a post. The poster can only edit it for a short while after the initial post.
Your User Name:
Your Password:
Login Options:
Remember Me On This Computer
Your Text:
Insert Slimies »
Insert UBB Code »
Close
Last Tag
|
All Tags
UBB Help
Skaarjj, no offense meant, I do think completion is good for resolution of such issues and I do agree on that and said it before. I do not think randomness is good, it is not a so called best practice at least. I do think you've experienced comp issues in the past. I have too. For 9 months now, I've resolved 40 issues of this kind per week for a multinational company. So yes, experience sounds good, I agree. Order in steps taken for the resolution, methodology and thinking sound even better. Of course, an advice is an advice, an opinion is an opinion, and everything is good for Insider, but my opinion is that you are wrong on the virus issue, and the way to investigate this. And I don't want to attack or insult you by saying this, I just happen to 150% disagree with you. Here we have proven, and logged evidence, of Iexplore being the originator of the issues: Insider's Windows reports it, not me. So this investigation should be "led to an end" prior to making stabs in the dark, me thinks, on this track we do already have some light. ---------------- Iexplore here is only acting as a "parent", cover to the real, software component which tries to register itself as Dcom and fails. An application in general involves lots of processes. Iexplore software components are shared, in part, by explorer.exe, hence the fact your explorer.exe "magically locks" each and every time an error pertaining to Iexplore is logged in your applications log: something is saying to IE "hold on, have to try registering myself as DCOM" and never succeeds. And it really is what happens: a sub process requires his top-level parent to wait for an action which can't be performed, and fails after a couple of seconds of lag. Consider the reformatting vs tracking down issue balance, also: which one will resolve the problem faster and with the smallest impact on bus... your activities :) The link you gave for DCOM is correct, try unchecking everything, restarting, checking everything again, restarting, etc. a couple of times. To let the system apply this setting fully on startup: it's important. Of course, a decent default state is important: is your system protected at all? Is it up-to-date? Issues like this can be bugfixed by Windows update. All my assumptions above take for granted a Windows XP sp 2 with at least a firewall, and maybe a popup blocker and casual spyware check. But the symptoms still don't look -at all- like a virus. A Virus which is stupid enough to tell the applications log it has messed up every three minutes would be dead before long, it would basically write down "hello world, I am a nasty piece of software causing others to lock". I just, in terms of logic and statistics, can't imagine such an obvious activity allow a virus to spread, as it would be identified so early. Let alone the fact that DCOM is rarely used. Lmao... Think of a nasty virus maker saying to himself "to hide my virus, I'll use a feature which is never used by normal applications and that will lead any error to cause a log entry about the origin". Way to go! The only possible worse way to write a virus would be writing one which auto-erases itself. My 2 cents. One more cent though: on the sysinternals site (www.sysinternals.com) there is a nice piece of software called "procmon": keep it running in the foreground,and when your comp hangs, procom can tell you the exact sub-process which causes this. If you get a procmon window to run in the foreground while the issue occurs... And of course, all this is advice indeed, hence the 2 cents price.
Loading...
Options:
Enable Slimies
Enable Linkwords
« Backwards
—
Onwards »