Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

hardware dying?


  • Please log in to reply

#46
iheartmaryjane

iheartmaryjane

    Member

  • Topic Starter
  • Member
  • PipPip
  • 42 posts
Sounds like fun :).
Thanks for all the help, i appreciate this very much :). Saves big $$ in the long run then just swapping out components. The Motherboard is on a 3 year warranty to im pretty sure, but the problem is my parents got it for me when i was living at home, and they gave the recipes to an accountant, is there another method of claiming your warranty :0 . Thanks again.

PS. use to be part of the website a while ago just lost the email account that i was using.

Edited by iheartmaryjane, 07 September 2010 - 05:51 PM.

  • 0

Advertisements


#47
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
If they registered everything then you would need the registration information I guess.
I would contact the manufacturer or whom ever the warranty is through. If need be have them look at everything that has been done here and see if they agree with my diagnosis of the problem.
I can see no other reason for the issue but the motherboard at this point.
  • 0

#48
iheartmaryjane

iheartmaryjane

    Member

  • Topic Starter
  • Member
  • PipPip
  • 42 posts
Kk thanks :), i will post back here and PM you on the futures results.
  • 0

#49
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Yes please let us know what the outcome is. We always like to know good or bad as this may also help someone later with the same problem. Thank you for your patience and cooperation with all the steps we took to diagnose the problem.
I really appreciate you sticking with me through all this and for your courteous replies to my questions and suggestions.
Please enjoy the other forums and I will continue to monitor this topic for your results. :) :) :) :)
  • 0

#50
iheartmaryjane

iheartmaryjane

    Member

  • Topic Starter
  • Member
  • PipPip
  • 42 posts
havnt changed the motherboard yet... but now PC shutting down watching videos online and such, this is the event viewer after shutdown.
the crash was at 11/09/2010 2:20:00ish when all this is happening Log: 'System' Date/Time: 11/09/2010 2:21:43 AM
Type: information Category: 0
Event: 7035 Source: Service Control Manager
The Terminal Services service was successfully sent a start control.


Vino's Event Viewer v01c run on Windows XP in English
Report run at 11/09/2010 2:58:59 AM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 11/09/2010 12:23:50 AM
Type: error Category: 0
Event: 8032 Source: BROWSER
The browser service has failed to retrieve the backup list too many times on transport \Device\NetBT_Tcpip_{96D73BED-E192-4CC4-85A7-FB87C310FF02}. The backup browser is stopping. 

Log: 'System' Date/Time: 10/09/2010 11:32:19 PM
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP      :1d" could not be registered on the Interface with IP address 192.168.1.103. The machine with the IP address 192.168.1.100 did not allow the name to be claimed by this machine. 

Log: 'System' Date/Time: 10/09/2010 11:25:16 PM
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP      :1d" could not be registered on the Interface with IP address 192.168.1.103. The machine with the IP address 192.168.1.100 did not allow the name to be claimed by this machine. 

Log: 'System' Date/Time: 10/09/2010 11:20:05 PM
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP      :1d" could not be registered on the Interface with IP address 192.168.1.103. The machine with the IP address 192.168.1.100 did not allow the name to be claimed by this machine. 

Log: 'System' Date/Time: 10/09/2010 11:18:14 PM
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP      :1d" could not be registered on the Interface with IP address 192.168.1.103. The machine with the IP address 192.168.1.100 did not allow the name to be claimed by this machine. 

Log: 'System' Date/Time: 10/09/2010 11:13:04 PM
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP      :1d" could not be registered on the Interface with IP address 192.168.1.103. The machine with the IP address 192.168.1.100 did not allow the name to be claimed by this machine. 

Log: 'System' Date/Time: 10/09/2010 11:07:54 PM
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP      :1d" could not be registered on the Interface with IP address 192.168.1.103. The machine with the IP address 192.168.1.100 did not allow the name to be claimed by this machine. 

Log: 'System' Date/Time: 10/09/2010 11:06:00 PM
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP      :1d" could not be registered on the Interface with IP address 192.168.1.103. The machine with the IP address 192.168.1.100 did not allow the name to be claimed by this machine. 

Log: 'System' Date/Time: 10/09/2010 11:00:49 PM
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP      :1d" could not be registered on the Interface with IP address 192.168.1.103. The machine with the IP address 192.168.1.100 did not allow the name to be claimed by this machine. 

Log: 'System' Date/Time: 10/09/2010 10:55:39 PM
Type: error Category: 0
Event: 4321 Source: NetBT
The name "WORKGROUP      :1d" could not be registered on the Interface with IP address 192.168.1.103. The machine with the IP address 192.168.1.100 did not allow the name to be claimed by this machine. 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 11/09/2010 2:22:19 AM
Type: information Category: 0
Event: 7036 Source: Service Control Manager
The HTTP SSL service entered the running state. 

Log: 'System' Date/Time: 11/09/2010 2:22:19 AM
Type: information Category: 0
Event: 7035 Source: Service Control Manager
The HTTP SSL service was successfully sent a start control. 

Log: 'System' Date/Time: 11/09/2010 2:21:57 AM
Type: information Category: 0
Event: 7036 Source: Service Control Manager
The IMAPI CD-Burning COM Service service entered the stopped state. 

Log: 'System' Date/Time: 11/09/2010 2:21:51 AM
Type: information Category: 0
Event: 7036 Source: Service Control Manager
The IMAPI CD-Burning COM Service service entered the running state. 

Log: 'System' Date/Time: 11/09/2010 2:21:51 AM
Type: information Category: 0
Event: 7035 Source: Service Control Manager
The IMAPI CD-Burning COM Service service was successfully sent a start control. 

Log: 'System' Date/Time: 11/09/2010 2:21:47 AM
Type: information Category: 0
Event: 7036 Source: Service Control Manager
The SSDP Discovery Service service entered the running state. 

Log: 'System' Date/Time: 11/09/2010 2:21:47 AM
Type: information Category: 0
Event: 7035 Source: Service Control Manager
The SSDP Discovery Service service was successfully sent a start control. 

Log: 'System' Date/Time: 11/09/2010 2:21:44 AM
Type: information Category: 0
Event: 7036 Source: Service Control Manager
The Google Update Service (gupdate1ca6ca7b6fb6f30) service entered the stopped state. 

Log: 'System' Date/Time: 11/09/2010 2:21:44 AM
Type: information Category: 0
Event: 7036 Source: Service Control Manager
The Terminal Services service entered the running state. 

Log: 'System' Date/Time: 11/09/2010 2:21:43 AM
Type: information Category: 0
Event: 7035 Source: Service Control Manager
The Terminal Services service was successfully sent a start control. 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 11/09/2010 1:23:43 AM
Type: warning Category: 0
Event: 4226 Source: Tcpip
TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts. 

Log: 'System' Date/Time: 11/09/2010 12:20:11 AM
Type: warning Category: 0
Event: 8021 Source: BROWSER
The browser was unable to retrieve a list of servers from the browser master \\KRIS-PC on the network \Device\NetBT_Tcpip_{96D73BED-E192-4CC4-85A7-FB87C310FF02}. The data is the error code. 

Log: 'System' Date/Time: 10/09/2010 10:47:38 AM
Type: warning Category: 0
Event: 8021 Source: BROWSER
The browser was unable to retrieve a list of servers from the browser master \\KRIS-PC on the network \Device\NetBT_Tcpip_{96D73BED-E192-4CC4-85A7-FB87C310FF02}. The data is the error code. 

Log: 'System' Date/Time: 10/09/2010 12:39:37 AM
Type: warning Category: 0
Event: 8021 Source: BROWSER
The browser was unable to retrieve a list of servers from the browser master \\KRIS-PC on the network \Device\NetBT_Tcpip_{96D73BED-E192-4CC4-85A7-FB87C310FF02}. The data is the error code. 

Log: 'System' Date/Time: 08/09/2010 10:13:29 PM
Type: warning Category: 0
Event: 8021 Source: BROWSER
The browser was unable to retrieve a list of servers from the browser master \\KRIS-PC on the network \Device\NetBT_Tcpip_{96D73BED-E192-4CC4-85A7-FB87C310FF02}. The data is the error code. 

Log: 'System' Date/Time: 08/09/2010 10:07:10 AM
Type: warning Category: 0
Event: 8021 Source: BROWSER
The browser was unable to retrieve a list of servers from the browser master \\KRIS-PC on the network \Device\NetBT_Tcpip_{96D73BED-E192-4CC4-85A7-FB87C310FF02}. The data is the error code. 

Log: 'System' Date/Time: 07/09/2010 9:34:13 AM
Type: warning Category: 0
Event: 8021 Source: BROWSER
The browser was unable to retrieve a list of servers from the browser master \\KRIS-PC on the network \Device\NetBT_Tcpip_{96D73BED-E192-4CC4-85A7-FB87C310FF02}. The data is the error code. 

Log: 'System' Date/Time: 06/09/2010 9:32:49 PM
Type: warning Category: 0
Event: 8021 Source: BROWSER
The browser was unable to retrieve a list of servers from the browser master \\KRIS-PC on the network \Device\NetBT_Tcpip_{96D73BED-E192-4CC4-85A7-FB87C310FF02}. The data is the error code. 

Log: 'System' Date/Time: 06/09/2010 9:19:08 PM
Type: warning Category: 0
Event: 8021 Source: BROWSER
The browser was unable to retrieve a list of servers from the browser master \\KRIS-PC on the network \Device\NetBT_Tcpip_{96D73BED-E192-4CC4-85A7-FB87C310FF02}. The data is the error code. 

Log: 'System' Date/Time: 06/09/2010 6:50:20 PM
Type: warning Category: 0
Event: 8021 Source: BROWSER
The browser was unable to retrieve a list of servers from the browser master \\KRIS-PC on the network \Device\NetBT_Tcpip_{96D73BED-E192-4CC4-85A7-FB87C310FF02}. The data is the error code. 


  • 0

#51
iheartmaryjane

iheartmaryjane

    Member

  • Topic Starter
  • Member
  • PipPip
  • 42 posts
think i also had a restart here
'System' Log - warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 11/09/2010 1:23:43 AM
Type: warning Category: 0
Event: 4226 Source: Tcpip
TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP