Mouse choppy

Comment below rating threshold, click here to show it.

HammerBro

Junior Member

07-23-2012

hello first post so here my problem I load up a game on summoner's rift not dom and as soon as I enter my mouse moves choppy the minions are even moving choppy i repaired the files I tried uninstalling and reinstalling and the game still has this issue im in need of some help cause i've spent alot of money on this game as it is and i dont wanna get rid of it.i used
the ICsI Netalyzr and i came up with these results so here ya so wrenchman plz look in to this for me i hadn't had a decent game all day thanks to this and thx for any help im about to recieve



Summary of Noteworthy Events +
Major Abnormalities
Your system has an IPv6 address that does not work
Minor Aberrations
Certain TCP protocols are blocked in outbound traffic
Network packet buffering may be excessive
The NAT's DNS proxy doesn't fully implement the DNS standard
Not all DNS types were correctly processed
Address-based Tests +
NAT detection (?): NAT Detected +
Local Network Interfaces (?): IPv6 connectivity problem
Your computer reports the following network interfaces, with the following IP addresses for each one:
eth0: (an ethernet interface)
eth1: (an ethernet interface)
eth2: (an ethernet interface)
eth3: (an ethernet interface)
fe80::d9ea:f82c:bc26:71b5 (a link-local IPv6 address)
eth4: (an ethernet interface)
eth5: (an ethernet interface)
eth6: (an ethernet interface)
eth7: (an ethernet interface)
eth8: (an ethernet interface)
eth9: (an ethernet interface)
lo: (a local loopback interface)
::1 (an IPv6 loopback address)
127.0.0.1 [www.007guard.com] (an IPv4 loopback address)
net0:
net1:
net10:
net11:
net12:
net2:
net3:
fe80::d5c7:2f73:f135:8095 (a link-local IPv6 address)
192.168.2.10 [Donovan-PC.gateway.2wire.net] (a private IPv4 address)
net4:
2001:0:4137:9e76:2029:11d1:3f57:fdf5 [Donovan-PC] (a Teredo IPv6 address)
fe80::2029:11d1:3f57:fdf5 [Donovan-PC] (a link-local IPv6 address)
net5:
net6:
fe80::5efe:c0a8:20a (a link-local IPv6 address)
net7:
net8:
net9:
ppp0:
ppp1:
Your system has an IPv6 address, yet was unable to fetch an image using IPv6. This can cause substantial problems as your web browser or other programs may first attempt to contact hosts using the non-functional IPv6 connection.
DNS-based host information (?): OK +
NAT support for Universal Plug and Play (UPnP) (?): Not found +
Reachability Tests +
TCP connectivity (?): Note
Direct TCP access to remote FTP servers (port 21) is allowed.
Direct TCP access to remote SSH servers (port 22) is allowed.
Direct TCP access to remote SMTP servers (port 25) succeeds, but does not return the expected content.
This suggests that your network enforces a mandatory SMTP proxy which may or may not allow you to send email directly from your system. This is probably a countermeasure against malware abusing infected machines for generating spam. You ISP also likely provides a specific mail server that is permitted. Also, webmail services remain unaffected.
The applet received an empty response instead of our normal banner. This suggests that a firewall, proxy, or filter initially allowed the connection and then terminated it, either because it did not understand our server's reply or decided to block the service.
Direct TCP access to remote DNS servers (port 53) is allowed.
Direct TCP access to remote HTTP servers (port 80) is allowed.
Direct TCP access to remote POP3 servers (port 110) is allowed.
Direct TCP access to remote RPC servers (port 135) is allowed.
Direct TCP access to remote NetBIOS servers (port 139) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote IMAP servers (port 143) is allowed.
Direct TCP access to remote SNMP servers (port 161) is allowed.
Direct TCP access to remote HTTPS servers (port 443) is allowed.
Direct TCP access to remote SMB servers (port 445) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote SMTP/SSL servers (port 465) is allowed.
Direct TCP access to remote secure IMAP servers (port 585) is allowed.
Direct TCP connections to remote authenticated SMTP servers (port 587) succeed, but do not receive the expected content.
The applet received the following reply instead of our expected header:
"421 Cannot establish SSL with SMTP server 67.202.37.63:465, SSL_connect error 336031996 "
Direct TCP access to remote IMAP/SSL servers (port 993) is allowed.
Direct TCP access to remote POP/SSL servers (port 995) is allowed.
Direct TCP access to remote OpenVPN servers (port 1194) is allowed.
Direct TCP access to remote PPTP Control servers (port 1723) is allowed.
Direct TCP access to remote SIP servers (port 5060) is allowed.
Direct TCP access to remote BitTorrent servers (port 6881) is allowed.
Direct TCP access to remote TOR servers (port 9001) is allowed.
UDP connectivity (?): OK +
Traceroute (?): OK +
Path MTU (?): OK +
Network Access Link Properties +
Network latency measurements (?): Latency: 31ms Loss: 0.0% +
TCP connection setup latency (?): 26ms +
Network background health measurement (?): no transient outages +
Network bandwidth (?): Upload 660 Kbit/sec, Download 6.8 Mbit/sec +
Network buffer measurements (?): Uplink 840 ms, Downlink 250 ms
We estimate your uplink as having 840 msec of buffering. This level can in some situations prove somewhat high, and you may experience degraded performance when performing interactive tasks such as web-surfing while simultaneously conducting large uploads. Real-time applications, such as games or audio chat, may also work poorly when conducting large uploads at the same time.
We estimate your downlink as having 250 msec of buffering. This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic.
HTTP Tests +
Address-based HTTP proxy detection (?): OK +
Content-based HTTP proxy detection (?): OK +
HTTP proxy detection via malformed requests (?): OK +
Filetype-based filtering (?): OK +
HTTP caching behavior (?): OK +
JavaScript-based tests (?): OK +
DNS Tests +
Restricted domain DNS lookup (?): OK +
Unrestricted domain DNS lookup (?): OK +
Direct DNS support (?): OK +
Direct EDNS support (?): OK +
DNS resolver address (?): OK +
DNS resolver properties (?): Lookup latency 110ms
Your ISP's DNS resolver requires 110 msec to conduct an external lookup. It takes 66 msec for your ISP's DNS resolver to lookup a name on our server.
Your resolver correctly uses TCP requests when necessary.
Your resolver is using QTYPE=A for default queries.
Your resolver is not automatically performing IPv6 queries.
Your DNS resolver requests DNSSEC records.
Your DNS resolver advertises the ability to accept DNS packets of up to 4096 bytes.
Your DNS resolver can successfully receive a smaller (~1400 byte) DNS response.
Your DNS resolver can successfully receive a large (>1500 byte) DNS response.
Your DNS resolver can successfully accept large responses.
Your resolver does not use 0x20 randomization, but will pass names in a case-sensitive manner.
Your ISP's DNS server cannot use IPv6.
No transport problems were discovered which could affect the deployment of DNSSEC.
Direct probing of DNS resolvers (?)
Your system is configured to use 1 DNS resolver(s).
The resolver at 192.168.2.1 could not process the following tested types:
EDNS0 (DNS extensions)
Medium (~1300B) TXT records
Large (~3000B) TXT records
Large (~3000B) TXT records fetched with EDNS0
RTYPE=1169 (deliberately unknown) records
It does not validate DNSSEC. It does not wildcard NXDOMAIN errors.
DNS glue policy (?): OK +
DNS resolver port randomization (?): OK +
DNS lookups of popular domains (?): OK +
DNS external proxy (?): OK +
DNS results wildcarding (?): OK +
DNS-level redirection of specific sites (?): OK +
Direct probing of DNS roots (?): +
IPv6 Tests +
DNS support for IPv6 (?): OK +
IPv4, IPv6, and your web browser (?): IPv6 connectivity problem +
IPv6 connectivity (?): No IPv6 support +
Host Properties +
System clock accuracy (?): OK +
Browser properties (?): OK +
Uploaded data (?): OK +
Feedback +
User-provided feedback +
ID 43ca253f-5988-95e65872-a45b-4c71-84a5