Author Topic: Lag / Ping of Death while offline Gaming  (Read 2253 times)

0 Members and 1 Guest are viewing this topic.

Offline dondon

  • Jr. Member
  • **
  • Join Date: Mar 2015
  • Posts: 72
  • Karma: 0
    • View Profile
Lag / Ping of Death while offline Gaming
« on: November 09, 2015, 12:47:14 AM »
This problem has occured to me several times and keeps coming back from time to time while gaming either online or offline.I get a huuuuge delay like in the image below(i divided it by red | so it can be read more easily ).

http://postimg.org/image/9p6k4k16p/

Dont't ask.Its a real number,not fake and really goes off the chart.I noticed it only late because my hole laptop was at halt.Luckly i had this opened and look what it found.OMG!

I identifyed to problems that might cause it:

Loose power plug
OR
Hardware Confilct
OR
Software Conflict

Arguments for my above statements:

Loose PowerPlug - i set my laptop to have high brightness while power plug is plugged on and low brightness while its plugged of.I notice sometimes my screen turns darker and brighter and this might cause it.Also i tryed gaming without power plug and the delays are much more frequent and everything happens in slow motion than happen while

Hardware conflict - i notice that a usb port goes on and off very often.This happens from time to time and i dont know why.If you suggest one usb device cable is loose it is wrong because only my mouse is plugged and never had single cursor freeze from it.Might be an internal usb port with a loose cable plugged.For this i will uplod additional data should it be required.

Software Conflict - well,this is partial true.Sometimes sound would fliker while gaming but the fliker would stop if i turn off wireless triver.So my suspicion is that and hardware conflict might also be involved


Looking forward to a reply.

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9860
  • Location: UK
  • Karma: 121
    • View Profile
Re: Lag / Ping of Death while offline Gaming
« Reply #1 on: November 09, 2015, 03:12:13 AM »
I would start with downloading drivers, starting with the Chipset and Video drivers, audio and then wireless and/or Ethernet drivers.

The South Bridge of the Chipset or Video drivers where no separate Chipset drivers will look after the USB problem, unless it is an internal fault.

It may also be worth doing a memory test - not sure if XP has this built in as Win 7 does but if not then you can use Memtest 86+

http://www.geekstogo.com/forum/topic/246994-guide-to-using-memtest86/

If you are only using a mouse plugged into an USB port and that works okay, what error are you getting so that you know a port is going off every now and again ?

You can get higher latency on battery to AC, so when possible, always use AC.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>ping google.co.uk

Pinging google.co.uk [62.24.158.34] with 32 bytes of data:
Reply from 62.24.158.34: bytes=32 time=30ms TTL=61
Reply from 62.24.158.34: bytes=32 time=29ms TTL=61
Reply from 62.24.158.34: bytes=32 time=29ms TTL=61
Reply from 62.24.158.34: bytes=32 time=29ms TTL=61

Ping statistics for 62.24.158.34:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 29ms, Maximum = 30ms, Average = 29ms

C:\Windows\system32>ping google.co.uk

Pinging google.co.uk [62.24.158.34] with 32 bytes of data:
Reply from 62.24.158.34: bytes=32 time=692ms TTL=61
Reply from 62.24.158.34: bytes=32 time=31ms TTL=61
Reply from 62.24.158.34: bytes=32 time=722ms TTL=61
Reply from 62.24.158.34: bytes=32 time=748ms TTL=61

Ping statistics for 62.24.158.34:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 31ms, Maximum = 748ms, Average = 548ms

C:\Windows\system32>

The first ping is on AC and the second is just on battery - don't ask me why as I've asked this before on a tech forum and no one had an answer.

This is doing a tracert cmd on AC and then on battery and as you can see, they are near identical, so it must be a power issue.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>tracert google.co.uk

Tracing route to google.co.uk [62.24.158.20]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  ROUTER [192.168.1.1]
  2    23 ms    22 ms    22 ms  host-78-148-0-1.as13285.net [78.148.0.1]
  3    30 ms    29 ms    30 ms  p1.nas18.man.opaltelecom.net [62.24.158.1]
  4    29 ms    29 ms    29 ms  p20.nas18.man.opaltelecom.net [62.24.158.20]

Trace complete.

C:\Windows\system32>tracert google.co.uk

Tracing route to google.co.uk [62.24.158.20]
over a maximum of 30 hops:

  1     4 ms     1 ms     1 ms  ROUTER [192.168.1.1]
  2    23 ms  1018 ms    24 ms  host-78-148-0-1.as13285.net [78.148.0.1]
  3    30 ms    30 ms    30 ms  p1.nas18.man.opaltelecom.net [62.24.158.1]
  4    29 ms    29 ms    30 ms  p20.nas18.man.opaltelecom.net [62.24.158.20]

Trace complete.

C:\Windows\system32>

When you checked your MTU previously using TCP Optimizer, did you set both the computer and router to 1500 before running TCP Optimizer ?
Tom.