|
Error Message Question :
Recently my computer froze while
playing WarCraft 3. This happened
after updating the graphics card
drivers. For your information, I am using a
GeForce FX5200 card. Since I suspected the
drivers to be at fault, I decided to revert back
to the previous version. Sadly, this did not
work out. The system still hangs at random.
Once I tried to login to Battle.net and it just
stuck at the login screen. Then there was
another time where WinAmp kept looping.
Below are the errors reported in the
application event viewer.
Event Type: Error
Event Source: EventSystem
Event Category: (50)
Event ID: 4609
Date: 8/21/2006
Time: 11:06:03 AM
User: N/A
Computer: POON
Description:
The COM+ Event System detected a bad
return code during its internal processing.
HRESULT was 00000005 from line 44 of
d:\nt_qxp\com\comlx\src\events\tierl\
eventsystemobj.cpp. Please contact
Microsoft Product Support Services to
report this error.
For more information, see Help and Support
Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: ipnathlp
Event Category: None
Event ID: 32003
Date: 8/21/2006
Time: 11:06:56 AM
User: N/A
Computer: POON
Description:
The Network Address Translator (NAT)
was unable to request an operation of the
kernel-mode translation module. This may
indicate misconfiguration, insufficient resources, or an internal error. The data is
the error code.
For more information, see Help and Support
Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 1f 00 00 00
Answer : First of all it could be highly
unlikely that a driver update would
cause system instabilities. This is
only if certified and official drivers are used
instead of using pre-release, beta or
modified versions. So make sure that the
graphics card drivers are not causing the
random lock-ups. Now taking a look at the
errors, it is safe to say that they are not
related to each other. This is because the
first error occurred at 11:06:03 while the
other triggered 53 seconds later. Another
fact is that the later error is related to a
network setting while the first is most likely
a bug. We dare not say that the system crash
is caused by either errors but it is possible
that the second error is the main cause. We
base our assumption on the fact that WarCraft 3 hung and also it could not log on
to Battle.net which is caused by the Network
Address Translator. To solve this, make sure
that the start address is not the same as the
end address. In other words, if Dynamic IP is
used try changing it to static IP instead.
|
