KingofLodis

The problem with my video card still persists, and nothing ever showed up in the event log before I reformated. So I reformated a while ago, and the problem happened AGAIN. At first, I got the blue screen of death, and then my comp restarted on it's own, then it did what it used to do (no bsod). Now something is showing up in the event log, and this is what it is (well actually, there's more than one event log problem . .):


Event Type: Error
Event Source: MRxSmb
Event Category: None
Event ID: 8003
Date: 10/15/2005
Time: 5:10:42 PM
User: N/A
Computer: CC-8F8980DAA84B
Description:
The master browser has received a server announcement from the computer ROBO2000 that believes that it is the master browser for the domain on transport NetBT_Tcpip_{D9496771-F247-4167-. The master browser is stopping or an election is being forced.
Data:
0000: 00 00 00 00 03 00 4e 00 ......N.
0008: 00 00 00 00 43 1f 00 c0 ....C..À
0010: 00 00 00 00 00 00 00 00 ........
0018: 04 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........



Event Type: Error
Event Source: NetBT
Event Category: None
Event ID: 4319
Date: 10/15/2005
Time: 4:57:43 PM
User: N/A
Computer: CC-8F8980DAA84B
Description:
A duplicate name has been detected on the TCP network. The IP address of the machine that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.
Data:
0000: 00 00 04 00 01 00 54 00 ......T.
0008: 00 00 00 00 df 10 00 c0 ....ß..À
0010: 01 01 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 79 7b a8 c0 y{¨À

Event Type: Warning
Event Source: EventSystem
Event Category: Firing Agent
Event ID: 4100
Date: 10/15/2005
Time: 10:20:54 AM
User: N/A
Computer: CC-8F8980DAA84B
Description:
The COM+ Event System failed to create an instance of the subscriber {6295DF2D-35EE-11D1-8707-00C04FD93327}. CoCreateInstanceEx returned HRESULT 8000401A.






Here's the order it goes in when it crashes::

Event Type: Information
Event Source: ATI Smart
Event Category: None
Event ID: 105
Date: 10/15/2005
Time: 2:09:20 PM
User: N/A
Computer: CC-8F8980DAA84B
Description:
The service was started.




Event Type: Information
Event Source: dcfssvc
Event Category: None
Event ID: 105
Date: 10/15/2005
Time: 2:09:21 PM
User: N/A
Computer: CC-8F8980DAA84B
Description:
The description for Event ID ( 105 ) in Source ( dcfssvc ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: The event log file is corrupt..


Event Type: Information
Event Source: ptssvc
Event Category: None
Event ID: 105
Date: 10/15/2005
Time: 2:09:23 PM
User: N/A
Computer: CC-8F8980DAA84B
Description:
The description for Event ID ( 105 ) in Source ( ptssvc ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: The event log file is corrupt..


Event Type: Information
Event Source: WMDM PMSP Service
Event Category: None
Event ID: 105
Date: 10/15/2005
Time: 2:09:35 PM
User: N/A
Computer: CC-8F8980DAA84B
Description:
The service was started.



Event Type: Warning
Event Source: EventSystem
Event Category: Firing Agent
Event ID: 4100
Date: 10/15/2005
Time: 2:09:45 PM
User: N/A
Computer: CC-8F8980DAA84B
Description:
The COM+ Event System failed to create an instance of the subscriber {6295DF2D-35EE-11D1-8707-00C04FD93327}. CoCreateInstanceEx returned HRESULT 8000401A.

Uranium-235

ook, I found a possible solution for your first problem.

http://www.cisco.com/en/US/products/...802373f3.shtml

I'll keep looking around for the rest

for the second one:

http://support.microsoft.com/?kbid=289650

KingofLodis

I can't seem to figure out the solution to the first problem . . . How do I do #1 in the solutions? XD

I did solution #2 instead.



For the second one:

I did what it said, but we'll see if the problem keeps happening . . .