DCOM conflict with Updates???

message from =?Utf-8?B?TWFtZQ==?= on 10 Jun 2004
Hello All,

I am having a dcom problem that has reoccured despite conducting a complete format and reinstall of xp and seems to only occur after running Windows Update. I ran my problem past a technician I know and he thought that it could be something to do with a conflict between a Windows driver update and SiS chipsets? Does anyone know about this issue and how it can be fixed? I have searched the net and not been able to find anthing that seems to match my problem. My full problem is detailed below. Please note that there are too many error logs to paste here. (I have had 21 error logs tonight alone. Contact me if you require any more information. Please dont tell me to 'not worry about it'. This is causing spontaneous reboots on my computer and is a serious problem that hasnt been fixed by a complete format and reinstall.

Last weeky computer began autorestarts, The computer spontaneously bluescreened, and then began a reboot (note that the bluescreen disappeared too quickly to read. During an attempted safe mode boot, the computer hanged at mup.sys. After many attempts at rebooting and system restore, I reinstalled Windows XP using a full format (not a quick format). I had only just recently cleaned up sasser and bobax from my computer (yes I turned off system restore and used the clean up tool after the updates/patches were installed), updated my antivirus, and installed ALL the Windows XP updates. I just assumed that the problem had resulted from virus damage and thought it would be easier to just do a complete reinstall. Anyhow, 3 days after the reinstall and 1 day after I completed all the Windows updates, the computer began doing it again - spontaneous shutdown and reboot but this time I was able to reboot and continue as normal after a few minutes. I ran fix sasser, antivirus and macafee stinger on my computer again thinking I had been reinfected despite all the Updates and my antivirus being up-t-odate. Nothing showed up. I ran this past my technician and he thought that it could be something to do with a conflict between a Windows driver update and SiS chipsets? Does anyone know about this issue and how it can be fixed?

Thanks, Mame du Bois
 
Navin R. Johnson replied to =?Utf-8?B?TWFtZQ==?= on 11 Jun 2004
I am having a dcom problem that has reoccured despite conducting a
complete format and reinstall of xp and seems to only occur after
running Windows Update. I ran my problem past a technician I know and he
thought that it could be something to do with a conflict between a
Windows driver update and SiS chipsets? Does anyone know about this
issue and how it can be fixed? I have searched the net and not been able
to find anthing that seems to match my problem. My full problem is
detailed below. Please note that there are too many error logs to paste
here. (I have had 21 error logs tonight alone. Contact me if you
require any more information. Please dont tell me to 'not worry about
it'. This is causing spontaneous reboots on my computer and is a serious
problem that hasnt been fixed by a complete format and reinstall.
Last weeky computer began autorestarts, The computer spontaneously
bluescreened, and then began a reboot (note that the bluescreen
disappeared too quickly to read. During an attempted safe mode boot, the
computer hanged at mup.sys. After many attempts at rebooting and system
restore, I reinstalled Windows XP using a full format (not a quick
format). I had only just recently cleaned up sasser and bobax from my
computer (yes I turned off system restore and used the clean up tool
after the updates/patches were installed), updated my antivirus, and
installed ALL the Windows XP updates. I just assumed that the problem
had resulted from virus damage and thought it would be easier to just do
a complete reinstall. Anyhow, 3 days after the reinstall and 1 day after
I completed all the Windows updates, the computer began doing it again -
spontaneous shutdown and reboot but this time I was able to reboot and
continue as normal after a few minutes. I ran fix sasser, antivirus and
macafee stinger on my computer again thinking I had been reinfected
despite all the Updates and my antivirus being up-t-odate. Nothing
showed up. I ran this past my technician and he thought that it could be
something to do with a conflict between a Windows driver update and SiS
chipsets? Does anyone know about this issue and how it can be fixed?

I have been using motherboards with SIS chipsets for years and have
never heard of this problem, or any other problem. In the past month
alone I've built four systems with SIS chipsets running with both XP
Home and Pro and they're all 100% stable. I would look at all the
various hardware components that are typically associated with reboots:
CPU overheat/bad CPU fan, loose plugs or boards, bad power supply,
flakey memory chips, clogged air intakes, etc.

If you brought your system to me with the problems you described I would
first vacuum out all the dust, including inside the power supply, the
heatsink under the CPU fan and the fan/heatsink on the video card. I'd
then power it up and check that all the fans were spinning normally. I'd
power it back down and remove all the circuit boards, including memory,
then reseat everything - on a really old system I'd even clean the card
edge connectors with a soft eraser. I'd then pull all the power plugs
and reseat them. At this point I'd power it back up and see how it runs
- with all the case covers back in place. I'll usually run a virus
scan/defrag/scandisk, anything that will heat up the system. At this
point, if I were still having trouble, I would pull out anything that
isn't essential to run the system; sound card, CD-ROMs, NIC, modem,
extra memory, etc. and test it with a different power supply. If all
seems well I would then start to slowly add back all the components I
pulled until problems occurred again - the last component added would be
the original power supply. If there are still problems even with
everything pulled, and using a different power supply I would then
suspect the motherboard or CPU.

Intermittent problems are always the toughest to diagnose and usually
require a great deal of patience and a fair amount of time. Good luck
solving yours.

NRJ
 
=?Utf-8?B?TWFtZQ==?= replied to Navin R. Johnson on 12 Jun 2004
Thankyou very much for your time in answering my problem. I know and appreciate how much time and thought goes into postings, so again, Thankyou :-)

I will go through what you mentioned but it should be noted that the second time it happened was a fresh, completely formatted installation with nothing but drivers and all the updates and antivirus updated. I did this intentionally as I initially thought it was a result of sasser or another virus. I made specific mention to the updates as it happened both time only after the update (althoug possibly a coincidentce) and I had been told (by someone with impecable computer knowledge) that there is a known conflict between SiS chipset and a Windows VGA driver update. I am going to try and unisntall the lastest driver update (if thats possible) and then leave it to monitor the situation.

Mame du Bois

"Navin R. Johnson" wrote:
 

Archived message: DCOM conflict with Updates??? (Microsoft Windows XP)
 
Note: To make this discussion more readable on the page the original messages have been edited to remove most of the references and quoting.